A screen reader needs to know what a piece of a page is, not only what it looks like. The ARIA role timer describes a region showing elapsed or remaining time.
What this role means
A region showing elapsed or remaining time.
ARIA roles add meaning to the accessibility tree. They do not automatically make something clickable, move keyboard focus or build an interface. Those behaviors come from native HTML controls or from correctly implemented JavaScript.
See timer in a real page
<!-- Example for timer semantics -->
<p role="timer" aria-label="Time remaining">05:00</p>Read the example
Look for role="timer" in the example. The role helps assistive technology classify the content. Read the surrounding text and labels too: those give the control or region its useful name.
Timer has no automatic live announcement; updating it requires JavaScript and an appropriate announcement strategy.
When to use it
Start with native HTML whenever possible. Add ARIA only when it provides missing meaning for an interface that you cannot build with the appropriate native element.
For changing messages, decide when the announcement should happen. A live-region role describes the message, but the timing, frequency and actual content updates are your responsibility.
Try it yourself
Put the example on a practice page and inspect it using your browser accessibility panel. If it includes interactive controls, reach them with Tab and check whether they work without a mouse. Explain whether the semantics come from native HTML or an explicit ARIA role.
Common Beginner Mistakes
- Adding
role="timer"without checking whether an ordinary HTML element already supplies the right semantics. - Timer has no automatic live announcement; updating it requires JavaScript and an appropriate announcement strategy.
- Confusing the role announced by a screen reader with the behavior that the browser implements.
Key Takeaways
timeris related to a region showing elapsed or remaining time.- Timer has no automatic live announcement; updating it requires JavaScript and an appropriate announcement strategy.
- Native HTML is the first choice; ARIA should clarify meaning, not replace working HTML.