ARIA page template

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

A number of macro calls appear at the top of the content section. You should update or delete them according to the advice below:

• {{deprecated_header}}—generates a Deprecated banner that indicates the technology is deprecated. If it isn't, then you can remove the macro call.
• {{ariaref}}—generates a suitable ARIA sidebar, depending on what tags are included on the page.

In 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-labelledby), ARIA widget, Experimental (if the role or attribute is experimental), and Deprecated (if it is deprecated).

In the value of the spec_urls frontmatter metadata key, update the URLs to point to the fragment IDs for the correct sections from the following specifications:

• ARIA: https://w3c.github.io/aria/
• ARIA Authoring Practices: https://w3c.github.io/aria-practices/

Additional resources:

• Accessibility Object Model: https://wicg.github.io/aom/spec/
• ARIA in HTML: https://w3c.github.io/html-aria/

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 appears as a tool tip on links to this page, so craft it well.

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

(Optional) Include a short description of the preceding example.

Include a complete description of the attribute or role.

Name of associated roles

Explanation of requirement, link to features pages.

Name of associated attribute(s)

Explanation of requirement, link to attribute's pages, along with link to JS required to change the value, if appropriate.

Required event handlers

Explanation of each

Changing attribute values

explanation of each

Each example must have an H3 heading (###) naming the example. The heading should be descriptive of what the example is doing. For example, "A simple example" does not say anything about the example and therefore, not a good heading. The heading should be concise. For a longer description, use the paragraph after the heading.

See our guide on how to add code examples for more information.

## Examples

### Using the fetch API
... example of Fetch

### More examples
...links to more examples on other pages

 ## Examples

 For examples of this API, see [the page on fetch()](https://example.org).

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.

Optionally, list any best practices that exist for this role. Remove the section if none exist.

Associated role

If that role is a required parent, child or sibling, and what it does.

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

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

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