Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 5 REVIEW 2 FIX

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Link & Button Quality

Action

100 links, 4 buttons — all OK

REVIEW

100 links, 4 buttons — all OK

8 image-only link(s) without alt text

8 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://support.1password.com/1password-privacy/; https://hackerone.com/1password; https://www.1password.community/; https://www.1password.community/category/top/blog/random-but-memorable; /newsletter; /legal; https://trust.1password.io/; https://marketplace.1password.com/

84 link(s) with descriptive text

100 links

0 empty

0 generic text

8 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://support.1password.com/1password-…	Privacy	new tab	Add '(opens in new tab)' to text
https://hackerone.com/1password	Bug bounty	new tab	Add '(opens in new tab)' to text
https://www.1password.community/	Community	new tab	Add '(opens in new tab)' to text
https://www.1password.community/category…	Podcast	new tab	Add '(opens in new tab)' to text
/newsletter	Newsletter	new tab	Add '(opens in new tab)' to text
/legal	Legal Center	new tab	Add '(opens in new tab)' to text
https://trust.1password.io/	Trust Center	new tab	Add '(opens in new tab)' to text
https://marketplace.1password.com/	1Password Marketplace	new tab	Add '(opens in new tab)' to text
https://twitter.com/1Password	1Password on X	new tab	Add '(opens in new tab)' to text
https://1password.social/@1password	1Password on Mastodon	new tab	Add '(opens in new tab)' to text
https://www.reddit.com/r/1Password	1Password on Reddit	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/1PasswordVideos	1Password on YouTube	new tab	Add '(opens in new tab)' to text
https://github.com/1Password	1Password on GitHub	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/1passwo…	1Password on LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/1password/	1Password on Instagram	new tab	Add '(opens in new tab)' to text
https://blog.1password.com/index.xml	1Password RSS	new tab	Add '(opens in new tab)' to text

88 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://support.1password.com/1password-privacy/; https://hackerone.com/1password; https://www.1password.community/; https://www.1password.community/category/top/blog/random-but-memorable; /newsletter; /legal; https://trust.1password.io/; https://marketplace.1password.com/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title California Consumer Privacy Act (CCPA) Opt-Out Icon ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

Name present: 1Password

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name 1Password ✓192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode browser ✗

Name 1Password Display Mode browser Theme Color #1a8cff Background Color #1a8cff Icons 2 icon(s)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

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 Detected ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 13 fail WCAG AA

REVIEW

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

7 pass 13 fail WCAG AA

h1 Secure access for every human and AI age…

1.25:1

#000000

#1D1D21

needs 3.0:1 (large text)

32px · above the fold

h2 Discover, secure, audit

1.24:1

#000000

#1C1C20

needs 3.0:1 (large text)

24px · above the fold

h2 Security has to keep up

2.94:1

#000000

#1451BD

needs 3.0:1 (large text)

24px · mid-page

h3 Govern credential and secret usage by hu…

1.37:1

#000000

#1A253B

needs 3.0:1 (large text)

19px · mid-page

h3 Secure and control passwords, passkeys, …

1.66:1

#000000

#19325F

needs 3.0:1 (large text)

19px · mid-page

h3 Discover apps, manage spend, and control…

2.06:1

#000000

#173E84

needs 3.0:1 (large text)

19px · mid-page

p Visibility and control for humans and AI…

1.25:1

#000000

#1D1D21

needs 4.5:1 (normal text)

16px · above the fold

span Talk to sales

1.25:1

#000000

#1D1D21

needs 4.5:1 (normal text)

16px · above the fold

span View plans

1.25:1

#000000

#1D1D21

needs 4.5:1 (normal text)

16px · above the fold

span Modern identity security for modern work

1.25:1

#000000

#1D1D21

needs 4.5:1 (normal text)

16px · above the fold

p 1Password brings control and governance …

1.27:1

#000000

#1B1F28

needs 4.5:1 (normal text)

16px · mid-page

span Explore 1Password® Unified Access

1.50:1

#000000

#1A2B4D

needs 4.5:1 (normal text)

16px · mid-page

span Try Enterprise Password Manager

1.85:1

#000000

#183872

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Secure access for ev…	1.25:1	3.0:1	#000000	#1D1D21	Fail
h2 Discover, secure, au…	1.24:1	3.0:1	#000000	#1C1C20	Fail
h2 Security has to keep…	2.94:1	3.0:1	#000000	#1451BD	Fail
h2 Bring modern access …	4.55:1	3.0:1	#000000	#2B6FE9	Pass
h3 Govern credential an…	1.37:1	3.0:1	#000000	#1A253B	Fail
h3 Secure and control p…	1.66:1	3.0:1	#000000	#19325F	Fail
h3 Discover apps, manag…	2.06:1	3.0:1	#000000	#173E84	Fail
title Passwords, Secrets, …	10.79:1	4.5:1	#000000	#CBB88E	Pass
a Skip to Main Content	10.79:1	4.5:1	#000000	#CBB88E	Pass
span Learn how Unified Ac…	10.79:1	4.5:1	#000000	#CBB88E	Pass
span agents	16.42:1	4.5:1	#000000	#EAE3D2	Pass
span Business	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Personal	21.00:1	4.5:1	#000000	#FFFFFF	Pass
p Visibility and contr…	1.25:1	4.5:1	#000000	#1D1D21	Fail
span Talk to sales	1.25:1	4.5:1	#000000	#1D1D21	Fail
span View plans	1.25:1	4.5:1	#000000	#1D1D21	Fail
span Modern identity secu…	1.25:1	4.5:1	#000000	#1D1D21	Fail
p 1Password brings con…	1.27:1	4.5:1	#000000	#1B1F28	Fail
span Explore 1Password® …	1.50:1	4.5:1	#000000	#1A2B4D	Fail
span Try Enterprise Passw…	1.85:1	4.5:1	#000000	#183872	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+

Landmark Structure

4 landmarks

PASS

4 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

20 headings, 1 skip(s)

PASS

20 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H6 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 Secure access for every human and AI agent
H2 Discover, secure, audit
H3 Govern credential and secret usage by humans and agents
H3 Secure and control passwords, passkeys, and secrets
H3 Discover apps, manage spend, and control SaaS access
H2 Security has to keep up
H3 88%AI adoption is accelerating
H3 70%SSO isn’t enough
H3 52%Shadow IT persists
H2 Bring modern access under control
H6 Downloads skipped
H6 1Password products
H6 Features
H6 Solutions
H6 Resources
H6 Developers
H6 Support
H6 Company
H6 Partners
H6 Downloads

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

All 18 images OK

PASS

All 18 images OK

1 image(s) with alt text over 125 characters

13 decorative image(s) correctly marked

4 image(s) with good alt text

18 images 4 good alt text 13 decorative

Issue	Count
too long	1 image(s)

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Favicon & Branding

8 icon(s) detected

PASS

8 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Lighthouse Accessibility Audits

Score 94/100 — 2 failing, 27 passed

PASS

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

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
Downloads `div.flex > div.bg-transparent > div > div.mb-3`
1Password products `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Features `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Solutions `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Resources `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Developers `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Support `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Company `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`
Partners `div.max-w-redesignFullWidth > div.flex > div > div.cursor-pointer`

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
Downloads `div.bg-transparent > div > div.mb-3 > h6.flex-[0_1_0%]`

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

●`[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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●ARIA input fields have accessible names

●Elements use only permitted ARIA attributes

●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 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.

●Skip links are focusable.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○Elements with `role="dialog"` or `role="alertdialog"` 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

○Links are distinguishable without relying on color.

○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>`.

○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.