w3c/wbs-design
or
by mail to sysreq
.
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-10-20 to 2023-11-01.
9 answers have been received.
Jump to results for question:
Review the draft proposal for Applying SC 2.5.7 Dragging Movements to Non-Web Documents and Software. Indicate whether this proposal is ready to incorporate into the editor's draft and note any desired changes.
Choice | All responders |
---|---|
Results | |
The proposed content is ready to incorporate into the editor's draft, as-is. | 6 |
The proposed content is ready to incorporate into the editor's draft, with the following changes. | 3 |
The proposal isn't ready yet. |
Responder | Review of proposed content for 2.5.7 Success Criterion Dragging Movements | Comments |
---|---|---|
Phil Day | The proposed content is ready to incorporate into the editor's draft, as-is. | |
Olivia Hogan-Stark | The proposed content is ready to incorporate into the editor's draft, as-is. | |
Mary Jo Mueller | The proposed content is ready to incorporate into the editor's draft, with the following changes. | Wondering if we should have separate non-web document and non-web software notes more similar to the ones we developed for SC 2.5.1 Pointer Gestures. This was done because user agents are software applications, so we want to scope them into meeting this SC. See https://deploy-preview-245--wcag2ict.netlify.app/#applying-sc-2-5-1-pointer-gestures-to-non-web-documents-and-software If we did this to be consistent with 2.5.1, the bullets might look more like this: (non-web documents) NOTE: This requirement applies to [content] that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology). (non-web software) NOTE: This requirement applies to [non-web software] that interprets pointer actions (i.e. this does not apply to actions that are required to operate the [underlying platform software] or assistive technology). |
Loïc Martínez Normand | The proposed content is ready to incorporate into the editor's draft, with the following changes. | I agree with Mary Jo's proposal of separate notes for non-web documents and non-web software, to make clear that non-web documents must deal with the SC if they go beyond user-agent input management, and that non-web software do so the same, but in relation with the underlying software platform. I'm also suggesting to add a second note for non-web documents, based on note 2 for 2.5.1: Note 2 Dragging movements for operation are less common in documents. An example where a document author could add such input is an interactive prototype document created in a software design tool. |
Bruce Bailey | The proposed content is ready to incorporate into the editor's draft, as-is. | I am not clear what WCAG2ICT should say about non-web documents. Application to non-web software is spot on. |
Mike Pluke | The proposed content is ready to incorporate into the editor's draft, with the following changes. | I agree with Mary Jo's comment about separating the guidance for software and to documents. |
Devanshu Chandra | The proposed content is ready to incorporate into the editor's draft, as-is. | |
Sam Ogami | The proposed content is ready to incorporate into the editor's draft, as-is. | |
Gregg Vanderheiden | The proposed content is ready to incorporate into the editor's draft, as-is. |
Is a bullet needed in the SC Problematic for Closed Functionality section for 2.5.7 Dragging Movements? If so, please suggest the text.
Choice | All responders |
---|---|
Results | |
No bullet needed. Applies, as written, to closed functionality software. | 9 |
Bullet needed in the SC problematic for closed functionality section. Explain. |
Responder | 2.5.7 Dragging Movements relevance to SC problematic for Closed Functionality | Comments |
---|---|---|
Phil Day | No bullet needed. Applies, as written, to closed functionality software. | Any examples I can think of with Closed functionality using dragging would fall under the 'essential' exception and are therefore already covered by the SC. |
Olivia Hogan-Stark | No bullet needed. Applies, as written, to closed functionality software. | |
Mary Jo Mueller | No bullet needed. Applies, as written, to closed functionality software. | |
Loïc Martínez Normand | No bullet needed. Applies, as written, to closed functionality software. | |
Bruce Bailey | No bullet needed. Applies, as written, to closed functionality software. | 2.5.7 is not problematic for Closed Functionality section. A bit off topic, but this question reminds me that I think we need a search and replace on "closed functionality software" to "software with closed functionality". |
Mike Pluke | No bullet needed. Applies, as written, to closed functionality software. | |
Devanshu Chandra | No bullet needed. Applies, as written, to closed functionality software. | |
Sam Ogami | No bullet needed. Applies, as written, to closed functionality software. | |
Gregg Vanderheiden | No bullet needed. Applies, as written, to closed functionality software. |
Review the WCAG definition for dragging movements. Indicate whether this term can be added to the section "Glossary Items that Apply to All Technologies". If not, indicate what specific non-web guidance is needed.
Choice | All responders |
---|---|
Results | |
Yes, the term applies to all technologies. | 9 |
No, the term needs some WCAG2ICT guidance. Explain. |
Responder | Adding the new term "dragging movements" | Comments |
---|---|---|
Phil Day | Yes, the term applies to all technologies. | |
Olivia Hogan-Stark | Yes, the term applies to all technologies. | |
Mary Jo Mueller | Yes, the term applies to all technologies. | |
Loïc Martínez Normand | Yes, the term applies to all technologies. | |
Bruce Bailey | Yes, the term applies to all technologies. | |
Mike Pluke | Yes, the term applies to all technologies. | |
Devanshu Chandra | Yes, the term applies to all technologies. | |
Sam Ogami | Yes, the term applies to all technologies. | |
Gregg Vanderheiden | Yes, the term applies to all technologies. | the definition is bad -- and should have been changed in WCAG as well. Dragging motions are used for many things -- and are dragging motions even when " the element (or a representation of its position) " does NOT follow the pointer. but we can't change WCAG -- and this applies here exactly the same as it does in WCAG -- so .... but if we want to we could say "Applies as written with x replacing y (as usual) but add a note NOTE: With some dragging motions " the element (or a representation of its position) " does not follow the cursor. |
The following persons have not answered the questionnaire:
Send an email to all the non-responders.
Compact view of the results / list of email addresses of the responders
WBS home / Questionnaires / WG questionnaires / Answer this questionnaire
w3c/wbs-design
or
by mail to sysreq
.