Edit comment LC-1070 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-617 Next: LC-1071

Comment LC-1070: Comment Shortname:; Commenter: Gian Sampson-Wild <gian@tkh.com.au>; Message-id:; Section of the document concerned:

or; Refinement of the section concerned:; Status:
assigned to; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
Baseline CSS: This mapping essentially says that if CSS is in the baseline then information can be put into the style sheet and not in the HTML. This appears to allow formatting (ie headings) via CSS and not HTML, important images included in CSS and not HTML, etc. How is someone who uses a screen reader going to interpret this? How are they going to be able to access the information they require?

Proposed Change:

Clarify baseline requirements; Related issues: (space separated ids); WG Notes: [TEAMA] We have a problem with newer CSS where you can put information in the style sheet. THe question has come up -- DO WE HAVE TO EITHER we have to 1) never allow those technologies into the baseline OR 2) we need to profile standards saying that only some parts of the technology are in the baseline. This is a VERY BIG ISSUE. If CSS is IN the baseline though - we are saying Everyone can use CSS and you can use it to meet WCAG. so that would mean you CAN put content in the style sheet. Which leads to the following conclusion?? If CSS is in the baseline - then if you turn it off or override it you may lose content - but that is ok. CSS is in the baseline so you should be able to handle CSS so just dont turn it off. Is that where we want to be? Not clear at all. [AL] Yes! If CSS is in your baseline and you turn it off, you should expect a lost of content or failure to meet certain sc that the content otherwise would pass. Propose to {not-accept} . Discussed in the 19 April 2007 telecon: resolution: close as proposed http://www.w3.org/WAI/GL/2007/04/19-wai-wcag-minutes.html {accept} Response: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jul/0106.html New issue: http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=2333; Resolution: If CSS is an accessibility-supported Web technology, then the author can rely on it to satisfy success criterion. However, the success criterion must still be satisfied. So, for instance, if non-text content that conveys information is included via CSS, SC 1.1.1 requires that a text alternative also present equivalent information. This information must be programmatically determined, that is, exposed to assistive technologies. So even if most of the features or functionality of a Web technology are accessibility supported, it may not be possible to use certain functionality in the technology and still conform to WCAG. We have completely rewritten the Conformance section, and this should now be clearer.; (Please make sure the resolution is adapted for public consumption)