Loading content
Accessibility testing is a systematic practice to identify and remediate barriers in digital products. It combines automated checks, manual inspections and user tests with people with disabilities to ensure WCAG conformance. It is applied across the development lifecycle.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Accessibility testing examines whether people with different abilities can perceive, understand, and operate a digital product. It combines technical evaluation criteria with manual interaction and the use of assistive technologies.
The approach evolved with the W3C and its Web Accessibility Initiative standardizing web accessibility. Testable WCAG success criteria created a shared foundation; since 2005, the resulting WCAG Evaluation Methodology has structured systematic conformance evaluation of websites.
A reliable evaluation works like a funnel: first define the goal, scope, and conformance level. The team then explores key pages, functions, and technologies, selects a representative sample, and evaluates it against WCAG criteria. Automated tools find repeatable technical patterns, manual tests examine keyboard use, focus, semantics, and interaction, and the experiences of people with disabilities reveal actual usability. The findings and the sample's limits are documented at the end.
The goal, product area, conformance level, and included technologies determine what is evaluated.
WCAG criteria provide traceable requirements and shared evaluation benchmarks.
Selected views and workflows should adequately represent the product's variety.
Tools identify certain patterns quickly; human evaluation assesses context, operability, and meaning.
People with disabilities reveal barriers and experiences that formal checks alone cannot capture.
Accessibility testing matters before releases, procurement, or redesign and for ongoing monitoring. Early evaluation reduces exclusion and rework. No tool can confirm conformance or actual usability on its own; knowledgeable manual evaluation and, where possible, involvement of real users are required.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.