{"canonical_url":"https://engineer.company/glossary/aria/","content_markdown":"# ARIA\n\n## What it is\n\nARIA is a W3C specification of HTML attributes that tells assistive technology what a page element\nis, what it is called and what state it is in, where the HTML alone says too little. The letters\nstand for Accessible Rich Internet Applications, and the specification's full title, WAI-ARIA, adds\nthe W3C's Web Accessibility Initiative. The current Recommendation is version 1.2.\n\nA `role` attribute says what kind of thing an element is: a widget such as `button` or `tab`, a\nstructural part such as `list`, one of the eight landmark roles such as `navigation` or `main`, or a\nlive region such as `status`, whose changes a screen reader announces unasked. The `aria-*`\nattributes then split into properties, like `aria-labelledby`, and states, like `aria-expanded`,\nwhich change as the user acts. The browser maps all of it into the operating system's accessibility\nAPI, which is what a screen reader or a voice-control program reads.\n\nARIA changes what is announced and nothing else. A `div` with `role=\"button\"` is read out as a\nbutton, yet it takes no focus and ignores Enter and Space until a `tabindex` and a script supply\nboth. Hence what the W3C's guide Using ARIA calls the first rule of ARIA use: when a native HTML\nelement or attribute already has the semantics and behaviour you need, use it instead of repurposing\nanother element and adding ARIA.\n\n```html\n\u003c!-- announced as a button, behaves like a div --\u003e\n\u003cdiv role=\"button\"\u003eSend\u003c/div\u003e\n\n\u003c!-- announced, focusable and operable as a button --\u003e\n\u003cbutton type=\"button\"\u003eSend\u003c/button\u003e\n```\n\nThe other half is the accessible name, the words a screen reader speaks for a control. The\nAccessible Name and Description Computation 1.2 fixes the order: `aria-labelledby` first, then\n`aria-label`, then the native label (a `label` element, an `alt`, an SVG `title`), then the\nelement's text content for roles that take their name from it, and the `title` attribute last. So an\n`aria-label` replaces the visible words of a button rather than adding to them.\n\n## Why it matters\n\nThe decision ARIA puts in front of a team is build or reuse. WCAG 2.2 success criterion 4.1.2, Name,\nRole, Value, asks that every user interface component expose its name and role to software, let its\nuser-settable states and values be set programmatically, and report when they change. A native\n`button`, `select` or `details` meets that by default. A custom tab strip, combobox or tree view\nmeets it only through ARIA and the script that keeps the ARIA true.\n\nThat makes a custom widget a recurring cost: keyboard handling, focus management, states that track\nevery interaction and testing in more than one screen reader, at every redesign. Judge a component\nlibrary by which pattern from the W3C's ARIA Authoring Practices Guide each widget follows, and by\nwhether that pattern's keyboard behaviour is there when the mouse is put away.\n\nThe legal pressure now reaches private companies. The Web Accessibility Directive, (EU) 2016/2102,\ncovers public-sector sites and apps. The European Accessibility Act, Directive (EU) 2019/882,\napplies from 28 June 2025 to a range of consumer products and services, e-commerce and consumer\nbanking among them, with microenterprises that provide services exempt. Both lean on the harmonised\nstandard EN 301 549, whose web requirements are WCAG at Level AA. Name, Role, Value sits at Level A,\nso a control whose name or role stays hidden from a screen reader fails the lowest level an auditor\nchecks.\n\n## What it looks like in practice\n\nThis site's templates use ARIA sparingly. The top bar on every inner page is a `div` with\n`role=\"banner\"`, not the usual `header` element. The template's comment explains why: the stylesheet\nstyles a bare `header` as the home page's full-height hero, so the element would drag that geometry\nonto every inner page, while the role gives the landmark and nothing else. The role is what puts the\nbrand mark, the link home, inside a landmark. That is the narrow case the first rule allows. The\nsite menu goes the other way: a `details` and `summary` pair, which leaves the open state, the\nbutton semantics and `aria-expanded` to the browser. The menu's `nav` and the footer's `nav` carry\ndifferent `aria-label` values, since two navigation landmarks with one name break the rule engine's\nuniqueness rule and the site's accessibility check gates on zero findings. The retained portfolio-filter\nimplementation uses a `role=\"status\"` region designed to stay silent until the reader types.\nThat filter is currently disabled with `searchEnabled = false`; it illustrates the retained\nimplementation, not an interaction available on the published pages.\n\nThe record of\n[taking the site to WCAG 2.2 Level AA](/portfolio/a-site-that-meets-the-accessibility-standard/)\nsupplies the other half of the banner story: when the rule engine's best-practice rules were\nswitched on, one of them failed at once, because on every inner page the brand mark belonged to no\nlandmark at all. The same page lists the absence of testing with real assistive technology among the\nlimits it publishes.\n\nThe write-up of\n[eleven defects the browser called healthy](/portfolio/the-accessibility-faults-your-checker-misses/)\nshows how far markup is from the experience. All eleven lived in how the page rendered, not in what\nits markup declared, and markup is all ARIA touches. Eight footer links stayed reachable with Tab\nafter a style had switched off pointer interaction with them and changed nothing else: the same\nshape as `aria-hidden` on a focusable element, where the screen reader loses the element and the\nkeyboard keeps it. And only seventy of the engine's hundred and five rules were switched on, with\nthe one that flags a missing landmark among those left off.\n\nThe last page shows the same problem on a platform where ARIA plays no part.\n[Naming all seventeen interface icons for screen readers](/portfolio/named-all-17-icons-for-screen-readers/)\ndescribes a SwiftUI application: no HTML and no `aria-` attribute anywhere. Its accessibility label\nis SwiftUI's own, the native counterpart of `aria-label` and not an instance of it. Controls drawn\nwith system symbols were read out by the symbol's internal name, so the send button announced as\n“arrow up circle, button”, and seventeen icon-only controls described their artwork instead of their\nfunction. Each got a label naming the action and tracking its state where that matters, and a linter\nnow requires a label within eight lines of the construction that creates an icon-only control, so an\neighteenth control gets in only with a label. The page states the limit, and it holds for\n`aria-label` too: the check confirms that some label sits close by, while whether it is the right\none is something only a person listening can judge.\n\n## Where it goes wrong\n\n**A role announces a widget the keyboard never reaches.** A `div` gets `role=\"button\"` and a click\nhandler. The screen reader says “button”, yet Tab passes over it and Enter does nothing. The third\nrule of ARIA use asks that every interactive ARIA control work from the keyboard. Use the native\nelement, or build the whole keyboard model of the APG pattern and test with the mouse unplugged.\n\n**Focus lands on something the screen reader treats as absent.** `aria-hidden=\"true\"` sits on a\nfocusable element or its ancestor, such as an off-screen drawer. Tab still moves there, and the user\nhears silence. The fourth rule of ARIA use rules this out. Remove hidden content from the tab order\ntoo, with `hidden`, `display: none` or `inert`, and keep `aria-hidden` for decoration that never\ntakes focus.\n\n**A name goes where the element accepts none.** `aria-label` on a `div`, `span` or `p` is meant to\nexplain it, but WAI-ARIA 1.2 prohibits naming the `generic` and `paragraph` roles, and screen\nreaders ignore it or read it inconsistently. On a control the label replaces the visible words, and\nwhen the two differ, a voice-control user who says what is on screen misses. Name elements that can\ncarry a name, and start any `aria-label` with the visible words, as WCAG 2.5.3, Label in Name, asks.\n\n**Two roles contradict each other.** An explicit role replaces the element's own. A link given\n`role=\"button\"` announces as a button but scrolls the page on Space; `role=\"tab\"` on an `h2` drops\nit from the heading list; `role=\"navigation\"` on a `ul` loses the list and its item count. The\nsecond rule of ARIA use is to change native semantics only when you must, and ARIA in HTML lists\nwhich roles each element may take.\n\n**A live region chatters.** `aria-live=\"assertive\"` or `role=\"alert\"` sits on a result count or a\ncountdown that changes every keystroke or second, and the screen reader interrupts the user for each\nvalue. Use polite updates, which `role=\"status\"` gives by definition, announce once input settles,\nand keep the region quiet at load.\n\n## Further reading\n\n- [WAI-ARIA 1.2](https://www.w3.org/TR/wai-aria-1.2/) — every role, state and property, which\n  attributes each role supports, and which roles may not be named.\n- [ARIA in HTML](https://www.w3.org/TR/html-aria/) — the roles and attributes each HTML element may\n  carry, and which of them are redundant.\n- [Using ARIA](https://www.w3.org/TR/using-aria/) — the W3C's practical guide, with the rules of\n  ARIA use and an example of each.\n- [Accessible Name and Description Computation 1.2](https://www.w3.org/TR/accname-1.2/) — the\n  algorithm that decides what a screen reader says a control is called.\n- [Understanding Name, Role, Value](https://www.w3.org/WAI/WCAG22/Understanding/name-role-value.html)\n  — what WCAG 2.2 success criterion 4.1.2 asks of every component, with techniques and failures.\n- [ARIA Authoring Practices Guide](https://www.w3.org/WAI/ARIA/apg/) — the markup and keyboard\n  behaviour for each common widget pattern, with working examples.\n\n\u003chttps://engineer.company/glossary/aria/\u003e\n","date_modified":"2026-11-08T02:22:23Z","description":"How ARIA roles, states and names reach a screen reader, when native HTML does the job better, what WCAG 2.2 and EU law expect, and five ways it misfires.","formats":{"gemtext":"https://engineer.company/glossary/aria/index.gmi","gopher":"https://engineer.company/glossary/aria/gophermap","html":"https://engineer.company/glossary/aria/","json":"https://engineer.company/glossary/aria/index.json","markdown":"https://engineer.company/glossary/aria/index.md","pdf":"https://engineer.company/glossary/aria/index.pdf"},"kind":"page","language":"en","title":"What is ARIA?","url":"https://engineer.company/glossary/aria/","version":1}