Accessibility ≠ Overlay: respecting user preferences
A person may already have configured their computer, browser, or assistive technology to use a particular text size, reduce motion, use specific colors, or navigate in a particular way. An accessible website should work with those preferences. Adding a layer that decides what an “accessible experience” should look like for the user is a very different approach.
Accessibility is not about choosing for the user
Two people with the same disability do not necessarily have the same needs, and one person may use different settings depending on device, context, or task. W3C explains that people adjust content presentation to make it easier to distinguish and understand. A website should not guess which configuration someone needs; it should be ready to respect and support their choices.
Preferences may exist before the user reaches our website
People do not start from zero on every site. They may have configured browser settings, zoom, their operating system, an extension, or assistive technology. W3C’s UAAG overview notes that some accessibility needs, including text customization and preferences, are better met in the user agent. The useful question is not “what controls can I add?” but “can my site adapt to preferences the user has already chosen?”
Personalization is not the same as repair
A text-size button or contrast selector can be useful. The problem starts when these features are presented as substitutes for an accessible implementation. WCAG 2.2 criterion 1.4.12 does not require a spacing button; it requires that content and functionality are not lost when users override specified text-spacing values. The interface must support user customization.
An “increase text” button does not replace an adaptable website
A site can offer a text-size control and still break when the user uses browser zoom or changes text settings. W3C says content should be designed and coded so it can adapt to changes in size, spacing, font, and color without losing information or functionality. An extra control can be convenient; adaptability is fundamental.
Reducing animation should not depend only on a widget
Some people need to avoid motion that can cause distraction, dizziness, or nausea. Operating systems can expose a reduced-motion preference and websites can respect it through mechanisms such as prefers-reduced-motion. WCAG documentation cites this technique for preventing non-essential motion. The user expresses a preference and the website respects it.
One user may need the exact opposite of another
One person may need very large text; another may need less visible information; another may change colors or avoid motion. WAI-Adapt is explicitly about enabling people to personalize presentation to meet individual needs and preferences. There is no single “disability mode” that represents everyone.
A good website leaves room for the user's tools
The browser, operating system, and assistive technologies are part of the user’s environment. The website should interoperate with them: do not block zoom, allow reflow, support text size and spacing changes, avoid components that break with different fonts, and respect preferences such as reduced motion. W3C recommends correctly designed and coded content that adapts to customization settings.
Offering additional options is not the problem
A website can provide additional presentation controls and they may be useful. The difference is who remains in control and what foundation the personalization is built on. An option can complement an accessible site; it should not justify an original interface that ignores the user’s existing preferences, tools, or settings.
Designing for preferences means designing for diversity
Accessibility is not about creating a special interface for an imaginary disabled user. It is about enabling different people to use the same product through different ways of perceiving, navigating, and interacting. A robust solution does not decide what an “accessible version” should look like for everyone; it creates an interface that can adapt.
Accessibility ≠ Overlay
An overlay may offer larger text, contrast changes, highlighted links, or stopped animations. Some features can be useful, but their presence does not prove that the website respects user preferences or is accessible. An adaptable website should allow choices made in the browser, operating system, or assistive technology to keep working. The goal is not to provide our accessible mode, but to respect how each person uses the Internet.
Official sources
W3C Web Accessibility Initiative (WAI)
Presentation — How People with Disabilities Use the Web
Understanding WCAG 2.2 — Text Spacing (1.4.12)
User Agent Accessibility Guidelines (UAAG) Overview
Understanding WCAG — Animation from Interactions
This article is part of the “Accessibility ≠ Overlay” series. Delivery 07 — Overlays and user preferences.