Edit comment LC-927 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-882 Next: LC-1304

Comment LC-927: Comment Shortname:; Commenter: Andi Snow-Weaver <andisnow@us.ibm.com> on behalf of IBM; 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:
The term "parsed unambiguously" is difficult to understand.

Proposed Change:

Change 4.1.1 to ""The structure of and relationships within web units and authored components can be determined without the need for user agents or assistive technologies to perform error correction.""

Eliminate the term ""parsed unambiguously"".; Related issues: 910
(space separated ids); WG Notes: [TEAMC] MISSING COMMAS "The structure of, and relationships within, web units and authored components can be determined without the need for user agents or assistive technologies to perform error correction." CLAIMS ARE ON WEB UNITS AND AUTHORED UNITS ARE NOT REQUIRED TO MEET WHEN NOT IN A WEB UNIT SO IT BECOMES. "The structure of, and relationships within, web units can be determined without the need for user agents or assistive technologies to perform error correction." IF WE CONSIDER RELATIONSHIPS PART OF STRUCTURE THEN IT BECOMES "The structure of, including relationships within, web units can be determined without the need for user agents or assistive technologies to perform error correction." Discussed in the 29 March 2007 telecon: Resolution: close 4.1.1 issues with proposal as amended http://www.w3.org/WAI/GL/2007/03/29-wai-wcag-minutes.html {partial accept} SEE ACTIONS FOR LC-910 BBC: Updated resolution to match 1013. Response: http://lists.w3.org/Archives/Public/public-comments-wcag20/2007Jun/0080.html; Resolution: 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.; (Please make sure the resolution is adapted for public consumption)