WAI Evaluation and Repair Tools Techniques Issues List

Last revised: $Date: 2000/11/08 08:17:25 $

This page tracks issues raised between releases of Working Drafts of the Evaluation and Repair Tools Techniques Document.

If there is an issue that is not on this list, or that is misrepresented or inadequately summarized, please send your comments to w3c-wai-er-ig@w3.org or contact the editor, Wendy Chisholm.

Table of Contents of Issues

Open Issues

Issues that need clarification from the WCAG WG

Closed Issues

Open Issues

links to WCAG techniques document

links to WCAG techniques document
From: Wendy A Chisholm (wendy@w3.org) Date: Sun, Jan 23 2000
Scope: General - 21 December release
Harvey Bingham supports. As well as including links to examples in the WCAG Curriculum being developed by EO.

Note or Recommendation?

Note or Recommendation? Question came up in discussion of priorities.
From: Chris Ridpath (chris.ridpath@utoronto.ca) Date: Tue, Jan 25 2000
Scope: General - 21 December release
Wendy Chisholm thinks Note.

Editorial comments

Editorial comments, including typos.
From: Leonard R. Kasday (kasday@acm.org)
Date: Sun, Jan 23 2000
Scope: General - 21 December release

"Crying wolf"

The introduction refers to "cry wolf" syndrome, should we be more specific?
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Scope: Introduction - 21 December release

Author indications that a warning has been checked

We need a way for an author to indicate that a warning has been checked.
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Scope: Introduction - 21 December release

How do we check if image is "complex"?

How do we check if image is "complex"?
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Scope: Technique 1.1.B - 21 December release

Combine similar techniques?

Combine and point out the differences.
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
1.1.C and 1.1.A are very similar.
Scope: Techniques 1.1.C and 1.1.A - 21 December release

Check APPLET for "alt" always needed?

Check applet for "alt" always needed? "APPLET element must have a valid ALT attribute." Is this needed if the user, in accordance with 1.1.E, has code before </applet> that shows up when user agent skips applets?
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Scope: Technique 1.1.D - 21 December release

Check APPLET and OBJECT for any HTML element

Check applet and OBJECT for any HTML element, not just valid text.
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Scope: Techniques 1.1.E and 1.1.F - 21 December release

FRAME "title" check not automatic

We can't automatically check if title "completely describes...".
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Scope: Technique 1.1.G - 21 December release

Valid "londesc"

The tool should check the file that is pointed to by the "londesc" attribute.
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Scope: Technique 1.1.G - 21 December release

Audio equivalents

Text equivalents for audio files do not have to be a text transcript file. The text can be on the page in which the A element resides.
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Scope: Technique 1.1.G - 21 December release

Content of NOSCRIPT

Don't limit to text description. Prompt for HTML that isfunctionally equivalent. This may be, for example, a list of links, form input to CGI, etc.
From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Scope: Technique 1.1.J - 21 December release

Multimedia

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Issues:
- define multimedia.
- Audio description not always necessary for multimedia. What if the multimedia object can be fully described with ALT text or text in the document?
Scope: Technique 1.3.A - 21 December release

User notification for appropriate markup language

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
User notification for appropriate markup language. Since this checkpoint only refers to images, why notify for all BODY Elements? Why not just Images? Also, I don't understand what "All body elements" mean. There is just one "Body Element" since that term means the start tag, end tag, and everything in between. Do you mean all elements that are part of the Body Element's content?
Scope: Technique 2.1.A - 21 December release

Allow user to change the units of measure.

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Allow user to change the units of measure. What if the absolute units are in a style sheet?
Scope: Technique 3.4.A - 21 December release

Check document for missing quote markup

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Current browsers don't render Q, so Q isn't usable today.
Scope: Technique 3.7.A - 21 December release

ABBR values should be shorter than 15 characters.

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
The ABBR should be pronounceable since the purpose is to be read by speech technology in the future (cf. http://www.w3.org/TR/WAI-WEBCONTENT-TECHS/#data-tables )
Scope: Technique - 21 December release

User notification of dynamic content changes

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
"User notification of dynamic content changes." A SCRIPT elements will generate this user notification also, any Javascript, e.g. onmouseover=".... code which changes something somewhere..."
This also applies to:
- User notification of usability when programatic objects are disabled
- User notification of device independent event handlers.
Scope: Technique - 21 December release

Testing embedded technologies

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
"If any programmatic elements are found in the document, provide a user notification." tool should include means to test the embedded technologies, e.g. java, at least by running them, preferably by including any test software supplied for the technology.
Scope: Technique - 21 December release

Server-side to client-side image map conversion

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Are there any common formats for the server side information? If so, provide means to convert to client side image map.
Scope: Technique - 21 December release

Logical tab order

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Do we always display the warning for logical tab order or can we limit it in some way?
Scope: Technique - 21 December release

Keyboard shortcuts

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Do we always display the warning for keyboard shortucts or can we limit it in some way?
Scope: Technique - 21 December release

Title

Title of the techniques document
From: Wendy A Chisholm (wendy@w3.org) Date: Mon, Jan 24 2000
Scope: General - 21 December release
Proposals
- Techniques for evaluation and repair of Web content
- Evaluation and Repair tool accessibility guidelines
- Techniques for automatic implementation of the Web Content Accessibility Guidelines
- Techniques for evaluation and repair of *accessible* web content
- Techniques for Accessibility Evaluation and Repair Tools

Alternative pages

Discussion of 11.4
Scope: Checkpoint 11.4 - 21 December release
From: Wendy A Chisholm (wendy@w3.org) Date: Mon, Jan 24 2000
Issues:
1. When does a person receive a message about providing an alternative page?
2. What are some automatic checks that we can perform to determine if a page as been identified as an alternative page is up to date?
3. What action do we take if we identify/verify that an alternative page exists?

Michael's suggestions

ERT Review From: Michael Cooper (mcooper@cast.org) Date: Mon, Jan 24 2000
Lots of technical feedback including several proposals for new techniques.
Scope: - 21 December release

Issues that need clarification from the WCAG WG

There must be only one H1 element in the document

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Why only one H1? So actually we have a problem with WCAG: it doesn't define "and use them according to specification".
Scope: Technique - 21 December release

Mark up lists and list items properly

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
what does WCAG's "properly" mean, beyond passing HTML validity?
Scope: Technique - 21 December release

Use markup to associate data cells and header cells

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
"Use markup to associate data cells and header cells" is not needed if the HTML4 Algorithm can identify the headers.
Scope: Technique - 21 December release

Check table for valid "summary" attribute

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
"Check table for valid "summary" attribute" I don't understand this guideline. Isn't a caption enough and Table headers enough, at least if it's a simple table? A summary would merely recite what's in the caption and headers anyway.
Scope: Technique - 21 December release
Wendy notes that this issue was brought to the WCAG WG last week. WCAG thread: Table summary, caption, and title.

User notification of style sheet use.

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Issue: "User notification of style sheet use." A LINK element with a REL attribute set to 'stylesheet' will generate this notification." Also: if tags have style attribute set, or <STYLE> element is used.
Scope: Technique - 21 December release

Quantifying flicker

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Issue: "how do we quantitatively distinguish between flicker and slow changes in images? " Is it the 4-59 hz in wcag? What does "quick changes" mean? Would "quick changes" mean that you can't bring up a new screen, which is a quick change? How big does the area have to be to cause trouble?
Scope: Technique - 21 December release

Use W3C technologies

From: Leonard R. Kasday (kasday@acm.org) Date: Sun, Jan 23 2000
Issue: Must we insist on W3C technologies if there are other standards with good accessibility? AFter all in the authoring guidelines we ask for accessibility in the non-w3c technologies implementing the editor.
Scope: Technique - 21 December release

Closed Issues

Technique short phrases

proposal for technique short phrases From: Wendy A Chisholm (wendy@w3.org) Date: Sun, Jan 23 2000.
Accepted. Changes will appear in the 28 January 2000 Working Draft.

Priorities

Priorities From: Wendy A Chisholm (wendy@w3.org) Date: Sun, Jan 23 2000
Chris Ridpath clear is up: Techniques should inherit from checkpoint. 1.1.K was a typo.