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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #ffffff
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 ModePartial Dark Mode
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::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 4 <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.
B
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 "Mobile nav" MAIN CONTENTINFO footer

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

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.

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
404 Error Page
HTTP 404, custom page
REVIEW
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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not found - Auth0 ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
10 icon(s) detected
REVIEW
10 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
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A+
Heading Hierarchy
52 headings
PASS
52 headings
Info::
Single H1 present
  • H1 Secure AI agents, humans, and whatever comes next
  • H2 Auth0 is an easy to implement, adaptable authentication and authorization platform
  • H3 Integrate Auth0 in any application in just 5 minutes
  • H2 Built for what you’re building
  • H2 Secure your AI Agents
  • H2 Safeguard internal AI tools
  • H2 Unlock enterprise deals
  • H2 More signups. Less friction.
  • H2 Built for what you’re building
  • H2 Secure your AI Agents
  • H2 Safeguard internal AI tools
  • H2 Unlock enterprise deals
  • H2 More signups. Less friction.
  • H2 You’re in great company
  • H3 Auth0 lets Philips Hue focus on R&D, not IAM
  • H3 Why Snyk Trusts Auth0 to Deliver Security from the Ground Up
  • H3 Auth0 lets Philips Hue focus on R&D, not IAM
  • H3 Why Snyk Trusts Auth0 to Deliver Security from the Ground Up
  • H2 Read. Watch. Code. More.
  • H3 Customer Identity Trends Report 2025: Securing customer trust in the age of AI
  • H3 Introducing Auth for GenAI: The future of AI security
  • H3 Securing your AI agents: A technical demo
  • H3 Unlock the future of customer trust & AI
  • H3 Customer Identity Trends Report 2025: Securing customer trust in the age of AI
  • H3 Introducing Auth for GenAI: The future of AI security
  • H3 Securing your AI agents: A technical demo
  • H3 Unlock the future of customer trust & AI
  • H3 How to power consistent, multi-brand, omnichannel experiences
  • H3 The future of development: Why identity and AI are perfect partners
  • H3 Build vs buy: Guide to evaluating identity management
  • H3 Why development teams choose ready-made CIAM solutions
  • H3 How to power consistent, multi-brand, omnichannel experiences
  • H3 The future of development: Why identity and AI are perfect partners
  • H3 Build vs buy: Guide to evaluating identity management
  • H3 Why development teams choose ready-made CIAM solutions
  • H3 Unlock the power of custom user flows with Auth0 forms
  • H3 Auth0 introduction
  • H3 The developer's guide to single sign-on (SSO)
  • H3 Fine-Grained Authorization (FGA): A technical primer
  • H3 Unlock the power of custom user flows with Auth0 forms
  • H3 Auth0 introduction
  • H3 The developer's guide to single sign-on (SSO)
  • H3 Fine-Grained Authorization (FGA): A technical primer
  • H3 Time to think about customer identity
  • H3 Make your UX dance with CIAM
  • H3 Your one-stop buyers guide to Customer Identity
  • H3 Build and scale your product faster
  • H3 Time to think about customer identity
  • H3 Make your UX dance with CIAM
  • H3 Your one-stop buyers guide to Customer Identity
  • H3 Build and scale your product faster
  • H3 Ready to start securing AI agents, delivering amazing user experiences, or building the next big B2B app?
A+
Alt Text Quality
All 130 images OK
PASS
All 130 images OK
Info::
55 decorative image(s) correctly marked
Info::
75 image(s) with good alt text
130 images 75 good alt text 55 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 4 controls have issues
PASS
1 of 4 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>
Info::
3 control(s) properly labeled
4 controls
3 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
selectselectLanguage selectoraria-label
#react-aria-:R6cje6:selectselectaria-label
#react-aria-:R1mje6:selectselectaria-label
selectselect(none)none

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

<select>

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

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 Secure AI agents, hu…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Auth0 is an easy to …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built for what you…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Secure your AI Agent…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Safeguard internal A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Unlock enterprise de…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 More signups. Less f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Built for what you…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Secure your AI Agent…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Safeguard internal A…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Unlock enterprise de…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 More signups. Less f…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 You’re in great co…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Read. Watch. Code. M…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Integrate Auth0 in a…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Auth0 lets Philips H…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Why Snyk Trusts Auth…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Auth0 lets Philips H…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Why Snyk Trusts Auth…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Customer Identity Tr…21.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 93/100 — 2 failing, 28 passed
PASS
93

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.

ARIA

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AI assistant body > q-focus-sentinel > div
After AI assistant body > q-focus-sentinel > div
AI assistant, start div#qualified-multimodal-host > div
AI assistant, end div#qualified-multimodal-host > div

These are opportunities to improve the usage of ARIA in your application which 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
Menu header.sc-dd041119-3 > nav.sc-dd041119-9 > div.sc-dd041119-10 > button.sc-dd041119-11

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
●`[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.
●Select elements have associated label elements.
●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
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<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
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields 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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○Identical links have the same purpose.
○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