DEV Community

Novida
Novida

Posted on

How to Audit Your Web App for Accessibility: A Practical Checklist for Developers

Accessibility audits have a reputation for being vague and preachy. This one isn't. It's a practical, ordered checklist you can run against any web app in a day or two, with the failures I see most often in production code.

0. Set your target: WCAG 2.2 AA

WCAG 2.2 at Level AA is the baseline most legislation and procurement policies reference. You don't need to memorise all 86 success criteria — the checklist below covers the ones that account for the vast majority of real-world failures.

1. Automated scan first (10 minutes, catches ~30%)

Run axe DevTools or Lighthouse on your key pages. Fix everything it flags — but understand its limits. Automated tools catch missing alt text, bad contrast ratios, and invalid ARIA, but they cannot tell you whether your alt text is meaningful, whether your focus order makes sense, or whether a screen-reader user can actually complete your checkout flow. Automation is the floor, not the ceiling.

2. Semantic HTML: use the platform

Half of accessibility bugs are divs pretending to be something else. Before reaching for ARIA, check whether native HTML already does the job:

<!-- Don't do this -->
<div class="btn" onclick="submit()">Save</div>

<!-- Do this -->
<button type="submit">Save</button>
Enter fullscreen mode Exit fullscreen mode

Native <button>, <a>, <input>, <select>, <dialog>, and heading elements come with keyboard behaviour, focusability, and accessibility-tree roles for free. Every custom reimplementation is a chance to get it wrong. Audit for clickable divs and spans with your inspector: if it has a click handler but no role and no tabindex, it's broken for someone.

3. Keyboard navigation: unplug the mouse

Tab through your entire app. Everything interactive must be reachable and operable by keyboard alone, with a visible focus indicator at all times. Common failures:

  • Focus outlines removed with outline: none and never replaced.
  • Modals and dropdowns that don't trap focus — tabbing escapes into the page behind.
  • Custom widgets (sliders, tabs, comboboxes) that don't implement the WAI-ARIA Authoring Practices keyboard patterns.

Test this sequence on every dialog: open it, confirm focus moves into it, tab through to the end, confirm focus cycles back to the start, press Escape, confirm focus returns to the trigger element.

4. Focus management in SPAs

Single-page apps are focus-management minefields. When a view changes without a page load, sighted users see the new content — screen-reader users hear nothing unless you tell them. The pattern:

// After a route change or major view update:
function announceViewChange(title) {
  document.title = title;
  const heading = document.querySelector('main h1');
  heading.setAttribute('tabindex', '-1');
  heading.focus({ preventScroll: false });
}
Enter fullscreen mode Exit fullscreen mode

Move focus to the new view's heading on navigation. For async updates (form submitted, list filtered), use a polite live region rather than moving focus.

5. ARIA: the first rule

The first rule of ARIA: don't use ARIA if you don't have to (see step 2). The second rule: if you do use it, get it exactly right — broken ARIA is worse than no ARIA, because it actively misleads assistive technology. Audit for:

  • aria-label on elements that don't accept accessible names.
  • Redundant roles (role="button" on a <button>).
  • aria-hidden="true" on focusable elements — this hides focused content from screen readers while keyboard users can still reach it. A classic, nasty bug.
  • Live regions (aria-live="polite") that are added to the DOM after the content changes — the region must exist before you update it, or the announcement never fires.

6. Contrast and text

Check text contrast against WCAG AA: 4.5:1 for normal text, 3:1 for large text and UI components. Placeholder text as a label substitute fails twice — low contrast and it disappears. Also verify your app at 200% zoom and 400% zoom: content must reflow without horizontal scrolling or clipped controls.

7. Test with a real screen reader

This is the step teams skip, and it's the one that finds the bugs that matter. NVDA (free, Windows) or VoiceOver (built into macOS/iOS) for 30 minutes on your core user flows. You'll discover things no checklist catches: the "click here" links, the icon buttons announced as "button" with no name, the form errors that appear visually but are never announced.

Why this matters beyond compliance

For services used by vulnerable people, accessibility isn't a nice-to-have — it's the product working at all. Take Novida, an Australian NDIS platform where participants search for disability support providers: if the search results aren't keyboard-navigable or the provider cards are div-soup, the very people the service exists for can't use it. When your users include people who depend on assistive tech daily, an accessibility failure is a service outage for them.

The bottom line

Run the automated scan, fix the semantics, unplug the mouse, manage focus, use ARIA sparingly and correctly, check contrast, and spend 30 minutes with a screen reader. Do that on every major release and accessibility stops being a scary audit — it becomes part of how you ship.

Top comments (0)