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

Search and other forms of navigation #65

Closed
Angelsaur opened this issue Jan 26, 2021 · 2 comments
Closed

Search and other forms of navigation #65

Angelsaur opened this issue Jan 26, 2021 · 2 comments
Assignees
Labels
accessibility Improves accessibilty for users with diverse needs Community Inclusion Supports diverse inclusion and builds community documentation Improvements or additions to documentation Milestone 4 MVP accessibility checks

Comments

@Angelsaur
Copy link
Collaborator

Summary

You’ll need to do some checks to see how accessible your website’s navigation is. Navigation includes things like search, site maps and navigation categories

Deadline

20/02/2021

What needs to be done?

Check your navigation behaves consistently
Things like search bars and breadcrumb trails (the list of links that appear at the top of the page to show where in your website’s navigation you currently are) should behave in the same way wherever they appear on your website.

You can check for this by going to a few of your sample pages and checking whether the navigational elements are presented consistently. If things like search boxes or navigation menus appear in different places across the pages, you’re probably not meeting this requirement.

Check links do not trigger on the down-press of a mouse
To open a link, a user has to click their mouse (known as a ‘down event’) and release it (known as an ‘up event’).

You need to check that this is how your links behave. Check a sample of your content pages and interact with some of the links - specifically to see whether the links are opened on the down click of the mouse, or whether they only open once you release the mouse button.

If they’re triggered on the down event, you’re likely not meeting this requirement.

Who can help?

@Angelsaur Angelsaur added documentation Improvements or additions to documentation accessibility Improves accessibilty for users with diverse needs Community Inclusion Supports diverse inclusion and builds community labels Jan 26, 2021
@Angelsaur Angelsaur added this to the Accessibility milestone Jan 26, 2021
@GeorgiaHCA
Copy link
Collaborator

Interesting! I had never thought of this @Angelsaur - but it's a really great/useful thing to consider. I've checked all the pages and they pass this test (luckily finding/using deliberately accessible source code solved this one). Closing this issue as the criterium is met throughout the MVP!

@GeorgiaHCA GeorgiaHCA reopened this Apr 1, 2021
@GeorgiaHCA GeorgiaHCA added the Milestone 4 MVP accessibility checks label May 24, 2021
@gedankenstuecke
Copy link
Member

Made issue #369 to create an accessibility checklist that can be used for the MVP and going forward. Closing this along with other accessibility checklist items for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Improves accessibilty for users with diverse needs Community Inclusion Supports diverse inclusion and builds community documentation Improvements or additions to documentation Milestone 4 MVP accessibility checks
Projects
None yet
Development

No branches or pull requests

5 participants