ACCESIBILIDAD ≠ OVERLAY · 24
Accessibility ≠ Overlay: personalisation without real accessibility
📅 October 2026 · ⏱ 7 min read
Controls for colours, fonts and spacing may help some people. But do they make an inaccessible website accessible?
Personalisation is not remediation
An overlay may provide contrast, text size or spacing controls. These are presentation options, not automatic fixes for the underlying content, structure or behaviour of a website.
Four barriers that remain
An unnamed button is still confusing to screen-reader users. An unlabelled form remains difficult to complete. A dialog that traps focus still blocks keyboard navigation. An informative image without alternative text remains unexplained.
When an extra layer creates barriers
Some settings may conflict with browser preferences or assistive technology. Changes in size or colour may also cause overlapping content or unusable controls if the layout is not resilient.
Personalisation can be valuable
The point is not to reject personalisation. WAI-Adapt recognises the benefits of tailoring content to individual needs. The problem arises when such features are presented as a complete accessibility solution.
What an accessible website needs
Semantic HTML, properly labelled controls, keyboard support, sensible focus management, text alternatives, adaptable layouts and testing of real tasks with assistive technology.
A practical test
Try completing a form or purchase using only a keyboard, then with a screen reader. Check whether errors and confirmations are communicated. Changing text colour cannot repair a broken workflow.
Conclusion
Real accessibility begins with design, content and code. Personalisation controls may complement an accessible experience; they cannot replace removing barriers.
♿ Accessibility is built into the website, not added with a single button.
Adapta tu Web · Accessibility ≠ Overlay · 24