Skip to content
https://okta.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
47
GRADE
F
FIX
8
REVIEW
3
PASS
2
INFO
0
Checks
13
2 PASS 3 REVIEW 8 FIX
F
Alt Text Quality
Action
56 of 109 images have issues
FIX
56 of 109 images have issues
Critical::
56 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
56 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
1 image(s) with alt text over 125 characters
Info::
24 decorative image(s) correctly marked
Info::
28 image(s) with good alt text
109 images 28 good alt text 24 decorative 56 missing
IssueCount
missing56 image(s)
too long1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
404 Error Page
Action
HTTP 404, custom page
FIX
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 404 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
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::
Skip navigation link detected
Info::
5 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 5 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Landmark Structure
12 landmarks
REVIEW
12 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
5 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "Secondary Navigation" 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

B
Heading Hierarchy
92 headings, 1 skip(s)
REVIEW
92 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Products
  • H4 Agentic AI Security
  • H4 Identity & Access Management
  • H4 Privileged Access Management
  • H4 Identity Threat Detection & Response
  • H4 Customer Identity & Access Management
  • H4 Identity Governance & Administration
  • H4 Integrations
  • H4 Platforms
  • H4 Okta
  • H4 Auth0
  • H3 Solutions
  • H4 By Identity Type
  • H4 By Industry
  • H4 Customer Success Stories
  • H3 Developers
  • H4 Okta Platform
  • H4 Auth0 Platform
  • H4 Release Overview
  • H3 Company
  • H4 About Okta
  • H4 Careers & community
  • H4 Values & Impact
  • H4 Discover our latest stories
  • H3 Products
  • H4 Agentic AI Security
  • H4 Identity & Access Management
  • H4 Privileged Access Management
  • H4 Identity Threat Detection & Response
  • H4 Customer Identity & Access Management
  • H4 Identity Governance & Administration
  • H4 Integrations
  • H4 Platforms
  • H4 Okta
  • H4 Auth0
  • H3 Solutions
  • H4 By Identity Type
  • H4 By Industry
  • H4 Customer Success Stories
  • H3 Developers
  • H4 Okta Platform
  • H4 Auth0 Platform
  • H4 Release Overview
  • H3 Company
  • H4 About Okta
  • H4 Careers & community
  • H4 Values & Impact
  • H4 Discover our latest stories
  • H1 Okta secures AI
  • H3 AI SECURITY STARTS HERE skipped
  • H3 Get expert resources for your AI strategy
  • H3 To get AI agent security right, you have to get identity right
  • H3 Secure all of your identities within an identity security fabric
  • H3 Ship amazing experiences with enterprise-grade customer identity
  • H2 Securing Fortune 100s, governments, and industries around the world
  • H3 McLaren Racing speeds toward seamless fan and partner experiences with Okta.
  • H3 Wyndham Hotels & Resorts gives 100 million users an unforgettable digital experience with Okta.
  • H3 Hitachi unifies governance and access for ~480,000 global users.
  • H3 With the Okta-powered TakedaID platform, Takeda delivers increased security that enables greater scalability.
  • H3 From chocolates to Chihuahuas: Okta helps Mars securely expand their universe of brands.
  • H3 FedEx improves their security posture by unifying identity and building a foundation for Zero Trust.
  • H2 Read. Watch. Learn. More.
  • H3 Okta announces new blueprint for the secure agentic enterprise
  • H3 The blueprint for the secure agentic enterprise
  • H3 Govern your AI agents from a single control plane
  • H3 Secure every identity, human and AI, with one fabric
  • H3 Unlocking ROI with Okta Identity Governance
  • H3 Securing AI agents at scale: Identity’s role in the agentic enterprise
  • H3 Explore the latest trends in secure, passwordless sign-in
  • H3 Explore our quarterly product release overview updates
  • H3 Look ahead to our top predictions for AI identity
  • H3 Cross App Access extends enterprise-grade security to your AI agents
  • H3 Todd’s Take: Why identity security is an AI imperative
  • H3 Learn to manage new AI risks and complex authorization
  • H3 Discover the details of our $1B share repurchase plan
  • H3 Meet the new SaaS and security leaders on our Board
  • H3 Okta deepens investment in India to drive global innovation
  • H2 A leader. Proven.
  • H2 Go further
  • H3 Start a free trial
  • H3 Expert webinars
  • H3 Talk to an expert
  • H2 (empty)
  • H2 Starting with Okta
  • H2 Help & Support
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary
  • H4 Functional
  • H4 Performance
  • H4 Marketing
  • H3 Cookie List

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

B
Lighthouse Accessibility Audits
Score 82/100 — 6 failing, 27 passed
REVIEW
82

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

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.sectioncontent > div#custom-carousel-logos-1 > div.sectioncontent__content > div.image
Go to slide 2 div.sectioncontent > div#custom-carousel-logos-1 > div.sectioncontent__content > div.image
Go to slide 3 div.sectioncontent > div#custom-carousel-logos-1 > div.sectioncontent__content > div.image
Go to slide 4 div.sectioncontent > div#custom-carousel-logos-1 > div.sectioncontent__content > div.image
Go to slide 5 div.sectioncontent > div#custom-carousel-logos-1 > div.sectioncontent__content > div.image
Go to slide 6 div.sectioncontent > div#custom-carousel-logos-1 > div.sectioncontent__content > div.image

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Customer carousel navigation div#container-3adf23bc50 > div.aem-Grid > div.sectioncontent > div#custom-carousel-logos-1

Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more about valid values for ARIA attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.sectioncontent > div#custom-carousel-logos-1 > div.sectioncontent__content > div.image

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.

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
AI SECURITY STARTS HERE div.cmp-content-block__content-wrapper > div.cmp-content-block__content > div.cmp-content-block__content-text > h3.cmp-content-block__overline

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.footer__wrapper > div.footer__foot-and-copyright > nav.intl-navigation > a#intl-menu-link-footer div.footer__wrapper > div.footer__foot-and-copyright > nav.intl-navigation > a#intl-menu-link-footer

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.

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
McLaren Racing speeds toward seamless fan and partner experiences with Okta. Se… div.sectioncontent > div#custom-customer-carousel-1 > div.sectioncontent__content > div.contentBlock
PRESS RELEASE Okta announces new blueprint for the secure agentic enterprise div.cmp-cards > div.cmp-cards__card-item-container > div.cmp-cards-item__wrapper > a.cmp-cards-item__wrapper-link
SOLUTION The blueprint for the secure agentic enterprise div.cmp-cards > div.cmp-cards__card-item-container > div.cmp-cards-item__wrapper > a.cmp-cards-item__wrapper-link
PRODUCT Govern your AI agents from a single control plane div.cmp-cards > div.cmp-cards__card-item-container > div.cmp-cards-item__wrapper > a.cmp-cards-item__wrapper-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-hidden="true"]` is not present on the document `<body>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[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.
●`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
●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
○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
○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
○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.
○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.
A+
Form Accessibility
All 8 controls labeled
PASS
All 8 controls labeled
Info::
8 control(s) properly labeled
8 controls
8 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ot-group-id-3checkboxFunctionalfor/id
#ot-group-id-2checkboxPerformancefor/id
#ot-group-id-4checkboxMarketingfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
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 Okta secures AI21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Securing Fortune 100…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Read. Watch. Learn. …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 A leader. Proven.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Go further21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Starting with Okta21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Help & Support21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Privacy Preference C…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Products21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Solutions21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Developers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Products21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Solutions21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Developers21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Company21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI SECURITY STARTS H…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Get expert resources…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 To get AI agent secu…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Secure all of your i…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.

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

Send Feedback