W3C

Edit comment LC-544 for Accessibility Guidelines Working Group

Quick access to

Previous: LC-1320 Next: LC-647

Comment LC-544
:
Commenter: Greg Gay <g.gay@utoronto.ca> on behalf of ATRC UofT

or
Resolution status:

Item Number: Success Criterion 4.1.1
Part of Item:
Comment Type: TE
Comment (Including rationale for any proposed change):

In guideline 4.1.1 does "parsed unambiguosly" mean "well formed" or "valid"? The techniques seem to suggest that markup must be valid, though you would be hard pressed to find invalid code that disrupts any relatively recent screen reader's ability to read a Web unit. It takes severely broken markup to affect accessibility, or specific types of errors (such as broken table structures). While I am all for valid markup, it is *not* a requirement for accessibility in most cases, particularly at level 1. I can see this requirement at level 2 perhaps.

Proposed Change:

What would be appropriate here to have a well formed requirement at level 1, and valid at level 2. And still this really has to do with compatibility with future technologies, rather than affects on accessibility using current technologies.
(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: 544.html,v 1.1 2017/08/11 06:41:39 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org