WAI-ARIA (Accessible Rich Internet Applications)

WAI-ARIA in one sentence: WAI-ARIA, short for Web Accessibility Initiative – Accessible Rich Internet Applications, is a W3C standard that defines HTML attributes developers use to tell assistive technologies such as screen readers what a custom interactive component is, what state it is in and how it changes. 

The golden rule is native HTML first: use a real HTML element whenever one exists, and add ARIA only when HTML cannot describe a component. Used well, ARIA helps a site meet WCAG; used badly, it makes components harder to use. 

What is WAI-ARIA? 

Modern websites are full of components HTML has no native element for: tabs, accordions, menus, sliders, live chat and search suggestions. WAI-ARIA, often shortened to ARIA, fills that gap so screen reader users get the same information sighted users see. 

W3C describes WAI-ARIA as a suite of web standards for Accessible Rich Internet Applications. The current version is WAI-ARIA 1.2, a W3C Recommendation since June 2023; version 1.3 is in draft. See the WAI-ARIA Overview on w3.org. 

ARIA changes only what assistive technology announces. It does not change how a component looks or behaves, so developers still need to add keyboard support themselves. 

What does WAI-ARIA define? 

  • Roles: what a component is, such as role="tablist", role="dialog" or role="progressbar", and page structure, such as regions and landmarks.
  • States: a component's current condition, such as aria-expanded="true" or aria-checked="false".
  • Properties: extra meaning or relationships, such as aria-label, aria-describedby or aria-controls.
  • Live regions: aria-live marks content that updates on its own, such as chat messages or form errors, so it is announced.
  • Keyboard interaction patterns: W3C's ARIA Authoring Practices Guide documents how each widget should respond to the keyboard.

How does WAI-ARIA work? 

Browsers turn HTML and ARIA attributes into an accessibility tree that screen readers and other assistive technologies read: 

Attribute type 
Example 
What a screen reader announces 

Role 

role="tab" 

"Tab" 

State 

aria-selected="true" 

"Selected" 

Property 

aria-label="Close dialog" 

"Close dialog, button" 

Relationship 

aria-controls="panel-2" 

Links the tab to the panel it opens 

Live region 

aria-live="polite" 

Reads new content when the user pauses 

Because ARIA overrides what the browser would announce, a wrong role or a state that is never updated gives users false information. 

What is the difference between WAI-ARIA and native HTML? 

Native HTML elements come with accessibility built in. A real <button> is focusable, works with Enter and Space and is announced as a button with no extra code. A <div> styled as a button needs role="button", tabindex="0" and custom keyboard scripting to match it. 

W3C's Using ARIA guidance sets five rules, in plain language: 

  1. Use native HTML elements and attributes before ARIA.
  2. Do not override the meaning of a native element unless you have to.
  3. Make every interactive ARIA component work with a keyboard.
  4. Never hide focusable elements from assistive technology.
  5. Give every interactive element an accessible name.

What are the main types of ARIA roles? 

  • Landmark roles: mark page regions, such as banner, navigation, main, search and contentinfo, so users can jump between them.
  • Widget roles: describe interactive components, such as tab, slider, menu, switch and combobox.
  • Document structure roles: describe content organization, such as heading, list, table and img.
  • Live region roles: announce changing content, such as alert, status and log.
  • Window roles: describe overlays, such as dialog and alertdialog.

Industry Insight

According to the WebAIM Million 2026 report, missing form labels appear on 51% of home pages, empty links on 46.3% and empty buttons on 30.6%. Many of these errors come from custom components without an accessible name, which is exactly what native HTML and correct ARIA prevent. 

What are the benefits of using WAI-ARIA correctly? 

  • Accessible interactive features: calculators, filters, carousels, chatbots and live form validation become usable with a screen reader.
  • WCAG conformance: correct names, roles and values help meet WCAG criteria such as Name, Role, Value.
  • Fixes that scale: a correctly built component fixes accessibility everywhere it is reused. See Widgets.
  • Better user experience: clear announcements make complex interfaces predictable.

How do you use WAI-ARIA correctly?

  • Follow proven patterns: use the ARIA Authoring Practices Guide for each widget's roles, states and keyboard behavior.
  • Keep states in sync: update attributes such as aria-expanded whenever the component changes.
  • Build it once: put ARIA into shared components and design systems, not into individual pages.
  • Test with real tools: check every interactive component with a keyboard and at least one screen reader.

Does Xperience by Kentico support WAI-ARIA? 

In Xperience by Kentico, developers have full control of front-end markup, so they decide where native HTML and ARIA are used. See Development. ARIA quality depends on each project's implementation and should be tested. 

  • Reusable widgets: developers build accessible Page Builder widgets once, and editors reuse them without touching code.
  • Structured content: reusable content keeps labels and text alternatives consistent wherever a component appears.
  • Alt text at the source: alt-text fields on Content Hub assets, with alt text suggested by AIRA.
  • Integrations: connect accessibility tools such as text-to-audio services. See Integrations.

Clearview Federal Credit Union's site includes loan and mortgage calculators, live chat and a chatbot, the kind of interactive tools where native HTML and ARIA choices matter most, and the team tested them against WCAG. Read more in The 5 Most Accessible Websites of 2026 on Xperience by Kentico. 

Who needs to understand WAI-ARIA?

Front-end developers, design system teams and QA testers use ARIA every day. Marketers and editors benefit from knowing the principle, native HTML first, when they request custom interactive features. Need specialist help? Find a Kentico partner. 

Frequently Asked Questions.

A page template defines the overall structure and layout of a page, while a widget defines an individual, configurable piece of content placed inside that structure. Templates give editors a starting point, such as a landing page layout with predefined sections, while widgets are what actually populate those sections with specific content like a hero banner or a product grid. In practice, a single page template can host many different widgets, and the same widget can appear across many different page templates.

No, using widgets is designed specifically so that non-technical users don't need coding knowledge. Editors add a widget to a page using a simple button, then adjust its properties, like text, images, or a number of columns, through a configuration dialog built by developers. Any code required to make the widget function, render, or style correctly is written once by a developer ahead of time; the editor only ever interacts with the friendly configuration layer on top of it.
Yes, this is what widget personalization is for. A single widget can have multiple personalization variants, each tied to a condition such as visitor segment or contact group. When a visitor loads the page, the system evaluates the conditions and displays whichever variant matches, so the same widget slot can show different content to different audiences without duplicating the page itself.
Yes, developers can restrict which widgets are allowed in specific editable areas or widget zones. This prevents editors from placing components that don't fit the intended layout or brand guidelines, such as accidentally adding a product carousel widget to a simple text-based landing page. It also keeps a growing widget library manageable, since not every widget needs to be available everywhere it technically could be used.
Widgets are built to be reused. Once a developer creates and registers a widget, it becomes available for editors to add to any page that supports Page Builder, as many times as needed, each with its own independent configuration. This is one of the main efficiency gains of a widget-based approach: the development work happens once, and editors get ongoing value from it every time they build or update a page.

Related terms.

Related content.

Cookie consent

We use necessary cookies to run our website and improve your experience while browsing to provide you with relevant information in your searches on our and other websites. The additional cookies are only used with your consent. With your consent, we may also transmit certain personal data to marketing platforms for targeted marketing purposes.

Configure