The Web Content Accessibility Guidelines (WCAG) define principles and success criteria for making web content accessible. They help developers and organizations plan, assess, and implement accessible user interfaces. WCAG supports legal compliance, inclusive user experiences, and technical interoperability. It is widely adopted as an international standard.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Technical building block: can be automated, integrated, or operated.
What organizes, connects, or makes decisions possible.
The Web Content Accessibility Guidelines (WCAG) are guidelines for accessible web content.
WCAG was developed by the World Wide Web Consortium’s Web Accessibility Initiative (WAI). The first version appeared in 1999; later versions continued its internationally used principles and success criteria.
The four principles—perceivable, operable, understandable, and robust—structure requirements for content and interfaces.
The approach combines core building blocks and flows.
Its use depends on the concrete task.
WCAG supports design, development, and quality assurance in identifying barriers for different usage situations early.
WCAG provides testable requirements for systematically planning and assessing web content accessibility.
Where this building block is located in the topic model.
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.