A (manual) accessibility audit is the only way to determine WCAG conformance. Automated scans flag approximately 25% of issues, which leaves the rest to trained auditors working through each success criterion by hand. The manual accessibility audit methodologies combine assistive technology evaluation, keyboard operation checks, visual and structural inspection, and code review. Every criterion under WCAG 2.1 AA or 2.2 AA is examined against real user interaction, not machine assumptions. The output is an audit report that identifies specific issues, their location, and what needs to change for conformance.
| Method | What It Covers |
|---|---|
| Screen reader evaluation | NVDA, JAWS, VoiceOver, and TalkBack review of announcements, focus, and reading order |
| Keyboard operation | Tab order, focus visibility, keyboard traps, skip links, and interactive control operability |
| Visual inspection | Color contrast, spacing, text resize, reflow, and visible focus indicators |
| Code inspection | Semantic HTML, ARIA use, name/role/value, headings, landmarks, and form labels |
| Content review | Alt text quality, link purpose, captions, transcripts, language, and error messaging |
Why Manual Evaluation Is the Core of an Audit
Automated checkers pattern-match against a limited set of rules. They can flag a missing alt attribute, but they cannot judge whether the alt text describes the image accurately. They can detect a low-contrast pair, but they cannot decide whether a decorative graphic needs a text alternative at all.
Manual evaluation is where the human judgment happens. An auditor works through each WCAG success criterion, page by page, screen by screen, applying context that software cannot. That is what produces an accurate view of conformance.
Screen Reader Evaluation
Screen reader review is a defining part of the audit. Auditors use NVDA and JAWS on Windows, VoiceOver on macOS and iOS, and TalkBack on Android. Each environment reveals different behavior, and pages that read well in one may fail in another.
The auditor listens to how the page is announced, checks whether interactive controls expose the correct role and state, and confirms that dynamic content updates are announced when they should be. This maps directly to criteria like 4.1.2 Name, Role, Value and 1.3.1 Info and Relationships.
Keyboard Operation Checks
Every interactive element must be operable without a mouse. Auditors tab through the page in order, activate controls with Enter or Space, and confirm nothing traps focus. Skip links, modal dialogs, menus, and custom widgets receive close attention.
Focus visibility is evaluated at the same time. If a user cannot see where focus currently sits, keyboard operation breaks down even when the underlying interaction works.
Visual and Structural Inspection
Color contrast is checked against WCAG minimums using measurement tools, but the decision about what qualifies as text or a meaningful graphic still requires an auditor. Text resize to 200%, reflow at 320 CSS pixels, and spacing overrides are all evaluated in the browser.
Structural inspection covers heading hierarchy, landmark regions, and reading order. These items shape how assistive technology users move through a page.
What Does Code Inspection Add to the Audit?
Code inspection confirms what the browser and assistive technology are actually receiving. Auditors open developer tools and the accessibility tree to verify that names, roles, and states match what the interface presents visually.
This catches issues that behavior alone can miss. A button that looks and acts correct on screen may still expose the wrong role in code, which affects users on assistive technology in ways that are not visible without inspection.
Content and Media Review
Alt text is reviewed for accuracy and appropriate length. Link text is checked for descriptive purpose out of context. Video content is reviewed for captions and, where required, audio description. Form fields are verified for programmatic labels, clear instructions, and accessible error messaging.
Content review is often where the largest volume of issues appears, since it touches nearly every page.
How the Methodology Comes Together
An Accessible.org auditor moves through each page applying every method above against every relevant WCAG 2.1 AA success criterion. Findings are recorded with the criterion reference, the location, a description of the issue, and remediation guidance. The result is an audit report that a development team can act on directly.
The full audit process is fully manual from start to finish. Automated tooling supports the audit where it makes sense, such as running contrast calculations, but it never substitutes for evaluation by a trained auditor.
Remediation After the Audit
Once the audit report is delivered, the development team works through accessibility remediation based on the findings. Prioritization can follow Risk Factor or User Impact prioritization formulas depending on the goal. After fixes are made, a validation round confirms that issues have been resolved and no new issues were introduced.
FAQs
How long does a manual accessibility audit take?
Turnaround depends on the number of pages or screens in scope and the complexity of the interface. A typical website audit can be completed in a few weeks. Larger web apps and mobile apps take longer because more unique states need evaluation.
Can automated tools replace manual evaluation?
No. Automated tools detect about 25% of accessibility issues. The remaining issues, including most of what affects users on assistive technology, require an auditor working through each success criterion by hand.
Which WCAG version should the audit use?
WCAG 2.1 AA remains the most requested standard and aligns with most current regulations. WCAG 2.2 AA adds a small number of criteria and is the right choice for organizations preparing for newer requirements or client procurement demands.
What deliverable does an audit produce?
The primary deliverable is an audit report that lists every identified issue, the WCAG success criterion it maps to, the location, and guidance for remediation. This report is what a development team uses to bring the digital asset into conformance.
Manual evaluation is the work behind every credible conformance claim. Accessible.org conducts every audit this way because it is the only method that produces an accurate result.
Contact Accessible.org for a manual WCAG audit quote.
