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

Content after the Start button referenced on website #4026

Closed
Tracked by #4167
selfthinker opened this issue Aug 9, 2024 · 1 comment · Fixed by #4170
Closed
Tracked by #4167

Content after the Start button referenced on website #4026

selfthinker opened this issue Aug 9, 2024 · 1 comment · Fixed by #4170
Assignees
Labels
accessibility audit july 2024 Issues from July 2024 external accessibility audit against WCAG 2.2 criteria

Comments

@selfthinker
Copy link
Contributor

This issue is from the accessibility audit of the Design System website by DAC in July 2024.

DAC's description

The placement for information that users may need to complete the service is located after the button used to start the service. Many users, including those who rely on screen reading software or enhanced screen magnification, navigate web content sequentially. If essential information is placed after the button, they might miss it because they are not aware they need to keep navigating beyond the button.

Screenshot which is used as an example on the website of a GOV.UK page showing content after the Start button

DAC's proposed solution

Consider placing the ‘Before you start’ heading and its following information to be placed before the control to start the service, so that all users can access it.

Background information

This is a known issues for start pages on www.gov.uk, nothing directly to do with the GOV.UK Design System, so nothing we can change directly.
But what we can do, though, is to update screenshots and update the guidance to reflect the best practice.

Related issues

Additional instances

This is a specific content issue that only appears on this page.

Needed roles

Content designer, designer

@selfthinker selfthinker added accessibility audit july 2024 Issues from July 2024 external accessibility audit against WCAG 2.2 criteria labels Aug 9, 2024
@selfthinker
Copy link
Contributor Author

selfthinker commented Aug 28, 2024

Transaction pages have the start button. A choice of three pages that have no content underneath it:

That would be a replacement for the first screenshot.

But the second screenshot is for a guide that has multiple pages. There is only one suitable example under the first 10 example pages and that is:

But I'm not sure if that is a good example because there is a sizeable amount of text before the start button, so not great for a screenshot. I guess we could just use a screenshot from the middle of the page?

owenatgov added a commit that referenced this issue Oct 2, 2024
This is in response to an issue raised by DAC that  the screenshots we use are putting content after the start button which is an accessibility issue.

See #4026
owenatgov added a commit that referenced this issue Oct 8, 2024
This is in response to an issue raised by DAC that  the screenshots we use are putting content after the start button which is an accessibility issue.

See #4026
@owenatgov owenatgov self-assigned this Oct 9, 2024
owenatgov added a commit that referenced this issue Oct 16, 2024
This is in response to an issue raised by DAC that  the screenshots we use are putting content after the start button which is an accessibility issue.

See #4026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility audit july 2024 Issues from July 2024 external accessibility audit against WCAG 2.2 criteria
Projects
Status: Done 🏁
Development

Successfully merging a pull request may close this issue.

3 participants