eramp, a strategic approach to accessibility, fingerspelling 'eramp quality'

WCAG 2.0 new technique submission reviews

Report on Technique recommendations. I’m not creating new techniques or turning them into finished presentable techniques, but rather simply exploring and summarizing each technique, discussing its usefulness and possible problems and necessary changes.

 

Table of Contents

 

 

Sailesh’s submission
http://lists.w3.org/Archives/Public/public-wcag2-techs/2008Aug/0001.html

 

appears to be covered
http://www.w3.org/TR/2008/NOTE-WCAG20-TECHS-20081211/SCR18

 

Recommendation

We could perhaps add some of his language but I don’t see that it will add too much. Suggest we adopt these examples

 

 

Government of Canada

When to open to a new window.

http://lists.w3.org/Archives/Public/public-wcag2-techs/2008Aug/0000.html

 

Recommendation

They are suggesting that opening to a new widow be allowed in three situations:

  1. Opening a page containing context-sensitive information (such as help instructions) or an alternate means of completing a form (such as a calendar-based date picker)
  2. will significantly disrupt a multi-step workflow (such as filling in and submitting a form) if the page is opened in the same window or tab.
  3. Opening a page outside of a secure session will prematurely break or destroy the secure session if the page is opened in the same window or tab.

This is not possible as an imperative given the current 2.0, however, I think this is good advice and that we should use it. We would adapt the language to suggestions rather than imperatives.   It would become the substance for the advisory for 3.2.1
“Opening new windows only when best from an accessibility perspective (future link)”

Sailesh
Server-side Scripting Techniques - Conveying form validation messages and suggestions for correction in text A similar technique, General Techniques - Providing text descriptions to identify validation errors and suggestions for correction upon form submission  Above,  which is similar to SCR18

 

Recommend going over the suggested technique and current SCR18 adding anything to it that will enrich it.

 

http://lists.w3.org/Archives/Public/public-wcag2-techs/2008Apr/0000.html
New techniques
Submitter's Name: Sheena McCullagh
Short Name: Specifying borders and layout in CSS to delineate areas of a Web page while not specifying text and text-background colors.

 

Recommend: yes, add that default presentation is black text on white background

http://lists.w3.org/Archives/Public/public-wcag2-techs/2008Apr/0001.html

<title>General Techniques - Specifying text and background colors of
secondary content such as banners, features and navigation in CSS while
not specifying text and background colors of the main content. from
WCAG 2.0 Techniques Submission Form on 2008-04-23
(public-wcag2-techs@w3.org from April 2008)</title>

Submitter's Name: Sheena McCullagh

 

Recommend combine with previous one on the same topic (above)

http://lists.w3.org/Archives/Public/public-wcag2-techs/2007Mar/0000.html
Short Name: Avoiding confusion in navigation.
Clayton
Description:
The objective of this technique is to avoid confusion in navigation. The approach is to use familiar, commonly used controls and presentations of location, and to avoid novel, unfamiliar methods.

 

Recommendation: It’s a little ambiguous, untestable perhaps add to advisory… needs formatting , unfinished – low priority

 

http://lists.w3.org/Archives/Public/public-wcag2-techs/2007Mar/0001.html
Technique ID: UNKNOWN
Short Name: Reducing user errors.
Technique Category: General Techniques
Guideline Reference: minimize-error
Success Criterion Reference: UNKNOWN

 

Recommendation: It’s a little ambiguous, untestable perhaps add to advisory… needs formatting , unfinished – low priority

http://lists.w3.org/Archives/Public/public-wcag2-techs/2007Mar/0002.html

Technique ID: UNKNOWN
Short Name: Making the functionality of content predictable.
Technique Category: General Techniques
Guideline Reference: consistent-behavior
Success Criterion Reference: UNKNOWN
 
Recommendation: ambiguous not testable , unfinished – low priority

http://lists.w3.org/Archives/Public/public-wcag2-techs/2006Jun/0000.html

Technique ID: UNKNOWN
Short Name: Using semantic markup whenever color cues are used
Technique Category: General Techniques
Guideline Reference: content-structure-separation-without-color
Success Criterion Reference: UNKNOWN

 

Recommendation: most blind users don’t know how to make a screen reader speak emphasis <Em> let’s leave the standard at an asterisk * until ARIA is released and overcomes the problems with HTML.

http://lists.w3.org/Archives/Public/public-wcag2-techs/2006Jun/0002.html

Technique ID: UNKNOWN
Short Name: Failure due to omitting labels for form controls for item selection or text input
Technique Category: Common Failures
Guideline Reference: content-structure-separation-programmatic
Success Criterion Reference: UNKNOWN

 

Recommendation:


Maybe: Discuss w/group…. We currently allow title with no label which is not explicit

http://lists.w3.org/Archives/Public/public-wcag2-techs/2005Oct/0001.html

Technology: Techniques Gateway 
Techniques Category: minimize-error 
Submitter's Name: Yvette Hoitink 
Submitter's Email: y.p.hoitink@heritas.nl

Yvette
Advisory/optional technique

If a legal transaction or data modification as the result of a form submission is reversible, inform the user of the legal transaction or data modification by e-mail and explain the process of cancelling the transaction or modification.

Sending an e-mail will give the user the opportunity to read and check the details or ask for assistance if necessary.

 

Recommendation
Discuss with group – beyond our scope?

http://lists.w3.org/Archives/Public/public-wcag2-techs/2005Oct/0000.html

Linking to the form element from the error text
Yvette

 

Recommendation: I thought we had it as advice but I didn’t see it in our documentation.  So let’s add it.

http://lists.w3.org/Archives/Public/public-wcag2-techs/2005Aug/0002.html

Technology: Techniques Gateway 
Techniques Category: navigation-mechanisms 
Submitter's Name: Yvette Hoitink 
Submitter's Email: y.p.hoitink@heritas.nl

 

Provide metadata about the delivery unit

 

Recommendation: Currently no AT uses this, possible future tech

http://lists.w3.org/Archives/Public/public-wcag2-techs/2005Aug/0004.html

Ben , image replace
http://www.tjkdesign.com/articles/tip.asp

 

Recommendation: I think the idea of a general technique with this as a link is good.

Note: Here’s my concern which has come up recently… Google has printed a policy that I had not seen. It appears it was written or at least updated on Dec 4, 2008. It uses very strong language against hidden text that could be “perceived” as deceptive.  I tested hiding text before we accepted our CSS hidden text technique C7 and there was no apparent punishment…  but the current language of the advisory is strong and the penalty is steep and I would not want WCAG to be responsible for someone being delisted if they follow our technique. Do we need UA notes? http://www.google.com/support/webmasters/bin/answer.py?answer=66353&topic=15263

 

 

http://lists.w3.org/Archives/Public/public-wcag2-techs/2004Nov/0000.html


Scripting is separated from markup in popup window links.

 

I think there is a problem with it, because if there are more than one popups on a page that go to different places every popup contains the last link.

David says: I've provided a working example here:

 

Recommendation: needs further review. perhaps get back to Becky.

http://lists.w3.org/Archives/Public/public-wcag2-techs/2004Oct/0003.html

Yvette
Use correct grammar and spelling


Recommendation: add

 

http://lists.w3.org/Archives/Public/public-wcag2-techs/2004Oct/0002.html

Highlight search terms
Yvette

 

Recommendation: accept For cognitive, advisory. 1.4.8

http://lists.w3.org/Archives/Public/public-wcag2-techs/2004Oct/0001.html

 

Yvette
Use sounds to focus user's attention


Recommendation: Accept

http://lists.w3.org/Archives/Public/public-wcag2-techs/2004Oct/0000.html

 

Hide optional form fields


Recommendation: turn into a general tech advisory

http://lists.w3.org/Archives/Public/public-wcag2-techs/2004Sep/0000.html

Becky
Blinking via JavaScript and CSS


Recommendation: accept

 

http://lists.w3.org/Archives/Public/public-wcag2-techs/2004Jul/0000.html

Ben

Image-based headings

David says: I put up a test example here


Recommendation: accept