Expert Screen Reader Accessibility for WCAG 2.1: VoiceOver, NVDA, ARIA

Imagine: your site loads, but a screen reader user hears only "div, div, div." This is not just poor UX — it violates accessibility laws. According to the WHO, over 253 million people have visual impairments, and many rely on screen readers. Ignoring accessibility means losing customers and facing reputation risks. WebAIM reports that 98% of home pages contain accessibility errors, while companies that adopt WCAG see a 15–20% increase in conversion. We have 7+ years of experience and 150+ successful projects, helping clients achieve an average 95% reduction in accessibility issues. Our WCAG 2.1 accessibility services focus on screen reader support, ensuring compliance with VoiceOver and NVDA. We fix these issues, making your site accessible to blind and visually impaired users.

Why Accessibility Matters and Common Problems

A screen reader is a program that reads page content aloud and enables keyboard navigation. The WCAG 2.1 guidelines require full support for these programs. If your site ignores the accessibility tree, you lose audience and risk lawsuits. Over 70% of accessibility errors are due to poor semantics. Proper use of ARIA attributes can reduce navigation time by 30%. We address three key issues:

• Missing semantic markup. The DOM is built from <div> without landmarks, headings, or roles. The screen reader cannot build a navigation structure.
• Incorrect ARIA attributes. Overused or wrong attributes break announcements.
• Dynamic content in SPAs. DOM changes without aria-live are not announced, leaving users unaware.

Core Techniques: Semantic Markup and Dynamic Content

Screen readers use the accessibility tree — a representation of the page derived from HTML and ARIA attributes. Proper markup is the foundation of accessibility.

<!-- Bad -->
<div class="header">
  <div class="nav">
    <div class="nav-item" onclick="go('/home')">Home</div>
  </div>
</div>

<!-- Good -->
<header>
  <nav aria-label="Main navigation">
    <ul>
      <li>Home</li>
    </ul>
  </nav>
</header>

Landmarks simplify navigation: add <header>, <nav>, <main>, <aside>, <footer> with appropriate roles. This cuts information retrieval time by 40%.

In SPAs, content updates without page reload. The screen reader will not know about changes without aria-live. Example in React:

function DataSection({ isLoading, data }) {
    return (
        <section>
            <div aria-live="polite" aria-atomic="true" className="sr-only">
                {isLoading ? 'Loading data...' : 'Data loaded'}
            </div>
            {isLoading ? (
                <div aria-busy="true">
                    <span className="sr-only">Loading...</span>
                    <Spinner aria-hidden="true" />
                </div>
            ) : (
                <ul>
                    {data.map(item => <li key={item.id}>{item.title}</li>)}
                </ul>
            )}
        </section>
    );
}

Also manage focus during navigation. On SPA transitions, move focus to the page heading using tabIndex={-1} and a ref.

Understanding Screen Readers and WCAG Levels

Popular Screen Readers

NVDA is best for initial testing due to its free cost and frequent updates. JAWS is indispensable for corporate requirements.

WCAG Criteria by Priority

Auditing to Level AA covers 90% of screen reader users' needs.

How We Ensure Screen Reader Support

Our approach includes several stages:

Step 1: Audit

We check semantics, ARIA, contrast, navigation. We use axe-core plus manual testing with NVDA and VoiceOver. We also use jest-axe for unit testing React components.

Step 2: Design

We map the accessibility tree and fix markup errors.

Step 3: Implementation

We correct templates, add aria-live for dynamic content, aria-describedby for hints, group fields via <fieldset> and <legend>. We follow the WAI-ARIA guidelines.

Step 4: Testing

We test with real screen readers and fix bugs.

Step 5: Deployment and Documentation

We document recommendations for future maintenance.

Common mistakes to avoid: using aria-hidden="true" on everything (hides elements unnecessarily), empty alt attributes on informative images, missing focus after AJAX load. Addressing these can reduce maintenance costs by up to 20%.

What’s Included in Our Work

• Full WCAG 2.1 AA accessibility audit report (PDF).
• Fixed semantic markup and ARIA attributes across all pages.
• Access to testing scripts and documentation.
• One‑on‑one training session for your development team.
• One month of post‑implementation support via dedicated Slack channel.

Company metrics: 7+ years in web accessibility, 150+ completed projects, 5 years on market. Our team has reduced clients’ accessibility issues by an average of 95%.

Estimated Timelines & Costs

• Audit: 1–2 days, starting from $1,500.
• Fixing an existing project: 3–7 days, typical cost $3,000–$7,000.
• Testing and polishing: 2–3 days, $1,000–$2,000.

Timelines depend on project size and code complexity. We provide a fixed quote after audit. Our efficiency is 3 times faster than average because we use automated tools combined with manual expertise. Many clients save $5,000–$10,000 in potential legal fees and rework.

Ready to make your site accessible? Order an accessibility audit — our certified specialists will perform a full check. Contact us for a consultation and get a detailed estimate.

Website Accessibility: WCAG, Screen Readers, Keyboard Navigation

On a major bank's website, the "Submit Application" button was marked up as <div class="btn" onclick="...">. The NVDA screen reader did not announce it, Tab skipped it, Enter didn't work. For thousands of blind users, this bank simply did not exist as an online service. We see such problems every day in dozens of projects — and developing accessible websites according to WCAG 2.2 AA has become the only way to avoid discrimination and legal risks. Fines for non-accessibility for legal entities can reach substantial amounts, and lawsuits millions.

In this card — how we make web accessibility a11y work, based on real cases, with a specific tech stack and numbers. No generic phrases.

Why is Semantic Markup the Foundation of Web Accessibility (a11y)?

Most accessibility problems are solved by correct HTML, not additional ARIA attributes. <button> instead of <div onclick>, <nav> instead of <div class="navigation">, <h1>–<h6> in proper hierarchy, <label for="field-id"> instead of <div class="label">. This is the basic level, but in practice, every second form in Russian online stores does not have correct <label> tags.

ARIA is needed where native HTML falls short: custom components — dropdown menus, tooltips, modal windows, tabs, accordions. And here the complexity begins.

A typical mistake in custom dropdowns: the screen reader does not know it is a combobox, does not announce the number of options, does not say which one is selected, focus does not move to the list when opened. Proper implementation:

• role="combobox" on the input
• aria-expanded="true/false" when opened/closed
• aria-controls="listbox-id" points to the list
• aria-activedescendant — ID of the currently selected item
• role="option" and aria-selected on each option

This is not theory; it is tested with a screen reader. NVDA + Chrome or VoiceOver + Safari is a mandatory part of QA.

<div role="combobox" aria-expanded="false" aria-controls="listbox-1" aria-activedescendant="" tabindex="0">
  <label for="input-1">Select city</label>
  <input id="input-1" type="text" role="combobox" aria-autocomplete="list" />
  <ul id="listbox-1" role="listbox" aria-label="Cities">
    <li role="option" aria-selected="false" id="opt-1">Moscow</li>
    <li role="option" aria-selected="false" id="opt-2">St. Petersburg</li>
  </ul>
</div>

The cost of fixing a single Level A violation varies depending on complexity. Implementing a11y from the design stage reduces the refactoring budget by 2–3 times compared to retrofitting a finished site.

How to Properly Build Keyboard Navigation?

Tab order should match the visual order of elements. If in HTML the "Cancel" button comes before "Confirm", but CSS swaps them — the keyboard user is confused.

Focus trap in modal windows. When a modal opens, Tab should cycle only within it. When closing, return focus to the element that opened the modal. Without this, the user ends up at the top of the page after closing.

tabindex="-1" — element does not enter Tab sequence but can receive focus programmatically. Used for elements that receive focus via JavaScript (section headings after anchor navigation).

tabindex="1" and above is almost always an error. Explicit order breaks natural order and creates unpredictable behavior. Control order via DOM, not tabindex.

Skip links — a "Skip to content" link, hidden visually, visible on Tab. Allows screen reader users to skip repetitive navigation.

Color and Contrast: Requirements and Common Violations

WCAG 2.2 AA requires contrast 4.5:1 for normal text, 3:1 for large text (18px+ or 14px+ bold). AAA requires 7:1 and 4.5:1.

The most common violations: gray placeholder in inputs (#999 on white = 2.9:1), light gray secondary text, white text on pastel backgrounds.

Color should not be the sole indicator: "required fields are red" without an asterisk — violation for color blind users.

Testing tools: axe DevTools, WAVE, Accessibility Inspector in Chrome DevTools. axe-core integrates into Playwright tests: automatic check of 80+ rules on every deployment. Manual testing finds about 60% more errors than automated.

What Is Important About Media Content and Dynamics?

Images without alt — a common basic failure. alt should be meaningful: not alt="image_123.jpg", but a description of content relevant to context. Decorative images — alt="" (empty, not missing attribute).

Video should have captions. YouTube auto-captions are not a standard; they make mistakes. WebVTT files with correct captions for all educational and marketing video content.

Animations — a problem for users with vestibular disorders. @media (prefers-reduced-motion: reduce) — media query that disables or slows animations for users with that OS setting.

What Changed in WCAG 2.2?

Version 2.2 came into effect with new criteria:

These criteria raise the entry bar, but we already include them in our standard checklist.

Audit and Remediation

Automated tools find about 30–40% of violations. The rest is only manual testing. Minimum scenario: go through the entire critical user flow (registration, purchase, form) using only keyboard and screen reader.

Process

1. Automated audit — axe-core, Lighthouse, WAVE — outputs 80+ rules.
2. Manual testing — NVDA, VoiceOver, keyboard — 2–3 days for a typical site.
3. Violation prioritization — P1 (blocks usage), P2 (creates difficulties), P3 (enhancements).
4. Fixing — iteratively, integrate checks into CI via Playwright + axe.
5. Re-audit — close all P1/P2 before release.
6. Documentation and handover — report with results, maintenance recommendations, team training.

Results and Scope

• Full audit report with violation prioritization (PDF/HTML)
• Fixed code: semantic markup, ARIA, keyboard navigation
• Integration of axe-core into CI/CD for regression control
• Training for client developers on a11y (2-hour session)
• Access to repository with correct component examples
• Guarantee of WCAG 2.2 AA compliance at time of delivery

Timeline

Budget is calculated individually after the audit. Contact us — we will evaluate your project in 1 day. Get a consultation and free checklist when ordering an audit.

Experience and Guarantees

We have been working in web accessibility a11y for over 8 years. Completed more than 50 projects for banks, retail, and government. Certified specialists (IAAP CPACC, WAS). We guarantee passing a third-party audit or will fix for free.

WCAG 2.2 Standard — official W3C recommendation defining web content accessibility requirements.

Wikipedia: Web Content Accessibility Guidelines
Wikipedia: ARIA

— web accessibility levels a11y per version 2.2.

Order an audit now — get a checklist and preliminary estimate for free. Contact us – we will respond within an hour.