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.

Difference between revisions of "Techniques/ARIA"

From WCAG WG
Jump to: navigation, search
(Handle Feedback)
(Needed for first pass)
Line 43: Line 43:
 
=== Needed for first pass ===
 
=== Needed for first pass ===
 
* Review Failures which may no longer be failures or need modification
 
* Review Failures which may no longer be failures or need modification
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F1 F1: Failure of Success Criterion 1.3.2 due to changing the meaning of content by positioning information with CSS] - Loretta: no update needed. If we were publishing aria-flowto, we should include it in the resources. But the description talks about "relying on CSS rather than structural mark-up", and aria-flowto would be part of the structural markup.
+
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F44 F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability] - '''[James]'''
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F44 F44: Failure of Success Criterion 2.4.3 due to using tabindex to create a tab order that does not preserve meaning and operability] - James
+
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F68 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] - '''[Detlev]'''
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F68 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] - Detlev
+
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F79 F79: Failure of Success Criterion 4.1.2 due to the focus state of a user interface component not being programmatically determinable or no notification of change of focus state available] - '''[James
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F79 F79: Failure of Success Criterion 4.1.2 due to the focus state of a user interface component not being programmatically determinable or no notification of change of focus state available] - James
+
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F85 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] - '''[Marc]'''
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F85 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] - Marc
+
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F86 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] - '''[Marc]'''
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F86 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] - Marc
+
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F87 F87: Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS] - '''[Marc]'''
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F87 F87: Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS] - Marc
+
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F89 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] - '''[Marc]'''
** [http://www.w3.org/TR/WCAG-TECHS/failures.html#F89 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] - Marc
+
  
 
* Review existing advisory techniques
 
* Review existing advisory techniques

Revision as of 22:16, 20 June 2013

Technology Notes Current ARIA Technology Notes

Also see Category:ARIA Techniques.

ToDo

Currently under WG Review

Ready for WG Review

Ready for TF Review

Handle Feedback

Needed for first pass

In Development (Not needed for first round)

Needed (later), Unassigned

Planning per Success Criterion

  • 1.1.1 Non-text content
    • Situation A: If a short description *can* serve the same purpose and present the same information as the non-text content
    • Situation B: If a short description *can not* serve the same purpose and present the same information as the non-text content (e.g., a chart or diagram):
    • Situation C: If non-text content is a control or accepts user input:
    • Situation D: If non-text content is time-based media (including live video-only and live audio-only); a test or exercise that would be invalid if presented in text; or primarily intended to create a specific sensory experience
    • Situation F: If the non-text content should be ignored by assistive technology:
      • Using role=presentation along with H67 (note that this is still being discussed by the WG)
    • Short text alternative techniques for use in sufficient techniques above
      • (not in the LC decision but still being discussed by the WG: aria-labeledby and aria-label)
    • Long text alternative techniques for use in sufficient techniques above [Marc]
      • Using aria-describedby
  • 1.2.1 Audio-only and Video-only (prerecorded)
  • 1.2.2 Captions (prerecorded)
  • 1.2.3 Audio Description or Media Alternative (pre-recorded)
  • 1.2.4 Captions (live)
  • 1.2.5 Audio Description (pre-recorded)
  • 1.2.6 Sign Language (pre-recorded)
  • 1.2.7 Extended Audio Description (Prerecorded)
  • 1.3.1 Info and Relationships [Joshue O Connor - 10-Oct-2012]
    • Using ARIA roles and properties (this applies to both situation A and situation B, because some of these duplicate things in HTML 5, and others provide semantics that HTML 5 does not)
    • Using ARIA relationships (this is more situation B, since HTML doesn't have most of these things, but in some situations, authors are duplicating HTML functionality)
    • Using ARIA landmarks [David MacDonald, WG survey 14 Jan 2013, returned to TF]
    • Headings using role=heading [Léonie Watson, WG survey 14 Jan 2013, returned to TF]
    • Situation A:
      • Using aria-label, aria-labledby, and aria-describedby to provide labels and descriptions [David MacDonald - see above]
      • TODO: List out all the other aria stuff....
    • Situation B:
    • Failures
      • Is there an equivalent to F62 for ARIA relationships?
  • 1.3.2 Meaningful Sequence
    • Using aria-flowto [Loretta - Done, WG survey 14 Jan 2013, postponed as low priority technique]
  • 1.4.1 Use of Color
  • 1.4.2 Audio Control
  • 1.4.4 Resize text
  • 1.4.5 Images of Text
  • 2.1.1 Keyboard


Failure Technique


Review Failures which may no longer be failures