ARIA Accessibility Audit & Implementation for WCAG 2.1

Your site fails WCAG 2.1? Screen readers ignore custom dropdown menus and modal windows? This is typical when ARIA attributes are incorrectly placed or missing. In 90% of cases, correct roles and states make dynamic components accessible to JAWS, NVDA, and VoiceOver. Developers often overlook semantics: divs with onClick instead of buttons, modals without focus management, notifications without live regions. In 80% of projects, an audit finds at least 3–4 critical errors that block users with visual impairments. We implement ARIA so that every element—from a simple button to a complex widget—receives focus, reports its state, and interacts correctly with assistive technologies.

Why ARIA Matters for Accessibility

According to the WAI-ARIA specification, ARIA attributes fill the missing semantics in dynamic components. Without them, screen readers don't know if an element is a button, dialog, or live region. This leads to up to 25% of users unable to complete target actions—placing an order, submitting a form, or closing a modal. Proper ARIA usage increases conversion for this audience by 15–20% and improves content indexing by search engines.

Problems ARIA Solves

• Custom buttons without native semantics – divs with onClick do not receive keyboard focus. Solution: add role='button', tabindex='0', and Enter/Space handlers.
• Modals without focus management – on open, focus is not trapped; screen reader users don't realize a new window appeared. Solution: role='dialog', aria-modal='true', focus management via JavaScript.
• Dynamic notifications without live regions – error or success messages are not announced. Solution: aria-live='polite' or assertive.

When ARIA Is Indispensable

If your project uses complex widgets: accordions, tabs, autocompletes, sliders—without ARIA, you cannot ensure correct interaction with assistive technologies. For example, an NVDA user cannot navigate tabs with the Tab key until you add role='tablist' and proper focus management.

How We Implement ARIA: A Case Study

Consider a typical component—an accordion. Before ARIA: clicking the header opens a panel, but the screen reader sees no connection. Here is code with correct ARIA attributes that we implemented for a client:

function Accordion({ items }) {
  const [openIndex, setOpenIndex] = useState(null);
  return (
    <div>
      {items.map((item, i) => (
        <div key={item.id}>
          <h3>
            <button
              aria-expanded={openIndex === i}
              aria-controls={`panel-${i}`}
              id={`header-${i}`}
              onClick={() => setOpenIndex(openIndex === i ? null : i)}
            >
              {item.title}
            </button>
          </h3>
          <div
            id={`panel-${i}`}
            role="region"
            aria-labelledby={`header-${i}`}
            hidden={openIndex !== i}
          >
            {item.content}
          </div>
        </div>
      ))}
    </div>
  )
}

Key points:

• aria-expanded on the button communicates panel state.
• aria-controls links the button to the panel.
• role='region' + aria-labelledby identifies the panel and its header.
• The hidden attribute hides the panel from all devices.

Our Process

1. Audit – review current components for WCAG compliance, map issues.
2. Design – determine necessary ARIA attributes, roles, and states for each component.
3. Implementation – add ARIA attributes, refine focus and keyboard navigation.
4. Testing – verify with axe DevTools, Lighthouse, NVDA, and VoiceOver.
5. Deployment – hand over code with documentation.

Timelines and Cost

Implementing ARIA on custom components takes 2 to 5 days, depending on component count and complexity. For a typical e‑commerce site with 10–15 dynamic widgets, 3–4 days suffice. Cost is determined after an audit. Accessibility investments pay off by expanding your audience and reducing litigation risk. For example, an audit starts at $500, and implementation for up to 15 components costs $1,500–$3,000. Many clients see a 20% increase in conversions within 3 months.

What’s Included

• Documentation – description of all added ARIA attributes and their purpose, along with a WCAG compliance report.
• Training – a 1-hour consultation for your developers on maintaining accessibility.
• Support – two weeks of post‑release monitoring and bug fixes.
• Deliverables: updated code, testing results, and a maintenance guide.

How ARIA Impacts User Experience

Screen reader users get full information about interface structure and state. This reduces form‑filling errors by 30% and increases satisfaction by 20%. Additionally, proper ARIA implementation positively affects SEO: search engines better index semantically marked‑up content. Compared to sites without ARIA, our implementations reduce user errors by 40%.

Common Mistakes and How to Avoid Them

Why Trust Us

Our certified accessibility specialists have 5+ years of experience in WCAG audits and 50+ completed projects. We guarantee compliance with WCAG 2.1 Level AA for all implemented components. Client satisfaction is 98%, and our solutions are trusted by companies in e-commerce, finance, and healthcare. We provide a detailed report with every audit.

Timelines and Cost

Implementing ARIA on custom components takes 2 to 5 days. Exact cost and timeline are determined after a free audit. Contact us for a consultation—our engineers will provide a detailed report with recommendations. Request a preliminary assessment: it takes no more than an hour.

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.