This Wiki page is edited by participants of the WCAG Working Group. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.

Failure of 4.1.2 due to using Using Abstract Roles

From WCAG WG
Revision as of 05:34, 13 November 2012 by Lguarino (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search


Status

Applicability

WAI-ARIA

This failure 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

This document describes a failure that occurs when Abstract WAI-ARIA roles are mistakenly used.

Examples

Failure Example 1: A developer was trying to create a form with text input fields and mistakenly applies role="input" to the text input fields.

Failure Example 2: A developer was trying to create a modal dialog window and mistakenly applies role="window" to the modal dialog.

Resources

Resources are for information purposes only, no endorsement implied.

Related Techniques

None

Procedure

  1. For every instance of the role attribute in the page check that the role attribute is not set to any of the following:
  • command
  • composite
  • input
  • landmark
  • range
  • roletype
  • section
  • sectionhead
  • select
  • structure
  • widget
  • window

If Step #1 is false, then this failure condition applies and the content fails the Success Criterion.