⚡ Quick answer Target WCAG 2.2 Level AA. It's the practical benchmark behind most laws and procurement requirements worldwide, and it aligns with India's GIGW and IS 17802. Build it in, don't bolt it on: accessible colours, focus states, semantic HTML, labelled forms, captions and clear content from the first wireframe. Test with people and tools: automated scans catch only part of the problem; keyboard, screen reader and zoom testing find the rest. Skip the overlay shortcut: widgets can't fix broken structure, and regulators have challenged misleading "instant compliance" claims. It pays off: more customers reached, better usability for everyone, stronger SEO and lower legal risk in India and abroad. Picture a customer in Hyderabad trying to book a hospital appointment on a budget Android phone with a cracked screen and the text size turned up. Or a retired teacher in Secunderabad using a screen reader to pay a bill. Or a young professional with a broken wrist navigating your site with one hand. If your website doesn't work for them, you're not just losing a sale; you're shutting people out. Website accessibility makes sure that doesn't happen. It's also one of the most misunderstood areas of web design: often reduced to "add alt text" or sold as a one-click widget. This guide gives you the full, practical picture. As an affordable website design company in Hyderabad that builds accessibility into every project, we've organised it by role so your designers, developers and content team each know exactly what to do. What Website Accessibility Really Means Website accessibility means people with disabilities can perceive, understand, navigate and interact with your website, using whatever devices and assistive technologies they rely on: screen readers, keyboard-only navigation, switch devices, voice control, magnification, captions or simplified reading settings. Who benefits Blind & low-vision usersScreen readers, magnification, high contrast Deaf & hard-of-hearing usersCaptions, transcripts, visual alerts People with motor disabilitiesKeyboard, switch and voice control Cognitive & learning differencesPlain language, predictable layouts Older adultsLarger text, clear contrast, simple flows Temporary & situational limitsInjuries, sunlight glare, noisy places, slow networks Why Accessibility Matters More in 2026 1.3 bnpeople worldwide experience significant disability (WHO estimate) 2.68 crpeople with disabilities counted in India's 2011 Census, widely seen as an undercount 94.8%of the top one million home pages had detectable WCAG failuresWebAIM Million 2025 79.1%of those home pages had low-contrast text, the most common failureWebAIM Million 2025 An ageing, mobile-first India: a large and growing population over 60 now banks, books and shops on smartphones. Essential services moved online: healthcare, education, government services, payments and travel all depend on usable websites. Legal expectations are rising: in India and in export markets like the EU and US. Accessibility and discoverability overlap: semantic structure, alt text, captions and clear headings help search engines and AI systems understand your content. Better UX for everyone: clearer forms, readable text and keyboard-friendly interfaces reduce friction for every visitor. The Four Principles of Accessibility (POUR) PerceivableInformation can be seen, heard or otherwise sensed: text alternatives, captions, contrast, adaptable layouts. OperableEverything works with keyboard and assistive tech, with enough time and no seizure risks. UnderstandableClear language, predictable behaviour and helpful error handling. RobustClean, standards-based code that works across browsers, devices and assistive technologies. WCAG has three conformance levels: A (essential), AA (the standard target for most organisations and laws) and AAA (enhanced, used selectively). What's New in WCAG 2.2 WCAG 2.2, published by the W3C in October 2023, builds on WCAG 2.1 with nine new success criteria and removes the obsolete "Parsing" criterion. Content that meets 2.2 also meets earlier 2.x versions. New success criteria in WCAG 2.2 CriterionLevelWhat it means in practice 2.4.11 Focus Not Obscured (Minimum)AASticky headers, cookie banners and chat widgets must not completely hide the keyboard-focused element. 2.4.12 Focus Not Obscured (Enhanced)AAANo part of the focused element is hidden. 2.4.13 Focus AppearanceAAAFocus indicators are large and high-contrast enough to see easily. 2.5.7 Dragging MovementsAAAnything done by dragging (sliders, kanban, maps) also has a single-tap alternative. 2.5.8 Target Size (Minimum)AATap targets are at least 24×24 CSS pixels, or spaced so they don't overlap. 3.2.6 Consistent HelpAHelp options (phone, chat, WhatsApp, FAQ) appear in the same place across pages. 3.3.7 Redundant EntryADon't make users re-type information they already gave in the same process. 3.3.8 Accessible Authentication (Minimum)AALogins mustn't rely on memory or puzzle tests alone; allow paste, password managers, OTP or passkeys. 3.3.9 Accessible Authentication (Enhanced)AAAStricter version, without object or image recognition tests. WCAG 3.0 is still a working draft. For 2026 projects, WCAG 2.2 AA is the standard to build and test against. Accessibility Rules in India and Around the World Key accessibility laws and standards RegionLaw / standardWhat it means for websites IndiaRights of Persons with Disabilities Act, 2016Requires accessible information and communication technology, with obligations for government and service providers and penalties for contraventions. IndiaGIGW 3.0 (Guidelines for Indian Government Websites)Mandatory for government websites and apps; aligned with WCAG. IndiaIS 17802 (BIS)India's ICT accessibility standard, based on the European EN 301 549, used in procurement. IndiaSupreme Court, Rajive Raturi v. Union of India (2024)Emphasised that accessibility standards must be mandatory and enforceable, directing the government to frame binding rules. European UnionEuropean Accessibility ActApplies since 28 June 2025 to many consumer products and services, including e-commerce, for businesses serving EU customers. United StatesADA; Title II rule for state and local governmentsADA applies to web accessibility; the Title II rule specifies WCAG 2.1 AA for public entities. Private lawsuits are common. GlobalWCAG 2.2 (W3C)The technical benchmark most laws reference. General information, not legal advice. Obligations depend on your sector, customers and markets; confirm with legal advisers. Hyderabad IT and export businesses serving EU or US clients should check those regimes too. Accessible Design Checklist Most accessibility problems are designed in long before a developer touches code. A user interface design company in Hyderabad that bakes these rules into the design system saves you expensive fixes later. 🎨For designers Text contrast at least 4.5:1 (3:1 for large text); UI components and icons at least 3:1 Never use colour alone to show meaning (errors, status, required fields); add icons or text Visible, high-contrast focus states for every interactive element Tap targets at least 24×24px (aim for 44–48px on mobile) with spacing Body text at least 16px; comfortable line height and line length Layouts that reflow at 320px width and at 200–400% zoom without horizontal scrolling Visible labels on form fields (not placeholder-only); clear error and success states Consistent navigation and help placement across pages Motion that respects "reduce motion" settings; nothing flashing more than three times a second Single-tap alternatives to drag interactions Design dark mode and high-contrast states, not just the default theme Brand colours are often the first barrier: pale greys, light oranges and pastel buttons frequently fail contrast. Creative branding services in Hyderabad can build an accessible palette, with accessible tints and shades for text, buttons and backgrounds, so your brand stays distinctive while passing WCAG. 🎯 Live Colour Contrast Checker (WCAG 2.2) Enter your text and background colours to check them against WCAG thresholds. Text colour Background colour Book your appointment Normal body text at 16px. Can you read this comfortably? —Contrast ratio —AA normal text (4.5:1) —AA large text / UI (3:1) —AAA normal text (7:1) Example: white on bright orange (#ff7a1a) fails for normal text. That's why this page uses deeper reds and burnt orange behind white text. Accessible Development Checklist The golden rule: use the right HTML element for the job. Native buttons, links, inputs and headings come with keyboard and screen reader support built in. Custom web development services in Hyderabad should treat these as non-negotiable: 💻For developers Correct lang attribute on the page (and on passages in other languages, e.g. lang="te") Semantic landmarks: <header>, <nav>, <main>, <footer>; one <h1> and a logical heading order A "Skip to main content" link as the first focusable element Real <button> and <a href> elements, never clickable <div>s Every form field has a programmatic <label>; errors are linked with aria-describedby and announced Correct autocomplete values (name, email, tel, postal-code, one-time-code) Logical focus order; no keyboard traps; modals trap focus and return it on close Dynamic updates announced with aria-live where appropriate ARIA only when native HTML can't do the job, and used correctly Icon-only buttons have accessible names Respect prefers-reduced-motion Tables with <th>, scope and captions for data Paste allowed in password and OTP fields; support password managers and passkeys Test single-page app route changes: update the title and move focus <!-- Accessible form field with error message --> <label for="phone">Mobile number</label> <input id="phone" name="phone" type="tel" inputmode="numeric" autocomplete="tel" aria-describedby="phone-hint phone-error" aria-invalid="true" required> <p id="phone-hint">10-digit Indian mobile number</p> <p id="phone-error" role="alert">Please enter a valid 10-digit number.</p> <!-- Icon-only button with an accessible name --> <button type="button" aria-label="Open menu"> <svg aria-hidden="true" focusable="false">...</svg> </button> Accessible Content Checklist ✍️For content & marketing teams Meaningful alt text for informative images; empty alt="" for decorative ones Descriptive link text ("Download the fee structure PDF", not "Click here") Plain language: short sentences, familiar words, explain jargon Headings that describe sections, in a logical order Captions for videos; transcripts for audio and podcasts No important text locked inside images or banners Accessible PDFs (tagged, with real text) or HTML alternatives Clear instructions and examples on forms Emoji used sparingly; screen readers read every one aloud Consistent terminology across the site Accessibility extends to every channel your customers use. Social media marketing experts in Hyderabad should add captions to reels, write alt text on image posts, avoid text-only graphics and use camel-case hashtags (#HyderabadFoodFestival) so screen readers pronounce them correctly. Want to know where your website stands? Get an expert WCAG 2.2 accessibility audit with a prioritised fix plan. Request an audit → Accessibility in the Indian Context Multilingual content: mark up Telugu, Hindi and Urdu correctly with lang attributes so screen readers switch voices, and ensure fonts render Indic scripts clearly at large sizes. Mobile screen readers: many Indian screen reader users rely on Android TalkBack; test with it as well as NVDA (Windows) and VoiceOver (iPhone/Mac). Budget devices and slow networks: heavy pages, autoplay video and complex animations hurt everyone, but especially users of assistive technology on low-end phones. OTP and CAPTCHA barriers: allow OTP autofill and paste, give enough time, and avoid image-puzzle CAPTCHAs without accessible alternatives. UPI and payment flows: make sure payment buttons, app-switching and confirmation screens are clearly labelled and announced. WhatsApp and chat widgets: chat launchers must be keyboard-accessible, labelled and must not cover focused content (WCAG 2.2 Focus Not Obscured). Regional-language captions: for video-heavy brands, captions in the viewer's language widen reach significantly. Why Accessibility Overlays Fall Short Accessibility overlays are widgets that add a toolbar (text resizing, contrast toggles, "screen reader mode") and often promise instant compliance. They're tempting because they're cheap and fast. But: They can't reliably fix the underlying code: missing labels, broken keyboard access, wrong heading structure, inaccessible custom components. Many disabled users already have these settings in their own devices and assistive technologies, and some overlays interfere with them. Accessibility specialists and disability advocates widely caution against relying on overlays. Regulators have scrutinised misleading claims. In 2025, the US Federal Trade Commission took action against an overlay provider over claims about its AI tool making sites compliant. Bottom line: preference controls can be a nice extra, but accessibility must be built into design, code and content. There is no one-line script that makes a site accessible. Accessibility Myths Myth: "Accessible sites look boring."Accessibility constrains contrast and clarity, not creativity. Many award-winning sites are both bold and accessible. Myth: "Only a few of our customers have disabilities."Disability is common and often invisible, and ageing, injuries and situational limits affect everyone at some point. Myth: "A Lighthouse score of 100 means we're accessible."Automated tools catch only some issues. A perfect score can still hide keyboard traps, confusing flows and meaningless alt text. Myth: "Accessibility is only for government websites."Private businesses in India serve customers with disabilities every day, and export markets increasingly require accessibility by law. Myth: "It's too expensive."Built in from the start, it adds relatively little. Retrofitting after launch is what gets expensive. How to Test Accessibility (Without Fooling Yourself) A practical accessibility testing toolkit MethodWhat it findsTools Automated scansMissing alt text, contrast failures, missing labels, ARIA errorsaxe DevTools, WAVE, Lighthouse Keyboard-only testFocus order, traps, invisible focus, unreachable controlsTab, Shift+Tab, Enter, Space, Esc, arrow keys Screen reader testLabels, announcements, reading order, landmarksNVDA, VoiceOver, Android TalkBack Zoom & reflowOverlaps, cut-off text, horizontal scrollingBrowser zoom 200–400%, 320px viewport Contrast checkText, icons, focus and UI component contrastContrast checkers, design plugins Motion & mediaFlashing, autoplay, missing captionsReduced-motion setting, manual review User testingReal-world barriers tools can't predictSessions with disabled users The 5-minute keyboard test anyone can do Open your homepage and press Tab repeatedly. Can you always see where you are? Can you open the menu, reach every link and close it with Esc? Can you complete your main enquiry or booking form without touching the mouse? Do pop-ups and chat widgets let you in and out without getting stuck? Does a sticky header or cookie bar ever hide the focused element? ✅ Free Accessibility Self-Assessment Tick everything that's true for your website today. Design Text and buttons pass WCAG AA contrast Focus indicators are clearly visible Colour is never the only way information is shown Tap targets are comfortably large on mobile Code Every feature works with keyboard only All form fields have labels and clear errors Headings and landmarks are used correctly Skip link present; no keyboard traps in modals Page works at 200% zoom and 320px width Content Images have meaningful alt text Videos have captions Links describe their destination PDFs are accessible or have HTML versions Process We test with a screen reader regularly We publish an accessibility statement with contact details We don't rely on an overlay for compliance Costs and a Practical Roadmap Indicative accessibility costs in India (excluding GST) ServiceIndicative costTypical timeline Accessibility audit (automated + manual, key templates)₹30,000 – ₹2,00,0001–3 weeks Remediation of an existing site₹50,000 – ₹5,00,000+3–12 weeks Accessible design system / component library₹1,00,000 – ₹4,00,0004–8 weeks Captions, transcripts and accessible PDFsPer minute / per documentOngoing Ongoing monitoring & regression testing₹5,000 – ₹25,000 / monthOngoing Indicative ranges; costs depend on site size, technology and how many issues exist. Accessibility built into a new project costs far less than retrofitting. Days 1–30Audit & quick winsAudit key templates and journeysFix contrast, labels, alt textAdd skip link and focus stylesPublish an accessibility statement Days 31–60Fix the foundationsKeyboard and focus fixesAccessible forms, menus and modalsCaptions and transcriptsAccessible PDFs Days 61–90Make it stickAccessible design systemAutomated checks in CIScreen reader test routineTeam training and ownership Accessibility also strengthens marketing. Integrated digital marketing services in Hyderabad can extend the same standards to emails, landing pages, ads and downloadable content, so every touchpoint is usable and your SEO benefits from clearer structure, captions and descriptive content. How BrandStory Builds Inclusive Websites As a website design and development company in Hyderabad, BrandStory designs to WCAG 2.2 AA from the first wireframe: accessible colour palettes, clear focus states, semantic and keyboard-friendly code, labelled forms, captioned media and plain-language content, tested with automated tools, keyboards and screen readers. For existing sites, we audit, prioritise and fix the barriers that matter most. Learn more about our team. Build a website everyone can use Talk to us about an accessible redesign or a WCAG 2.2 audit. Contact BrandStory → Frequently Asked Questions What is website accessibility? Website accessibility means designing and building websites so people with disabilities, including visual, hearing, motor, speech, cognitive and neurological disabilities, can perceive, understand, navigate and interact with them. It also helps older users, people with temporary injuries and anyone using a phone in bright sunlight or a noisy place. Which accessibility standard should Indian websites follow in 2026? WCAG 2.2 Level AA is the practical target. Indian government websites follow GIGW 3.0, which aligns with WCAG, and India's ICT accessibility standard IS 17802 is based on the European EN 301 549. Meeting WCAG 2.2 AA puts most businesses in a strong position for Indian and international requirements. Is website accessibility a legal requirement in India? The Rights of Persons with Disabilities Act, 2016 requires accessible information and communication technology, with specific obligations for government bodies and service providers, and Indian courts have increasingly treated accessibility as an enforceable right. Businesses serving customers in the EU or US may also fall under the European Accessibility Act or the ADA. Take legal advice for your specific situation. What changed in WCAG 2.2? WCAG 2.2, published in October 2023, added nine success criteria, including Focus Not Obscured, Dragging Movements, Target Size (Minimum), Consistent Help, Redundant Entry and Accessible Authentication, and made the old Parsing criterion obsolete. Six of the new criteria apply at Level A or AA. Do accessibility overlay widgets make a website compliant? No. Overlays can add user preference controls, but they cannot reliably fix missing labels, broken keyboard access, poor focus order, inaccessible forms or confusing structure. Accessibility experts widely caution against relying on them, and regulators have challenged misleading compliance claims. Real accessibility is built into design, code and content. What is the minimum colour contrast for accessible text? WCAG Level AA requires a contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (about 24px regular or 18.66px bold), and at least 3:1 for important user interface components and graphics. Does accessibility improve SEO? Often, yes. Semantic HTML, clear headings, descriptive link text, alt text, captions and transcripts help search engines and AI systems understand content, while faster, clearer pages improve engagement. Accessibility isn't a ranking shortcut, but it reinforces good SEO. How much does it cost to make a website accessible in India? Indicatively, a professional accessibility audit costs ₹30,000 to ₹2,00,000 depending on site size, and remediation ranges from ₹50,000 to ₹5,00,000 or more. Building accessibility into a new website from the start costs far less than retrofitting it later. Final Word: Inclusive by Default Accessibility isn't a feature you add at the end or a widget you install. It's a quality standard, like speed or security, that runs through design, code and content. In 2026, with WCAG 2.2 as the benchmark, rising legal expectations in India and abroad, and customers of every age and ability living online, inclusive web design is simply good web design. Start with an audit, fix what blocks people most, and build accessibility into how your team works. If you'd like help making your website accessible, get in touch with BrandStory. BS BrandStory Web & UX TeamDesigners, developers and content specialists building inclusive, WCAG-aligned websites for businesses across India. About us