Techniques for WCAG 2.0

On this page:

-

# G108: Using markup features to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes

## Applicability

Markup technologies where it is possible to expose the name and role, allow user-settable properties to be directly set, and provide notification of changes.

This technique relates to:

- Success Criterion 4.1.2 (Name, Role, Value)
  - How to Meet 4.1.2 (Name, Role, Value)
  - Understanding Success Criterion 4.1.2 (Name, Role, Value)

## Description

The objective of this technique is to allow assistive technology to understand Web content so that it can convey equivalent information to the user through an alternate user interface and allow them to operate controls through the AT.

This technique involves using standard, documented and supported features to expose these properties to AT. It relies on the fact that these standard controls in standard browsers meet the requirements.

For HTML these assumptions are good. They may also be appropriate for some other technologies.

Even when the components support accessibility, it is essential that some information be provided by the author. For example, a control may have the ability to provide a name but the author still has to provide the name. The role attribute however may already be provided since it is a standard component with a fixed role.

## Examples

### Example 1

Example 1: A Web page written in HTML or XHTML uses standard form controls, and identifies the form control using the title attribute. The user agent makes information about these controls, including the name, available to assistive technology through the DOM and through a platform-specific Accessibility API.

## Resources

Resources are for information purposes only, no endorsement implied.

## Related Techniques

- G135: Using the accessibility API features of a technology to expose names and roles, to allow user-settable properties to be directly set, and to provide notification of changes
- H44: Using label elements to associate text labels with form controls
- H88: Using HTML according to spec
- H91: Using HTML form controls and links
- SCR21: Using functions of the Document Object Model (DOM) to add content to a page

## Tests

### Procedure

1. Visually inspect the markup or use a tool.

2. Check that proper markup is used such that the name and role, for each user interface component can be determined.

3. Check that proper markup is used such that the user interface components that accept user input can all be operated from AT.

### Expected Results

- Step #2 and #3 are both true for each user interface component

- Top
- Contents
- Intro
- Previous: Technique G107
- Next: Technique G110