Skip to content
https://city-data.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
F
Heading Hierarchy
Action
26 headings, 4 skip(s)
FIX
26 headings, 4 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
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.
  • H2 Welcome to City-Data
  • H2 Quick navigation
  • H4 Our California data skipped
  • H2 By category
  • H4 Cities skipped
  • H4 Schools
  • H4 Neighborhoods
  • H4 Assessments
  • H4 Restaurant Inspection Findings
  • H2 Interactive data map
  • H2 Our data in action. City-Data Blog.
  • H2 Join our community. City-Data Forum.
  • H2 Our City Guides.
  • H2 Our Tools
  • H4 Compare two cities skipped
  • H4 Advanced U.S. city search
  • H4 Ideal Meeting Place
  • H4 Travel Time Maps
  • H4 Gasoline Usage Calculators for Trips
  • H2 House and Property Values
  • H2 Restaurant Inspections and Reviews
  • H2 Canada
  • H2 What's on City-Data.com
  • H4 Local data skipped
  • H4 Additional data
  • H4 General information

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

D
Form Accessibility
Action
6 of 6 controls have issues
FIX
6 of 6 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <select id="selColType">; <input type="text" id="vmapOSM">; <select id="selmapOSM">; <input type="text" id="sbox">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="NM" id="intelligent_search">
6 controls
0 labeled
1 placeholder only
5 unlabeled
ControlTypeLabelMethod
#intelligent_searchtext(Search City-Data.com)placeholder only
inputsubmit(none)none
#selColTypeselect(none)none
#vmapOSMtext(none)none
#selmapOSMselect(none)none
#sboxtext(none)none

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

<input type="submit">; <select id="selColType">; <input type="text" id="vmapOSM">; <select id="selmapOSM">; <input type="text" id="sbox">

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 type="text" name="NM" id="intelligent_search">

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

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ 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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Back-to-top link detected
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)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
D
Lighthouse Accessibility Audits
Action
Score 66/100 — 8 failing, 14 passed
FIX
66

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
CA div#quickview_tabSelected > p > a > span.badge
CA div#quickview_tabSelected > p > a > span.badge
CA div#quickview_tabSelected > p > a > span.badge
CA div#quickview_tabSelected > p > a > span.badge
Loading data... please wait div#mapOSM > div#loadingMSG > center > strong
Loading data... please wait div#interactiveBoxMap > div#mapBox > div#lastCont > div#mapOSM_legend
City-Data Blog div.col-md-12 > div.col-md-9 > p.textowo > a
Popular New Year’s resolutions div.blog-articles > ul.list-inline > li > a
Dec 31 div.blog-articles > ul.list-inline > li > i
Christmas is America’s favorite holiday season div.blog-articles > ul.list-inline > li > a
Dec 24 div.blog-articles > ul.list-inline > li > i
Fish in the American dish: recreational fishing div.blog-articles > ul.list-inline > li > a
Dec 10 div.blog-articles > ul.list-inline > li > i
American hunting and wildlife div.blog-articles > ul.list-inline > li > a
Nov 19 div.blog-articles > ul.list-inline > li > i
The National Football League is an American treasure div.blog-articles > ul.list-inline > li > a
Nov 12 div.blog-articles > ul.list-inline > li > i
city guides div.col-md-12 > div.col-md-9 > p.textowo > a
Alberta div.col-md-6 > ul.canada_list > li > a
British Columbia div.col-md-6 > ul.canada_list > li > a
Manitoba div.col-md-6 > ul.canada_list > li > a
New Brunswick div.col-md-6 > ul.canada_list > li > a
Newfoundland and Labrador div.col-md-6 > ul.canada_list > li > a
Northwest Territories div.col-md-6 > ul.canada_list > li > a
Nova Scotia div.col-md-6 > ul.canada_list > li > a
Nunavut div.col-md-6 > ul.canada_list > li > a
Ontario div.col-md-6 > ul.canada_list > li > a
Prince Edward Island div.col-md-6 > ul.canada_list > li > a
Quebec div.col-md-6 > ul.canada_list > li > a
Saskatchewan div.col-md-6 > ul.canada_list > li > a
Yukon Territory div.col-md-6 > ul.canada_list > li > a

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
City-Data Blog. div.col-md-9 > h2.featurette-heading > span.text-muted > a
City-Data Blog div.col-md-12 > div.col-md-9 > p.textowo > a
City-Data Forum. div.col-md-9 > h2.featurette-heading > span.text-muted > a
city guides div.col-md-12 > div.col-md-9 > p.textowo > a
Top 100 City Lists div.container > div.col-md-7 > p > a
Top 101 City Lists div.container > div.col-md-7 > p > a
random city pictures div.container > div.col-md-7 > p > a

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
Our California data div.col-md-12 > div#by_state_map > div#quickview_tabSelected > h4
Cities div#tabs_by_category > div.tab-content > div#home1 > h4.h4-lista
Compare two cities div.container > div.col-md-12 > div.col-md-6 > h4
Local data div.container > div.col-md-6 > div.col-md-12 > h4.h4-lista-footer

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
div#mapBox > div#firstCont > div#map_searchPanel > input#sbox div#mapBox > div#firstCont > div#map_searchPanel > input#sbox

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
Median household income ($) Median household income (% change since 2000) House… div#interactiveBoxMap > div#mapBox > div#firstCont > select#selmapOSM

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.navbar > div.container-menu > div.navbar-header > a.navbar-brand div.navbar > div.container-menu > div.navbar-header > a.navbar-brand

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
div.navbar > div.container-menu > div.navbar-header > a.navbar-brand div.navbar > div.container-menu > div.navbar-header > a.navbar-brand
OK div.col-md-12 > div#by_state_map > div > a.states_map_links
ND div.col-md-12 > div#by_state_map > div > a.states_map_links
SD div.col-md-12 > div#by_state_map > div > a.states_map_links
NE div.col-md-12 > div#by_state_map > div > a.states_map_links
KS div.col-md-12 > div#by_state_map > div > a.states_map_links
AR div.col-md-12 > div#by_state_map > div > a.states_map_links
LA div.col-md-12 > div#by_state_map > div > a.states_map_links
MS div.col-md-12 > div#by_state_map > div > a.states_map_links
AL div.col-md-12 > div#by_state_map > div > a.states_map_links
GA div.col-md-12 > div#by_state_map > div > a.states_map_links
SC div.col-md-12 > div#by_state_map > div > a.states_map_links
IL div.col-md-12 > div#by_state_map > div > a.states_map_links
MI div.col-md-12 > div#by_state_map > div > a.states_map_links
IN div.col-md-12 > div#by_state_map > div > a.states_map_links
OH div.col-md-12 > div#by_state_map > div > a.states_map_links
TN div.col-md-12 > div#by_state_map > div > a.states_map_links
KY div.col-md-12 > div#by_state_map > div > a.states_map_links
NC div.col-md-12 > div#by_state_map > div > a.states_map_links
WV div.col-md-12 > div#by_state_map > div > a.states_map_links
VA div.col-md-12 > div#by_state_map > div > a.states_map_links
PA div.col-md-12 > div#by_state_map > div > a.states_map_links
NY div.col-md-12 > div#by_state_map > div > a.states_map_links
VT div.col-md-12 > div#by_state_map > div > a.states_map_links
NH div.col-md-12 > div#by_state_map > div > a.states_map_links
RI div.col-md-12 > div#by_state_map > div > a.states_map_links
CT div.col-md-12 > div#by_state_map > div > a.states_map_links
NJ div.col-md-12 > div#by_state_map > div > a.states_map_links
DE div.col-md-12 > div#by_state_map > div > a.states_map_links
MD div.col-md-12 > div#by_state_map > div > a.states_map_links
MA div.col-md-12 > div#by_state_map > div > a.states_map_links
DC div.col-md-12 > div#by_state_map > div > a.states_map_links
div#firstCont > label#CM_seriesSwitch > div > input div#firstCont > label#CM_seriesSwitch > div > input
YT div.col-md-12 > div.col-md-6 > div > a.canada_map_links
NT div.col-md-12 > div.col-md-6 > div > a.canada_map_links
NU div.col-md-12 > div.col-md-6 > div > a.canada_map_links
BC div.col-md-12 > div.col-md-6 > div > a.canada_map_links
AB div.col-md-12 > div.col-md-6 > div > a.canada_map_links
MB div.col-md-12 > div.col-md-6 > div > a.canada_map_links
ON div.col-md-12 > div.col-md-6 > div > a.canada_map_links
PE div.col-md-12 > div.col-md-6 > div > a.canada_map_links
NS div.col-md-12 > div.col-md-6 > div > a.canada_map_links
NB div.col-md-12 > div.col-md-6 > div > a.canada_map_links
Nova Scotia div.col-md-6 > ul.canada_list > li > a
Nunavut div.col-md-6 > ul.canada_list > li > a
Ontario div.col-md-6 > ul.canada_list > li > a
Saskatchewan div.col-md-6 > ul.canada_list > li > a
Yukon Territory div.col-md-6 > ul.canada_list > li > a
Forum Archive 1, div.col-md-3 > ul.footer-lista > li > a
2, div.col-md-3 > ul.footer-lista > li > a
3, div.col-md-3 > ul.footer-lista > li > a
4, div.col-md-3 > ul.footer-lista > li > a
5, div.col-md-3 > ul.footer-lista > li > a
6, div.col-md-3 > ul.footer-lista > li > a
7, div.col-md-3 > ul.footer-lista > li > a
8, div.col-md-3 > ul.footer-lista > li > a
9, div.col-md-3 > ul.footer-lista > li > a
10, div.col-md-3 > ul.footer-lista > li > a
11, div.col-md-3 > ul.footer-lista > li > a
12, div.col-md-3 > ul.footer-lista > li > a
13, div.col-md-3 > ul.footer-lista > li > a
14, div.col-md-3 > ul.footer-lista > li > a
15, div.col-md-3 > ul.footer-lista > li > a
16, div.col-md-3 > ul.footer-lista > li > a
17, div.col-md-3 > ul.footer-lista > li > a
18, div.col-md-3 > ul.footer-lista > li > a
19, div.col-md-3 > ul.footer-lista > li > a
20, div.col-md-3 > ul.footer-lista > li > a
21, div.col-md-3 > ul.footer-lista > li > a
22, div.col-md-3 > ul.footer-lista > li > a
23, div.col-md-3 > ul.footer-lista > li > a
24, div.col-md-3 > ul.footer-lista > li > a
25, div.col-md-3 > ul.footer-lista > li > a
26, div.col-md-3 > ul.footer-lista > li > a
27, div.col-md-3 > ul.footer-lista > li > a
28, div.col-md-3 > ul.footer-lista > li > a
29, div.col-md-3 > ul.footer-lista > li > a
30, div.col-md-3 > ul.footer-lista > li > a
31 div.col-md-3 > ul.footer-lista > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Document has a `<title>` element
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`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
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted 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
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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 type="image">` elements have `[alt]` text
○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.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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 (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

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

B
Alt Text Quality
2 of 38 images have issues
REVIEW
2 of 38 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
36 image(s) with good alt text
38 images 36 good alt text 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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 1 fail WCAG AA
REVIEW

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

19 pass 1 fail WCAG AA 1 pass AA only
title City-Data.com - Stats about all US citie…
2.26:1
#000000
on
#474747
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Welcome to19.59:13.0:1
#000000
#F7F7F6
Pass
h2 Quick navigation19.59:13.0:1
#000000
#F7F7F6
Pass
h2 By category19.59:13.0:1
#000000
#F7F7F6
Pass
h2 Interactive data map19.59:13.0:1
#000000
#F7F7F6
Pass
h2 Our data in action.19.59:13.0:1
#000000
#F7F7F6
Pass
h2 Join our community.19.59:13.0:1
#000000
#F7F7F6
Pass
h2 Our19.59:13.0:1
#000000
#F7F7F6
Pass
h2 Our19.59:13.0:1
#000000
#F7F7F6
Pass
h2 Canada19.59:13.0:1
#000000
#F7F7F6
Pass
h2 What's on19.59:13.0:1
#000000
#F7F7F6
Pass
title City-Data.com - Stat…2.26:14.5:1
#000000
#474747
Fail
span Toggle navigation6.66:14.5:1
#000000
#919191
Pass
a Forum21.00:14.5:1
#000000
#FFFFFF
Pass
a Cities21.00:14.5:1
#000000
#FFFFFF
Pass
a Cities21.00:14.5:1
#000000
#FFFFFF
Pass
a Schools21.00:14.5:1
#000000
#FFFFFF
Pass
a Schools21.00:14.5:1
#000000
#FFFFFF
Pass
a Neighborhoods21.00:14.5:1
#000000
#FFFFFF
Pass
a Neighborhoods21.00:14.5:1
#000000
#FFFFFF
Pass
a Assessments21.00:14.5:1
#000000
#FFFFFF
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
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - City-Data.com ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback