<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Novida</title>
    <description>The latest articles on DEV Community by Novida (@novidaau).</description>
    <link>https://dev.to/novidaau</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4258461%2Fb568d460-f2ae-42d7-bdb1-08fd5d7fd409.png</url>
      <title>DEV Community: Novida</title>
      <link>https://dev.to/novidaau</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/novidaau"/>
    <language>en</language>
    <item>
      <title>How to Audit Your Web App for Accessibility: A Practical Checklist for Developers</title>
      <dc:creator>Novida</dc:creator>
      <pubDate>Sun, 22 Nov 2026 11:34:41 +0000</pubDate>
      <link>https://dev.to/novidaau/how-to-audit-your-web-app-for-accessibility-a-practical-checklist-for-developers-cpf</link>
      <guid>https://dev.to/novidaau/how-to-audit-your-web-app-for-accessibility-a-practical-checklist-for-developers-cpf</guid>
      <description>&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  0. Set your target: WCAG 2.2 AA
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Automated scan first (10 minutes, catches ~30%)
&lt;/h2&gt;

&lt;p&gt;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 &lt;em&gt;meaningful&lt;/em&gt;, 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.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Semantic HTML: use the platform
&lt;/h2&gt;

&lt;p&gt;Half of accessibility bugs are divs pretending to be something else. Before reaching for ARIA, check whether native HTML already does the job:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight html"&gt;&lt;code&gt;&lt;span class="c"&gt;&amp;lt;!-- Don't do this --&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;div&lt;/span&gt; &lt;span class="na"&gt;class&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"btn"&lt;/span&gt; &lt;span class="na"&gt;onclick&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"submit()"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;Save&lt;span class="nt"&gt;&amp;lt;/div&amp;gt;&lt;/span&gt;

&lt;span class="c"&gt;&amp;lt;!-- Do this --&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;button&lt;/span&gt; &lt;span class="na"&gt;type&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"submit"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;Save&lt;span class="nt"&gt;&amp;lt;/button&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Native &lt;code&gt;&amp;lt;button&amp;gt;&lt;/code&gt;, &lt;code&gt;&amp;lt;a&amp;gt;&lt;/code&gt;, &lt;code&gt;&amp;lt;input&amp;gt;&lt;/code&gt;, &lt;code&gt;&amp;lt;select&amp;gt;&lt;/code&gt;, &lt;code&gt;&amp;lt;dialog&amp;gt;&lt;/code&gt;, 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.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Keyboard navigation: unplug the mouse
&lt;/h2&gt;

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

&lt;ul&gt;
&lt;li&gt;Focus outlines removed with &lt;code&gt;outline: none&lt;/code&gt; and never replaced.&lt;/li&gt;
&lt;li&gt;Modals and dropdowns that don't trap focus — tabbing escapes into the page behind.&lt;/li&gt;
&lt;li&gt;Custom widgets (sliders, tabs, comboboxes) that don't implement the &lt;a href="https://www.w3.org/WAI/ARIA/apg/" rel="noopener noreferrer"&gt;WAI-ARIA Authoring Practices&lt;/a&gt; keyboard patterns.&lt;/li&gt;
&lt;/ul&gt;

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

&lt;h2&gt;
  
  
  4. Focus management in SPAs
&lt;/h2&gt;

&lt;p&gt;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:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// After a route change or major view update:&lt;/span&gt;
&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;announceViewChange&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;title&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;title&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;heading&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;document&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;querySelector&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'main h1'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="n"&gt;heading&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;setAttribute&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'tabindex'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s1"&gt;'-1'&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="n"&gt;heading&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;focus&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;preventScroll&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;false&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. ARIA: the first rule
&lt;/h2&gt;

&lt;p&gt;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:&lt;/p&gt;

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

&lt;h2&gt;
  
  
  6. Contrast and text
&lt;/h2&gt;

&lt;p&gt;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 &lt;em&gt;and&lt;/em&gt; it disappears. Also verify your app at 200% zoom and 400% zoom: content must reflow without horizontal scrolling or clipped controls.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Test with a real screen reader
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this matters beyond compliance
&lt;/h2&gt;

&lt;p&gt;For services used by vulnerable people, accessibility isn't a nice-to-have — it's the product working at all. Take &lt;a href="https://novida.com.au" rel="noopener noreferrer"&gt;Novida&lt;/a&gt;, 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.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bottom line
&lt;/h2&gt;

&lt;p&gt;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.&lt;/p&gt;

</description>
      <category>a11y</category>
      <category>frontend</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
