Techniques sorting notes

• 9.3: Text for images used as links
  • sufficient in combination with (to be written) general techs
  • works today
  • baseline ideal
• 9.4: Image and text links side by side
  • sufficient
  • works today, though there are sometimes UA issues with doing this without impacting visual design. additional CSS techniques needed? @@ Tom to collect examples.
  • baseline ideal for HTML, combined with CSS technique makes it more ideal.
  • this also maps to 1.1 L1 #3. at level 1, this would be advisory because it's a constraint on the visual design. - need to document user agent issues here - in some cases, making this technique work can be difficult - goal for CSS techniques is to provide techniques that make it less of an issue. this technique is important, but turns out there are ways to do this technique incorrectly @@ examples need cleanup such that they include table information to show how this can be a problem @@ need reference to (to be written) CSS technique for this.
• 10.4: Short text alternatives for object elements (future)
  • not sufficient, because not supported
  • does not work today, thus a future technique
  • this is the baseline ideal, spec-conformant solution, but UAAG doesn't require rendering alternatives correctly. Transition issue here in that we have been recommending that people do this since WCAG 1.0.
• 10.5: Non-explicit text alternatives for object
  • sufficient techniques
  • works today , though not baseline ideal
  • @@ global search and replace of dlink with link to external description in techniques docs
• 11.1: Use client side image map
  • baseline ideal (if the image map is simple)
  • numerous issues here, we need to describe providing alternates to complex imagemaps
• 11.2: Text links for server side image maps.
  • sufficient, if server-side image map is simple
• 11.3: Redundant text links for client side image maps (deprecated)
  • works today
  • not ideal
  • not sufficient, because if you only did this, you'd fail (not standard)
  • technique is both optional and deprecated
• 11.4: Text alternatives for client-side image maps
  • sufficient techniques
  • works today (though alternatives are not displayed when images are off)
  • baseline ideal
• 12.3: Alternative content for programmatic objects
  • see ednote
  • seems to overlap with 10.5
• 12.4: Text and non-text alternatives for object
  • not sufficient (it doesn't work)
  • seems to be ideal
  • use of this technique would not cause you to fail
  • overlaps with 10.4
  • techs need to make it clear that at the end of the chain of non-text alternatives for non-text content, you get a text alternative.
• 12.5: Alternative content for applet
  • does not work today
  • seems to be ideal for longer descriptions
  • deprecated for current specifications (transitional for HTML 4)
• 12.6: Alt text for applet
  • sufficient
  • works today
  • also transitional
• 12.7: Alternative content for embed
  • sufficient
  • users can't get to noembed content reliably in current AT
  • baseline ideal - ideal in terms of using embed, but use of embed itself is not ideal since it's not in spec
• 12.8: Alt text for embed
  • less ideal than noembed
  • @@ user agent testing needed on this - not sure if it works today
• 14.4: Writing for browsers that do not support FRAME
  • sufficient if frameset is simple
  • works today , though so does frame titles
  • would not cause you to fail SC
  • relates to baseline - if you have a frame-based web application, you could use noframes to provide an equiv. alternative
• 15.7: Text alternatives for submit buttons
  • sufficient
  • baseline ideal
  • works today
• 16.1: Text alternatives for scripts
  • dependent on baseline
• 16.2: JavaScript URLs
  • @@ mapping needs work
  • potentially a baseline issue (noscript for this use of script doesn't make sense)
• 16.3: Scripted form submission
  • many issues with mapping, etc. on this one