W3C

Site Navigation

Nearby

Results of Questionnaire WCAG2ICT - Review updated proposals for SC problematic for closed functionality bullets

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-08-25 to 2023-08-30.

5 answers have been received.

Jump to results for question:

1.3.2 Meaningful Sequence
1.4.12 Text spacing

1. 1.3.2 Meaningful Sequence

This survey is about bullets aimed for the SC Problematic for Closed Functionality section. In the 3 August meeting, the group discussed 1.3.2 Meaningful Sequence and was split between the first two options below thinking that option 2 was too verbose. Option 3 is an attempt to make this less verbose, yet still clear. Indicate which is your preference, and indicate any language tweaks or suggestions in the entry field below.

Option 1:

1.3.2 Meaningful Sequence—Requires information in a programmatically determinable form; a correct reading sequence output that helps the user correlate information that is provided auditorily or through some other non-visual means with the corresponding information displayed on the screen.

Option 2:

1.3.2 Meaningful Sequence—Requires information in a programmatically determinable form. It is recommended that a correct reading sequence be output to help the user correlate information that is provided by the accessibility features of the closed system in auditory form or through some other non-visual means with the corresponding information displayed on the screen.

Option 3:

1.3.2 Meaningful Sequence—Requires information in a programmatically determinable form. Instead, closed functionality software provides a meaningful reading sequence through auditory output or some other non-visual means that helps users correlate the output with with the corresponding information displayed on the screen.

Summary

Choice	All responders
Choice	Results
Prefer option 1, as-is
Prefer option 1, with changes
Prefer option 2, as-is	1
Prefer option 2, with changes
Prefer option 3, as-is
Prefer option 3, with changes	4
Something else. Make a suggestion in the entry field below.

Details

Responder	1.3.2 Meaningful Sequence
Olivia Hogan-Stark	Prefer option 3, with changes	Attempted to rephrase 3 for readability. WCAG 1.3.2 Meaningful Sequence—Information must be presented in a programmatically determinable form. In the case of closed functionality software, a meaningful reading sequence must be provided through auditory output or some other alternative non-visual means that help users correlate the output with the corresponding on-screen information.
Fernanda Bonnin	Prefer option 2, as-is
Loïc Martínez Normand	Prefer option 3, with changes	I propose a minor change to option 3, saying that closed functionality software "can provide" instead of "provides". Full proposal below: 1.3.2 Meaningful Sequence—Requires information in a programmatically determinable form. Instead, closed functionality software *can provide* a meaningful reading sequence through auditory output or some other non-visual means that helps users correlate the output with with the corresponding information displayed on the screen.
Mike Pluke	Prefer option 3, with changes	I support option 3 with the change proposed by Loïc.
Mary Jo Mueller	Prefer option 3, with changes	Olivia's edits using "must" can't be done, as we need to avoid normative language. To be consistent with other SCs that talk about programmatic information, I think it's best to leave the first sentence as-is. I do like Loïc's changes. There's an extra "with" in the proposals that need removing.

2. 1.4.12 Text spacing

This survey is about bullets aimed for the SC Problematic for Closed Functionality section. The TF discussed 1.4.12 Text Spacing in meetings on the 10th and 17th of August. We were close to consensus on edits to the proposed bullet in two proposed edits we worked on, noted below. Indicate which is your preference, and indicate any language tweaks or suggestions in the entry field below.

Option 1:

1.4.12 Text Spacing—Applicability of this Success Criterion to closed functionality software is limited to software implemented using markup languages, which is rare. Closed functionality technologies also rarely support user modification of line, paragraph, letter or word spacing; this requirement is only applicable to systems that do support these modifications.

Option 2:

1.3.2 Meaningful Sequence—Closed functionality software rarely supports user modification of line, paragraph, letter or word spacing. In such infrequent cases the Success Criterion applies as noted in the Guidance on Applying Success Criterion 1.4.12 to Non-Web Documents and Software.

Summary

Choice	All responders
Choice	Results
Prefer option 1, as-is	1
Prefer option 1, with changes
Prefer option 2, as-is
Prefer option 2, with changes	4
Something else. Make a suggestion in the entry field below.

Details

Responder	1.4.12 Text spacing
Olivia Hogan-Stark	Prefer option 2, with changes	Attempted to rephrase 2 for readability. Would be okay with as-is. 1.3.2 Meaningful Sequence—In closed functionality software the ability for users to modify line, paragraph, letter, or word spacing is rarely supported. However, if encountered, the Success Criterion applies as noted in the Guidance on Applying Success Criterion 1.4.12 to Non-Web Documents and Software.
Fernanda Bonnin	Prefer option 1, as-is	survey question 2 option 2 says "meaningful sequence" instead of text spacing.
Loïc Martínez Normand	Prefer option 2, with changes	My change proposal is only an editorial one. Option 2 in the survey starts with "1.3.2 Meaningful Sequence", and it should start with "1.4.12 Text Spacing".
Mike Pluke	Prefer option 2, with changes	Option 2 is fine with the name change that Loïc highlighted.
Mary Jo Mueller	Prefer option 2, with changes	Yes, copied the survey question when creating the survey and neglected to change the SC name in the 2nd option. That needs fixing. Also needs an oxford comma in the first sentence.