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.

Techniques/Flash

From WCAG WG
Jump to: navigation, search


Also see Category:ARIA Techniques.

  • 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
      • Using aria-labeledby (note: on img, you must also use @alt to be valid HTML 5 as of last call draft) [James Nurthen]
      • Using aria-label (note: on img, you must also use @alt to be valid HTML 5 as of last call draft) [James Nurthen]
      • using title [James Nurthen]
    • 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
      • 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 [Matt May, Joshue O Connor]
    • 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]
    • 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....
    • Failures
      • Is there an equivalent to F62 for ARIA relationships?
  • 1.3.2 Meaningful Sequence
  • 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
    • Using aria-activedecendant [Adam]
    • Using role with scripted event handlers (to fix F42)
  • 2.3.1 Three Flashes or Below Threshold
  • 2.4.1 Bypass Blocks
  • 2.4.3 Focus Order
  • 2.4.4 Link Purpose (in context) [Marc Johlic, Jon Gunderson]
  • 2.4.5 Multiple Ways
  • 2.4.6 Headings and Labels
  • 2.4.7 Focus Visible
  • 2.4.8 Location
    • same as 2.4.5
  • 2.4.10 Section Headings
  • 3.1.1 Language of Page
  • 3.1.2 Language of Parts
  • 3.1.3 Unusual Words [Christophe Strobbe]
    • Using details and summary
  • 3.1.4 Abbreviations
  • 3.1.5 Reading Level
  • 3.1.6 Pronunciation
    • Using details and summary
  • 3.2.1 On Focus
  • 3.2.2 On Input
  • 3.2.3 Consistent Navigation
  • 3.2.4 Consistent Identification
  • 3.2.5 Change on Request
  • 3.3.1 Error Identification [Marc Johlic]
    • Using aria-alertdialog
    • Using ARIA Live Regions
  • 3.3.2 Labels or Instructions [Detlev]
    • Using aria-label (does this work? Needs to be visible, right?) [Detlev]
    • Using aria-labeledby [Detlev? See also David's techniques]
    • Using aria-describedby [Detlev? See also David's techniques]
    • TODO: is there anything in aria for linking instructions?
  • 3.3.3 Error Suggestion [Tim]
  • 3.3.4 Error Prevention (legal, financial, data)
  • 3.3.5 Help
    • Using aria-describedby [David]
  • 3.3.6 Error Prevention (All)
    • Same as 3.3.4
  • 4.1.1 Parsing
  • 4.1.2 Name, Role, Value [Loretta]