W3C

Site Navigation

Nearby

Results of Questionnaire WCAG2ICT-SC 1.4.12 Text Spacing readiness to incorporate into editors draft

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-02-24 to 2023-03-08.

6 answers have been received.

Jump to results for question:

Review of proposal for Success Criterion 1.4.12 Text Spacing

1. Review of proposal for Success Criterion 1.4.12 Text Spacing

The draft proposal for the section Guidance When Applying Success Criterion 1.4.12 to Non-Web Documents and Software has been updated from previous input and discussions. Review the latest proposal and indicate if you agree. Note any suggested edits for improvement and/or reasoning in the comments field.

Summary

Choice	All responders
Choice	Results
The proposal can be incorporated into the WCAG2ICT editor's draft as-is.	1
The proposal can be incorporated into the WCAG2ICT editor' draft with some changes.	3
The proposal isn't ready to incorporate yet.	2

Details

Responder	Review of proposal for Success Criterion 1.4.12 Text Spacing	Comments
Sam Ogami	The proposal can be incorporated into the WCAG2ICT editor's draft as-is.
Mitchell Evan	The proposal isn't ready to incorporate yet.	I'm looking at this proposal: https://github.com/w3c/wcag2ict/issues/62#issuecomment-1441968689 I agree with "Summarized list of changes" where it says "the S.C. doesn’t require that the markup is exposed for user modification" Yet the word substitution still says "markup is exposed and available to user modification". This direct contradiction leaves me unclear what I'm voting on.
Mike Pluke	The proposal isn't ready to incorporate yet.	I agree with Mitchell Evan that there definitely seems to be some internal contradictions. It is not the markup that needs to be modifiable, it is the text style properties that need to be modifiable. I think we need to end up with something like: In content implemented using markup languages in a way that supports modification of the following text style properties; no loss of content or functionality occurs by setting all of the following and by changing no other style property: ...
Laura Miller	The proposal can be incorporated into the WCAG2ICT editor' draft with some changes.	Agree with the contradiction mentioned by Mitchell but propose to change the addition "in such a way that the markup is exposed and available to user modification" to "if markup is exposed and available to user modification" This would remove the contradiction.
Fernanda Bonnin	The proposal can be incorporated into the WCAG2ICT editor' draft with some changes.	To answer the concern outlined on answers to the questionnaire about a contradiction, the summary of changes says: "Added clarification on note 1, to represent that the S.C. doesn’t require that the markup is exposed for user modification. Kept the examples as they can help understand cases on how the markup could be exposed for users to modify." The comment is addressing previous feedback that Note 1 could suggest that the author had a responsibility to implement a mechanism to allow the user to change text spacing properties; thus the change in Note 1 is adding the following text: "However, this S.C. does not require that content implement its own mechanisms to allow users to change the text spacing properties." The substitution text from the S.C. text: replacing "In content implemented using markup languages that support" with "For non-web documents or software using markup languages that are exposed to user manipulation and that support" was proposed in a previous TF meeting and not modified in this last iteration of the proposed text. This is following a similar pattern than 4.1.1 Parsing. As a proposal: we could completely eliminate the addition of: "in such a way that the markup is exposed and available to user modification" as this is covered in Notes 1 and 2. This would leave the guidance text as close as possible with the original S.C. text.
Mary Jo Mueller	The proposal can be incorporated into the WCAG2ICT editor' draft with some changes.	on. The idea is that if the content is implemented in markup, including text properties, and if those text properties are exposed in such a way that a user can modify them (but that mechanism isn't the responsibility of the non-web document or software to implement), then this SC applies. The difficulty is getting the language of the SC to reflect that clearly enough without misinterpretation. I've taken a stab at it in my comment on the issue: https://github.com/w3c/wcag2ict/issues/62#issuecomment-1461274257