What is ARIA?

ARIA (Accessible Rich Internet Applications) is a set of HTML attributes that add roles, states and labels so assistive technology can understand custom interface components.

Does your site get ARIA right?

I’ll run a quick accessibility pass and send the issues most likely to block real visitors, free.

No newsletter. Just what you asked for, from me. Privacy

In plain English

ARIA is a W3C specification. Attributes like aria-expanded, aria-label and role="dialog" tell a screen reader what a component is and what state it’s in, which matters for menus, tabs and pop-ups that plain HTML doesn’t describe on its own.

ARIA changes what’s announced, not how anything behaves. Adding a role doesn’t make an element keyboard-friendly. The first rule of ARIA, from the W3C itself, is to use a native HTML element instead whenever one exists.

Why it matters for a small business

Used sparingly, it fills real gaps. Used carelessly, it makes things worse: WebAIM’s yearly survey of a million homepages has repeatedly found more detected errors on pages that use ARIA. Most small business sites need very little of it if the HTML underneath is sound.

An example

A Calgary brewery’s mobile menu is opened by a styled div that responds only to a tap. Screen readers announce nothing useful and keyboards can’t reach it. Replacing it with a real button that has aria-expanded and aria-controls set correctly makes it announce as a menu button and report whether it’s open. (More for breweries.)

Common mistakes

Where I see ARIA go wrong most often.

  1. Adding role="button" to a div without adding the keyboard handling a real button gets for free.

  2. Giving a control an aria-label that contradicts its visible text, which confuses voice control users.

  3. Setting aria-hidden="true" on elements that can still receive keyboard focus.

FAQ

ARIA, answered

  1. Only where native HTML can’t describe a component, like a custom tab panel or a menu toggle’s open state. Most content needs none.

  2. No. It’s a labelling tool. Accessibility depends on structure, keyboard support, contrast and clear content, with ARIA filling the occasional gap.

Keep reading

Let’s begin

Let’s build something you’re proud to share.

Let’s Talk