Structural Accessibility
Accessibility is not a layer added to a finished design. It is the outcome of getting the structure right in the first place.
Accessibility is not a layer added to a finished design. It is the outcome of getting the structure right in the first place.
What it is
Structural accessibility is the design of layout and content organisation so that it communicates clearly to all users: those navigating by keyboard, those using screen readers, those with cognitive differences that make dense or unpredictable layouts difficult to process. It is not primarily about ARIA attributes or alt text — those describe a structure. The structure itself must be sound. Semantic HTML, logical reading order, clear heading hierarchy, and predictable navigation are structural decisions, not technical patches.
What it does
A structurally accessible layout makes explicit what a visual layout communicates implicitly. A sighted user understands that a large heading is more important than the text below it — a screen reader user needs that hierarchy expressed in heading levels. A sighted user understands that a group of links forms a navigation menu — a screen reader user needs a nav landmark to know this. A user with a cognitive difference needs consistent navigation and clear visual hierarchy not as accommodations, but as baseline good design. Structural accessibility is good structure, described correctly.
What changes
When accessibility is designed in from the beginning rather than audited at the end, the result is a layout that works better for every user. Logical reading order benefits keyboard users and users who skim. Clear heading hierarchy benefits anyone who does not read linearly. Accessible form labels and error messages benefit anyone filling out a form in a hurry, on a phone, in difficult conditions. The users who need structure most are also the users who reveal most clearly when structure is absent.
The mistake
Treating accessibility as a compliance checklist applied after design is complete. Adding ARIA roles to a structurally broken layout does not fix the layout — it describes the broken structure more precisely. A screen reader experience built on poor visual hierarchy and inconsistent navigation will remain poor regardless of how many ARIA attributes are added. Accessibility must be structural, not cosmetic.
The takeaway
Before any visual design work begins, resolve: one h1 per page with logical heading nesting below it; landmark regions (header, main, nav, footer); reading order that matches the intended content sequence; all interactive elements reachable and operable without a mouse; keyboard focus always visible. These are structural decisions that cost nothing to make correctly at the start, and significant time and effort to retrofit at the end. See Responsive Structure for the parallel considerations across screen sizes.