Skip to content
https://www.minicabit.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
4
PASS
15
INFO
0
Checks
24
15 PASS 4 REVIEW 5 FIX
D
Landmark Structure
Action
11 landmarks
FIX
11 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
9 <nav> landmark(s) found
Warning::
9 of 9 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 MAIN (missing!) CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

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::
9 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 9 <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
Alt Text Quality
2 of 64 images have issues
REVIEW
2 of 64 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
9 decorative image(s) correctly marked
Info::
53 image(s) with good alt text
64 images 53 good alt text 9 decorative 2 missing
IssueCount
missing2 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

B
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - minicabit ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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
A+
Heading Hierarchy
34 headings
PASS
34 headings
Info::
Single H1 present
  • H1 Pre-Book Taxis Online - Cheap Minicab Quotes
  • H2 How it works
  • H3 Pick your location and time
  • H3 Choose your ride
  • H3 Pay securely
  • H3 Ride with confidence
  • H3 Pay with:
  • H2 minicabit in numbers:
  • H2 Trusted by millions of travellers, UK wide
  • H2 Latest from Us
  • H3 How minicabit Works?
  • H3 Share £15 when you Refer a Friend
  • H3 Cab tips for summer festivals
  • H3 Getting to airports UK wide
  • H3 Pre-Book Taxis Online - Cheap Minicab Quotes
  • H2 Get a ride that fits your needs
  • H3 Car Types available
  • H2 Book on the move with the minicabit app!
  • H3 Comparing & booking minicab & taxi quotes online will save you time and effort vs. if you dial local taxi numbers to gather cab fares on the telephone.
  • H3 minicabit calculates fares from mini-cab companies across Great Britain, enabling you to compare real-time online taxi quotes pre-set by the companies themselves.
  • H3 minicabit compares professional, licensed taxi cab companies (known as Private Hire Operators). With minicabit, you can book Executive car mini-cabs, hybrid mini-cabs as well as taxis for up to 8 pass
  • H2 Frequently Asked Questions
  • H3 Do you need help to book a cab?
  • H3 Check our Frequently Asked Questions!
  • H2 Main Cities we cover
  • H2 Main Airports we cover
  • H2 See what our Minicabit customers think
  • H2 Official booking partner for:
  • H2 In the media:
  • H2 We support your bookings 24/7, contactable by
  • H3 FAQs
  • H3 Chat
  • H3 Phone
  • H3 Email
A
Heading Text Quality
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Warning::
3 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H3: 151 chars - H3: 162 chars - H3: 200 chars
Got: 3 >120-char heading(s)
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
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+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A+
Iframe Accessibility
All 3 iframe(s) have descriptive titles
PASS
All 3 iframe(s) have descriptive titles
Info::
All 3 iframe(s) have title attributes
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+
Mobile-Readable Font Sizes
All 137 visible text node(s) render at >= 12 CSS pixels
PASS
All 137 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
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
h1 Pre-Book Taxis Onlin…18.64:13.0:1
#000000
#EDF2F7
Pass
h2 How it works18.64:13.0:1
#000000
#EDF2F7
Pass
h2 minicabit in numbers…18.64:13.0:1
#000000
#EDF2F7
Pass
h2 Trusted by millions …18.64:13.0:1
#000000
#EDF2F7
Pass
h2 Latest from Us18.64:13.0:1
#000000
#EDF2F7
Pass
h2 Get a ride that fits…18.64:13.0:1
#000000
#EDF2F7
Pass
h2 Book on the move wit…18.64:13.0:1
#000000
#EDF2F7
Pass
h2 Frequently Asked Que…18.64:13.0:1
#000000
#EDF2F7
Pass
h2 Main Cities we cover18.64:13.0:1
#000000
#EDF2F7
Pass
h2 Main Airports we cov…18.64:13.0:1
#000000
#EDF2F7
Pass
h2 See what our Minicab…18.64:13.0:1
#000000
#EDF2F7
Pass
h2 Official booking par…18.64:13.0:1
#000000
#EDF2F7
Pass
h2 In the media:18.64:13.0:1
#000000
#EDF2F7
Pass
h2 We support your book…18.64:13.0:1
#000000
#EDF2F7
Pass
h3 Pick your location a…18.64:13.0:1
#000000
#EDF2F7
Pass
h3 Choose your ride18.64:13.0:1
#000000
#EDF2F7
Pass
h3 Pay securely18.64:13.0:1
#000000
#EDF2F7
Pass
h3 Ride with confidence18.64:13.0:1
#000000
#EDF2F7
Pass
h3 Pay with:18.64:13.0:1
#000000
#EDF2F7
Pass
h3 How minicabit Works?18.64:13.0:1
#000000
#EDF2F7
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 Audits
Score 90/100 — 3 failing, 26 passed
PASS
90

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

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
User reviews count div > div > div > span

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Plans change? Easily cancel for a full refund div.advantages-section > div.advantages-section__item > div.advantages-section__text > div.advantages-section__desc
Transparent, fixed price rides with quality drivers div.advantages-section > div.advantages-section__item > div.advantages-section__text > div.advantages-section__desc
Up to 15 minutes, 45 minutes at airports div.advantages-section > div.advantages-section__item > div.advantages-section__text > div.advantages-section__desc
Easy to add diverse luggage items & multiple stops div.advantages-section > div.advantages-section__item > div.advantages-section__text > div.advantages-section__desc
Best prices for trips booked up to 12 months in advance div.advantages-section > div.advantages-section__item > div.advantages-section__text > div.advantages-section__desc
By email, live chat or phone, we're here to help div.advantages-section > div.advantages-section__item > div.advantages-section__text > div.advantages-section__desc
Pick a destination and date and we’ll search 1,000’s of taxi providers to find … div.booking-stages__items > div.booking-stages__items-item > div.booking-stages__items-item-description > p
Choose from a range of cars to suit your needs All licensed, high quality drive… div.booking-stages__items > div.booking-stages__items-item > div.booking-stages__items-item-description > p
Pay for your fixed price ride securely through our website or app. div.booking-stages__items > div.booking-stages__items-item > div.booking-stages__items-item-description > p
Drivers and their cab providers independently rated by customers div.booking-stages__items > div.booking-stages__items-item > div.booking-stages__items-item-description > p
For economy travel div.car-types__items > div.swiper-wrapper > div.car-type__item > div.car-type_appointment
For greener travel div.car-types__items > div.swiper-wrapper > div.car-type__item > div.car-type_appointment
Gerlinde div.swiper-wrapper > div.local-reviews-item > div.local-reviews-item-header > div.name
Tony div.swiper-wrapper > div.local-reviews-item > div.local-reviews-item-header > div.name
View FAQs div.container > div.support-list > div.support-item > a
Open Live chat div.container > div.support-list > div.support-item > a
+44 1322 251 351 div.container > div.support-list > div.support-item > p
info@minicabit.com div.container > div.support-list > div.support-item > p

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Let us help you: Dial a cab Taxi Fare Calculator Student Discount footer#footer > div.container > nav.navigation > ul#menu-footer-top-menu
Airport Transfers Airport transfers Heathrow Airport Taxi Gatwick Airport Taxi… div.container > div.footer__middle_section > nav.navigation > ul#menu-airport-transfers-1
Train Station Transfers Victoria Station Taxi Paddington Station Taxi Reading … div.container > div.footer__middle_section > nav.navigation > ul#menu-train-station-transfers-1

These are opportunities to improve the experience of reading tabular or list data using 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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[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
●`[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
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 are distinguishable without relying on color.
●Links have a discernible name
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○Form elements have associated labels
○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.
○`[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.
○Uses ARIA roles only on compatible elements
○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