Toegankelijkheid ≠ Overlay: semantische HTML, de basis die een overlay niet kan vervangen
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.
Semantiek vertelt wat elk element is
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.
Koppen en regio’s zijn navigatie
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.
Een knop hoort een knop te zijn
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.
Formulieren hebben echte relaties nodig
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 vult aan; het vervangt correcte HTML niet
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.
Wat een overlay aantreft als het te laat komt
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.
En Blind Reader?
Blind Reader is ondersteunende technologie die de gebruiker helpt. Het kan toegang of interactie vergemakkelijken, maar de website heeft nog steeds begrijpelijke structuur nodig. Blind Reader helpt de gebruiker; het vervangt semantische HTML niet en certificeert de site niet.
Eerst goed bouwen, daarna lagen toevoegen
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