Web accessibility means designing and developing websites that people with disabilities can perceive, understand, navigate, and interact with effectively. With an estimated 26.8 million people with disabilities in India according to the 2011 Census (the actual number is likely much higher), accessibility is both an ethical imperative and a business opportunity that most Indian websites overlook.
Understanding WCAG
The Web Content Accessibility Guidelines (WCAG) are the internationally recognised standards for web accessibility, published by the World Wide Web Consortium (W3C). The current version, WCAG 2.2, organises its success criteria around four principles, often remembered by the acronym POUR:
Perceivable: Information and interface components must be presentable to users in ways they can perceive. This means providing text alternatives for non-text content, captions for videos, and ensuring content can be presented in different ways without losing meaning.
Operable: Interface components and navigation must be operable. All functionality must be available from a keyboard, users must have enough time to read and interact with content, and content must not cause seizures or physical reactions.
Understandable: Information and the operation of the interface must be understandable. Text must be readable, web pages must appear and operate in predictable ways, and users must be helped to avoid and correct mistakes.
Robust: Content must be robust enough to be interpreted reliably by a wide variety of user agents, including assistive technologies like screen readers, magnifiers, and voice control software.
WCAG Conformance Levels
WCAG defines three levels of conformance:
Level A: The minimum level of accessibility. Meeting these criteria removes the most significant barriers. Examples include providing alt text for images, ensuring all functionality is keyboard-accessible, and not relying solely on colour to convey information.
Level AA: Addresses the most common barriers for disabled users. This is the level most laws and policies reference, and it is the standard most businesses should aim for. It includes requirements like minimum colour contrast ratios (4.5:1 for normal text), visible focus indicators, and consistent navigation.
Level AAA: The highest level of accessibility. While desirable, it is not always achievable for all content types. It includes enhanced contrast ratios (7:1), sign language interpretation for audio content, and more.
Legal Context in India
The Rights of Persons with Disabilities Act 2016 mandates that government websites and services be accessible. While enforcement on private businesses has been limited, the trend globally and in India is toward stricter accessibility requirements. The Guidelines for Indian Government Websites (GIGW) reference WCAG 2.0 Level AA compliance.
Beyond legal compliance, there is a strong business case. Accessible websites reach a larger audience, perform better in search engines (many accessibility practices overlap with SEO best practices), and demonstrate corporate social responsibility.
Common Accessibility Issues and How to Fix Them
Missing Alt Text on Images
Every informative image needs descriptive alt text that conveys the image purpose. Decorative images should have an empty alt attribute (alt=””) so screen readers skip them. Avoid generic alt text like “image” or “photo” — describe what the image shows and why it matters in context.
Poor Colour Contrast
Text must have sufficient contrast against its background. WCAG AA requires a minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text (18px bold or 24px regular). Use tools like the WebAIM Contrast Checker to verify your colour combinations meet these thresholds.
Missing Keyboard Navigation
All interactive elements — links, buttons, form fields, dropdown menus, modal dialogs — must be usable with a keyboard alone. Users should be able to tab through the page in a logical order, see a clear focus indicator on the currently focused element, and activate controls with Enter or Space keys.
Incorrect Heading Structure
Headings (H1 through H6) create a document outline that screen reader users rely on for navigation. Use headings in hierarchical order — do not skip from H2 to H4, and do not use heading tags purely for visual styling. Each page should have exactly one H1.
Inaccessible Forms
Every form field needs an associated label element. Do not rely on placeholder text as the only label, as it disappears when the user starts typing. Group related fields with fieldset and legend elements. Provide clear error messages that identify which field has an error and how to correct it.
Missing Skip Navigation Links
Screen reader and keyboard users should not have to tab through the entire navigation menu on every page. A “Skip to main content” link at the top of the page allows them to jump directly to the page content.
Testing for Accessibility
Automated Tools: Browser extensions like axe DevTools, WAVE, and Lighthouse audit your pages for common accessibility issues. These tools can catch roughly 30 to 40 percent of accessibility problems automatically.
Manual Testing: Navigate your website using only the keyboard. Can you reach and operate every interactive element? Is the focus indicator visible? Is the tab order logical? Try your website with a screen reader like NVDA (free for Windows) to understand the experience for visually impaired users.
User Testing: The most valuable testing involves people with disabilities actually using your website. Their feedback reveals issues that no automated tool or simulation can detect.
Getting Started with Accessibility
You do not need to achieve perfect accessibility overnight. Start with the most impactful improvements: add meaningful alt text, fix colour contrast issues, ensure keyboard navigability, and correct your heading structure. Then progressively address additional WCAG criteria. Making your website accessible is an ongoing commitment that benefits all users, not just those with disabilities.
