Skip to content
https://amittravelsjbp.netlify.app

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
8
REVIEW
5
PASS
11
INFO
0
Checks
24
11 PASS 5 REVIEW 8 FIX
F
Heading Hierarchy
Action
79 headings, 5 skip(s)
FIX
79 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Best Taxi & Car RentalService in Jabalpur
  • H3 Get Instant Quote skipped
  • H2 Travel With Confidence
  • H4 Safe Travel skipped
  • H4 24/7 Service
  • H4 Comfortable Fleet
  • H4 Affordable Pricing
  • H4 Experienced Drivers
  • H4 Customer Support
  • H2 Taxi & Car Rental Service in Jabalpur
  • H2 Our Fleet
  • H3 Swift Dzire
  • H3 Ertiga
  • H3 Innova Crysta
  • H3 Tempo Traveller
  • H3 Force Urbania
  • H2 Book Force Urbania in Jabalpur
  • H4 Luxury Pushback Seats skipped
  • H4 Full AC Cabin
  • H4 Charging Points
  • H4 Entertainment System
  • H4 Premium Interior
  • H4 13–17 Seater
  • H2 Spiritual Destinations from Jabalpur
  • H3 Ayodhya
  • H3 Kashi
  • H3 Ujjain
  • H3 Chitrakoot
  • H3 Amarkantak
  • H3 Orchha
  • H3 Sanchi
  • H3 Khajuraho
  • H2 Popular Destinations from Jabalpur
  • H3 Kanha
  • H3 Pachmarhi
  • H3 Bandhavgarh
  • H3 Amarkantak
  • H3 Khajuraho
  • H3 Pench
  • H2 Explore the Best of Jabalpur
  • H3 Dhuandhar Falls
  • H3 Marble Rocks – Bhedaghat
  • H3 Balance Rock
  • H3 Kachnar Shiv Temple
  • H3 Bargi Dam
  • H3 Narmada Ghat
  • H2 Our Services
  • H4 Airport Pickup & Drop skipped
  • H4 Railway Station Transfer
  • H4 Local Taxi
  • H4 Outstation Taxi
  • H4 Wedding Travel
  • H4 Corporate Travel
  • H4 Tempo Traveller
  • H4 Urbania Rental
  • H2 Customer Reviews
  • H2 Why Choose Amit Travels?
  • H2 Popular Tour Packages
  • H3 Jabalpur Local Sightseeing
  • H3 Jabalpur to Kanha
  • H3 Jabalpur to Bandhavgarh
  • H3 Jabalpur to Pachmarhi
  • H3 Jabalpur to Amarkantak
  • H3 Jabalpur to Pench
  • H3 Jabalpur to Khajuraho
  • H3 Jabalpur to Ayodhya
  • H3 Jabalpur to Kashi
  • H2 From Our Blog
  • H2 Frequently Asked Questions
  • H2 Ready to Travel?
  • H2 Contact Amit Travels
  • H4 Address skipped
  • H4 Phone
  • H4 Business Hours
  • H4 Website
  • H3 Send Us a Message
  • H4 Services
  • H4 Popular Routes
  • H4 Contact

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

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

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
Form Accessibility
Action
16 of 16 controls have issues
FIX
16 of 16 controls have issues
Critical::
6 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="date" name="travel_date">; <select name="vehicle_type">; <select name="trip_type">; <input type="date" name="travel_date">; <select name="vehicle_type">; <select name="trip_type">
Warning::
10 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input name="name">; <input type="tel" name="phone">; <input name="pickup">; <input name="destination">; <input type="number" name="passengers">; <input name="name">; <input type="tel" name="phone">; <input name="pickup">; <input name="destination">; <input type="number" name="passengers">
16 controls
0 labeled
10 placeholder only
6 unlabeled
ControlTypeLabelMethod
nameinput(Your Name *)placeholder only
phonetel(Phone Number *)placeholder only
pickupinput(Pickup Location)placeholder only
destinationinput(Destination)placeholder only
passengersnumber(Passengers)placeholder only
nameinput(Your Name *)placeholder only
phonetel(Phone Number *)placeholder only
pickupinput(Pickup Location)placeholder only
destinationinput(Destination)placeholder only
passengersnumber(Passengers)placeholder only
trip_typeselect(none)none
travel_datedate(none)none
travel_datedate(none)none
vehicle_typeselect(none)none
vehicle_typeselect(none)none
trip_typeselect(none)none

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

<input type="date" name="travel_date">; <select name="vehicle_type">; <select name="trip_type">; <input type="date" name="travel_date">; <select name="vehicle_type">; <select name="trip_type">

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.

<input name="name">; <input type="tel" name="phone">; <input name="pickup">; <input name="destination">; <input type="number" name="passengers">; <input name="name">; <input type="tel" name="phone">; <input name="pickup">; <input name="destination">; <input type="number" name="passengers">

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

D
Mobile Keyboard & Autofill
Action
6/6 eligible field(s) missing autocomplete or inputmode
FIX
6/6 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: name.
Got: <input name="name">, <input name="name">
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, numeric.
Got: <input type="tel" name="phone">, <input type="number" name="passengers">, <input type="tel" name="phone">, <input type="number" name="passengers">
D
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ 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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Tap Target Adequacy
Action
5 tap target(s) too small or too close together
REVIEW
5 tap target(s) too small or too close together
Warning::
5 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.
C
Mobile-Readable Font Sizes
Action
82% of visible text renders at >= 12 CSS px (85 below threshold)
REVIEW
82% of visible text renders at >= 12 CSS px (85 below threshold)
Warning::
85 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 ("Car Rental & Taxi Service"); <span> 11.2px ("Sedan"); <span> 11.2px ("MPV"); <span> 11.2px ("Tempo Traveller"); <span> 11.2px ("Urbania").
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 ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h1 Best Taxi & Car Rental
1.67:1
#000000
on
#1D354C
needs 3.0:1 (large text)
32px · mid-page
h1 Service in
1.67:1
#000000
on
#1D354C
needs 3.0:1 (large text)
32px · mid-page
h2 Travel With Confidence
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Taxi & Car Rental Service in Jabalpur
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Fleet
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Book Force Urbania in Jabalpur
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Spiritual Destinations from Jabalpur
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Popular Destinations from Jabalpur
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Explore the Best of Jabalpur
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Services
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Customer Reviews
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why Choose Amit Travels?
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Popular Tour Packages
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 From Our Blog
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently Asked Questions
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to Travel?
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Contact Amit Travels
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Get Instant Quote
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Swift Dzire
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ertiga
1.19:1
#000000
on
#061A2E
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Best Taxi & Car Rent…1.67:13.0:1
#000000
#1D354C
Fail
h1 Service in1.67:13.0:1
#000000
#1D354C
Fail
h2 Travel With Confiden…1.19:13.0:1
#000000
#061A2E
Fail
h2 Taxi & Car Rental Se…1.19:13.0:1
#000000
#061A2E
Fail
h2 Our Fleet1.19:13.0:1
#000000
#061A2E
Fail
h2 Book Force Urbania i…1.19:13.0:1
#000000
#061A2E
Fail
h2 Spiritual Destinatio…1.19:13.0:1
#000000
#061A2E
Fail
h2 Popular Destinations…1.19:13.0:1
#000000
#061A2E
Fail
h2 Explore the Best of …1.19:13.0:1
#000000
#061A2E
Fail
h2 Our Services1.19:13.0:1
#000000
#061A2E
Fail
h2 Customer Reviews1.19:13.0:1
#000000
#061A2E
Fail
h2 Why Choose Amit Trav…1.19:13.0:1
#000000
#061A2E
Fail
h2 Popular Tour Package…1.19:13.0:1
#000000
#061A2E
Fail
h2 From Our Blog1.19:13.0:1
#000000
#061A2E
Fail
h2 Frequently Asked Que…1.19:13.0:1
#000000
#061A2E
Fail
h2 Ready to Travel?1.19:13.0:1
#000000
#061A2E
Fail
h2 Contact Amit Travels1.19:13.0:1
#000000
#061A2E
Fail
h3 Get Instant Quote1.19:13.0:1
#000000
#061A2E
Fail
h3 Swift Dzire1.19:13.0:1
#000000
#061A2E
Fail
h3 Ertiga1.19:13.0:1
#000000
#061A2E
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.

C
Lighthouse Accessibility Audits
Action
Score 79/100 — 5 failing, 19 passed
REVIEW
79

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.

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
WhatsApp div.container > nav.nav-menu > div.nav-cta-mobile > a.btn
WhatsApp Now div.container > div.hero-text > div.hero-cta > a.btn
Book on WhatsApp section.final-cta-section > div.container > div.cta-buttons > a.btn
© 2026 Amit Travels – Car Rental in Jabalpur. All rights reserved. footer.footer > div.container > div.footer-bottom > p

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Get Instant Quote div.hero-form-wrap > div#booking-form-section > form.booking-form > h3
Safe Travel div.container > div.grid > div.trust-card > h4
Luxury Pushback Seats div.container > div.grid > div.urbania-card > h4
Airport Pickup & Drop div.container > div.grid > div.service-card > h4
Address div.contact-info > div.contact-card > div > h4

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form.booking-form > div.bf-grid > div.bf-field > input form.booking-form > div.bf-grid > div.bf-field > input
form.booking-form > div.bf-grid > div.bf-field > input form.booking-form > div.bf-grid > div.bf-field > input

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Vehicle Type Swift Dzire Ertiga Innova Crysta Tempo Traveller Force Urbania form.booking-form > div.bf-grid > div.bf-field > select
Trip Type Local One Way Round Trip Airport Railway Station Sightseeing Outstati… form.booking-form > div.bf-grid > div.bf-field > select
Vehicle Type Swift Dzire Ertiga Innova Crysta Tempo Traveller Force Urbania form.booking-form > div.bf-grid > div.bf-field > select
Trip Type Local One Way Round Trip Airport Railway Station Sightseeing Outstati… form.booking-form > div.bf-grid > div.bf-field > select

These are opportunities to improve the semantics of the controls in your application. This 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
Go to review 2 section.section > div.container > div.slider-dots > button.slider-dot
Go to review 3 section.section > div.container > div.slider-dots > button.slider-dot
Go to review 4 section.section > div.container > div.slider-dots > button.slider-dot
Go to review 5 section.section > div.container > div.slider-dots > button.slider-dot
Go to review 6 section.section > div.container > div.slider-dots > button.slider-dot

These items highlight common accessibility best practices.

○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>`
●`[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.
●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
●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
●Document has a main landmark.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[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
○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
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 CONTENTINFO footer

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

A+
Heading Text Quality
All 79 heading(s) have substantive, well-formed text
PASS
All 79 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 40 images OK
PASS
All 40 images OK
Info::
40 image(s) with good alt text
40 images 40 good alt text
All images have appropriate alt text.
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+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
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 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback