-
Notifications
You must be signed in to change notification settings - Fork 355
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update multi-thumb slider design pattern #221
Comments
modified aria-practices.html: In the multi-thumb slider design pattern, made the following changes. 1. Added link at the beginning of the section to issue 221. 2. Rephrased introduction to simplify language and clarify meaning. 3. replaced keyboard interaction list with a link to the single thumb slider pattern. 4. Revised roles, states, and properties section to be consistent with APG editorial guidelines. 5. replaced links to external examples with link to issue 124.
Per discussion in teleconference on Jan 23, 2017, removed suggestion to implement aria-controls. It is not clear how assistive technologies would be able to exploit aria-controls in order to enhance the accessibility of a multi-thumb slider. |
Group thinks this is a good idea - perhaps a filter for max min required price.
Yes this needs to be done. |
For issue #221, made editorial revisions to the multi-thumb slider (id="slidertwothumb") design pattern in aria-practices.html. 1. Clarified wording of description. 2. Added link to single-thumb slider pattern in the description. 3. Changed format of example section to paragraph instead of list because there is only one example. 4. Changed target of link in keyboard interaction to go directly to the keyboard interaction section of single-thumb slider. 5. Removed a "must" from the roles, states, and properties.
No issues detected. |
Thank you @annabbott! Closing as complete. |
The multi-thumb slider design pattern
is largely complete. However, some open issues remain.
On December 13, 2016, I made revisions to improve consistency with the APG editorial guidelines, and noticed the following potential deficiencies in the pattern.
Final Review Requested October 22, 2017
All required changes and editorial cleanup are complete. The task force has previously discussed changes. Need only double-check of final editorial revisions.
The text was updated successfully, but these errors were encountered: