Test Accessible Website: What a good test actually needs to cover
A useful website accessibility test does more than scan a homepage. It checks whether your visitors can navigate forms, keyboard focus paths, and mobile pages without barriers.
What a website accessibility test should verify
To meet the legal compliance requirements of WCAG 2.1 AA and the BFSG, all interactive sections must be free of obstacles.
Ensure heading hierarchies, document landmarks, and form field descriptions are constructed logically for screen readers.
All interactive elements (menus, buttons, links) must be reachable, operational, and visually highlighted using the tab key.
Input fields must have explicit labels, and validation errors must be programmatically linked to their corresponding inputs.
Text elements, inline symbols, and active states (focus, hover) must have high enough contrast ratios relative to their background.
Touch targets must be sufficiently large, hamburger menus must not lock, and complex zoom scales must wrap appropriately.
Modal popups, slider filters, cookie banners, and tab segments must trap, move, and return keyboard focus logically.
What typical scanners usually miss
Simple raw source-code crawlers only capture half the truth. Here is the direct comparison.
Login Barriers & Walls
Cookie Consent
Dynamic Overlays
Keyboard Traps
Mobile-specific Bugs
Form Error Handling
Hidden Menus
Complex Journeys
How to Properly Test a Website
An accessible website cannot be guaranteed by a single tool at the push of a button. Every website should go through a structured, sequential testing process. The more dynamic and interactive your site is, the deeper the required testing scope.
Step 1: Quick Single-Page Scan
Best for initial evaluation. Highlights obvious coding violations on a single URL, but is insufficient for complete compliance claims.
Step 2: Template & Section Review
Evaluates main static layout components. Identifies global layout errors occurring in the header, footer, or core content blocks.
Step 3: Deep State Audit (incl. Flows)
Covers dynamic overlays, account login environments, shopping carts, and mobile states. Highly recommended for transactional portals.
Step 4: Combined Audit (Auto + Manual)
Integrates automated tests with manual evaluations by accessibility experts (e.g. screen reader navigation). Ensures maximum legal safety.
Step 5: Documentation & Monitoring
Consolidate all findings into a single compliance report and monitor the site continuously to catch regressions in new releases instantly.
What website pages and states must be tested
Accessibility is determined in the interactive states of your website, not just on the first page load.
What automated checkers can and cannot accomplish
Manual testing is important for things scanners cannot judge reliably, such as whether alt text is actually meaningful, whether keyboard focus moves logically through complex flows, whether screen reader output makes sense, and whether language is understandable for real users. It is especially useful for login areas, forms, dialogs, and multi-step journeys where interaction quality matters more than raw code checks.
Well suited for automation
- Technical layout syntax and HTML validation
- Missing image descriptions (completely empty alt attributes)
- Color contrast ratios between text characters and backgrounds
- Missing input labels on standard form elements
- Keyboard tab access for standard anchors and buttons
Requires manual expert evaluation
- The actual quality of alt text descriptions (e.g. 'Photo 43' vs details)
- Logical flow sequence of keyboard tabs across dynamic inputs
- Readability level of language texts and terms
- True interaction experience of assistive tools like screen readers
- Exemption cases and disproportionate burden checks (Section 17 BFSG)
navable combines both methodologies: use the high-speed automated engine for bulk validation, and log manual expert samples in the same platform for unified reporting.
Who owns which accessibility checks
Successful accessibility is a team effort. Every department contributes a critical part in practice.
Responsible for color palettes, contrast ratios, logical user flows, keyboard focus visual outlines, and screen reader design concept alternatives.
Responsible for meaningful image alt descriptions, semantic heading structures, accessible PDF document downloads, and plain language text.
Responsible for semantic HTML tags, WAI-ARIA roles, full keyboard support, focus trap preventions, and automated CI/CD pipeline checks.
Responsible for the BFSG/WCAG accessibility statement, continuous compliance monitoring, release signing, and team alignment.
How navable bridges the gap in website testing
navable was engineered from the ground up to eliminate scanner blind spots and streamline professional auditing workflows.
Auditing behind cookie banners and logins
Easily declare auth credentials and banner states in navable to check protected dashboards automatically.
Testing dynamic interface states
We don't just scan raw markup – we interact with dropdowns, dialogs, and slideouts to uncover barrier transitions.
Desktop vs. Mobile comparisons
navable checks your layouts across various screen widths to identify mobile touch targets or viewport scaling bugs.
Unified compliance database
Consolidate both your automated scanning files and manual test records inside a single cloud dashboard.
Developer & AI integrations
Export detected issues directly as structured dev tickets or fix-prompts to accelerate resolution cycles.
Frequently Asked Questions about Website Testing
Standards and Official References
Use these official resources and guidelines to deepen your compliance knowledge.