WCAG A/AA requirement Priority: Serious
There is no quick way to skip to the main content
The page has no skip link, heading or main landmark that lets keyboard and screen reader users jump past the header and menu.
This text was translated automatically and has not been reviewed by a native speaker yet.
Why it matters to your customers
Keyboard users must press Tab through the whole header, menu and filters on every page before they reach the products or the cart. Screen reader users have no quick way to find where the content starts.
Who is affected
- keyboard users
- screen reader users
- people with motor disabilities
How to fix it
Add a "Skip to content" link as the first focusable element on the page, pointing to the main content, and make it visible when it receives focus. Wrap the main content in a <main> element and give the page a clear heading structure starting with an <h1>. Having all three is best.
On Shopify
Most current themes include a skip link and <main>; older or heavily customised themes may lose them. Restore them in layout/theme.liquid.
On Shoptet (CZ)
Decided by the template. Check whether a newer template version adds a skip link; otherwise ask Shoptet or a partner.
On PrestaShop
Default themes usually provide headings and a main content area; custom themes may not. Add a skip link and <main> in the theme's layout .tpl files.
On WooCommerce
Depends on the theme; some page-builder headers or blank canvas templates drop the skip link or <main>. Add them in the child theme's header template or the builder's theme settings.
Standards
| Standard | Clause |
|---|---|
| WCAG 2.2 | 2.4.1 (A) Bypass Blocks |
| WCAG 2.1 | 2.4.1 (A) Bypass Blocks |
| WCAG 2.0 | 2.4.1 (A) Bypass Blocks |
| EN 301 549 4.1.1 | 9.2.4.1 |
| EN 301 549 3.2.1 | 9.2.4.1 |
| Section 508 2017 | E205.4 |
| ДСТУ EN 301 549 2022 | 9.2.4.1 |
Automated check: axe-core rule bypass.
dequeuniversity.com, github.com, www.w3.org
Related checks
-
Some progress bars have no name
WCAG 1.1.1 A
-
Some gauges have no name
WCAG 1.1.1 A
-
Accessibility attributes are used in the wrong situation
WCAG 4.1.2 A
-
Custom input fields have no label
WCAG 4.1.2 A