Recommended practice Priority: Minor
Several elements use the same keyboard shortcut
The page defines keyboard shortcuts with the accesskey attribute, and two or more elements share the same key. This is a recommended practice, not a WCAG AA requirement.
This text was translated automatically and has not been reviewed by a native speaker yet.
Why it matters to your customers
A keyboard user who presses the shortcut may land on a different element than expected, or nothing happens. Shortcuts can also clash with those of the browser or screen reader. Few shoppers use them, so the effect on sales is small.
Who is affected
- keyboard users
- screen reader users
- people with motor disabilities
How to fix it
Give every accesskey a unique value, or better, remove accesskey attributes altogether: they often conflict with browser and assistive technology shortcuts, and most users do not know they exist. If you need shortcuts, list them on the page and let users turn them off or change them.
On Shopify
Standard themes rarely use accesskey; it usually comes from custom code or an app. Search the theme code for "accesskey" and remove or rename the duplicates.
On Shoptet (CZ)
Usually from custom code added to the shop. Remove or rename the duplicate accesskey in your custom code; if the template adds it, ask Shoptet or a partner.
On PrestaShop
Usually from an older theme or module templates. Search the .tpl files for "accesskey" and remove the duplicates, preferably via a theme override.
On WooCommerce
Usually from a plugin, page builder or an older theme. Search the theme and child theme templates for "accesskey" and fix the duplicates in the child theme.
Standards
Not a WCAG success criterion: a recommended practice that makes the site easier to use.
Automated check: axe-core rule accesskeys.
dequeuniversity.com, github.com