A screen reader needs to know what a piece of a page is, not only what it looks like. The ARIA role document describes a document-reading region inside a complex application.
What this role means
A document-reading region inside a complex application.
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 document in a real page
<div role="document" aria-label="Instructions">
<h2>Instructions</h2>
<p>Read this section before beginning.</p>
</div>Read the example
Look for role="document" 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.
Rarely useful in ordinary documents; do not wrap an entire site unnecessarily.
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.
In an accessibility inspector, compare the accessible role and name with the visible content. The important goal is that both keyboard users and screen-reader users can understand the page.
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="document"without checking whether an ordinary HTML element already supplies the right semantics. - Rarely useful in ordinary documents; do not wrap an entire site unnecessarily.
- Confusing the role announced by a screen reader with the behavior that the browser implements.
Key Takeaways
documentis related to a document-reading region inside a complex application.- Rarely useful in ordinary documents; do not wrap an entire site unnecessarily.
- Native HTML is the first choice; ARIA should clarify meaning, not replace working HTML.