Skip to content
https://www.amazon.co.uk/ref=nav_logo

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
70
GRADE
C
FIX
7
REVIEW
7
PASS
10
INFO
0
Checks
24
10 PASS 7 REVIEW 7 FIX
D
Heading Hierarchy
Action
36 headings, 2 skip(s)
FIX
36 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H4 Select your cookie preferences
  • H2 Skip to
  • H2 Keyboard shortcuts
  • H5 International Shopping Transition Alert skipped
  • H2 Top offersTop offers
  • H2 Beauty & Wellness
  • H2 Popular categories
  • H2 Garden essentials
  • H2 Must have products
  • H2 Run, don't walk. All under £10.
  • H2 Get Deliveroo Plus Silver with Prime
  • H2 Office supplies
  • H2 Unlimited streaming of movies & TV
  • H3 Top Kindle Books on Deal
  • H2 Resale: more savings, less waste
  • H2 Books going viral right now
  • H2 Japan Store
  • H2 Home & Gardening from Japan
  • H2 Back to school prep under £20
  • H2 Save big on discounted returned electronics
  • H2 Your Haul awaits. All under £20
  • H2 Extra 10% off orders £30+
  • H2 Up to 15% off on subscriptions
  • H5 Amazon Music skipped
  • H5 AbeBooks
  • H5 ACX
  • H5 Veeqo
  • H5 Amazon Web Services
  • H5 Audible
  • H5 Goodreads
  • H5 Amazon Home Services
  • H5 IMDb
  • H5 Kindle Direct Publishing
  • H5 Shopbop
  • H5 Amazon Resale
  • H5 Amazon Business

Every page should have one H1 that describes the page content.

Why this matters

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.

Why this matters

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

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

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

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
No web manifest found
No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark ModeNo Dark Mode Detected
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
No print-specific styles detected
When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.
Print Stylesheet No Print Styles
Print stylesheet Not found ✗Inline @media print Not detected ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) landmark
Warning::
Skip navigation link is missing (WCAG 2.4.1)
Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.
Page Structure — as a screen reader sees it
BANNER header NAV "Shortcuts menu" MAIN ASIDE "Your recently viewed items and featured recommendations" CONTENTINFO (missing!)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

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

C
Form Accessibility
Action
12 of 16 controls have issues
REVIEW
12 of 16 controls have issues
Critical::
12 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit" id="nav-search-submit-button">; <input type="submit">; <input type="submit">; <select>; <select>; <select>; <select>; <select>; <select>; <select> (+2 more)
Info::
4 control(s) properly labeled
16 controls
4 labeled
0 placeholder only
12 unlabeled
ControlTypeLabelMethod
#sp-cc-acceptsubmitAcceptaria-label
#sp-cc-rejectall-linksubmitDeclinearia-label
#searchDropdownBoxselectSelect the department you want to search infor/id
#twotabsearchtextboxtextSearch Amazon.co.ukaria-label
#nav-search-submit-buttonsubmit(none)none
inputsubmit(none)none
inputsubmit(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(none)none
selectselect(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">; <select>; <select>; <select>; <select>; <select>; <select>; <select> (+2 more)

Why this matters

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

B
Tabindex Anti-Patterns
0 positive, 5 -1-on-focusable
REVIEW
0 positive, 5 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a id="nav-assist-search">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="nav-assist-cart">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="nav-assist-home">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a id="nav-assist-your-orders">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="nav-assist-show-shortcuts">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
B
Tap Target Adequacy
2 tap target(s) too small or too close together
REVIEW
2 tap target(s) too small or too close together
Info::
2 tap target(s) too small or too close to neighbors
WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.
B
Mobile-Readable Font Sizes
92% of visible text renders at >= 12 CSS px (12 below threshold)
REVIEW
92% of visible text renders at >= 12 CSS px (12 below threshold)
Info::
12 text node(s) render below 12 CSS pixels on mobile
Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("USD"); <span> 10.0px ("99"); <span> 10.0px ("USD"); <span> 10.0px ("62"); <span> 10.0px ("USD").
C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Lighthouse Accessibility Audits
Score 86/100 — 5 failing, 31 passed
REVIEW
86

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Search Amazon.co.uk form#nav-search-form > div.nav-fill > div.nav-search-field > input#nav-search-keywords
Free delivery on your first order Try us, no delivery fee. New customers only. … div#gwm-Deck-cf > div#gwm-window-layout > div#gwm-window-container > ul#gwm-window

ARIA roles must have valid values in order to perform their intended accessibility functions. Learn more about valid ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#nav-app-banner-container > div.nav-app-banner-elements > div.nav-app-banner-left-section > i#nav-app-banner-close-button div#nav-app-banner-container > div.nav-app-banner-elements > div.nav-app-banner-left-section > i#nav-app-banner-close-button

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Sorry, we thought we had more recommendations. div#gwm-Deck-cf > div#gwm-window-layout > div#gwm-window-container > div#WD-carousel-end-arialabel-marker

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Privacy Notice div#nav-ftr > ul.nav-ftr-horiz > li.nav-li > a.nav-a
Interest-Based Ads Notice div#nav-ftr > ul.nav-ftr-horiz > li.nav-li > a.nav-a

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
0 div#navbar > div#nav-logobar > div.nav-right > a#nav-button-cart
Backpacks Backpacks div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Pencil cases Pencil cases div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Briefcases Briefcases div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Wheeled bags Wheeled bags div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Fashion Fashion div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Tech Tech div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Kitchen Kitchen div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Home Home div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Home & Gardening Home & Gardening div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
PC & Electronics PC & Electronics div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Futon & Mattress Futon & Mattress div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Toys & Games Toys & Games div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Fashion Fashion div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Electronics Electronics div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Kitchen Kitchen div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
Beauty Beauty div.a-cardui-body > div._multi-category-card_style_container__3HW_J > div > a.a-link-normal
○Interactive controls are keyboard focusable
○Interactive elements indicate their purpose and state
○The page has a logical tab order
○Visual order on the page follows DOM order
○User focus is not accidentally trapped in a region
○The user's focus is directed to new content added to the page
○HTML5 landmark elements are used to improve navigation
○Offscreen content is hidden from assistive technology
○Custom controls have associated labels
○Custom controls have ARIA roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[role]`s are contained by their required parent element
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●Form elements have associated labels
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Image elements do not have `[alt]` attributes that are redundant text.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements with the `role=text` attribute do not have focusable descendents.
○ARIA toggle fields have accessible names
○ARIA `tooltip` elements have accessible names
○ARIA `treeitem` elements have accessible names
○The page contains a heading, skip link, or landmark region
○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
○Definition list items are wrapped in `<dl>` elements
○ARIA IDs are unique
○No form fields have multiple labels
○`<frame>` or `<iframe>` elements have a title
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`<td>` elements in a large `<table>` have one or more table headers.
A+
Heading Text Quality
All 36 heading(s) have substantive, well-formed text
PASS
All 36 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A
Alt Text Quality
1 of 74 images have issues
PASS
1 of 74 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
2 image(s) with alt text over 125 characters
Info::
16 decorative image(s) correctly marked
Info::
55 image(s) with good alt text
74 images 55 good alt text 16 decorative 1 missing
IssueCount
missing1 image(s)
too long2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

A+
Form Input Types
16 form control(s) checked, no type mismatches
PASS
16 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
16 form control(s) checked, no input-semantic issues
PASS
16 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-gb"
PASS
Lang attribute set to "en-gb"
Info::
<html lang="en-gb"> is set and valid
Got: en-gb
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="about:blank")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Skip to15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Keyboard shortcuts15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Beauty & Wellness15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Popular categories15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Garden essentials15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Must have products15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Run, don't walk. All…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Get Deliveroo Plus S…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Office supplies15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Unlimited streaming …15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Resale: more savings…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Books going viral ri…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Japan Store15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Home & Gardening fro…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Back to school prep …15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Save big on discount…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Your Haul awaits. Al…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Extra 10% off orders…15.46:13.0:1
#000000
#DDDDDD
Pass
h2 Up to 15% off on sub…15.46:13.0:1
#000000
#DDDDDD
Pass
title Amazon.co.uk: Low Pr…15.46:14.5: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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback