{"id":1605,"date":"2026-06-08T19:07:26","date_gmt":"2026-06-08T18:07:26","guid":{"rendered":"https:\/\/thomas-sokolowski.com\/en\/?p=1605"},"modified":"2026-06-08T20:31:49","modified_gmt":"2026-06-08T19:31:49","slug":"the-three-layers-of-accessibility","status":"publish","type":"post","link":"https:\/\/thomas-sokolowski.com\/en\/the-three-layers-of-accessibility\/","title":{"rendered":"The Three Layers of Accessibility"},"content":{"rendered":"<section class=\"wpb-content-wrapper\"><p>[vc_row][vc_column][vc_column_text]<\/p>\n<h5>Many designers experience accessibility as a form of creative restriction.<\/h5>\n<p>They want to create digital products that are accessible to as many people as possible and can be used reliably by people with disabilities. At the same time, they often feel that meeting accessibility requirements makes their solutions more similar, less expressive, and less distinctive. They perceive accessibility requirements as a very tight straitjacket that leaves little room for creative freedom.<\/p>\n<p>When numerous technical, visual, and perceptual requirements must be met, it seems almost impossible to deviate from established patterns.<\/p>\n<h5>This criticism is not entirely unfounded. It raises a number of important questions:<\/h5>\n<ul>\n<li><strong>Is meeting accessibility standards enough for good inclusive design?<\/strong><\/li>\n<li><strong>Is compliance with these standards the only quality criterion in accessible design?<\/strong><\/li>\n<li><strong>If not, where is the space for originality, emotion, visual metaphor, ambiguity, or a deliberate break with established conventions?<\/strong><\/li>\n<\/ul>\n<p>Good design thrives on differentiation, visual metaphors, associative relationships, and sometimes even on ambiguity, surprise, or a deliberate break with established conventions.<\/p>\n<p>These questions are the starting point for the following reflections.<\/p>\n<p>&nbsp;<\/p>\n<h3>A familiar tension: Novice Support vs. Expert Efficiency<\/h3>\n<p>We encounter similar issues outside the realm of inclusive design as well\u2014many software applications must cater to very different user groups: Beginners need guidance, explanations, help texts, elements that are as intuitive and consistent with their expectations as possible, and reduced complexity. Experienced users, on the other hand, want direct access, keyboard shortcuts, powerful functions, as little redundancy as possible, and no unnecessary assistance.<\/p>\n<p>What supports some users can get in the way of others. What gives some users confidence can feel slow, restrictive, or unnecessarily cumbersome to others.<\/p>\n<p>This tension can be described as a conflict between overwhelming beginners and slowing down experts. A user interface that is too complex overwhelms inexperienced users. An interface that is too heavily geared toward inexperienced users reduces their efficiency.<\/p>\n<p>&nbsp;<\/p>\n<h2>Below is an overview of typical areas of tension in interface design<\/h2>\n<table class=\"simple_table\">\n<tr>\n<td>Conformity vs. Actual Usability<\/td>\n<td>An interface can be WCAG-compliant yet still be cumbersome, confusing, or inefficient for certain people.<\/td>\n<\/tr>\n<tr>\n<td>Visible Guidance vs. Uninterrupted Use<\/td>\n<td>Tooltips and detailed explanatory text help beginners but disrupt experienced users.<\/td>\n<\/tr>\n<tr>\n<td>Simplicity vs. Precision<\/td>\n<td>Simplification can increase comprehensibility, but it can also lead to the loss of relevant content or meaning.<\/td>\n<\/tr>\n<tr>\n<td>\u00abOne size fits all\u00bb vs. Situational Needs (or Standardization vs. Individualization)<\/td>\n<td>\u00abThe same solution for everyone\u00bb does not truly address individual needs. Universal Design should allow for flexibility and different ways of use.<\/td>\n<\/tr>\n<tr>\n<td>Error Prevention vs. Efficiency<\/td>\n<td>Confirmation dialogs, warnings, and protective mechanisms help inexperienced users but can unnecessarily slow down experienced users.<\/td>\n<\/tr>\n<tr>\n<td>Cognitive Relief vs. Completeness<\/td>\n<td>What reduces cognitive load for some users may feel oversimplified, inefficient, or incomplete to others.<\/td>\n<\/tr>\n<\/table>\n<p>&nbsp;<\/p>\n<p>Modern UX design addresses this with concepts such as progressive disclosure, layered or adaptive interfaces \u2014 see the list at the end of this post.<\/p>\n<p>Features, help options, and complexity are not presented to everyone in the same way, but are made available gradually, contextually, or optionally. Beginners receive support. Advanced users can hide this support, skip it, or replace it with workflows that suit them.<\/p>\n<p><strong>These are precisely the principles we need in accessibility as well.<\/strong><\/p>\n<p>&nbsp;<\/p>\n<h2>Three Types of Accessibility Measures<\/h2>\n<p>Not all accessibility measures have the same effect. That is why it is helpful to categorize them into three groups.<\/p>\n<h3>1. Universal Baseline Measures<\/h3>\n<p>The first group includes measures that benefit nearly everyone and do not significantly disadvantage anyone. These include a clear structure, consistent navigation, easily recognizable interactive elements, meaningful labels, sufficient contrast, good readability, logical information architecture, and understandable feedback.<\/p>\n<p>These measures improve not only accessibility but also overall usability. They are not a special solution for people with disabilities, but rather an expression of professional interface quality.<\/p>\n<h3>2. Invisible or Non-Disruptive Assistive Measures<\/h3>\n<p>The second group comprises measures that significantly help certain people but are barely noticeable to others. These include semantically correct HTML, keyboard accessibility, clean focus handling, screen reader-compatible labels, correctly marked error messages, or technical compatibility with assistive technologies.<\/p>\n<p>A user who works with a mouse and screen barely notices these measures. For a person navigating with a screen reader or keyboard, however, they can be crucial. These measures should therefore be standard practice. They do not interfere with others, but they can substantially improve accessibility.<\/p>\n<h3>3. Preference-Based Support Measures<\/h3>\n<p>The third group is the most challenging. It includes measures that are very helpful for some people but may be disruptive, restrictive, or inefficient for others.<\/p>\n<p>These include, for example: Easy Language, very large font sizes, high-contrast mode, reduced animations, highly simplified user interfaces, detailed help texts, icon support, read-aloud functions, or alternative forms of navigation.<\/p>\n<p>These measures are important. However, they should not automatically replace the standard presentation. A version in Easy Language can be an enormous help for people with cognitive disabilities, lower literacy, or limited language proficiency. For others, however, the same simplification may reduce precision, nuance, or usefulness \u2014 especially in legal, medical, scientific, or technical contexts.<\/p>\n<p>Technical terms, metaphors, linguistic nuance, and complex arguments are not inherently barriers. In certain contexts, they are necessary.<\/p>\n<p>This is particularly true for legal, medical, scientific, or technical content. In these areas, language often needs to maintain a high degree of precision. If it is oversimplified, it can lose accuracy.<\/p>\n<p>&nbsp;<\/p>\n<h2>The three layers of accessibility<\/h2>\n<table class=\"simple_table\">\n<tr>\n<th><\/th>\n<th>Layer<\/th>\n<th>Effectiveness<\/th>\n<th>Examples<\/th>\n<\/tr>\n<tr>\n<td>1<\/td>\n<td><strong>Universal Baseline Measures<\/strong><\/td>\n<td>Benefit everyone and do not disadvantage others.<\/td>\n<td>Good readability, logical structure, sufficient contrast, clear user guidance, consistency<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td><strong>Invisible or Non-Disruptive Assistive Measures<\/strong><\/td>\n<td>Help some users while remaining invisible to everyone else.<\/td>\n<td>Semantic HTML, keyboard accessibility, screen reader support<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td><strong>Preference-Based Support Measures<\/strong><\/td>\n<td>Significantly benefit certain people, but may distract, slow down, or underchallenge others.<\/td>\n<td>Easy Language, very large font-sizes, high-contrast mode, disabled animations, highly simplified UI, detailed and prominent help prompts<\/td>\n<\/tr>\n<\/table>\n<p>&nbsp;<\/p>\n<h2>Accessibility needs standards. Inclusion needs adaptability<\/h2>\n<p>This is also why a website that conforms to the Web Content Accessibility Guidelines is not automatically a truly inclusive website. WCAG is strongest at the first two layers of this model: universal baseline measures and invisible or non-disruptive assistive measures. These are areas where accessibility can often be translated into relatively objective, testable criteria: contrast ratios, keyboard accessibility, visible focus, semantic structure, labels, error identification, or compatibility with assistive technologies.<\/p>\n<p>The third layer is more complex. It includes measures whose usefulness depends heavily on the audience, context, task, prior knowledge, cognitive load, and personal preference. WCAG has included understandability as one of its core principles since version 2.0. However, understandability cannot be measured in the same way as a contrast ratio or keyboard operability.<\/p>\n<p>For whom is a text understandable? In which situation? With what level of prior knowledge? For which task?<\/p>\n<p>A legally precise contract, a medical report, a scientific analysis, or technical documentation cannot be simplified without limits. At some point, simplification may improve access for some users while reducing precision, nuance, or usefulness for others. Conversely, the same linguistic complexity can be a substantial barrier for people with lower literacy, cognitive disabilities, limited language proficiency, or little domain knowledge.<\/p>\n<p>This is where accessibility can no longer be solved by universal minimum standards alone. It requires alternative representations, adaptive interfaces, user preferences, and context-sensitive support.<\/p>\n<p>&nbsp;<\/p>\n<h2>Accessibility Requires Self-Determination in Both Directions<\/h2>\n<p>Accessibility is often viewed as a moral obligation \u2014 and it is. A society that takes digital inclusion seriously must give special consideration to people with disabilities. But this does not automatically mean that everyone must use the same simplified or adapted interface.<\/p>\n<p>People with disabilities should be given the opportunity to use content and interfaces in the way they need: with higher contrast, reduced motion, easier-to-understand language, larger font, alternative input methods, or additional guidance.<\/p>\n<p>At the same time, people who do not need this support should not be unnecessarily slowed down, underchallenged, or restricted in their ability to absorb information.<\/p>\n<p>This is neither discrimination nor segregation, as long as the alternative modes are designed to be equivalent, respectful, and non-stigmatizing. On the contrary: it is an expression of respect not to confine people to a single form of use.<\/p>\n<p>&nbsp;<\/p>\n<h3>From \u00abOne Size Fits All\u00bb to Adaptive Accessibility<\/h3>\n<p>Digital design has a major advantage over analog media: interfaces do not have to be static. They can adapt.<\/p>\n<p><strong>A good accessible product should therefore consist of several layers:<\/strong><\/p>\n<ol>\n<li>a robust, accessible foundation that applies to everyone<\/li>\n<li>technical layers that are as invisible as possible and reliably support assistive technologies<\/li>\n<li>individual customization options, alternative visual representations that appeal to different senses and usage patterns, and adaptive modes that account for different user needs<\/li>\n<\/ol>\n<ul><strong>These could include:<\/strong><\/p>\n<ul class=\"narrow-list\">\n<li>an Easy Language mode<\/li>\n<li>an expert mode<\/li>\n<li>a reduced (reading) mode<\/li>\n<li>a high-contrast theme<\/li>\n<li>adjustable font sizes<\/li>\n<li>the option to reduce motion or disable autoplaying media<\/li>\n<li>the ability to adjust the density of information<\/li>\n<li>the ability to turn icon-based navigation on or off<\/li>\n<li>displaying explanatory help or context-sensitive support<\/li>\n<li>the ability to use keyboard shortcuts<\/li>\n<\/ul>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>Conclusion<\/h2>\n<p>Inclusive design and creative freedom do not have to be mutually exclusive. Conflict arises primarily when accessible solutions are implemented as rigid \u201cone-size-fits-all\u201d approaches.<\/p>\n<p><strong>The challenge, therefore, is not:<\/strong> How do we design an interface that is as accessible as possible and works in exactly the same way for all users? <strong>Rather:<\/strong> Where do people need choices because their needs differ?<\/p>\n<p>Accessibility should therefore not be seen as a limitation, but as a basic requirement: a stable, inclusive foundation for everyone, supplemented by adaptive and customizable layers for different abilities, preferences, and usage contexts.<\/p>\n<p><strong>Not everyone needs the same interface. But everyone deserves an interface that meets their needs.<\/strong><\/p>\n<p>&nbsp;<\/p>\n<h2>Concepts for implementing an adaptable, inclusive design<\/h2>\n<h3>Progressive Disclosure<\/h3>\n<p>Complexity is revealed step by step. The primary interface shows only the essentials; advanced features remain accessible but do not dominate. This concept is particularly relevant for addressing the conflict between novice and expert usage.<\/p>\n<h3>Progressive Enhancement<\/h3>\n<p>The core experience is robust and accessible; additional visual, interactive, or performance-enhancing layers are added on top without compromising the basic functionality.<\/p>\n<h3>Universal Design<\/h3>\n<p>The classic universal design principles already incorporate the principle of accommodating different preferences and abilities. Particularly relevant are \u00abEquitable Use\u00bb, \u00abFlexibility in Use\u00bb and \u00abSimple and Intuitive Use\u00bb. Universal Design demonstrates that adaptable systems function better than segregated specialized solutions.<\/p>\n<h3>User Preference Media Features<\/h3>\n<p>Modern CSS\/browser mechanisms such as prefers-reduced-motion, prefers-contrast, prefers-color-scheme, forced-colors, or prefers-reduced-transparency allow for respecting users\u2019 operating system preferences. \u00abMedia Queries Level 5\u00bb documents these user preference features.<\/p>\n<h3>WAI-Adapt \/ Personalization Semantics<\/h3>\n<p>W3C is working on approaches that allow content, icons, help text, links, buttons, and keyboard shortcuts to be semantically marked up in such a way that user agents or extensions can adapt them to individual preferences.[\/vc_column_text][\/vc_column][\/vc_row]<\/p>\n<\/section>","protected":false},"excerpt":{"rendered":"<p>Why Inclusive Interfaces Should Not Be the Same for Every User<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[40,3],"tags":[],"class_list":["post-1605","post","type-post","status-publish","format-standard","hentry","category-accessibility","category-visual-design-2"],"_links":{"self":[{"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/posts\/1605","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/comments?post=1605"}],"version-history":[{"count":7,"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/posts\/1605\/revisions"}],"predecessor-version":[{"id":1617,"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/posts\/1605\/revisions\/1617"}],"wp:attachment":[{"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/media?parent=1605"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/categories?post=1605"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thomas-sokolowski.com\/en\/wp-json\/wp\/v2\/tags?post=1605"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}