Accessibility Testing
Automated checks, their ceiling, and the manual testing that has to sit above it.
4 to work through
-
intermediate Multiple choice
A public-sector organisation runs 40 services on a shared component library and must meet WCAG 2.2 AA. An automated scan in each service's pipeline reports no violations, and an external audit finds 60 issues, most of them keyboard traps and focus-order problems in shared components. Where should the verification effort be placed?
3 min answer -
intermediate
Review this setup at a ticketing platform in the mould of Ticketmaster. Every design-system component carries unit tests plus an automated accessibility check and all of them pass. The queue page announces "you are number 12000 in line" through a polite live region updated every two seconds. An external audit fails the checkout flow on focus order and on announcements. What would you change, and what would you leave alone?
3 min answer -
intermediate
What can be tested automatically for accessibility, what cannot, and what is the architectural dimension?
2 min answer -
intermediate
Your automated accessibility scan reports zero issues. Legal asks whether the product is compliant. What is your answer?
2 min answer
4 terms in this topic
Accessibility Testing
Verifying that an interface is usable by people with disabilities, through automated checks, assistive technology testing and structural review.
patternAccessible Component Contract
A published, tested statement of a shared component's keyboard model, roles, names and announced states, so that accessibility is verified once where…
metricAutomated Accessibility Coverage
The proportion of accessibility criteria a tool can decide mechanically — around a third — and the explicit acknowledgement that the rest needs people.
conceptComposition Accessibility Defect
An accessibility failure that exists only in the assembled page - focus order, landmark duplication, heading structure, announcement rate - and that …
Neighbouring topics
Testing & Quality Architecture
General material on designing a testing strategy as an architectural concern.
Test Architecture Strategy
Choosing what to verify where, given the failure modes that actually occur.
Test Pyramid Shapes
Pyramid, trophy and honeycomb, and the system properties that justify each shape.
Integration Test Boundaries
What sits inside a test's boundary, what is faked, and the confidence that follows.
Contract Testing at Scale
Keeping dozens of services compatible without an environment that runs all of them.
Consumer-Driven Contracts
Consumers declaring what they rely on, and providers verifying against those declarations.
Test Data Management
Realistic data without copying production personal data into a weaker environment.
Synthetic Data
Generating data with the shape and edge cases of the real thing, and where it misleads.
Environment Parity
The differences between staging and production that decide which bugs survive to release.
Service Virtualisation
Standing in for a dependency you cannot call, and keeping the stand-in honest.
End-to-End Test Economics
Why broad end-to-end suites get slow, flaky and abandoned, and what to keep.
Non-Functional Test Strategy
Testing availability, latency, security and recovery rather than only behaviour.
Performance Test Design
Workload models, warm-up, think time, and the distribution the average hides.
Chaos as a Test
Fault injection with a hypothesis, a blast radius and an abort condition.
Security Testing in the Pipeline
SAST, DAST, dependency and secret scanning, and what to do with the findings.
Mutation Testing
Measuring whether tests would actually notice a defect, not just cover a line.
Flaky Test Management
Quarantine, detection, and the trust a suite loses once red stops meaning broken.
Testing in Production
Synthetic transactions, dark launches and shadow traffic, done deliberately and safely.
Quality Gates
Thresholds that block a release, who may override them, and how they decay.