Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

3 PASS 4 REVIEW 6 FIX

Form Accessibility

Action

7 of 11 controls have issues

FIX

7 of 11 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="submit">; <input type="submit">

5 control(s) rely on placeholder only

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

Got: <input type="text" name="firstname" id="firstname-66814d48-6cf0-48d8-b0a4-6941ec393eeb_fsq_hs_form_speak-to-expert-v3-53023773-61ad-44ef-843b-b33dc489eaff66814d48-6cf0-48d8-b0a4-6941ec393eeb">; <input type="text" name="lastname" id="lastname-66814d48-6cf0-48d8-b0a4-6941ec393eeb_fsq_hs_form_speak-to-expert-v3-53023773-61ad-44ef-843b-b33dc489eaff66814d48-6cf0-48d8-b0a4-6941ec393eeb">; <input type="email" name="email" id="email-66814d48-6cf0-48d8-b0a4-6941ec393eeb_fsq_hs_form_speak-to-expert-v3-53023773-61ad-44ef-843b-b33dc489eaff66814d48-6cf0-48d8-b0a4-6941ec393eeb">; <textarea name="how_can_location_help_" id="how_can_location_help_-66814d48-6cf0-48d8-b0a4-6941ec393eeb_fsq_hs_form_speak-to-expert-v3-53023773-61ad-44ef-843b-b33dc489eaff66814d48-6cf0-48d8-b0a4-6941ec393eeb">; <input type="email" name="email" id="email-71cea14a-e9f8-4b6e-92c1-ecc26d2999af_fsq_hs_form_newsletter-e926ccad-5cae-4dce-8aa6-378464d7e2ff71cea14a-e9f8-4b6e-92c1-ecc26d2999af">

4 control(s) properly labeled

11 controls

4 labeled

5 placeholder only

2 unlabeled

Control	Type	Label	Method
#search_field	search		none
#LEGAL_CONSENT.subscription_type_356123413-66814d48-6cf0-48d8-b0a4-6941ec393eeb_fsq_hs_form_speak-to-expert-v3-53023773-61ad-44ef-843b-b33dc489eaff66814d48-6cf0-48d8-b0a4-6941ec393eeb	checkbox		none
#LEGAL_CONSENT.subscription_type_356123413-71cea14a-e9f8-4b6e-92c1-ecc26d2999af_fsq_hs_form_newsletter-e926ccad-5cae-4dce-8aa6-378464d7e2ff71cea14a-e9f8-4b6e-92c1-ecc26d2999af	checkbox		none
#LEGAL_CONSENT.processing-71cea14a-e9f8-4b6e-92c1-ecc26d2999af_fsq_hs_form_newsletter-e926ccad-5cae-4dce-8aa6-378464d7e2ff71cea14a-e9f8-4b6e-92c1-ecc26d2999af	checkbox		none
#how_can_location_help_-66814d48-6cf0-48d8-b0a4-6941ec393eeb_fsq_hs_form_speak-to-expert-v3-53023773-61ad-44ef-843b-b33dc489eaff66814d48-6cf0-48d8-b0a4-6941ec393eeb	textarea	(How can our location intelligence help you?)	placeholder only
#firstname-66814d48-6cf0-48d8-b0a4-6941ec393eeb_fsq_hs_form_speak-to-expert-v3-53023773-61ad-44ef-843b-b33dc489eaff66814d48-6cf0-48d8-b0a4-6941ec393eeb	text	(First name*)	placeholder only
#email-71cea14a-e9f8-4b6e-92c1-ecc26d2999af_fsq_hs_form_newsletter-e926ccad-5cae-4dce-8aa6-378464d7e2ff71cea14a-e9f8-4b6e-92c1-ecc26d2999af	email	(Enter email address...*)	placeholder only
#lastname-66814d48-6cf0-48d8-b0a4-6941ec393eeb_fsq_hs_form_speak-to-expert-v3-53023773-61ad-44ef-843b-b33dc489eaff66814d48-6cf0-48d8-b0a4-6941ec393eeb	text	(Last name*)	placeholder only
#email-66814d48-6cf0-48d8-b0a4-6941ec393eeb_fsq_hs_form_speak-to-expert-v3-53023773-61ad-44ef-843b-b33dc489eaff66814d48-6cf0-48d8-b0a4-6941ec393eeb	email	(Work email*)	placeholder only
input	submit	(none)	none
input	submit	(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

Link & Button Quality

Action

14 issue(s) across 172 links and 3 buttons

FIX

14 issue(s) across 172 links and 3 buttons

2 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: https://foursquare.com/; https://foursquare.com/products/

12 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://foursquare.com/resources/blog/products/foursquare-open-source-places-… ("Read more"); https://foursquare.com/products/attribution/ ("Learn more"); https://foursquare.com/products/audience/ ("Learn more"); https://foursquare.com/products/proximity/ ("Learn more"); https://foursquare.com/products/workbench/ ("Learn more"); https://foursquare.com/products/h3hub/ ("Learn more"); https://foursquare.com/products/spatial-desktop/ ("Learn more"); https://foursquare.com/products/studio/ ("Learn more"); https://foursquare.com/products/movement-sdk/ ("Learn more"); https://foursquare.com/products/places-api/ ("Learn more") (+2 more)

3 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://foursquare.com/products/workbench/"]; a[href="https://foursquare.com/products/h3hub/"]; a[href="https://foursquare.com/products/spatial-desktop/"]

23 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://opensource.foursquare.com/; https://swarmapp.com/; https://superlocal.com/; https://foursquare.com/developers/signup/?utm_source=websitelocation&&utm_cam…; https://docs.foursquare.com/; https://discord.com/invite/HRbXgRp8BN; https://docs.foursquare.com/developer/docs/developer-console-get-started; https://support.foursquare.com/hc/en-us/requests/new; https://opensource.foursquare.com/placemaker/; https://swarmapp.com/ (+13 more)

132 link(s) with descriptive text

172 links

2 empty

12 generic text

23 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://foursquare.com/	(empty)	empty	Add link text or aria-label
https://opensource.foursquare.com/	Open Source	new tab	Add '(opens in new tab)' to text
https://swarmapp.com/	Foursquare Swarm	new tab	Add '(opens in new tab)' to text
https://superlocal.com/	Superlocal	new tab	Add '(opens in new tab)' to text
https://foursquare.com/products/workbenc…	Spatial Workbench	img no alt	Add alt attribute to the image
https://foursquare.com/products/h3hub/	Spatial H3 Hub	img no alt	Add alt attribute to the image
https://foursquare.com/products/spatial-…	Spatial Desktop	img no alt	Add alt attribute to the image
https://foursquare.com/developers/signup…	Developer console	new tab	Add '(opens in new tab)' to text
https://docs.foursquare.com/	Documentation	new tab	Add '(opens in new tab)' to text
https://discord.com/invite/HRbXgRp8BN	Discord	new tab	Add '(opens in new tab)' to text
https://docs.foursquare.com/developer/do…	Quick start guide	new tab	Add '(opens in new tab)' to text
https://support.foursquare.com/hc/en-us/…	Support	new tab	Add '(opens in new tab)' to text
https://opensource.foursquare.com/placem…	Become a Placemaker	new tab	Add '(opens in new tab)' to text
https://foursquare.com/resources/blog/pr…	Read more	generic text	Replace with descriptive text
Before: Read more Suggested: Foursquare Open Source Places A New Foundational Dataset For The Geospatial Community
https://foursquare.com/products/	(empty)	empty	Add link text or aria-label
https://swarmapp.com/	Download Swarm	new tab	Add '(opens in new tab)' to text
https://studio.foursquare.com/api/auth/l…	Studio	new tab	Add '(opens in new tab)' to text
https://www.placed.com/ui/login	Attribution	new tab	Add '(opens in new tab)' to text
https://accounts.factual.com/login	Audience and Proximity	new tab	Add '(opens in new tab)' to text
https://foursquare.com/developers/signup…	Developer Console	new tab	Add '(opens in new tab)' to text
https://foursquare.com/resources/reports…	Get the guide	new tab	Add '(opens in new tab)' to text
https://foursquare.com/products/attribut…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Attribution
https://foursquare.com/products/audience…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Audience
https://foursquare.com/products/proximit…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Proximity
https://foursquare.com/products/workbenc…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Workbench
https://foursquare.com/products/h3hub/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: H3hub
https://foursquare.com/products/spatial-…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Spatial Desktop
https://foursquare.com/products/studio/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Studio
https://foursquare.com/products/movement…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Movement Sdk
https://foursquare.com/products/places-a…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Places Api
https://opensource.foursquare.com/os-pla…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Os Places
https://foursquare.com/products/places/	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Places
https://foursquare.com/products/privacy-…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://location.foursquare.com/legal/pr…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://swarmapp.com/	Download Swarm	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/foursqu…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://x.com/foursquare?lang=en	Twitter	new tab	Add '(opens in new tab)' to text
https://discord.com/channels/10022309259…	Discord	new tab	Add '(opens in new tab)' to text
https://vimeo.com/foursquarehq	Vimeo	new tab	Add '(opens in new tab)' to text
https://foursquare-studio.slack.com/	Slack	new tab	Add '(opens in new tab)' to text

135 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

https://foursquare.com/; https://foursquare.com/products/

Why this matters

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.

https://foursquare.com/resources/blog/products/foursquare-open-source-places-… ("Read more"); https://foursquare.com/products/attribution/ ("Learn more"); https://foursquare.com/products/audience/ ("Learn more"); https://foursquare.com/products/proximity/ ("Learn more"); https://foursquare.com/products/workbench/ ("Learn more"); https://foursquare.com/products/h3hub/ ("Learn more"); https://foursquare.com/products/spatial-desktop/ ("Learn more"); https://foursquare.com/products/studio/ ("Learn more"); https://foursquare.com/products/movement-sdk/ ("Learn more"); https://foursquare.com/products/places-api/ ("Learn more") (+2 more)

Why this matters

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

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://foursquare.com/products/workbench/"]; a[href="https://foursquare.com/products/h3hub/"]; a[href="https://foursquare.com/products/spatial-desktop/"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://opensource.foursquare.com/; https://swarmapp.com/; https://superlocal.com/; https://foursquare.com/developers/signup/?utm_source=websitelocation&&utm_cam…; https://docs.foursquare.com/; https://discord.com/invite/HRbXgRp8BN; https://docs.foursquare.com/developer/docs/developer-console-get-started; https://support.foursquare.com/hc/en-us/requests/new; https://opensource.foursquare.com/placemaker/; https://swarmapp.com/ (+13 more)

Why this matters

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

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 ✗

Heading Hierarchy

28 headings, 1 skip(s)

REVIEW

28 headings, 1 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

1 empty heading(s)

Empty headings appear in the document outline but provide no information.

H1 (empty)
H1 Connect real-world behavior to business outcomes duplicate H1
H3 #1 in location intelligence skipped
H3 500%+ with FSQ Attribution
H3 Best innovation in mobile & device development for Places API
H3 Discover the new standard for marketing measurement
H2 The trusted leader in location technology & data
H3 Quality at scale
H3 Privacy-forward
H3 Expertise
H3 Flexibility
H2 Harness the power of location data
H3 Attribution
H3 Audience
H3 Proximity
H3 Spatial Workbench
H3 Spatial H3 Hub
H3 Spatial Desktop
H3 Spatial Studio
H3 Movement SDK
H3 Places API
H3 Open Source
H3 Places
H4 Jamie Ogus
H2 Committed to data privacy
H2 Foursquare data, your way
H2 Speak to our experts
H2 Get the latest from Foursquare

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Foursquare ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 13 fail WCAG AA

REVIEW

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

7 pass 13 fail WCAG AA 1 pass AA only

h1 Connect

1.03:1

#000000

#000025

needs 3.0:1 (large text)

32px · bottom of viewport

h1 to business outcomes

1.03:1

#000000

#000025

needs 3.0:1 (large text)

32px · bottom of viewport

h2 The trusted leader in location technolog…

1.03:1

#000000

#000025

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Harness the power of location data

1.03:1

#000000

#000025

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Foursquare data, your way

1.03:1

#000000

#000025

needs 3.0:1 (large text)

24px · bottom of viewport

h3 #1 in location intelligence

1.03:1

#000000

#000025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 500%+ with FSQ Attribution

1.03:1

#000000

#000025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Best innovation in mobile & device devel…

1.03:1

#000000

#000025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Discover the new standard for marketing …

1.03:1

#000000

#000025

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Flexibility

1.03:1

#000000

#000025

needs 3.0:1 (large text)

19px · bottom of viewport

span Search

1.03:1

#000000

#000025

needs 4.5:1 (normal text)

16px · above the fold

a Products

1.03:1

#000000

#000025

needs 4.5:1 (normal text)

16px · above the fold

p Marketers

1.00:1

#000025

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Connect	1.03:1	3.0:1	#000000	#000025	Fail
h1 to business outcomes	1.03:1	3.0:1	#000000	#000025	Fail
h2 The trusted leader i…	1.03:1	3.0:1	#000000	#000025	Fail
h2 Harness the power of…	1.03:1	3.0:1	#000000	#000025	Fail
h2 Committed to data pr…	20.45:1	3.0:1	#FFFFFF	#000025	Pass
h2 Foursquare data, you…	1.03:1	3.0:1	#000000	#000025	Fail
h2 Speak to our experts	20.45:1	3.0:1	#FFFFFF	#000025	Pass
h3 #1 in location intel…	1.03:1	3.0:1	#000000	#000025	Fail
h3 500%+ with FSQ Attri…	1.03:1	3.0:1	#000000	#000025	Fail
h3 Best innovation in m…	1.03:1	3.0:1	#000000	#000025	Fail
h3 Discover the new sta…	1.03:1	3.0:1	#000000	#000025	Fail
h3 Flexibility	1.03:1	3.0:1	#000000	#000025	Fail
title Location Intelligenc…	11.72:1	4.5:1	#000000	#CEB6FC	Pass
a Skip to content	11.72:1	4.5:1	#000000	#CEB6FC	Pass
span Close	11.72:1	4.5:1	#000000	#CEB6FC	Pass
p Prove TV performance…	11.72:1	4.5:1	#000000	#CEB6FC	Pass
a Download now	4.60:1	4.5:1	#000000	#7C6DA6	Pass
span Search	1.03:1	4.5:1	#000000	#000025	Fail
a Products	1.03:1	4.5:1	#000000	#000025	Fail
p Marketers	1.00:1	4.5:1	#000025	#000025	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.

A+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Alt Text Quality

15 of 115 images have issues

PASS

15 of 115 images have issues

15 image(s) with generic alt text

48 decorative image(s) correctly marked

52 image(s) with good alt text

115 images 52 good alt text 48 decorative 15 generic

Issue	Count
generic	15 image(s)

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 29 passed

PASS

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.

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
Discover the new standard for marketing measurement `div.container > div.media_and_text__body > div.media_and_text__content > h3`

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.u-flex-column > div.site-branding > h1.site-title > a `div.u-flex-column > div.site-branding > h1.site-title > a`

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.

○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

●`[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

●Input buttons have discernible text.

●Form elements have associated labels

●`[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

●ARIA input fields have accessible names

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●All heading elements contain content.

●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 `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

○Select elements have associated label elements.

○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>`.

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.