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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
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::
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)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
4 landmarks
REVIEW
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
Info::
No banner (header) 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 (missing!) NAV MAIN ASIDE "Language selected: English" 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

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 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 Maps that do more
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Bring location to life with beautiful ma…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Optimize routing with customized navigat…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Generate insights with comprehensive loc…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Customer stories
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to get started?
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
24px · bottom of viewport
h3 3D Lanes provide true-to-life road detai…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Toyota’s next-generation navigation sy…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mapbox style update: Beautiful, detailed…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Give AI agents geospatial context to del…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Subscribe to our newsletter
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Transform location features with search
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 The Operating System 9 delivers all-new …
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Visualize 20 billion daily forecasts wit…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Reduce costs, enhance service delivery, …
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Highlight superior 5G coverage with live…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Delight customers with reliable, on time…
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PRODUCTS
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Maps
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Search
1.10:1
#000000
on
#0E1012
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Maps that do more1.10:13.0:1
#000000
#0E1012
Fail
h2 Bring location to li…1.10:13.0:1
#000000
#0E1012
Fail
h2 Optimize routing wit…1.10:13.0:1
#000000
#0E1012
Fail
h2 Generate insights wi…1.10:13.0:1
#000000
#0E1012
Fail
h2 Customer stories1.10:13.0:1
#000000
#0E1012
Fail
h2 Ready to get started…1.10:13.0:1
#000000
#0E1012
Fail
h3 3D Lanes provide tru…1.10:13.0:1
#000000
#0E1012
Fail
h3 Toyota’s next-gene…1.10:13.0:1
#000000
#0E1012
Fail
h3 Mapbox style update:…1.10:13.0:1
#000000
#0E1012
Fail
h3 Give AI agents geosp…1.10:13.0:1
#000000
#0E1012
Fail
h3 Subscribe to our new…1.10:13.0:1
#000000
#0E1012
Fail
h3 Transform location f…1.10:13.0:1
#000000
#0E1012
Fail
h3 The Operating System…1.10:13.0:1
#000000
#0E1012
Fail
h3 Visualize 20 billion…1.10:13.0:1
#000000
#0E1012
Fail
h3 Reduce costs, enhanc…1.10:13.0:1
#000000
#0E1012
Fail
h3 Highlight superior 5…1.10:13.0:1
#000000
#0E1012
Fail
h3 Delight customers wi…1.10:13.0:1
#000000
#0E1012
Fail
h3 PRODUCTS1.10:13.0:1
#000000
#0E1012
Fail
h3 Maps1.10:13.0:1
#000000
#0E1012
Fail
h3 Search1.10:13.0:1
#000000
#0E1012
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.

B
Lighthouse Accessibility Audits
Score 87/100 — 4 failing, 22 passed
REVIEW
87

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
Sign up div.nav_header-right > div.nav_control-actions > div#sign-up > a.button
Get started for free div.container > div.flex > div.w-layout-hflex > a.button
Automotive div.tabs-light-wrapper > div.tabs-cases > a#w-tabs-0-data-w-tab-0 > div
Discover Mapbox for Automotive → div.position-relative > div.position-relative > a.link > p.text-size-18px
Sign up for free div.link-group_layout-new > a.button_component > div.button_inner > div.text-style-link

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
3D Lanes provide true-to-life road detail for in-vehicle and mobile navigation div.home-carousel-slide > a.home-carousel-slide-in > div.position-relative > h3.heading

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.nav_layout > div.nav_header > div.nav_header-left > a.nav_brand div.nav_layout > div.nav_header > div.nav_header-left > a.nav_brand
div.nav_header > div.nav_header-right > div.nav_control-menu-toggle > a#menu div.nav_header > div.nav_header-right > div.nav_control-menu-toggle > a#menu

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
Terms div.footer_bottom-layout > div.footer_bottom-left > div.footer_legal-links > a.footer_link
Privacy div.footer_bottom-layout > div.footer_bottom-left > div.footer_legal-links > a.footer_link
Security div.footer_bottom-layout > div.footer_bottom-left > div.footer_legal-links > a.footer_link
Your California Privacy Choices div.footer_bottom-layout > div.footer_bottom-left > div.footer_legal-links > a.footer_link

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>`
●`[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
●`[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 use only permitted ARIA attributes
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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 buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○Links are distinguishable without relying on color.
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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
○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
Heading Hierarchy
27 headings, 1 skip(s)
PASS
27 headings, 1 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.
  • H1 Maps that do more
  • H3 3D Lanes provide true-to-life road detail for in-vehicle and mobile navigation skipped
  • H3 Toyota’s next-generation navigation system is built with Mapbox
  • H3 Mapbox style update: Beautiful, detailed building facades
  • H3 Give AI agents geospatial context to deliver accurate, location-aware answers
  • H3 Subscribe to our newsletter
  • H2 Bring location to life with beautiful maps
  • H2 Optimize routing with customized navigation
  • H3 Transform location features with search
  • H2 Generate insights with comprehensive location data
  • H2 Customer stories
  • H3 The Operating System 9 delivers all-new navigation built with Mapbox
  • H3 Visualize 20 billion daily forecasts with high-performance maps
  • H3 Reduce costs, enhance service delivery, and improve fleet efficiency
  • H3 Highlight superior 5G coverage with live maps
  • H3 Delight customers with reliable, on time arrivals
  • H2 Ready to get started?
  • H3 PRODUCTS
  • H3 Maps
  • H3 Search
  • H3 Other
  • H3 Navigation
  • H3 Data
  • H3 solutions
  • H3 Developers
  • H3 Resources
  • H3 Company

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

A+
Alt Text Quality
All 46 images OK
PASS
All 46 images OK
Info::
46 decorative image(s) correctly marked
46 images 46 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback