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 7 FIX

Link & Button Quality

Action

5 issue(s) across 124 links and 19 buttons

FIX

5 issue(s) across 124 links and 19 buttons

5 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /customers/figma; /customers/openai; /customers/ramp; /customers/cursor; /customers/vercel

6 image-only link(s) without alt text

5 link(s) open in new tab without warning

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

Got: https://www.instagram.com/notionhq/; https://twitter.com/NotionHQ; https://www.linkedin.com/company/notionhq/; https://www.facebook.com/NotionHQ/; https://www.youtube.com/channel/UCoSvlWS5XcwaSzIcbuJ-Ysg

108 link(s) with descriptive text

124 links

5 empty

0 generic text

5 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/customers/figma	(empty)	empty	Add link text or aria-label
/customers/openai	(empty)	empty	Add link text or aria-label
/customers/ramp	(empty)	empty	Add link text or aria-label
/customers/cursor	(empty)	empty	Add link text or aria-label
/customers/vercel	(empty)	empty	Add link text or aria-label
/customers/toyota	Streamlined workflows to reduc…	img no alt	Add alt attribute to the image
/customers/ramp	“With Notion, every person a…	img no alt	Add alt attribute to the image
/customers/vercel	“Notion understands that you…	img no alt	Add alt attribute to the image
/customers/match	“Notion has been the most po…	img no alt	Add alt attribute to the image
/customers/cursor	“Using the most AI‑native …	img no alt	Add alt attribute to the image
/customers/figma	One hub for work and AI keeps …	img no alt	Add alt attribute to the image
https://www.instagram.com/notionhq/	Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com/NotionHQ	X	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/notionh…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/NotionHQ/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCoSvlWS…	YouTube	new tab	Add '(opens in new tab)' to text

127 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/customers/figma; /customers/openai; /customers/ramp; /customers/cursor; /customers/vercel

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.instagram.com/notionhq/; https://twitter.com/NotionHQ; https://www.linkedin.com/company/notionhq/; https://www.facebook.com/NotionHQ/; https://www.youtube.com/channel/UCoSvlWS5XcwaSzIcbuJ-Ysg

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

Action

HTTP 401, custom page

FIX

HTTP 401, custom page

Unexpected status code: HTTP 401

Expected HTTP 404 but received 401. This may confuse search engine crawlers.

Got: HTTP 401

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 401 ✗Page Title Notion ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 2 <nav> element(s)

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.

Landmark Structure

13 landmarks

PASS

13 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

A+

Heading Hierarchy

27 headings

PASS

27 headings

Single H1 present

H2 AI features
H2 Explore use cases
H2 Teams
H2 Company size
H2 Use Cases
H2 Browse
H2 Discover
H2 Learn
H1 One workspace. Zero busywork.
H2 Notion is where your teams and AI agents capture knowledge, find answers, and automate projects. Now a team of 7 feels like 70.
H2 Introducing Notion 3.0
H3 Notion Agent
H3 Custom Agents
H2 Automate repetitive tasks.
H3 Enterprise Search
H2 One search for everything.
H3 AI Meeting Notes
H2 Perfect notes, every time.
H3 Flexible workflows
H2 Manage any project, big or small.
H2 More productivity. Fewer tools.
H2 Trusted by teams that ship.
H2 Let Notion AI handle the busywork.
H2 Try for free.
H3 Get started on Notion
H3 Notion Mail
H3 Notion Calendar

A+

Alt Text Quality

All 30 images OK

PASS

All 30 images OK

16 decorative image(s) correctly marked

14 image(s) with good alt text

30 images 14 good alt text 16 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 13 controls labeled

PASS

All 13 controls labeled

13 control(s) properly labeled

13 controls

13 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
tools	checkbox		none
teamSize	number	Team size	none

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)

Element	Ratio	Required	FG	BG	Result
h1 One workspace. Zero …	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 AI features	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Explore use cases	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Teams	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Company size	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Use Cases	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Browse	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Discover	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Learn	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Notion is where your…	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Introducing Notion 3…	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Automate repetitive …	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 One search for every…	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Perfect notes, every…	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Manage any project, …	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 More productivity. F…	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Trusted by teams tha…	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Let Notion AI handle…	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h2 Try for free.	19.29:1	3.0:1	#000000	#F6F5F4	Pass
h3 Custom Agents	19.29:1	3.0:1	#000000	#F6F5F4	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 97/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.

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
New `header.bentoHeader_header__vF0Xh > a.bentoHeader_headingLink__bmWJK > h3.semanticTypography_semanticTypography__mWJkv > span.badge_badge__4ppzB`
See what Custom Agents can do `div.homepage_customAgentsSection__m_WOD > section#:R9bikjm: > div.flex > h3.semanticTypography_semanticTypography__mWJkv`

These are opportunities to improve the legibility of your content.

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
Download `div.downloadApps_downloadsContainer__l1wNv > div.downloadApps_block__ZSEcT > div.downloadApps_blockContent__r_j_n > a.button_button__atjat`
Download `div.downloadApps_downloadsContainer__l1wNv > div.downloadApps_block__ZSEcT > div.downloadApps_blockContent__r_j_n > a.button_button__atjat`

○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

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

●ARIA attributes are used as specified for the element's role

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

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

●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

○`button`, `link`, and `menuitem` elements have accessible names

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

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

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