Skip to content
https://notion.site

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-itriy8
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://notion.site/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://notion.site/manifest.json

Manifest contains invalid JSON.

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
No navigation patterns
FIX
No navigation patterns
Info::
2 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 2 <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.
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 25 passed
REVIEW
88

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

Some ARIA roles have required attributes that describe the state of the element to screen readers. Learn more about roles and required attributes.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Notion uses cookies to offer you a better experience. div.column-content > div > div > p#consent-dialog-title

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.

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 a.homepageBentoCarousel_headerLink__bHx_5 > header.bento_bentoHeader__v_SR2 > div.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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Go to slide 1 div.bentoCarouselHeader_header__9fxKg > div.bentoCarouselHeader_mobileFooter__DA14D > div.bentoCarouselHeader_dots__ILMaq > button.bentoCarouselHeader_dot__wg0Vi
Go to slide 2 div.bentoCarouselHeader_header__9fxKg > div.bentoCarouselHeader_mobileFooter__DA14D > div.bentoCarouselHeader_dots__ILMaq > button.bentoCarouselHeader_dot__wg0Vi
Go to slide 3 div.bentoCarouselHeader_header__9fxKg > div.bentoCarouselHeader_mobileFooter__DA14D > div.bentoCarouselHeader_dots__ILMaq > button.bentoCarouselHeader_dot__wg0Vi
Go to slide 4 div.bentoCarouselHeader_header__9fxKg > div.bentoCarouselHeader_mobileFooter__DA14D > div.bentoCarouselHeader_dots__ILMaq > button.bentoCarouselHeader_dot__wg0Vi

These items highlight common accessibility best practices.

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>`
●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
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●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.
○No element has a `[tabindex]` value greater than 0
○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
○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.
A
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
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" MAIN CONTENTINFO footer

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
31 headings
PASS
31 headings
Info::
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 Meet the night shift.
  • H2 Keep work moving 24/7.
  • H2 Automate repetitive work for your team.
  • H3 See what Custom Agents can do
  • H3 Triage product feedback→
  • H3 Resolve support tickets in Slack→
  • H3 Respond to security alerts faster→
  • H3 Automate weekly reporting→
  • H3 Create your own Custom Agent→
  • H2 Ask your on-demand assistants.
  • H2 You assign the tasks. Notion Agent does the work.
  • H2 One search for everything.
  • H2 Perfect notes, every time.
  • H2 Bring all your work together.
  • H2 Simple and powerful.
  • H2 One source of truth for teams and agents.
  • H2 Less tracking. More progress.
  • H2 More productivity. Fewer tools.
  • H2 Trusted by teams that ship.
  • H2 Try for free.
  • H3 Get started on Notion
  • H3 Notion Mail
  • H3 Notion Calendar
A+
Alt Text Quality
All 70 images OK
PASS
All 70 images OK
Info::
34 decorative image(s) correctly marked
Info::
36 image(s) with good alt text
70 images 36 good alt text 34 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 13 controls labeled
PASS
All 13 controls labeled
Info::
13 control(s) properly labeled
13 controls
13 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
toolscheckboxnone
teamSizenumberTeam sizenone
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 Meet the night shift…15.07:13.0:1
#000000
#D9DAE1
Pass
h2 AI features15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Explore use cases15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Teams15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Company size15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Use Cases15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Browse15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Discover15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Learn15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Keep work moving 24/…15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Automate repetitive …15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Ask your on-demand a…15.07:13.0:1
#000000
#D9DAE1
Pass
h2 You assign the tasks…15.07:13.0:1
#000000
#D9DAE1
Pass
h2 One search for every…15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Perfect notes, every…15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Bring all your work …15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Simple and powerful.15.07:13.0:1
#000000
#D9DAE1
Pass
h2 One source of truth …15.07:13.0:1
#000000
#D9DAE1
Pass
h2 Less tracking. More …15.07:13.0:1
#000000
#D9DAE1
Pass
h2 More productivity. F…15.07:13.0:1
#000000
#D9DAE1
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