Constraint Details

Constraints restrict the degree of freedom in providing solutions.

Table of Contents

  1. Author Skill Sets Differ
    1. Different Techniques Require Different Skills
      1. Simplicity
      2. Support Tools
      3. Educational Material
  2. Breaking Backwards Compatibility is an Intolerable Cost
    1. Existing Tools
    2. Existing Content
    3. Existing Documentation
  3. Bridging Technology is Backward
    1. WAI-ARIA is a Bridging Technology
    2. WAI-ARIA Goal and Dangers
    3. Shirking Off Long Description Semantics to ARIA
  4. Description Available in a Separate Document Provides Efficiency
    1. Powerful Technique
    2. Examples in the Wild
    3. Code and User Interface Patterns
  5. Equal Access to Dual Functionality
    1. Dual Functionality Provides Accommodation
    2. One Link Cannot Take a User to Two Locations
    3. Disallowing Equal Access is Unacceptable
  6. Forced Visual Encumbrance Adds Visual Clutter
    1. Visual Clutter
    2. Natively Free from a Visual Encumbrance Solves a Problem
    3. Allowing for Discoverability Serves Other Use Cases
      1. Existing Discoverability Tools Fulfill These Use Cases
      2. Incentive for More Discoverability Tools
  7. Forcing Descriptions on Users is Harmful
  8. Programmatic Determinability Aids Accessibility
  9. Semantics Improve Communication
    1. Higher Level of Communication
    2. Precedent
    3. WAI-ARIA Provides Missing Semantics
    4. HTML is Not Missing Native Semantics
  10. Structured Markup Facilitates Critical Functionality
    1. Enabling Functional Long Description Content
      1. JAWS Examples
    2. Plain String Text Voids This Functionality
    3. Examples in the Wild Utilize Structured Markup
  11. User Agent Support
    1. Growth in User Agent Support
      1. llongdesk
      2. TellMeMore
      3. Scripted Implementations
      4. Long Description Favelet
  12. Alternative Techniques Are Not Viable
    1. aria-describedat
      1. Status
      2. Use Cases
      3. Bridging Technology
      4. Forces a Visual Encumbrance
      5. Different Authors Have Different Skill Sets
      6. Lack of ARIA Educational Material
      7. Lacks Backwards Compatibility
      8. No Examples in the Wild
      9. No Implementations
      10. Reinvents the Wheel
      11. No Evidence of Improvement
    2. aria-describedby
      1. Bridging Technology
      2. Adds Needless Complexity
      3. Lacks Ability to Provide Description in a Separate Document
      4. Different Authors Have Different Skill Sets
      5. Lacks ARIA Educational Material
      6. Two-Step Retrieval Instead of One-Step Retrieval
      7. Lacks Support for Structured Text
      8. Is Forced Upon Users
      9. Forces a Visual Encumbrance
      10. Lacks Vendor Support
      11. Reinvents the Wheel
      12. Lacks Backwards Compatibility
      13. Retrofitting Problem
      14. No Examples in the Wild
      15. No Evidence of Improvement
    3. canvas
      1. Illogical Technique
      2. Semantics
      3. Adds Needless Complexity
      4. Overloading canvas
      5. No Examples in the Wild
      6. Lacks Educational Material
      7. No Evidence of Improvement
      8. Lacks Backwards Compatibility
      9. Retrofitting Problem
    4. Cascading Style Sheets
      1. Violates Search Engine Guidelines/Can Result in Being Removed From Search Engine Indexes
      2. Adds Needless Complexity, Page Weight, and Inconsistency
      3. Strips Structure From Any Hidden Content Referenced by ARIA
      4. No Evidence of Improvement Over Longdesc
    5. figcaption
      1. Semantics
      2. Forces a Visual Encumbrance
      3. Lacks Ability to Provide Description in a Separate Document
      4. Reinvents the Wheel
      5. Lacks Educational Material
      6. Lacks Examples in the Wild
      7. Lacks Backwards Compatibility
      8. Retrofitting Problem
      9. No Evidence of Improvement
    6. a href
      1. Semantics
      2. Not Programmatic Determinable
      3. Impossible for One Link to Have Two Destinations
      4. Forces a Visual Encumbrance
      5. No Evidence of Improvement
    7. hidden
      1. Lacks Discoverability Specification
      2. Lacks Discoverability Tools
      3. Strips Structure From Text Reducing it to a String
        1. No Accessible Object Representing the Text Description is Exposed in the Accessibility API
      4. As Implemented is Hidden From its Target Audience
      5. Will Likely Result in Pages Being Removed From Search Engine Indexes
      6. Lacks Authoring Tools
      7. Is a Confusing and Complex Technique
      8. Lacks Examples in the Wild
      9. Lacks Backwards Compatibility
      10. Retrofitting Problem
      11. Presents No Evidence of Improvement Over longdesc
    8. iframe
      1. Incorrect Semantics
      2. Forces a Visual Encumbrance
      3. Reinvents the Wheel
      4. Lacks Educational Material
      5. Lacks Examples in the Wild
      6. Lacks Backwards Compatibility
      7. Retrofitting Problem
      8. No Evidence of Improvement
    9. imagemap
      1. Illogical Technique
      2. Semantics
      3. Adds Needless Complexity
      4. Programmatic Determinability
      5. Impossible for One Link to Have Two Destinations
      6. Lacks Examples in the Wild
      7. Retrofitting Problem
      8. Lacks Educational Material
      9. No Improvement
    10. New HTML Attribute
      1. Status
      2. Reinvents the Wheel
      3. No Evidence of Improvement
      4. Use Cases
      5. No Examples in the Wild
      6. Lacks Vendor Support
      7. Lacks Educational Material
      8. Lacks Backwards Compatibility
    11. summary/details
      1. Semantics
      2. Forces a Visual Encumbrance
      3. Lacks Ability to Provide Description in a Separate Document
      4. Lacks Backwards Compatibility
      5. No Examples in the Wild
      6. Retrofitting Problem
      7. No Evidence of Improvement
    12. rel="longdesc"
      1. Semantics
      2. Impossible for One Link to Have Two Destinations
      3. Forces a Visual Encumbrance
      4. Reinvents the Wheel
      5. No Examples in the Wild
      6. No Improvement
      7. No Implementations
      8. Lacks Backwards Compatibility