Content · Web Development · HTML

HTML comment ARIA Role: Reference and Examples

Understand the comment ARIA role, when it helps accessibility, a clear HTML example and mistakes to avoid.

1 views Published Oct 19, 2026 Updated Oct 19, 2026 Admin

A screen reader needs to know what a piece of a page is, not only what it looks like. The ARIA role comment describes a response or reaction attached to another piece of content.

What this role means


A response or reaction attached to another piece of content.

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 comment in a real page


<article role="comment" aria-label="Comment by Maya">
    <p>Helpful explanation. Thank you!</p>
</article>

Read the example


Look for role="comment" 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.

Support varies; keep author and context understandable in visible text.

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="comment" without checking whether an ordinary HTML element already supplies the right semantics.
  • Support varies; keep author and context understandable in visible text.
  • Confusing the role announced by a screen reader with the behavior that the browser implements.

Key Takeaways


  • comment is related to a response or reaction attached to another piece of content.
  • Support varies; keep author and context understandable in visible text.
  • Native HTML is the first choice; ARIA should clarify meaning, not replace working HTML.
Share this resourceSend this page to someone who may find it useful.