Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLink & Button QualityAction5 issue(s) across 281 links and 12 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| https://www.amazon.fr/-/en/b/?_encoding=… | Enjoy your offer nowEnjoy your… | new tab | Add '(opens in new tab)' to text |
| <input> | (empty) | empty | Add button text or aria-label |
| <input> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
a#nav-top; a#skippedLink; a (#701 on page)
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://www.amazon.fr/-/en/b/?_encoding=UTF8&node=216377093031&pd_rd_w=7FHHY&…
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
input[type="submit"].a-button-input (#710 on page); input[type="submit"].a-button-input (#714 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
FFavicon & BrandingAction2 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BLandmark Structure6 landmarksREVIEW
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.
Learn more ▾ ▴
WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.
Source: WCAG 2.1 SC 2.4.1
CHeading HierarchyAction32 headings, 1 skip(s)REVIEW
- H4 Cookies and Advertising Choices
- H2 Skip to
- H2 Keyboard shortcuts
- H2 High-Tech that makes life easier
- H2 €10 off with the app
- H2 Lawn & Garden
- H2 Sports & Outdoors
- H2 Best Sellers in Beauty
- H2 Best Sellers in Toys & Games
- H2 Music
- H2 Software
- H2 Grocery and homecare
- H2 Abonnement Kindle
- H2 Discover the French Vitrine
- H2 Best Sellers in Books
- H2 Shop Spring Essentials
- H2 Wireless products
- H2 Fashion accessories
- H2 Refurbished wireless tech
- H2 Unlock exclusive savings on baby items
- H2 Sports
- H2 Garden
- H2 Toys
- H5 Amazon Music skipped
- H5 AbeBooks
- H5 Amazon Web Services
- H5 Audible
- H5 Kindle Direct Publishing
- H5 Amazon Resale
- H5 Shopbop
- H5 Amazon Advertising
- H5 Amazon Business
Every page should have one H1 that describes the page content.
No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.
Learn more ▾ ▴
The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.
Source: WCAG 2.4.6 / Google Search Central
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.
Learn more ▾ ▴
Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.
Source: WCAG 2.1 SC 1.3.1 / W3C WAI
BAlt Text Quality1 of 132 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 1 image(s) |
| too long | 5 image(s) |
Images without alt text are invisible to screen readers.
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
CForm AccessibilityAction3 of 7 controls have issuesREVIEW
| Control | Type | Label | Method |
|---|---|---|---|
| #sp-cc-accept | submit | Accept | aria-label |
| #sp-cc-rejectall-link | submit | Decline | aria-label |
| #searchDropdownBox | select | Select the department you want to search in | for/id |
| #twotabsearchtextbox | text | Search Amazon.fr | aria-label |
| #nav-search-submit-button | submit | (none) | none |
| input | submit | (none) | none |
| input | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" id="nav-search-submit-button">; <input type="submit">; <input type="submit">
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Source: WCAG 2.1 SC 3.3.2
C404 Error PageActionHTTP 404, custom pageREVIEW
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h2 Skip to | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Keyboard shortcuts | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 High-Tech that makes… | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 €10 off with the a… | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Lawn & Garden | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Sports & Outdoors | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Music | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Software | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Grocery and homecare | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Abonnement Kindle | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Shop Spring Essentia… | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Wireless products | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Fashion accessories | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Refurbished wireless… | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Unlock exclusive sav… | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Sports | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Garden | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| h2 Toys | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
| title Amazon.fr: books, DV… | 15.46:1 | 4.5:1 | #000000 | #DDDDDD | Pass |
| h4 Cookies and Advertis… | 15.46:1 | 3.0:1 | #000000 | #DDDDDD | Pass |
Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.
A+Lighthouse Accessibility AuditsScore 97/100 — 1 failing, 11 passedPASS
Accessibility
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Best practices
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
html.a-no-js html.a-no-js |
These items highlight common accessibility best practices.