Accessibilité ≠ Overlay : HTML sémantique, la base qu’un overlay ne peut pas remplacer
A site can look perfectly organised and still be confusing to someone using a screen reader, keyboard or other assistive technology. The reason may be invisible: HTML. Elements such as <main>, <nav>, <button>, <label> and headings carry meaning, not just appearance.
La sémantique indique ce qu’est chaque élément
Two pieces of text can look identical but mean different things to the browser. An <h2> identifies a section; a CSS-enlarged <p> remains a paragraph. W3C explains that well-marked structure supports navigation and orientation.
Titres et régions servent à la navigation
Headings communicate content organisation. Elements such as <header>, <nav>, <main>, <aside> and <footer> identify regions that screen readers and other tools can use for efficient navigation.
Un bouton doit être un bouton
A native <button> already provides known semantics and behaviour. Recreating one with a <div> means rebuilding semantics, focus and keyboard behaviour. The first rule of ARIA recommends native HTML when an appropriate element exists.
Les formulaires ont besoin de vraies relations
Visually placing “Email” beside a field is not enough. W3C recommends associating labels with controls, normally with <label>, so assistive technologies can identify the field purpose.
ARIA complète ; il ne remplace pas un HTML correct
ARIA is essential when native HTML cannot provide required semantics, especially in complex interfaces. It is not intended to replace correct HTML unnecessarily, and incorrect ARIA can alter the semantics exposed to assistive technology.
Ce qu’un overlay trouve lorsqu’il arrive trop tard
A layer running after page load acts on a structure that already exists. If the base contains incorrect elements, missing relationships or poorly built custom components, the problem began before the overlay. Building correctly at source and testing with assistive technology is more robust.
Et Blind Reader ?
Blind Reader est une technologie d’assistance destinée à aider l’utilisateur. Elle peut faciliter l’accès ou l’interaction, mais le site doit toujours offrir une structure compréhensible. Blind Reader aide l’utilisateur ; il ne remplace pas le HTML sémantique et ne certifie pas le site.
Bien construire avant d’ajouter des couches
Semantics are not an invisible technical detail; they are part of the user experience. Before adding a layer that interprets or transforms the page, use the right element for each function. Accessibility starts in the code.
Fuentes / Sources
W3C WAI — Page Structure Tutorial
Accesibilidad ≠ Overlay · 11