- From: Wendy A Chisholm <wendy@w3.org>
- Date: Thu, 17 Feb 2000 13:55:13 -0500
- To: w3c-wai-er-ig@w3.org
Len wrote the following comments [1] in reference to the 21 December 2000 release [2]: <blockquote> | Technique 3.1.A [priority 2] User notification for appropriate markup | language | | Evaluation: | | * All BODY elements will generate a user notification. LRK:: 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? </blockquote> This is an interesting question. Yes, primarily when IMG elements or OBJECT used to embed images are identified, the author ought to be asked if the image could be converted to an appropriate markup language (MathML, HTML with style sheets, etc.). However, are there cases where another element within the body of the document could be converted to a markup language? For example, PRE elements to layout numbers converted to a TABLE, or PDF converted to HTML or in the future ascii art could be converted to SVG. Is there a case where something in a P element should be marked up? ascii art is the only thing I can think of. Headers, forms, lists...all seem to be marked up well. Tables being converted to style sheets are covered in other checkpoints. Therefore, I think I disagree that all elements in the BODY element should generate this warning. I think it should be limited to: IMG OBJECT/EMBED PRE what about the future? what about XML? RDF? --wendy [1] http://lists.w3.org/Archives/Public/w3c-wai-er-ig/2000Jan/0059.html [2] http://www.w3.org/WAI/ER/IG/ert/ert-19991221.html -- wendy a chisholm world wide web consortium web accessibility initiative madison, wi usa tel: +1 608 663 6346 /--
Received on Thursday, 17 February 2000 13:51:20 UTC