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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
2
REVIEW
6
PASS
5
INFO
0
Checks
13
5 PASS 6 REVIEW 2 FIX
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::
3 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 3 <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
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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 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
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page Not Found | Bitwarden ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
19 icon(s) detected
REVIEW
19 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color #175ddc ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

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

19 pass 1 fail WCAG AA 1 pass AA only
title Best Password Manager for Business, Ente…
1.73:1
#000000
on
#0C3276
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Defend against hacke…18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Simple to use18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Easy to manage18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Trusted security18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Why millions trust B…18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Business protection18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Personal security18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Uncover shadow IT an…18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Everything you need …18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Generate, save, and …18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Centralized administ…18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Integrate with your …18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Easy imports18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Share with others18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Self-host option18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Best enterprise pass…18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Why you need a passw…18.57:13.0:1
#000000
#F0F1F2
Pass
h3 Get powerful, truste…18.57:13.0:1
#000000
#F0F1F2
Pass
title Best Password Manage…1.73:14.5:1
#000000
#0C3276
Fail
p This page is display…5.55:14.5:1
#000000
#6D84AD
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
Heading Hierarchy
49 headings, 1 skip(s)
PASS
49 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.
  • H5 Password Manager
  • H5 Developer Products
  • H5 Explore More
  • H5 Personal Plans Top Features
  • H5 Business Plans Top Features
  • H5 Top Tools
  • H5 Resource Library
  • H5 Security & Trust
  • H5 Training
  • H5 Password Manager
  • H5 Developer Products
  • H5 Explore More
  • H5 Personal Plans Top Features
  • H5 Business Plans Top Features
  • H5 Top Tools
  • H5 Resource Library
  • H5 Security & Trust
  • H5 Training
  • H1 Defend against hackers and data breaches
  • H3 Simple to use skipped
  • H3 Easy to manage
  • H3 Trusted security
  • H3 Why millions trust Bitwarden
  • H3 Business protection
  • H3 Personal security
  • H3 Uncover shadow IT and reduce credential risks
  • H3 Everything you need in a password manager
  • H3 Generate, save, and autofill
  • H3 Centralized administration
  • H3 Integrate with your tools
  • H3 Easy imports
  • H3 Share with others
  • H3 Self-host option
  • H3 Best enterprise password manager
  • H3 Why you need a password manager
  • H4 Protect against hackers
  • H4 Autofill effortlessly
  • H4 Don’t feed the phish!
  • H3 Get powerful, trusted password security now. Pick your plan.
  • H4 Basic Free
  • H4 Premium
  • H4 Families
  • H4 Teams
  • H4 Enterprise
  • H4 Request a quote
  • H4 Products
  • H4 Company
  • H4 Resources
  • H4 Tools & Help

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

A
Alt Text Quality
1 of 27 images have issues
PASS
1 of 27 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
26 image(s) with good alt text
27 images 26 good alt text 1 missing
IssueCount
missing1 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

A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#footer-languageselectLanguagefor/id
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Bitwarden
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Bitwarden ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Bitwarden Display Mode standalone Theme Color #175ddc Background Color #ffffff Icons 8 icon(s)
A+
Lighthouse Accessibility Audits
Score 99/100 — 1 failing, 29 passed
PASS
99

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
Simple to use div.@3xl:flex > div.@3xl:w-2/3 > div > h3.h5

These are opportunities to improve keyboard navigation in your application.

○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
●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
●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.
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●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 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
○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.
○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