ARIA Page Template


Remove before publishing

Title and slug

An ARIA role page should have a title and slug of NameOfTheRole. For example, the button role has a title and slug of ARIA Button Role and the aria-labelledby attribute has a title of ARIA-labeledby Attribute.

Top macros

There are four macro calls at the top of the template by default. You should update or delete them according to the advice below:

  • {{draft()}} — this generates a Draft banner that indicates that the page is not yet complete, and should only be removed when the first draft of the page is completely finished. After it is ready to be published, you can remove this.
  • {{deprecated_header}} — this generates a Deprecated banner that indicates the technology is deprecated. If it isn't, then you can remove the macro call.
  • {{ariaref}} — this generates a suitable ARIA sidebar, depending on what tags are included on the page.


In an ARIA role or attribute subpages, you need to include the following tags (see the Tags section at the bottom of the editor UI): ARIA, Reference, ARIA Role or ARIA Attribute, the name of the Role or Attribute (e.g. ARIA button or aria-labeledby), ARIA widget, Relationship Attribute as appropriate, Experimental (if the role or attribute is experimental), and Deprecated (if it is deprecated).


Update the fragment link within the following specifications to the correct section:

  • ARIA:
  • ARIA Authoring Practices:

Additional resources:

  • Accessibilty Object Model:
  • ARIA in HTML:

This page is not complete.


The summary paragraph — start by naming the role or attribute and saying what it does. This should ideally be 1 or 2 short sentences. This content will appear as a tool tip on links to this page, so craft it well.

<!-- Insert code block showing common use cases -->


Include a complete description of the attribute or role

Include note about semantic alternatives to using this role or attribute. The first rule of ARIA use is you can use a native feature with the semantics and behavior you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so. Then post full details in best practices section below.


Fill in a simple example that nicely shows a typical usage of the property, then perhaps some more complex examples (see our guide on how to add code examples for more information).

my code block

And/or include a list of links to useful code samples that live elsewhere:

  • x
  • y
  • z

Accessibility concerns

Optionally, warn of any potential accessibility concerns that exist with using this property, and how to work around them. Remove this section if there are none to list.

Best Practices

Optionally, warn of any potential accessibility concerns that exist with using this property, and how to work around them. Remove this section if there are none to list.

Added Benefits

Any additional benefits this feature has for non-typical screen reader users, like Google or mobile speech recognition.


Specification Status
Accessible Rich Internet Applications (WAI-ARIA)
The definition of 'NameOfRoleOrAttribute' in that specification.
The definition of 'NameOfRoleOrAttribute' in that specification.

Precedence Order

What are the related properties, and in what order will this attribute or property be read (which property will take precendence over this one, and which property will be overwritten.

Screen Reader Support


See also


  • Include list of
  • other links related to
  • this role or attribute that might
  • be useful

Document Tags and Contributors

Contributors to this page: estelle
Last updated by: estelle,