Accessibility Audit
Test any webpage for WCAG accessibility issues. Identify barriers that prevent users with disabilities from accessing your content.
What is web accessibility?
Web accessibility ensures that websites and applications are usable by everyone, including people with disabilities. This includes users who are blind or have low vision, deaf or hard of hearing, have motor disabilities, cognitive disabilities, or temporary impairments.
Accessible websites don’t just help people with disabilities -they improve the experience for everyone. Clear navigation, readable text, and keyboard support benefit all users, especially those on mobile devices or in challenging environments.
Understanding WCAG
The Web Content Accessibility Guidelines (WCAG) are the international standard for web accessibility. They’re organised around four principles -websites should be:
Perceivable - Information must be presentable in ways users can perceive. This includes text alternatives for images, captions for video, and sufficient colour contrast.
Operable - Interface components must be operable by all users. This means keyboard accessibility, enough time to read content, and no content that causes seizures.
Understandable - Information and operation must be understandable. Pages should be readable, predictable, and help users avoid and correct mistakes.
Robust - Content must be robust enough to work with current and future technologies, including assistive technologies like screen readers.
WCAG conformance levels
WCAG has three conformance levels:
| Level | Difficulty | Requirement |
|---|---|---|
| Level A | Minimum | Basic accessibility features. Without these, some users cannot access content at all. |
| Level AA | Standard | Addresses the most common barriers. This is the legal requirement in most jurisdictions. |
| Level AAA | Enhanced | Highest level of accessibility. Not required but recommended for specialised audiences. |
Most organisations target WCAG 2.1 Level AA, which is the standard referenced by accessibility laws in Australia (DDA), the EU (EN 301 549), and the US (Section 508).
Common accessibility issues
Missing alt text - Images without alternative text are invisible to screen reader users. Every meaningful image needs a description of its content or purpose.
Insufficient colour contrast - Text that doesn’t contrast enough with its background is hard to read for users with low vision or colour blindness. WCAG requires a contrast ratio of at least 4.5:1 for normal text.
Missing form labels - Form inputs need associated labels so screen readers can announce what information is required. Placeholder text alone is not sufficient.
Keyboard traps - Users who navigate with keyboards must be able to move focus to and away from all interactive elements. Modal dialogs often trap focus incorrectly.
Missing document structure - Proper heading hierarchy (h1, h2, h3) helps screen reader users understand page structure and navigate quickly to relevant sections.
No skip links - Long pages with navigation menus should provide a “skip to main content” link so keyboard users don’t have to tab through every navigation item.
Legal requirements
Web accessibility is a legal requirement in many jurisdictions:
Australia - The Disability Discrimination Act (DDA) requires accessible websites. Government agencies must meet WCAG 2.1 AA under the Digital Service Standard.
European Union - The European Accessibility Act and EN 301 549 mandate WCAG 2.1 AA compliance for public sector websites.
United States - Section 508 requires federal agencies to make electronic content accessible. ADA lawsuits increasingly target private websites.
United Kingdom - The Equality Act 2010 and Public Sector Bodies Accessibility Regulations require WCAG 2.1 AA compliance.
How this tool works
Enter a URL to scan the page for accessibility issues. The tool uses the axe-core engine -the same technology used by major browsers’ developer tools -to test against WCAG success criteria. Results are categorised by severity and include specific elements that need attention. Powered by a QuantCDN Edge Function.
Note: Automated testing can identify approximately 30-40% of accessibility issues. A complete accessibility audit requires manual testing with assistive technologies and user testing with people who have disabilities.