Part of Item:
Comment Type: substantive
Comment (including rationale for proposed change):
It\'s still unclear what \"parsed unambiguously\" means when applied to CSS documents. Even a loose interpretation is still a heavy burden for authors as this SC is level 1 and may not improve accessibility.
(This was discussed on list but no resolution.)
Proposed Change:
Clearly define what \"parsed unambiguously\" means when applied to CSS documents. Move SC to level 2 for CSS documents.
To make this requirement easier to understand, we have reworded SC 4.1.1 to clarify that it must be possible to parse content without the need for user agent repair. The revised SC reads as follows:
4.1.1 Content implemented using markup languages has elements with complete start and end tags, except as allowed by their specifications, and are nested according to their specifications. (Level A)
Note: Start and end tags that are missing a critical character in their formation, such as a closing angle bracket or a mismatched attribute value quote are not complete.
We believe this is appropriate at Level A for CSS as well as other technologies.