Admin: On the permits report page, in Chrome and IE with JAWS, the keyboard would only sporadically function correctly with the radio buttons

[JohnHewittCriterion]

Notes

On the permits report page, in Chrome and IE with JAWS, the keyboard would only sporadically function correctly with the radio buttons. Most of the time the radio buttons would not change values with the arrow keys. Refreshing the JAWS memory and reloading the page were tried to fix this but it would not always work. It was only sporadically successful in allowing the radio buttons to be changed with the arrow keys in both the Search by and To generate a report radio button groupings.

Same issue exists on Season Dates page: https://forest-service-trees-staging.app.cloud.gov/admin/christmas-trees/season-dates

Same issue exists on Districts Dates page: https://forest-service-trees-staging.app.cloud.gov/admin/christmas-trees/district-dates

Linkage: CTF-82
WCAG: 2.1.1 Keyboard

Acceptance criteria

• jaws works?

Tasks

• add alt text to the radios

Definition of Done

• Code unit / e2e tested and comply with QWASP
• No new security vulnerabilities
• Internal team code review
• Documentation / readme.md / CircleCI updated
• Docker updated
• Compare finished design with mockup
• Usability tested

[sadlerw]

This bug here? https://community.articulate.com/discussions/articulate-storyline/jaws-screen-reader-and-radio-buttons-sl2#reply-425609

We can add alt text. Do you have any information about the bug in JAWS that would break the keyboard though? I don't know how to fix that.

[JohnHewittCriterion]

Yes, that seems like the bug identified.

As for the keyboard, if it's just JAWS and it's inconsistent then we'll have to note it in the accessibility statement and wait on JAWS for a fix.

[sadlerw]

I can confirm that at least in osx voice over in safari right and left arrows work fine with the radios

[sadlerw]

ok I added aria-labelledby on the forest radios - I think that might have been the issue

[sadlerw]