Accessibility testing evaluates whether a website can be used by people with disabilities, including visual, auditory, motor, and cognitive impairments, by measuring compliance against the Web Content Accessibility Guidelines (WCAG) standards. With over 26 million visually impaired and 70 million disabled individuals in India, accessible web design is both a moral imperative and a business opportunity. WCAG 2.2 AA compliance ensures your website works for screen readers, keyboard-only navigation, and assistive technologies while also improving SEO and overall user experience for everyone.
Last updated October 2026
What Is WCAG and Which Level Should You Target?
WCAG (Web Content Accessibility Guidelines) is published by the W3C and defines three conformance levels:
| Level | Description | Target |
|---|---|---|
| A | Basic accessibility — minimum barrier removal | Absolute minimum for all websites |
| AA | Strong accessibility — recommended standard | Industry standard; legally required in many jurisdictions |
| AAA | Highest accessibility — maximum inclusivity | Specialized sites serving disabled users |
Target WCAG 2.2 AA — it is the accepted standard for commercial websites worldwide and the benchmark referenced in India’s Rights of Persons with Disabilities Act (2016) and GIGW (Guidelines for Indian Government Websites).
What Are the Four Principles of WCAG?
WCAG is organized around four principles (POUR):
- Perceivable — information must be presentable in ways users can perceive (text alternatives for images, captions for videos, sufficient color contrast).
- Operable — interface components must be operable by all users (keyboard navigation, enough time to read, no seizure-inducing content).
- Understandable — information and UI operation must be understandable (readable text, predictable navigation, error identification).
- Robust — content must be robust enough to be interpreted by diverse user agents and assistive technologies (valid HTML, ARIA attributes, semantic markup).
How to Perform Automated Accessibility Testing
Automated tools catch approximately 30–40% of accessibility issues. Use multiple tools for broader coverage:
- axe DevTools (browser extension) — industry standard, catches WCAG violations with clear remediation guidance. Free for basic use.
- WAVE (web-based and extension) — visual overlay showing errors, alerts, and structural elements directly on the page.
- Lighthouse (built into Chrome DevTools) — includes accessibility audit scoring 0–100 with specific failure items.
- Pa11y (CLI tool) — automate accessibility testing in CI/CD pipelines. Run on every deployment to catch regressions.
- Accessibility Insights (Microsoft) — detailed automated + guided manual testing for WCAG 2.2.
How to Perform Manual Accessibility Testing
Manual testing catches the 60–70% of issues automated tools miss. Essential manual tests:
Keyboard Navigation Test
Unplug your mouse and navigate the entire website using only keyboard. Tab through every interactive element, activate buttons and links with Enter/Space, navigate dropdowns with arrow keys. Check that: focus is visible at all times, tab order follows a logical sequence, no keyboard traps exist (elements you cannot Tab out of), all functionality is accessible without a mouse.
Screen Reader Test
Test with at least one screen reader. Free options: NVDA (Windows), VoiceOver (macOS/iOS), TalkBack (Android). Check that: images have meaningful alt text, form fields have associated labels, headings create a logical outline, dynamic content updates are announced, ARIA landmarks identify page regions.
Color and Contrast Test
Use the Colour Contrast Analyser or browser DevTools to verify: text contrast ratio of at least 4.5:1 for normal text and 3:1 for large text (18pt+), UI components and graphical objects have at least 3:1 contrast, and information is not conveyed by color alone.
Most Common WCAG Violations on Indian Websites
- Missing alt text (WCAG 1.1.1) — images without alt attributes or with generic text like “image1.jpg”.
- Low color contrast (WCAG 1.4.3) — light gray text on white backgrounds, trendy low-contrast designs.
- Missing form labels (WCAG 1.3.1) — input fields without associated <label> elements.
- No skip navigation (WCAG 2.4.1) — keyboard users must Tab through the entire header/nav on every page.
- Non-descriptive link text (WCAG 2.4.4) — links saying “click here” or “read more” with no context.
- Missing page language (WCAG 3.1.1) — no lang attribute on the <html> element.
- Inaccessible custom widgets (WCAG 4.1.2) — custom dropdowns, modals, and sliders without ARIA roles and states.
- Auto-playing media (WCAG 1.4.2) — videos or audio that play automatically without user control.
Accessibility Testing Checklist for Indian Businesses
- All images have descriptive alt text (decorative images use alt=””)
- Color contrast meets AA ratios (4.5:1 for text, 3:1 for large text)
- All pages are navigable by keyboard alone
- Focus indicator is visible on all interactive elements
- Heading hierarchy is logical (H1 → H2 → H3, no skipped levels)
- Form fields have visible labels and error messages
- Videos have captions and audio descriptions where applicable
- Page language is declared in HTML lang attribute
- Skip navigation link present on all pages
- ARIA landmarks used for major page regions
- Touch targets are at least 44×44 CSS pixels on mobile
- Content is readable at 200% zoom without horizontal scrolling
Frequently Asked Questions
Is web accessibility legally required in India?
India’s Rights of Persons with Disabilities Act (2016) requires government websites to be accessible following GIGW guidelines, which reference WCAG 2.0 AA. Private sector websites are not yet explicitly mandated, but the Act’s broad language covers “services” including digital services. Additionally, businesses serving international customers must consider ADA (US), EAA (EU), and other laws that mandate accessibility.
How much does it cost to make a website WCAG AA compliant?
For existing websites, an accessibility audit typically costs ₹30,000–₹1,50,000 depending on site size. Remediation costs vary widely: simple fixes (alt text, contrast, labels) can be done in ₹20,000–₹50,000, while complex fixes (custom widget rebuilds, structural changes) may cost ₹1,00,000–₹5,00,000. Building accessibility into new projects from the start adds only 5–10% to development costs.
Do accessibility overlays and widgets work?
No. Overlay tools that add a toolbar to your site (like accessiBe, UserWay, etc.) do not fix underlying code issues and are widely rejected by the disability community and accessibility professionals. They can actually make sites less accessible by interfering with screen readers. Fix your code instead.
Does accessibility help SEO?
Yes. Many accessibility practices directly improve SEO: descriptive alt text helps image search, semantic HTML helps crawlers understand page structure, heading hierarchy aids content comprehension, fast-loading accessible pages score better on Core Web Vitals, and transcripts/captions create indexable text content from multimedia.
How often should I test for accessibility?
Run automated tests on every deployment via CI/CD. Conduct manual screen reader and keyboard testing quarterly. Perform a full WCAG audit annually or after major redesigns. Include accessibility acceptance criteria in your development workflow for every new feature.
