W3C

Site Navigation

The results of this questionnaire are available to anybody. In addition, answers are sent to the following email address: maryjom@us.ibm.com

This questionnaire was open from 2023-11-13 to 2023-11-15.

9 answers have been received.

Jump to results for question:

Review the draft proposal to add WCAG 2.0 and 2.1 guidance to the section Applying SC 4.1.1 Parsing to Non-Web Documents and Software. The specific changes are in Pull request 262. Indicate whether this update is ready to be incorporated into the editor's draft.

Choice	All responders
Choice	Results
Incorporate the update, as-is.	8
Incorporate the update, with edits.	1
Something else.

Responder	Review of updated proposal for Success Criterion 4.1.1 Parsing	Comments
Mitchell Evan	Incorporate the update, as-is.
Fernanda Bonnin	Incorporate the update, as-is.
Phil Day	Incorporate the update, as-is.
Mike Pluke	Incorporate the update, as-is.
Sam Ogami	Incorporate the update, as-is.
Olivia Hogan-Stark	Incorporate the update, as-is.
Mary Jo Mueller	Incorporate the update, as-is.
Bruce Bailey	Incorporate the update, as-is.
Loïc Martínez Normand	Incorporate the update, with edits.	I see some normative language (should) in text that I think is non-normative. I suggest to change the wording to avoid using "should". First appearance under the heading "WCAG 2.0 and 2.1 Guidance": "... Therefore, the application of 4.1.1 Parsing to non-web documents and software should follow the new guidance provided..." I suggest: "Therefore, the application of 4.1.1 Parsing to non-web documents and software is to follow the new guidance provided..." Second "should", in note 2 (last sentence): "Therefore, 4.1.1 Parsing should no longer be a requirement for accessibility." I suggest: "Therefore, 4.1.1 Parsing is no longer a requirement for accessibility."