Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction3 landmarksFIX
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
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.
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
FForm AccessibilityAction14 of 25 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| #map-ui-layer-mapnik | radio | Standard | for/id |
| #map-ui-layer-cyclosm | radio | CyclOSM | for/id |
| #map-ui-layer-cyclemap | radio | Cycle Map | for/id |
| #map-ui-layer-transportmap | radio | Transport Map | for/id |
| #map-ui-layer-tracestracktopo | radio | Tracestrack Topo | for/id |
| #map-ui-layer-hot | radio | Humanitarian | for/id |
| #map-ui-layer-shortbread | radio | Shortbread | for/id |
| #map-ui-layer-openmaptiles_osm | radio | MapTiler OMT | for/id |
| input | checkbox | none | |
| input | checkbox | none | |
| input | checkbox | none | |
| #route_to | text | (To) | placeholder only |
| #query | text | (Search) | placeholder only |
| #route_from | text | (From) | placeholder only |
| #route_to | text | (To) | placeholder only |
| #query | text | (Search) | placeholder only |
| #route_from | text | (From) | placeholder only |
| #modes_bicycle | radio | (none) | none |
| #modes_foot | radio | (none) | none |
| #routing_engines | select | (none) | none |
| #routing_engines | select | (none) | none |
| #modes_car | radio | (none) | none |
| #modes_bicycle | radio | (none) | none |
| #modes_foot | radio | (none) | none |
| #modes_car | radio | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="radio" name="modes" id="modes_car">; <input type="radio" name="modes" id="modes_bicycle">; <input type="radio" name="modes" id="modes_foot">; <select name="routing_engines" id="routing_engines">; <input type="radio" name="modes" id="modes_car">; <input type="radio" name="modes" id="modes_bicycle">; <input type="radio" name="modes" id="modes_foot">; <select name="routing_engines" id="routing_engines">
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 type="text" name="query" id="query">; <input type="text" name="route_from" id="route_from">; <input type="text" name="route_to" id="route_to">; <input type="text" name="query" id="query">; <input type="text" name="route_from" id="route_from">; <input type="text" name="route_to" id="route_to">
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
DLink & Button QualityAction11 issue(s) across 43 links and 20 buttonsFIX
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| # | (empty) | empty | Add link text or aria-label |
| /about | Learn More | generic text | Replace with descriptive text |
Before: Learn More Suggested: About | |||
| https://wiki.openstreetmap.org/wiki/Open… | Layer Info | new tab | Add '(opens in new tab)' to text |
| https://wiki.openstreetmap.org/wiki/Cycl… | Layer Info | new tab | Add '(opens in new tab)' to text |
| https://wiki.openstreetmap.org/wiki/Open… | Layer Info | new tab | Add '(opens in new tab)' to text |
| https://wiki.openstreetmap.org/wiki/Tran… | Layer Info | new tab | Add '(opens in new tab)' to text |
| https://wiki.openstreetmap.org/wiki/Trac… | Layer Info | new tab | Add '(opens in new tab)' to text |
| https://wiki.openstreetmap.org/wiki/Huma… | Layer Info | new tab | Add '(opens in new tab)' to text |
| https://wiki.openstreetmap.org/wiki/Shor… | Layer Info | new tab | Add '(opens in new tab)' to text |
| https://wiki.openstreetmap.org/wiki/MapT… | Layer Info | new tab | Add '(opens in new tab)' to text |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
| <button> | (empty) | empty | Add button text or aria-label |
Links without text are announced as raw URLs by screen readers.
#
Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.
Source: WCAG 2.1 SC 2.4.4
Generic link text like 'click here' doesn't describe the destination.
/about ("Learn More")
Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.
Learn more ▾ ▴
Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.
Source: WCAG 2.4.4 / Google Search Central
Add '(opens in new tab)' to link text or aria-label.
https://wiki.openstreetmap.org/wiki/OpenStreetMap_Carto; https://wiki.openstreetmap.org/wiki/CyclOSM; https://wiki.openstreetmap.org/wiki/OpenCycleMap; https://wiki.openstreetmap.org/wiki/Transport_Map; https://wiki.openstreetmap.org/wiki/Tracestrack; https://wiki.openstreetmap.org/wiki/Humanitarian; https://wiki.openstreetmap.org/wiki/Shortbread; https://wiki.openstreetmap.org/wiki/MapTiler
Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.
Learn more ▾ ▴
Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.
Source: MDN target / OWASP
Icon-only buttons need an aria-label so screen readers can announce them.
button.btn (#56 on page); button.btn (#74 on page); button.reverse_directions (#113 on page); button.btn (#116 on page); button.btn (#146 on page); button.btn (#186 on page); button.reverse_directions (#225 on page); button.btn-close (#230 on page); button.btn-close (#352 on page)
Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.
Source: WCAG 2.1 SC 4.1.2
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
C404 Error PageActionHTTP 404, custom pageREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 8 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Select Language | 13.09:1 | 3.0:1 | #000000 | #AAD3DF | Pass |
| h2 Welcome to OpenStree… | 18.78:1 | 3.0:1 | #000000 | #EAF4F7 | Pass |
| h2 Map Layers | 18.78:1 | 3.0:1 | #000000 | #EAF4F7 | Pass |
| h2 Legend | 18.78:1 | 3.0:1 | #000000 | #EAF4F7 | Pass |
| h2 Share | 18.78:1 | 3.0:1 | #000000 | #EAF4F7 | Pass |
| title OpenStreetMap | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| a OpenStreetMap | 21.00:1 | 4.5:1 | #000000 | #FFFFFF | Pass |
| button Where is this? | 2.66:1 | 4.5:1 | #000000 | #445459 | Fail |
| option GraphHopper | 2.66:1 | 4.5:1 | #000000 | #445459 | Fail |
| option OSRM | 2.66:1 | 4.5:1 | #000000 | #445459 | Fail |
| option Valhalla | 2.40:1 | 4.5:1 | #000000 | #434C53 | Fail |
| a Edit | 2.66:1 | 4.5:1 | #000000 | #445459 | Fail |
| a Edit with iD (in-bro… | 3.29:1 | 4.5:1 | #000000 | #605F5D | Fail |
| a Edit with Remote Con… | 3.34:1 | 4.5:1 | #000000 | #61605D | Fail |
| a History | 2.88:1 | 4.5:1 | #000000 | #545759 | Fail |
| a Export | 6.16:1 | 4.5:1 | #000000 | #8C8B87 | Pass |
| button More | 7.49:1 | 4.5:1 | #000000 | #979B9D | Pass |
| a GPS Traces | 4.70:1 | 4.5:1 | #000000 | #797774 | Pass |
| a User Diaries | 17.44:1 | 4.5:1 | #000000 | #EBEAE6 | Pass |
| a Communities | 18.30:1 | 4.5:1 | #000000 | #F2EFE9 | 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.
AHeading Hierarchy7 headingsPASS
- H1 OpenStreetMap
- H1 Select Language duplicate H1
- H1 (empty)
- H2 Welcome to OpenStreetMap!
- H2 Map Layers
- H2 Legend
- H2 Share
A page should have only one H1. Multiple H1s dilute the document outline.
Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.
Learn more ▾ ▴
HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.
Source: WCAG 2.4.6 / Google Search Central
Empty headings appear in the document outline but provide no information.
Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.
Source: WCAG 2.4.6
A+Alt Text QualityAll 9 images OKPASS
AFavicon & Branding22 icon(s) detectedPASS
AWeb ManifestPWA-readyPASS
A+Print StylesheetPrint styles detectedPASS
A+Lighthouse Accessibility AuditsScore 96/100 — 1 failing, 22 passedPASS
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
body.map-layout > header.d-flex > h1.d-flex > a#menu-icon body.map-layout > header.d-flex > h1.d-flex > a#menu-icon |
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.