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.
Completed ARIA Techniques
From WCAG WG
ARIA Techniques in published techniques document
- ARIA1: (Current) - ARIA1: Using the aria-describedby property to provide a descriptive label for user interface controls'
- ARIA2: (Current) - ARIA2: Identifying a required field with the aria-required property
- (commented out in XML) ARIA3: (Current) - ARIA3: Identifying valid range information with the aria-valuemin and aria-valuemax properties'
- F15: Failure of Success Criterion 4.1.2 due to implementing custom controls that do not use an accessibility API for the technology, or do so incompletely
- F38 (Current) @ F38: Failure of Success Criterion 1.1.1 due to not marking up decorative images or applets in HTML in a way that allows assitive technology to ignore them
- F43 (Current) @ F43: Failure of Success Criterion 1.3.1 due to using structural markup in a way that does not represent relationships in the content
- F59 (Current) @ ARIA-edit: F59: Failure of Success Criterion 4.1.2 due to using script to make div or span a user interface control in HTML
- F63 (Current) @ ARIA-edit: F63: Failure of Success Criterion 2.4.4 due to providing link context only in content that is not related to the link
- F65 (Current) @ Aria-Edit: F65: Failure of Success Criterion 1.1.1 due to omitting the alt attribute on img elements, area elements, and input elements of type image
- F68 (Current) @ ARIA-edit: F68: Failure of Success Criterion 1.3.1 and 4.1.2 due to the association of label and user interface controls not being programmatically determinable
- F85 (Current) @ F85: Failure of Success Criterion 2.4.3 due to using dialogs or menus that are not adjacent to their trigger control in the sequential navigation order
- F86 (Current) @ F86: Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part form field, such as a US telephone number
- F89: Failure of Success Criteria 2.4.4, 2.4.9 and 4.1.2 due to using null alt on an image where the image is the only content in a link F89 (Current): F89 Edit
- Using a WAI-ARIA role to expose the role of a user interface component - ARIA4
- Using WAI-ARIA state and property attributes to expose the state of a user interface component - ARIA5
- Using aria-label to provide labels for objects - ARIA6
- Using aria-labelledby for link purpose - ARIA7
- Using aria-label for link purpose - ARIA8
- Using aria-labelledby to concatenate a label from several text nodes - ARIA9
- Using aria-labelledby to provide a text alternative for non-text content - ARIA10
- Using ARIA landmarks to identify regions of a page - ARIA11
- Using role=heading to identify headings - ARIA12
- Using aria-labelledby to name regions and landmarks - ARIA13
- Using aria-label to provide an invisible label where a visible label cannot be used] - ARIA14
- Using aria-describedby to provide descriptions of images - ARIA15
- Failure_of_Success_Criterion_1.3.1_due_to_the_use_of_role_presentation_on_content_which_conveys_semantic_information - F92
- Using aria-labelledby to provide a name for user interface controls - ARIA16
- Using grouping roles to identify related form controls - ARIA17
- Using aria-alertdialog to Identify Errors - ARIA18
- Using ARIA Live Regions or role=alert to Identify Errors [Paul] In Review of Techs comments and ARIA techniques for September 22, 2013 (awaiting example from Alastair) - ARIA19
