summary of the 8 proposals for checkpoint 3.1

We now have eight proposals to choose from.  So much for trying to narrow 
it down to one proposal...

1. <blockquote> 3.1 Use markup rather than raster-based images to convey 
information. [Priority 2] This checkpoint is strongly tied to checkpoint 
11.1. Note: Until style and graphic markup languages are more common, 
minimize the use of text in images. For example, use HTML text styled with 
CSS. Choose common fonts (such as Arial and Times) that can be rendered 
using CSS. You may use text in images for logos and limited accent elements 
where specialized fonts and text treatments are required and cannot be 
achieved with CSS. </blockquote>
http://lists.w3.org/Archives/Public/w3c-wai-gl/2000OctDec/0290.html

2. This revision conveys part of the message of the current 3.1; the Note 
does not convey the part about "style sheets to format text and control 
layout". This isn't so bad since that requirement is covered by checkpoint 
3.3. Therefore I recommend in a clarification to WCAG 1.0 that the clause 
"use style sheets to format text and control layout [rather than images]" 
be moved to 3.3 as an example.
http://lists.w3.org/Archives/Public/w3c-wai-gl/2000OctDec/0298.html

3. <blockquote> 3.1 When an appropriate markup language exists, use markup 
rather than images to convey information. [Priority 2] For example, use SVG 
for line art, MathML to mark up mathematical equations, and CSS for 
text-oriented special effects. Avoid using images to represent text 
(including in repeated navigation elements) -- use text and style sheets 
instead. You may use text in images for logos and limited accent elements 
where specialized fonts and text treatments are required and cannot be 
achieved with CSS. Refer also to guideline 6 and guideline 11. </blockquote>
http://lists.w3.org/Archives/Public/w3c-wai-gl/2000OctDec/0288.html

4. <blockquote> 3.1 When an appropriate markup language exists, use markup 
rather than images to convey information. [Priority 2] For example, use SVG 
for line art, MathML to mark up mathematical equations, and CSS for 
text-oriented special effects. Avoid using images to represent text 
(including in repeated navigation elements) -- use text and style sheets 
instead. You may use text in images for logos and limited accent elements 
where specialized fonts and text treatments are required and cannot be 
achieved with markup. Refer also to guideline 6 and guideline 11. 
</blockquote>
http://lists.w3.org/Archives/Public/w3c-wai-gl/2000OctDec/0291.html

5. You may use text in images when the text does not convey its literal 
meaning, but has a more grafical function, if the effect cannot be achieved 
with CSS, (as in the case of some for logos and limited accent elements) 
provided that you provide a textual equivalent to the content contained in 
the image.
http://lists.w3.org/Archives/Public/w3c-wai-gl/2000OctDec/0303.html

6. i would add (to proposal #1)
<blockquote> provided that you provide a textual equivalent to the content 
contained in the image. (Refer to Checkpoint 1.1)
</blockquote>
http://lists.w3.org/Archives/Public/w3c-wai-gl/2000OctDec/0301.html

7. Can't we just vote on the question, "Are small graphical text buttons 
level two compliant?" from private e-mail from Bruce Bailey.

8. Delete checkpoint 3.1.
http://lists.w3.org/Archives/Public/w3c-wai-gl/2000OctDec/0286.html

--wendy
--
wendy a chisholm
world wide web consortium
web accessibility initiative
madison, wi usa
tel: +1 608 663 6346
/--

Received on Thursday, 26 October 2000 14:58:12 UTC