TaggedWorks - Digital Accessibility Firm
Guides[ ARTICLE D'INGÉNIERIE ]

How to Conduct an Enterprise Manual Accessibility Audit

An insider walkthrough of the testing methodology senior accessibility specialists use to discover critical defects that automated scanners miss.

TaggedWorks Audit Practice
Publié le : 2024-06-02
12 min de lecture

Normes référencées

WCAG 2.2 AASection 508W3C ACT Rules
[ AUDIT D'INGÉNIERIE ]

Besoin d'un audit technique rigoureux de vos produits numériques au regard de ces normes ?

Demander un audit

Step 1: Representative Scoping

An enterprise audit does not require testing all 50,000 pages of a website. It requires sampling every distinct page template, authenticated state, modal dialog, interactive component, and critical conversion pathway (login, search, checkout, file upload, form submission).

Step 2: Full Keyboard Navigation

Disconnect your mouse and navigate through the entire interface using only Tab, Shift+Tab, Enter, Space, Escape, and arrow keys. Check for visible focus indicators, logical focus order, modal focus traps, and bypass blocks (skip links).

Step 3: 400% Zoom and Reflow

Set browser zoom to 400% at a 1280px desktop resolution (simulating a 320px mobile viewport). Verify that content reflows into a single column without requiring horizontal scrolling (WCAG 2.2 SC 1.4.10) and that fixed navigation bars do not obscure reading content.

Step 4: Screen Reader Inspection

Launch NVDA on Windows or VoiceOver on macOS. Navigate by headings (H), landmarks (D), links (K), and form fields (F). Verify that custom components accurately convey their role, name, state (expanded/collapsed), and dynamic alerts.

Step 5: DOM & Accessibility Tree Inspection

Use browser DevTools Accessibility Tree to confirm that semantic roles are properly exposed to the operating system accessibility API without redundant or conflicting ARIA overrides.

TW

TaggedWorks Audit Practice

Pôle de recherche et d'ingénierie en accessibilité numérique

Les publications de recherche de TaggedWorks sont rédigées par des ingénieurs et spécialistes praticiens. Nos préconisations reflètent les interprétations actuelles des WCAG 2.2, les comportements des navigateurs et les matrices de compatibilité des technologies d'assistance.