Skip to content
https://www.24hrmobiletyrefitting.london

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
5
PASS
14
INFO
0
Checks
24
14 PASS 5 REVIEW 5 FIX
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #dc1c29
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 ModePartial Dark Mode
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Mobile Keyboard & Autofill
Action
4/8 eligible field(s) missing autocomplete or inputmode
REVIEW
4/8 eligible field(s) missing autocomplete or inputmode
Warning::
4 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel, email.
Got: <input type="tel" name="phone" id="m26f-callback-phone-2875">, <input type="tel" name="phone" id="m26f-callback-phone-7671">, <input type="tel" name="phone" id="m26f-quote-phone-5670">, <input type="email" name="email" id="m26f-quote-email-5670">
B
Tabindex Anti-Patterns
0 positive, 5 -1-on-focusable
REVIEW
0 positive, 5 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
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>
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 <input id="m26f-website-2875">
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 <input id="m26f-website-7671">
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 <input id="m26f-website-5670">
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
Mobile-Readable Font Sizes
97% of visible text renders at >= 12 CSS px (2 below threshold)
REVIEW
97% of visible text renders at >= 12 CSS px (2 below threshold)
Info::
2 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: <p> 11.5px ("Not sure? Send us a photo of the sidewal..."); <div> 11.0px ("Our Services").
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 19 fail WCAG AA
REVIEW

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

1 pass 19 fail WCAG AA
h1 24hr
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
32px · bottom of viewport
h2 24 Hour Mobile
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fitting London
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Tyres For All Types Of Car
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mobile Tyre Services
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Back On The Road In
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How Do You Determine The Size Of Tyres N…
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our mobile tyre service is available 24 …
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Testimonials
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Work Image Gallery
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Areas We
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently Asked
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Most Recent
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Request a
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Request a callback
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get a price
1.22:1
#000000
on
#181C1D
needs 3.0:1 (large text)
24px · bottom of viewport
title 24hr Mobile Tyre Fitting London: Same Da…
4.24:1
#000000
on
#DC1C29
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to content
4.24:1
#000000
on
#DC1C29
needs 4.5:1 (normal text)
16px · top of page (header area)
a 07707717000
4.24:1
#000000
on
#DC1C29
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 24hr1.22:13.0:1
#000000
#181C1D
Fail
h2 24 Hour Mobile1.22:13.0:1
#000000
#181C1D
Fail
h2 Fitting London1.22:13.0:1
#000000
#181C1D
Fail
h2 Tyres For All Types …1.22:13.0:1
#000000
#181C1D
Fail
h2 Mobile Tyre Services1.22:13.0:1
#000000
#181C1D
Fail
h2 Back On The Road In1.22:13.0:1
#000000
#181C1D
Fail
h2 How Do You Determine…1.22:13.0:1
#000000
#181C1D
Fail
h2 Our mobile tyre serv…1.22:13.0:1
#000000
#181C1D
Fail
h2 Testimonials1.22:13.0:1
#000000
#181C1D
Fail
h2 Our Work Image Galle…1.22:13.0:1
#000000
#181C1D
Fail
h2 Areas We1.22:13.0:1
#000000
#181C1D
Fail
h2 Frequently Asked1.22:13.0:1
#000000
#181C1D
Fail
h2 Our Most Recent1.22:13.0:1
#000000
#181C1D
Fail
h2 Request a1.22:13.0:1
#000000
#181C1D
Fail
h2 Request a callback1.22:13.0:1
#000000
#181C1D
Fail
h2 Get a price1.22:13.0:1
#000000
#181C1D
Fail
title 24hr Mobile Tyre Fit…4.24:14.5:1
#000000
#DC1C29
Fail
a Skip to content4.24:14.5:1
#000000
#DC1C29
Fail
a 077077170004.24:14.5:1
#000000
#DC1C29
Fail
a info@24hrmobiletyref…21.00:14.5:1
#000000
#FFFFFF
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+
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" MAIN CONTENTINFO footer
A+
Heading Hierarchy
34 headings
PASS
34 headings
Info::
Single H1 present
  • H1 24hr
  • H2 24 Hour Mobile Tyre Fitting London
  • H3 45/60 Minute Rapid Response
  • H3 From Central London Up to 25 Miles
  • H3 More Than 1000+ Pleased Clients
  • H3 24-Hour Emergency Service
  • H2 Tyres For All Types Of Car
  • H2 24HR Mobile Tyre Services
  • H3 24-Hour Emergency Service
  • H3 Mobile Tyre Replacement
  • H3 Tyre Repair on the Go
  • H3 Locking Wheel Nut Removal
  • H2 Back On The Road In Three Steps
  • H3 Call or send your reg
  • H3 We quote and dispatch
  • H3 Fitted on the spot
  • H2 How Do You Determine The Size Of Tyres Needed?
  • H2 Our mobile tyre service is available 24 hours a day, 7 days a week.
  • H2 Testimonials
  • H2 Our Work Image Gallery
  • H2 Areas We Cover
  • H2 Frequently Asked Questions
  • H3 How quickly can you get to me?
  • H3 Do you work at night and on bank holidays?
  • H3 Can my tyre be repaired instead of replaced?
  • H3 What areas do you cover?
  • H3 How do I find my tyre size?
  • H3 What payment methods do you take?
  • H2 Our Most Recent Posts
  • H3 How Mobile Tyre Replacement Helps Prevent Costly Car Repairs
  • H3 Emergency Tyre Problems in London: What Every Driver Should Know
  • H2 Request a Callback
  • H2 Request a callback
  • H2 Get a price
A+
Heading Text Quality
All 34 heading(s) have substantive, well-formed text
PASS
All 34 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 17 images OK
PASS
All 17 images OK
Info::
15 decorative image(s) correctly marked
Info::
2 image(s) with good alt text
17 images 2 good alt text 15 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 35 controls have issues
PASS
1 of 35 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
34 control(s) properly labeled
35 controls
34 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#m26ts-reg-9706textVehicle registrationfor/id
#m26ts-w-9706selectWidthfor/id
#m26ts-p-9706selectProfilefor/id
#m26ts-r-9706selectRimfor/id
#m26ts-raw-9706textOr type the full sizefor/id
#m26ts-reg-8200textVehicle registrationfor/id
#m26ts-w-8200selectWidthfor/id
#m26ts-p-8200selectProfilefor/id
#m26ts-r-8200selectRimfor/id
#m26ts-raw-8200textOr type the full sizefor/id
#m26f-callback-name-2875textYour name *for/id
#m26f-callback-phone-2875telPhone number *for/id
#m26f-callback-postcode-2875textWhere are you? (postcode or road) *for/id
#m26f-callback-tyre_size-2875textTyre size or registrationfor/id
#m26f-callback-message-2875textareaWhat has happened?for/id
#m26f-consent-2875checkboxI agree to be contacted about this enquiry.for/id
#m26f-callback-name-7671textYour name *for/id
#m26f-callback-phone-7671telPhone number *for/id
#m26f-callback-postcode-7671textWhere are you? (postcode or road) *for/id
#m26f-callback-tyre_size-7671textTyre size or registrationfor/id
#m26f-callback-message-7671textareaWhat has happened?for/id
#m26f-consent-7671checkboxI agree to be contacted about this enquiry.for/id
#m26f-quote-name-5670textYour name *for/id
#m26f-quote-phone-5670telPhone number *for/id
#m26f-quote-email-5670emailEmailfor/id
#m26f-quote-reg-5670textRegistrationfor/id
#m26f-quote-vehicle-5670textVehiclefor/id
#m26f-quote-tyre_size-5670textTyre sizefor/id
#m26f-quote-tyre_size_rear-5670textRear size, if differentfor/id
#m26f-quote-quantity-5670selectHow many tyres?for/id
#m26f-quote-postcode-5670textPostcode *for/id
#m26f-quote-when-5670selectWhen do you need us?for/id
#m26f-quote-message-5670textareaAnything else?for/id
#m26f-consent-5670checkboxI agree to be contacted about this enquiry.for/id
#g-recaptcha-response-100000textarea(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

A+
Form Input Types
35 form control(s) checked, no type mismatches
PASS
35 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
35 form control(s) checked, no input-semantic issues
PASS
35 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A
Iframe Accessibility
1/3 iframe(s) missing title; 0 placeholder(s)
PASS
1/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
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+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Quick Tyre Services ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
2 mobile-depth signal(s) detected
PASS
2 mobile-depth signal(s) detected
Info::
Browser-chrome `theme-color` meta tag present
The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.
Info::
Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices
The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.
A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 31 passed
PASS
96

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
How quickly can you get to me? div.elementor-element > div.elementor-accordion > div.elementor-accordion-item > h3#elementor-tab-title-6021

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.

○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
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○Elements with `role="dialog"` or `role="alertdialog"` 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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○`[lang]` attributes have a valid value
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback