Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 6 REVIEW 5 FIX

Form Accessibility

Action

6 of 6 controls have issues

FIX

6 of 6 controls have issues

2 control(s) without accessible label

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

Got: <input type="number" id="vqw_f80051_hours">; <input type="number" id="vqw_f80051_pax">

4 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text" id="vqw_f80051_pickup">; <input type="text" id="vqw_f80051_dropoff">; <input type="text" id="vqw_f80051_date">; <input type="text" id="vqw_f80051_time_disp">

6 controls

0 labeled

4 placeholder only

2 unlabeled

Control	Type	Label	Method
#vqw_f80051_pickup	text	(Address, airport, hotel…)	placeholder only
#vqw_f80051_dropoff	text	(Address, airport, hotel…)	placeholder only
#vqw_f80051_date	text	(Select date…)	placeholder only
#vqw_f80051_time_disp	text	(Select time…)	placeholder only
#vqw_f80051_hours	number	(none)	none
#vqw_f80051_pax	number	(none)	none

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

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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Tap Target Adequacy

Action

4 tap target(s) too small or too close together

REVIEW

4 tap target(s) too small or too close together

4 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.

Mobile-Readable Font Sizes

Action

85% of visible text renders at >= 12 CSS px (28 below threshold)

REVIEW

85% of visible text renders at >= 12 CSS px (28 below threshold)

28 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> 11.2px ("Premium Black Car Service"); <span> 11.0px ("Luxury. Comfort. Excellence"); <span> 10.0px ("From"); <span> 10.0px ("To"); <span> 10.0px ("Pickup Date").

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 18 fail WCAG AA

REVIEW

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

2 pass 18 fail WCAG AA

h2 Where

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 meets

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 the horizon

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Executive Fleet

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Corporate Travel

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 24/7 Hourly Service

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Services

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Airport Transfer

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Corporate Travel

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Hourly Chauffeur

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Weddings & Events

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Group Transportation

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 City Tours & Leisure

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Choose Your

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Luxury Sedan

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Luxury SUV

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Premium SUV

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Premium Sedan

1.21:1

#000000

#1E1A16

needs 3.0:1 (large text)

24px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Premium Black	15.70:1	3.0:1	#F3F3F3	#1E1915	Pass
h1 Car Service in	15.58:1	3.0:1	#F3F3F3	#1E1A16	Pass
h2 Where	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 meets	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 the horizon	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Executive Fleet	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Corporate Travel	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 24/7 Hourly Service	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Services	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Airport Transfer	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Corporate Travel	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Hourly Chauffeur	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Weddings & Events	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Group Transportation	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 City Tours & Leisure	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Choose Your	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Luxury Sedan	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Luxury SUV	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Premium SUV	1.21:1	3.0:1	#000000	#1E1A16	Fail
h2 Premium Sedan	1.21:1	3.0:1	#000000	#1E1A16	Fail

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.

Lighthouse Accessibility Audits

Score 80/100 — 6 failing, 17 passed

REVIEW

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.