W3C

Edit comment LC-486 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1413 Next: LC-580

Comment LC-486
:
Commenter: Chris Ridpath <chris.ridpath@utoronto.ca>

or
Resolution status:

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.

Proposed Change:

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.
910
(space separated ids)
(Please make sure the resolution is adapted for public consumption)


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: 486.html,v 1.1 2017/08/11 06:41:35 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org