Skip to content
BENIBIX Learn

Semantic HTML vs ARIA Attributes

People think ARIA is the way to make a page accessible, and it is not the first step. Semantic HTML comes first: a real button or nav already tells a screen reader what it is. ARIA fills the gaps that no HTML element covers.

Development🌐 Web Development

Semantic HTML

Pick the HTML tag that says what each part is, like nav, main or button.

Semantic HTML means picking the element that says what a part is. Use nav for the menu, main for the main content and footer for the bottom. Use button for a button, not a box made to look like one. The page can look the same either way. But screen readers, search engines and other developers can now tell the parts apart.

Example
Emma swaps her plain div boxes for header, nav, main and footer. A screen reader can now jump straight to her menu.
Why it matters
It makes a site usable with a screen reader and a keyboard. It also helps search engines read the page.
Full entry
Design♿ Accessibility

ARIA Attributes

Extra labels in the code. They tell screen readers what a part is and does.

ARIA is a set of extra HTML labels that tell helper tools what a part is and what state it is in. It adds roles, like dialog or tab, and states, like open or checked. It only changes what a screen reader says, not how a part looks or acts. The first rule of ARIA is to use a real HTML element when one exists. Wrong ARIA is worse than none.

Example
A home-made menu button gets one ARIA label. Now a screen reader says Menu, shut. After a press, it says open.
Why it matters
Custom widgets are silent to screen readers without it. With it, they can be described.
Full entry

In one line

Semantic HTML
Pick the HTML tag that says what each part is, like nav, main or button.
ARIA Attributes
Extra labels in the code. They tell screen readers what a part is and does.

These live in different corners of the glossary (Development and Design), which is exactly why they get confused.