-
Notifications
You must be signed in to change notification settings - Fork 19
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
Dispatch: Special Issues checkboxes are not grouped together (End: 7/10) #12123
Comments
Alisa can you tell me where this view (the url) is located? |
Sure - these issues are all related to Caseflow Demo: www.caseflowdemo.com This specific issue is on http://www.caseflowdemo.com/dispatch/establish-claim/1#/decision |
@alisan16 Does a solution to this problem require testing with JAWS or is VoiceOver testing considered to be sufficient? Asking after I peaked in on issue 12096 |
@ajspotts Yes, please take a look at the linked epic for instructions for how to reproduce and test the issues. You can use the standard screenreader installed on your computer, which on Mac is Voiceover and on Windows is Narrator, I believe. If you have access to a GFE or CAG Windows computer, the JAWS program should be installed and you can use that as well. |
Resolved by this ticket |
Reopening, per the latest accessibility audit this is not resolved:
|
@araposo-tistatech The Mac screen reader only reads the checkbox group once the first time you interact with it. Subsequently, it does not include the group information when reading each checkbox. This behavior is happening on the Dispatch page, as well as the W3 page. The code for the page does have the recommended HTML code to group the checkboxes, using a fieldset with a legend (here's a snippet just from the top, and the checkboxes are contained within the fieldset). This was added in Alec's PR here.
|
Here's a screenshot of the first time the voiceover reader interacts with a checkbox within the group. Same happens if it's another checkbox in the right column of checkboxes, but only if it's the first one we interact with. Since this is the same behavior as the example of the standard, not sure what else we can do. |
@chandracarney please see the above and advise how we should move forward. |
Checked this out with JAWS today too, and am seeing similar behavior. The first checkbox item gets the group title announced, but not every checkbox. Same for the W3 page. If navigating away from the checkbox group, and then back again, it reads the group name again for the first checkbox item. Here's some notes from the JAWS voice text: When navigating to the checkbox group - reads group for first one only Navigating back to the above element Reads the group again when we go back |
Checkboxes need to be grouped and labeled for 'Special Issues' on Establish Next Claim page
On the Establish Next claim page the label: Special Issue(s) is not read with the check box selections for assistive technology users. (New: 08/27/2019) The boxes need to be grouped and the label read “select special issue(s)” with all the checkboxes
Suggested fix: https://www.w3.org/WAI/tutorials/forms/grouping/
The text was updated successfully, but these errors were encountered: