Closed dav-idc closed 1 year ago
Popping this comment here so it doesn't get lost on the other card: https://github.com/alphagov/govuk-frontend/issues/3464#issuecomment-1582807104
Comment from @davidc-gds on Slack, copied here for posterity:
this one would be real nice to see if we can resolve in some tricky way. If we can figure it out, would be a good bit to contribute and share with other design systems too. If we can’t figure it out, then it’s a good one to include in the ‘usability’ portion of our accessibility statement.
The accessibility statement has been updated to include this issue. https://github.com/alphagov/govuk-design-system/pull/2995
This issue is from May 2023 external accessibility audit report.
Usability issue
Issue ID: DAC_Usability_Detail_Component_01
URLs: https://signin.account.gov.uk/sign-in-or-create
Screen shots
The details component ‘About GOV.UK One Login’, is not easily accessible for all user groups. The details element is no recognised by verbal commands for users navigating with Dragon Naturally Speaking, and the user is required to use verbal keyboard commands such as ‘press tab’. For users of screen reading assistive technologies the details component does not convey its state or functionality for users navigating with VoiceOver.
Current code ref(s)
#main-content > div > div > details
User comments
Screen reader user
Voice activation user
Solution
Consider using a button for the default detail component as this will mean it is recognised by and will convey its correct state to all assistive technologies.