Accessibility finding
The same component, icon or destination has different names on different pages
Accessibility Warning Severity: Medium
Part of the audit The same function is named differently across pages. Finding id: accessibility.consistentIdentification.
What it costs you
People who use a screen reader, and people who find new layouts hard, learn a control by its name. When 'Search' is 'Find' on the next page, they have to work out again what it does.
What to do
Worth checking; we assume the name most pages use is the one that was meant. Pick one name per function and print it from one shared component, so it cannot drift.
What it checks
- Same icon with different names
- Same destination with different link text
- Navigation order changes between pages
- Search or login labeled differently
- Help in a different place on some pages
How to fix it
Print the control from one shared component
- Find the templates behind the pages that use the less common name.
- Replace their copy of the control by the shared one.
- Keep navigation items in the same order on every page; add items at the end or inside a section.
How to check: Recrawl: the component, image or destination is no longer reported.
Thresholds
| Name | Default | Meaning |
|---|---|---|
min_pages_per_variant | 5 | A link text that differs from the most used one for the same destination is reported when at least this many pages use it. That keeps one-off links in running text out. |
help_link_pattern | %/contact% | SQL LIKE pattern, in lower case, for the address of the site's contact or help page. Set it to the site's own address. |
help_link_pattern_2 | %/help% | A second pattern for a help page, in lower case. Repeat the first one if the site has only one such page. |
How to verify by hand
A person.
What this relies on
The most common name is the intended one.