Accessibility Audit Checklist for Digital Products

An accessibility audit is a systematic evaluation to ensure your digital products—websites, applications, and software—are usable by people with a wide range of abilities and disabilities. Beyond legal compliance, it's a fundamental practice for ethical design, reaching a broader market, and improving overall user experience. This checklist provides a structured, high-priority framework for conducting a thorough accessibility audit, moving beyond basic checks to uncover the barriers that truly impact users.

Understanding WCAG 2.1 Level AA as Your Benchmark

The Web Content Accessibility Guidelines (WCAG) 2.1 are the internationally recognized standard for digital accessibility, with Level AA conformance being the most common target for legal and practical compliance. These guidelines are organized around four principles, often remembered by the acronym POUR: Perceivable, Operable, Understandable, and Robust. Your audit checklist must verify adherence to each. This means not just checking for the presence of alternative text, but ensuring it is meaningful and contextual. It involves validating that all functionality is available via a keyboard (Operable) and that content appears and operates in predictable ways (Understandable). Treat the Level AA success criteria as your definitive checklist items; each one translates into a specific test or verification point during your audit.

Executing Automated and Manual Testing Procedures

Relying solely on automated tools is a critical mistake. A robust audit employs a dual approach. Automated testing uses software to quickly scan for easily detectable issues across many pages, such as missing image alt text, improper heading structures, or color contrast failures for large text. Tools like axe DevTools or WAVE are excellent for this initial sweep. However, they can only catch about 30-40% of potential issues. This is why manual testing is indispensable. Manual testing involves human evaluators systematically interacting with the product using assistive technologies and strategic methods to uncover logical flaws, contextual errors, and usability barriers that machines cannot perceive. The two methods are complementary: automated tools provide scalable coverage, while manual testing provides the essential depth and user-centric insight.

Conducting Screen Reader, Keyboard, and Visual Accessibility Checks

This is the core of manual operability testing. Screen reader compatibility testing requires you to navigate the interface using a screen reader like NVDA (with Firefox), VoiceOver (with Safari), or JAWS. The goal is to assess the experience for users who are blind or have low vision. You must verify that all interactive elements are announced correctly, that form fields are properly labeled, that status messages are conveyed, and that the reading/navigation order is logical. Simultaneously, keyboard navigation verification tests the experience for users who cannot use a mouse, including those with motor disabilities. Disconnect your mouse and try to complete all tasks using only the Tab, Arrow, Enter, and Escape keys. You are checking for a logical tab order, visible keyboard focus indicators, the ability to bypass repetitive blocks with a "skip link," and that no functionality is trapped in "keyboard traps" like inaccessible modal dialogs.

Visual accessibility ensures content is perceivable by people with low vision, color vision deficiencies, or other visual impairments. Color contrast checks are quantitative: you must measure the luminance ratio between text (or essential graphical elements) and its background. For normal text, Level AA requires a contrast ratio of at least 4.5:1; for large text (approximately 18pt or 14pt bold), it's 3:1. Use a tool like the Colour Contrast Analyser to validate this. Beyond contrast, assess visual accessibility by checking that color is not used as the sole means of conveying information (e.g., "required fields are in red" should also have an icon or text). Ensure that content remains usable when zoomed to 200% and that users can pause, stop, or hide any moving, blinking, or auto-updating content to prevent distractions or seizures.

Incorporating Cognitive and Mobile Accessibility Considerations

Often overlooked, cognitive accessibility considerations address the needs of users with learning disabilities, attention deficits, or memory impairments. This involves auditing for clear, simple language and consistent navigation. Verify that instructions, error messages, and labels are easy to understand. Check that interactive elements are predictable—a button should look and behave like a button everywhere. Allow users enough time to complete tasks with mechanisms to extend or turn off time limits. Mobile accessibility testing brings its own set of challenges and must be conducted on real devices. Test touch target sizes (minimum 44x44 pixels), ensure sufficient spacing to prevent accidental activation, and verify that all mobile-specific gestures (like swipe) have a single-tap alternative. Check that viewport zoom is not disabled and that the experience holds up in both portrait and landscape orientations.

Documenting Findings and Prioritizing Remediation

The final, crucial phase transforms your audit from an assessment into an action plan. Documentation of findings must be clear, actionable, and traceable. For each issue, record: the WCAG success criterion violated, the location (URL and component), a detailed description of the problem, the steps to reproduce it, and the severity level (e.g., Critical, High, Medium). Include screenshots or screen recordings, especially for screen reader or keyboard issues. Following this, employ remediation prioritization strategies to guide development efforts. A common framework prioritizes based on a combination of factors: the severity of the impact on users (does it block a core task?), the frequency of the issue, and the effort required to fix it. Critical barriers that prevent task completion for disabled users must be addressed first. Presenting findings in a prioritized roadmap helps stakeholders make informed decisions and allocate resources effectively to achieve meaningful compliance.

Common Pitfalls

1. Over-Reliance on Automated Tools: Treating an automated scan report as a complete audit. Correction: Always combine automated testing with extensive manual testing, particularly with screen readers and keyboard-only navigation, to uncover the nuanced, contextual barriers that users face.
2. Ignoring Context in Alt Text: Writing alt text that is merely descriptive ("blue graph") instead of conveying the same information and function. Correction: Alt text for an informative image should describe its content and purpose. For a complex chart, provide a brief summary in the alt attribute and a detailed description in adjacent text or a link.
3. Assuming Mobile is Inherently Accessible: Believing that because a product is built with a modern mobile framework, it automatically passes accessibility checks. Correction: Mobile platforms have unique interaction patterns and assistive technologies. You must conduct dedicated testing on iOS and Android with their respective screen readers (VoiceOver and TalkBack) and switch controls.
4. Treating Accessibility as a One-Time Checklist: Conducting an audit only before a launch or in response to legal pressure, leading to recurring issues. Correction: Integrate accessibility checks into your design system definition, component development, code review, and QA processes. This "shift-left" approach prevents bugs and builds an inclusively designed product from the start.

Summary

• A comprehensive accessibility audit validates compliance against WCAG 2.1 Level AA criteria through a mandatory combination of automated testing for scalable issue detection and manual testing for nuanced, user-experience barriers.
• Core manual verification must include screen reader compatibility testing (with NVDA, VoiceOver, or JAWS) and full keyboard navigation verification to ensure operability for users who are blind, have low vision, or have motor impairments.
• Visual checks require measuring color contrast to meet specific ratios, while broader considerations must include cognitive accessibility (clarity, predictability) and dedicated mobile accessibility testing on real devices with platform-specific assistive tech.
• Effective audit output requires detailed documentation of findings linked to WCAG criteria and actionable remediation prioritization strategies focused on user impact to guide efficient and meaningful fixes.