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
Line 68: Line 68:
 
* [[Using ARIA trees]]  '''[Jon Gunderson]'''
 
* [[Using ARIA trees]]  '''[Jon Gunderson]'''
 
* [[Using aria-describedby for link purpose]]  '''[Jon Gunderson]'''
 
* [[Using aria-describedby for link purpose]]  '''[Jon Gunderson]'''
* [http://www.w3.org/WAI/GL/wiki/Using_aria-activedescendant_to_allow_changes_in_focus_within_widgets_to_be_communicated_to_Assistive_Technology Using aria-activedescendant] '''[Adam-in process-group discussion indicated that this technique not relevant to this sc]''' ''and'' [[Use CSS to highlight the focused element]]
+
* [http://www.w3.org/WAI/GL/wiki/Using_aria-activedescendant_to_allow_changes_in_focus_within_widgets_to_be_communicated_to_Assistive_Technology Using aria-activedescendant] '''[Adam-in process]''' ''and'' [[Use CSS to highlight the focused element]]
 
* Using aria-describedby  '''[Detlev - has made a small closed button example that needs to be added to an existing tech - Maybe Davids.]'''
 
* Using aria-describedby  '''[Detlev - has made a small closed button example that needs to be added to an existing tech - Maybe Davids.]'''
 
* [[Using WAI-ARIA aria-checked=mixed]] '''[Jon Gunderson]'''
 
* [[Using WAI-ARIA aria-checked=mixed]] '''[Jon Gunderson]'''
Line 139: Line 139:
 
* 2.4.6 Headings and Labels
 
* 2.4.6 Headings and Labels
 
* 2.4.7 Focus Visible
 
* 2.4.7 Focus Visible
** [http://www.w3.org/WAI/GL/wiki/Using_aria-activedescendant_to_allow_changes_in_focus_within_widgets_to_be_communicated_to_Assistive_Technology Using aria-activedescendant] '''[Adam-in process]''' ''and'' [[Use CSS to highlight the focused element]]
+
** [http://www.w3.org/WAI/GL/wiki/Using_aria-activedescendant_to_allow_changes_in_focus_within_widgets_to_be_communicated_to_Assistive_Technology Using aria-activedescendant] '''[Adam-in process-group discussion indicated that this technique not relevant to this sc-need to confirm this]''' ''and'' [[Use CSS to highlight the focused element]]
 
* 2.4.8 Location
 
* 2.4.8 Location
 
** same as 2.4.5
 
** same as 2.4.5

Revision as of 08:11, 1 May 2013

Technology Notes Current ARIA Technology Notes

Also see Category:ARIA Techniques.

ToDo

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