-
Notifications
You must be signed in to change notification settings - Fork 25
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
EPIC: Review accessibility guidance #1948
Comments
Also from the 'WCAG 2.2 user research 2024', of the users that had used the per-profession accessibility guidance, they had accessed it when starting their role, as part of onboarding. They had not come back to it since. Two thoughts:
|
Also, DigInclusion's report on the accessibility guidance identified that we could add more info on all WCAG 2.1 criteria. For now, we have decided not to do that and only to highlight the 6 new criteria - in addition to design system updates. We do not know if our users will want more detail about all WCAG 2.1 criteria (these are covered in the accessibility checklist anyway) but we suspect this will be too much info for them. Worth exploring as part of the review. |
There are also some accessibility resources on NHSE's CoE SharePoint, including some duplicate content. |
We will be carry out some user research into people's needs around accessibility guidance, starting June 2024, and how we can better meet those needs in the service manual. |
Our analytics suggest that the accessibility guidance is not well used. Our WCAG 2.2 user research 2024 suggests that some professions (e.g. product and delivery, devs and designers) do not refer routinely or at all to the profession sections.
It would be worth reviewing the accessibility guidance - and how best to present accessibility requirements and best practice across:
Also taking into account cross-gov work on accessibility guidance and resources.
Can we better signpost and integrate the accessibility checklist in the service manual?
Tasks for this epic
Related backlog tickets
The text was updated successfully, but these errors were encountered: