Skip to content
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

Potential accessibility issue with date field pattern #3240

Open
JonathanCulling opened this issue Feb 2, 2023 · 3 comments
Open

Potential accessibility issue with date field pattern #3240

JonathanCulling opened this issue Feb 2, 2023 · 3 comments
Labels
accessibility concern Bug, feature request or question about the accessibility of a portion of a product (not a WCAG fail) accessibility date input validation errors Help users to recover from validation errors

Comments

@JonathanCulling
Copy link

What

I have recently been conducting accessibility research with Assistive Technology users on our service, which was built using the Gov.uk Design System. Our service is in public Beta, and it can be found at https://www.support-with-employee-health-and-disability.dwp.gov.uk/support-with-employee-health-and-disability

Why

We interviewed 2 blind JAWS (screen reader) users and both had problems inputting a date into our system. Both had suggestions, based on their experience using other websites, about how date entry could be clearer for them and error free.

Anything else

I have attached a slide from my report co
GDS standard potential issues 1
vering this potential issue. Please can someone let me know if we could take this feedback into consideration and update the design standard?

@querkmachine querkmachine added the awaiting triage Needs triaging by team label Feb 2, 2023
@querkmachine
Copy link
Member

Hello! Thanks for your feedback. I'm going to shift this over to our Frontend repository. We have an ongoing discussion about date inputs here: alphagov/govuk-design-system-backlog#42.

We have also previously published a blog post with our findings using dropdowns for date input. There we found that they presented more problems for users compared to text inputs: https://designnotes.blog.gov.uk/2013/12/05/asking-for-a-date-of-birth/

@querkmachine querkmachine transferred this issue from alphagov/govuk-design-system-backlog Feb 2, 2023
@stevenjmesser
Copy link

Hi @JonathanCulling, do you have an indication of the proportion of users affected in your testing? How many users in total did you test with? What percentage of those users were using JAWS?

Trying to establish whether this is a finding where all JAWS users encounter the same problem or only a proportion do. That will help in assessing it alongside other issues.

Please do let us know. If we don't hear back in 2 weeks' time we'll close this issue, but it is linked to the ongoing discussion so will be reviewed (as previously mentioned).

@JonathanCulling
Copy link
Author

Hello Steven,
We conducted face-to-face research with 11 AT users, 10 of whom used some form of screen reader. Of these:
• 2 JAWS readers had the problem identified,
• 8 users of other screen readers (NVDA, Voiceover, Read&Write, Microsoft built-in screenreader) did not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility concern Bug, feature request or question about the accessibility of a portion of a product (not a WCAG fail) accessibility date input validation errors Help users to recover from validation errors
Projects
Development

No branches or pull requests

4 participants