Re: Remarks on Checkpoints

> "A.5.2 Use foreground and background color combinations that 
>  provide sufficient contrast when viewed by someone with color 
>  deficits or when viewed on a black and white screen. [Priority 1]"
> 
> This in my view should apply only to raster images (e.g., GIF, JPEG) 

Good point on image, although one might argue this is also addressed
by alt and longdesc (i.e. if you can't see the image because of
colorblindess, you should be able to access the textual description)

> and to deprecated HTML methods, (attibitues of BODY, FONT). When style 
> sheets are used for colors, colorblind people or users of monochrome
> screens can (and should due to their special circumtances) override all 
> authors colors.

Beyond using Style Sheet, lots of UA will provide a setting to render
text with the desktop colors of choice, thus overiding author colors.

> "A.9.4 For pages that use style sheets, ensure that the contents of 
>  each page are ordered and structured so that they may read in the 
>  intended order even when the style sheet is not used. [Priority 1]"
> 
> This should be extended:
> "For pages that use style sheets or presentational markup, ensure that 
> the contents of each page are ordered and structured so that they may 
> read properly even when the style sheet and presentational 
> markup is oveeriden by the user. [Priority 1]"

Agreed.

> "A.1.3 For all image map links, provide alternative text for 
> each link (e.g., via the "alt" attribute of HTML AREA element). 
> [Priority 1]" 
> 
> This is confusing as there is no need for alternative if the content 
> of MAP is a paragraph with anchors. I propose:
> "For all image map links created with the AREA element, provide 
> alternative text for each link via the "alt" attribute. 
> [Priority 1]" 

I'd rather be inclusive than restrictive:
  "A.1.3 For all image map links, provide alternative text for 
  each link (e.g., via the "alt" attribute of HTML AREA element or the
  content of the A element). 
 
> "A.8.1 If a table is used for layout, do not use any structural 
>  markup for the purpose of visual formatting..."
> 
> This is a contradiction as TABLE itself is structural.
> Should be "If an HTML table is used for layout, use only TD 
>  to mark the table's cells."

Agreed, it's more focused like that.
 
> "A.13.5 Until user agents and screen readers are able to handle text 
>  presented side-by-side, all tables that lay out text in parallel, 
>  word-wrapped columns require a linear text alternative (on the 
>  current page or some other). [Priority 2]" 
> 
> This is a very dangereous checkpoint since it 
> encourages authors to use frames,

How come ?
As long as it's not a P1, I'm fine.

Received on Thursday, 7 January 1999 08:32:16 UTC