Home
Bookmarks
Leagues
LEARN
Courses
Career Paths
Assessments
Tutorials
Arcade
Glossary
GROW
Certifications
Log in
Glossary
Log inSign up
Courses/Introduction to Design Systems/Accessibility First: WCAG & Inclusive Foundations/
Exercise #6

ARIA: When to Use It and the 'First Rule of ARIA'

ARIA (Accessible Rich Internet Applications) is a set of attributes that supplement HTML to convey roles, states, and properties to assistive technologies.

However, the First Rule of ARIA states:

'If you can use a native HTML element or attribute with the semantics and behavior you already require, then do so instead of re-purposing an element and adding an ARIA role, state or property to make it accessible.'

For example:

  • Wrong: <div onClick={submit} role="button" tabIndex={0}>Submit</div> (requires manual keypress handlers, focus styling, and state management).
  • Right: <button type="submit">Submit</button> (native keyboard support, enter/space triggers, disabled state, and native accessibility tree representation out of the box).

Topics

Accessibility as a Systemic Multiplier
The 4 Core Principles of WCAG (POUR)
Color Contrast Standards: WCAG AA vs AAA
Visible Focus Rings & Focus Management
Focus Trapping in Modals & Dialogs
ARIA: When to Use It and the 'First Rule of ARIA'
Touch Targets & Pointer Cancellation (WCAG 2.2)
Motion Sensitivity & `prefers-reduced-motion`
Screen Reader Testing & Semantic Landmarks
Challenge: Auditing an Inaccessible Form Field

From lesson

2

Accessibility First: WCAG & Inclusive Foundations

Level 2 · Core Principles & Governance

Top contributors

Community contribution details will appear here once real learner activity is available.

Share