-
Notifications
You must be signed in to change notification settings - Fork 237
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
Add guidance for accessibility of details component #3904
base: main
Are you sure you want to change the base?
Conversation
Add more reference to the accessibility issues for Dragon users.
✅ You can preview this change here:
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A very minor preferential point on link text, plus a full stop. I'm not gonna kick off about the preference tbh. This looks all good otherwise.
src/components/details/index.md
Outdated
@@ -45,4 +45,4 @@ Make the link text short and descriptive so users can quickly work out if they n | |||
|
|||
There is [evidence that some users avoid clicking the link to show more details](https://github.com/alphagov/govuk-design-system-backlog/issues/44#issuecomment-629122091), as they think it will take them away from the page. | |||
|
|||
There are [concerns that some users of voice assist software will not be able to interact with the component](https://github.com/alphagov/govuk-design-system-backlog/issues/44#issuecomment-628082040). Some software might require the user to specifically refer to the link to show more details as a button in order to interact with it. | |||
It is known that [some users of voice assist software will not be able to interact with the component](https://github.com/alphagov/govuk-design-system-backlog/issues/44#issuecomment-628082040). Some software might require the user to specifically refer to the link to show more details as a button in order to interact with it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not anything you changed, but I find the second sentence confusing. I've read it 3 times now and can't work out what it's trying to tell me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@calvin-lau-sig7 are you able to help me with making this a bit clearer?
Co-authored-by: Owen Jones <64783893+owenatgov@users.noreply.github.com> Co-authored-by: Ed Horsford <mail@edwardhorsford.com>
What
Add more reference to the accessibility issues for Dragon users.
Why
After visiting the Digital Accessibility Centre (DAC) and meeting a user of Dragon in and out of work, I was made aware of the difficulty they experience when using details components on pages.
I also witnessed how the language we used in our details guidance to refer to the issue made them feel untrusted.
This change is likely something we can do alongside improving the component.