Skip to content
https://hcaptcha.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 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
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::
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.
C
Landmark Structure
Action
6 landmarks
REVIEW
6 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 contentinfo (footer) 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 header NAV "Footer" MAIN (missing!) CONTENTINFO (missing!)

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
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-0bqve3spllsb">; <textarea name="h-captcha-response" id="h-captcha-response-0bqve3spllsb">
2 controls
0 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#g-recaptcha-response-0bqve3spllsbtextarea(none)none
#h-captcha-response-0bqve3spllsbtextarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-0bqve3spllsb">; <textarea name="h-captcha-response" id="h-captcha-response-0bqve3spllsb">

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

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 ✗
A
Heading Hierarchy
41 headings
PASS
41 headings
Warning::
Multiple H1 headings (7 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H5 hCaptcha Enterprise
  • H1 Understand intent. Stop abuse.
  • H2 Protect your services from automated and human threats, while preserving user privacy.
  • H3 or Contact Sales
  • H2 Looking for hCaptcha Free or Pro?
  • H3 compare plans
  • H1 Protecting category leaders in every industry duplicate H1
  • H1 Switch from reCAPTCHA with two lines of code. duplicate H1
  • H2 Comprehensive Security On Demand
  • H3 One integration, many use cases
  • H3 Ultra low friction, fully customizable
  • H2 Compliant and Universal
  • H3 Works in every country
  • H3 Designed for accessibility
  • H2 A new kind of MFA. Zero tolling attacks.
  • H3 We flipped the script on SMS
  • H3 Stronger Verification
  • H3 Richer Signals for ATO Detection
  • H1 Find Threats Without Fingerprinting Your Users duplicate H1
  • H2 Use Advanced Threat Signatures
  • H2 Stop Account Takeovers
  • H2 Find Human Fraud and Abuse Fast
  • H3 Private Learning is a Revolution in Security ML
  • H3 Risk Insights Powers Analysis and Your Own ML
  • H1 Our Expertise is Applied 24/7 duplicate H1
  • H2 Compare Plans
  • H3 Publisher
  • H3 Pro
  • H3 Enterprise
  • H1 Who uses hCaptcha? duplicate H1
  • H2 hCaptcha is the largest independent service of its kind. From Global 2000 to startups, thousands of enterprises choose hCaptcha to protect their online services.
  • H2 Enterprise Features
  • H2 Our Expertise is Applied 24/7
  • H3 Empower your SOC with Security ML, or let us manage response
  • H1 See hCaptcha Enterprise in Action duplicate H1
  • H2 Company
  • H2 Resources
  • H2 Contact Us
  • H2 Company
  • H2 Resources
  • H2 Contact

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

A+
Alt Text Quality
All 122 images OK
PASS
All 122 images OK
Info::
105 decorative image(s) correctly marked
Info::
17 image(s) with good alt text
122 images 17 good alt text 105 decorative
All images have appropriate alt text.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Understand intent. S…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Protecting category …21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Find Threats Without…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Our Expertise is App…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Who uses hCaptcha?21.00:13.0:1
#000000
#FFFFFF
Pass
h1 See21.00:13.0:1
#000000
#FFFFFF
Pass
h1 in Action21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Protect your service…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Looking for hCaptcha…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Comprehensive Securi…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Compliant and Univer…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A new kind of MFA. Z…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Use Advanced Threat …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Stop Account Takeove…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Find Human Fraud and…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Compare Plans21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Enterprise Features21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Expertise is App…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Resources21.00:13.0: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+
Lighthouse Accessibility Audits
Score 95/100 — 3 failing, 24 passed
PASS
95

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
Contact Sales div.cta-flex-row > h3.grey-500-text > a.contact-sales-link-v2 > span.vavilon
e-Commerce div.tabs-2 > div.enterprisev2-box-content-subtitle > a#w-tabs-1-data-w-tab-0 > div.who-category

These are opportunities to improve the legibility of your content.

Best practices

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.w-mod-js html.w-mod-js

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
two lines of code div.enterprisev2-box-with-img-container > div.div-block-136 > h1.enterprivev2-box-heading-center > a.teal-link
○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
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Links have a discernible name
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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
○Buttons have an accessible name
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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
○`<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.
○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.

Send Feedback