Skip to content
https://yubico.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
8
REVIEW
2
PASS
3
INFO
0
Checks
13
3 PASS 2 REVIEW 8 FIX
F
Form Accessibility
Action
8 of 15 controls have issues
FIX
8 of 15 controls have issues
Critical::
4 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">
Warning::
4 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="text" name="s">; <input type="text" name="s">; <input type="email" name="email">
Info::
7 control(s) properly labeled
15 controls
7 labeled
4 placeholder only
4 unlabeled
ControlTypeLabelMethod
#CybotCookiebotDialogBodyLevelButtonNecessarycheckboxStrictly necessary cookiesfor/id
#CybotCookiebotDialogBodyLevelButtonPreferencescheckboxFunctional cookiesfor/id
#CybotCookiebotDialogBodyLevelButtonStatisticscheckboxPerformance cookiesfor/id
#CybotCookiebotDialogBodyLevelButtonMarketingcheckboxTargeting cookiesfor/id
#CybotCookiebotDialogBodyContentCheckboxPersonalInformationcheckboxDo not sell or share my personal informationfor/id
selectselectLanguage selectionaria-label
selectselectLanguage selectionaria-label
stext(Search Yubico)placeholder only
stext(Search Yubico)placeholder only
emailemail(Enter your email)placeholder only
stext(Search Yubico)placeholder only
#CybotCookiebotDialogBodyLevelButtonMarketingInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonNecessaryInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonPreferencesInlinecheckbox(none)none
#CybotCookiebotDialogBodyLevelButtonStatisticsInlinecheckbox(none)none

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

<input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonNecessaryInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonPreferencesInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonStatisticsInline">; <input type="checkbox" id="CybotCookiebotDialogBodyLevelButtonMarketingInline">

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="s">; <input type="text" name="s">; <input type="text" name="s">; <input type="email" name="email">

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

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 ✓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::
Search functionality detected
Got: role-search
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
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
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH 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

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

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

0 pass 20 fail WCAG AA
h1 Powerful Protection,
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
32px · bottom of viewport
h2 How It Works.
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Why our customers
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 How YubiKeys protect you online.
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Join our newsletter
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Plug In & Tap YubiKey
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Instant Login
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Stay Protected
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Ready to Try It?
2.03:1
#000000
on
#404040
needs 3.0:1 (large text)
19px · bottom of viewport
title Yubico | YubiKey Strong Two Factor Authe…
2.03:1
#000000
on
#404040
needs 4.5:1 (normal text)
16px · top of page (header area)
a Consent
2.03:1
#000000
on
#404040
needs 4.5:1 (normal text)
16px · top of page (header area)
a Details
1.90:1
#000000
on
#3A3D33
needs 4.5:1 (normal text)
16px · top of page (header area)
a [#IABV2SETTINGS#]
1.69:1
#000000
on
#30371F
needs 4.5:1 (normal text)
16px · top of page (header area)
a About
1.07:1
#000000
on
#060C0E
needs 4.5:1 (normal text)
16px · above the fold
div This website uses cookies
1.06:1
#000000
on
#060B0C
needs 4.5:1 (normal text)
16px · above the fold
div We use cookies to ensure that you get th…
1.05:1
#000000
on
#05090A
needs 4.5:1 (normal text)
16px · above the fold
div [#GPC_BANNER_ICON#]
1.05:1
#000000
on
#05090A
needs 4.5:1 (normal text)
16px · above the fold
div [#GPC_TOAST_TEXT#]
1.05:1
#000000
on
#05090A
needs 4.5:1 (normal text)
16px · above the fold
legend Consent Selection
1.05:1
#000000
on
#05090A
needs 4.5:1 (normal text)
16px · above the fold
strong Strictly necessary cookies
1.04:1
#000000
on
#040708
needs 3.0:1 (large text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Powerful Protection,2.03:13.0:1
#000000
#404040
Fail
h2 How It Works.2.03:13.0:1
#000000
#404040
Fail
h2 Why our customers2.03:13.0:1
#000000
#404040
Fail
h2 How YubiKeys protect…2.03:13.0:1
#000000
#404040
Fail
h2 Join our newsletter2.03:13.0:1
#000000
#404040
Fail
h3 Plug In & Tap YubiKe…2.03:13.0:1
#000000
#404040
Fail
h3 Instant Login2.03:13.0:1
#000000
#404040
Fail
h3 Stay Protected2.03:13.0:1
#000000
#404040
Fail
h3 Ready to Try It?2.03:13.0:1
#000000
#404040
Fail
title Yubico | YubiKey Str…2.03:14.5:1
#000000
#404040
Fail
a Consent2.03:14.5:1
#000000
#404040
Fail
a Details1.90:14.5:1
#000000
#3A3D33
Fail
a [#IABV2SETTINGS#]1.69:14.5:1
#000000
#30371F
Fail
a About1.07:14.5:1
#000000
#060C0E
Fail
div This website uses co…1.06:14.5:1
#000000
#060B0C
Fail
div We use cookies to en…1.05:14.5:1
#000000
#05090A
Fail
div [#GPC_BANNER_ICON#]1.05:14.5:1
#000000
#05090A
Fail
div [#GPC_TOAST_TEXT#]1.05:14.5:1
#000000
#05090A
Fail
legend Consent Selection1.05:14.5:1
#000000
#05090A
Fail
strong Strictly necessary c…1.04:13.0:1
#000000
#040708
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+
Heading Hierarchy
9 headings
PASS
9 headings
Info::
Single H1 present
  • H1 Powerful Protection, Instant Access
  • H2 How It Works.
  • H3 Plug In & Tap YubiKey
  • H3 Instant Login
  • H3 Stay Protected
  • H3 Ready to Try It?
  • H2 Why our customers love us.
  • H2 How YubiKeys protect you online.
  • H2 Join our newsletter
A
Alt Text Quality
3 of 73 images have issues
PASS
3 of 73 images have issues
Warning::
3 image(s) with generic alt text
Info::
70 image(s) with good alt text
73 images 70 good alt text 3 generic
IssueCount
generic3 image(s)
A
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 31 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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ybc-nav-topbar > div.ybc-nav-utilities > ybc-nav-menu-toggle > button.ybc-nav-menu-toggle div.ybc-nav-topbar > div.ybc-nav-utilities > ybc-nav-menu-toggle > button.ybc-nav-menu-toggle

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.

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
Consent div#CybotCookiebotDialogNav > ul#CybotCookiebotDialogNavList > li.CybotCookiebotDialogNavItem > a#CybotCookiebotDialogNavDeclaration
Accept all div.CybotCookiebotScrollArea > div#CybotCookiebotDialogBodyButtons > div#CybotCookiebotDialogBodyButtonsWrapper > button#CybotCookiebotDialogBodyLevelButtonLevelOptinAllowAll

These are opportunities to improve the legibility of your content.

○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
●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.
●Select elements have associated label elements.
●`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
●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
●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.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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
○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.
○`<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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback