Part of Item:
Comment Type: TE
Comment (Including rationale for any proposed change):
The term "parsed unambiguously" is ambiguous. Parsing requires a set of rules and without those rules the parsing result may be meaningless. For example, an HTML file may be parsed using the rule "by line". It may also be parsed using the rule "by sentence and word". This parsing will produce an unambiguous tree structure but has no effect on accessibility. I believe the intent of the SC is to include the set of rules (e.g. DTD or schema) that has an effect on accessibility.
Include text that specifies the set of rules needed to parse the document. Example: "Web units or authored components can be parsed unambiguously using the specification that affects accessibility...". In the techniques document you can specify the appropriate rules such as in HTML use one of the standard DTDs.
We have reworded SC 4.1.1 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.