Accessibility is crucial for creating inclusive digital experiences. It encompasses techniques and standards to facilitate interaction for individuals with varying abilities, ensuring all users can access the content.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Accessibility is the design of digital content and products so that as many people as possible can use them independently, including people with disabilities and users of assistive technologies.
In digital products, accessibility grew from the practical problem that many websites, apps, and documents could be used directly only by part of their audience. The W3C and its Web Accessibility Initiative made the web-specific expectation concrete through the WCAG: content should be perceivable, operable, understandable, and robust. That turned a broad inclusion goal into a testable design and quality frame.
Think of accessibility as three stacked layers: information must be perceivable and readable, interaction must work without special detours, and the underlying technology must be interpreted reliably by browsers and assistive tools. If one layer is missing, the product may be visible to many people but not truly usable.
Screen readers, magnification, voice control, or switch devices translate content and input into usable forms.
Testable requirements make clear what a website or app must provide for accessible use.
Core functions must be reachable without a mouse; focus order and visible focus are essential.
Headings, labels, and roles give people and tools orientation within the content.
Accessibility is considered early so that special workarounds, rework, and exclusion become less common.
Accessibility matters in product development, redesign, procurement, and quality review. Early decisions about structure, contrast, alternatives, and keyboard control avoid expensive rework. Automated checks find only part of the problem; real usability also depends on context, content, and manual evaluation.
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.