ARIA Role Lookup

You opened a pull request and ran into role="feed" or role="status" with no clear idea of what it promises to someone using a screen reader. Or you are deciding between role="dialog" and role="alertdialog" and the WAI-ARIA spec is far too long for the moment you are in. Type the role name and the page gives you one line describing its purpose. The table holds 69 roles.

What you get is the purpose, not the full contract. Every role carries required attributes and an expected child structure: a checkbox without aria-checked communicates no state at all; a tab has to live inside a tablist and point at its tabpanel; a slider wants aria-valuenow, aria-valuemin and aria-valuemax. None of that shows up in the answer, so treat the result as a starting point and check the spec before shipping.

The first rule of ARIA is not to use ARIA. A button element already has role button, nav is already navigation, and native elements bring focus and keyboard behavior for free. ARIA only changes what assistive technology announces, never how the element behaves. A few ARIA 1.2 roles such as code, generic, paragraph, meter and time are missing from this table and come back as unrecognized, which does not make them invalid. The lookup runs locally, with no network request.