Skip to content
https://sentry.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 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-5bon6w
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
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
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 Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://sentry.io/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://sentry.io/manifest.json

Manifest contains invalid JSON.

D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #6a5fc1
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 ModePartial Dark Mode
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::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
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.
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 Code
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
32px · bottom of viewport
h1 fix it faster
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Developer first.
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Everything’s
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Debugging needs context—
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Loved by developers
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get started
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built to be secure,
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Get monthly product updates
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fix It
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Solutions
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Products
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Products
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Integrations
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Integrations
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
h3 SDKs
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
h3 SDKs
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Learn
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Learn
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Support
1.31:1
#000000
on
#271944
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Code1.31:13.0:1
#000000
#271944
Fail
h1 fix it faster1.31:13.0:1
#000000
#271944
Fail
h2 Developer first.1.31:13.0:1
#000000
#271944
Fail
h2 Everything’s1.31:13.0:1
#000000
#271944
Fail
h2 Debugging needs cont…1.31:13.0:1
#000000
#271944
Fail
h2 Loved by developers1.31:13.0:1
#000000
#271944
Fail
h2 Get started1.31:13.0:1
#000000
#271944
Fail
h2 Built to be secure,1.31:13.0:1
#000000
#271944
Fail
h2 Get monthly product …1.31:13.0:1
#000000
#271944
Fail
h2 Fix It1.31:13.0:1
#000000
#271944
Fail
h3 Solutions1.31:13.0:1
#000000
#271944
Fail
h3 Products1.31:13.0:1
#000000
#271944
Fail
h3 Products1.31:13.0:1
#000000
#271944
Fail
h3 Integrations1.31:13.0:1
#000000
#271944
Fail
h3 Integrations1.31:13.0:1
#000000
#271944
Fail
h3 SDKs1.31:13.0:1
#000000
#271944
Fail
h3 SDKs1.31:13.0:1
#000000
#271944
Fail
h3 Learn1.31:13.0:1
#000000
#271944
Fail
h3 Learn1.31:13.0:1
#000000
#271944
Fail
h3 Support1.31:13.0:1
#000000
#271944
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.

B
Lighthouse Accessibility Audits
Score 89/100 — 3 failing, 28 passed
REVIEW
89

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.transition-colors > main#main-content > div.toggle-container body.transition-colors > main#main-content > div.toggle-container

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Automatically root-cause any issue Catch critical issues before you merge and … div.feature-carousel-wrapper > div.carousel-gradient-container > div#feature-carousel-ojaxx97oi > div.carousel-item
Break production less Predict and prevent the errors that matter most before t… div.feature-carousel-wrapper > div.carousel-gradient-container > div#feature-carousel-ojaxx97oi > div.carousel-item
Stay in the flow From GitHub, Slack, Jira, and Linear to coding agents with Se… div.feature-carousel-wrapper > div.carousel-gradient-container > div#feature-carousel-ojaxx97oi > div.carousel-item

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.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Next.js Angular Android iOS Flutter React Native .NET MAUI Python Node.js React… div.getting-started-container > div.flex > div.select-wrapper > select#installation-dropdown-23

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.

○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 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
●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.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●All heading elements contain content.
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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 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
○`<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
○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>`.
○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.
A+
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV "main" MAIN CONTENTINFO footer
A+
Heading Hierarchy
37 headings
PASS
37 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H3 Solutions
  • H3 Products
  • H3 Products
  • H3 Integrations
  • H3 Integrations
  • H3 SDKs
  • H3 SDKs
  • H3 Learn
  • H3 Learn
  • H3 Support
  • H3 Support
  • H3 Hang out with us
  • H3 Hang out with us
  • H3 Bi-weekly Intro to Sentry Demo
  • H1 Code breaks, fix it faster
  • H2 Developer first. Always.
  • H3 Monitor in five lines
  • H3 Automatically root-cause any issue
  • H3 Break production less
  • H3 Stay in the flow
  • H3 Monitor in five lines
  • H3 Automatically root-cause any issue
  • H3 Break production less
  • H3 Stay in the flow
  • H2 Everything’s connected
  • H3 Go from Issue → Context → Fix.
  • H2 Debugging needs context—
with or without AI
  • H2 Loved by developers worldwide
  • H2 Get started in minutes
  • H2 Built to be secure, Designed to not get in your way
  • H2 Get monthly product updates
from our newsletter
  • H3 (empty)
  • H2 Fix It
  • H3 Company
  • H3 Platform
  • H3 Solutions
  • H3 Get Help

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A
Alt Text Quality
All 58 images OK
PASS
All 58 images OK
Info::
20 image(s) with alt text over 125 characters
Info::
26 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
58 images 12 good alt text 26 decorative
IssueCount
too long20 image(s)
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select id="installation-dropdown-23">
Info::
2 control(s) properly labeled
3 controls
2 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#EmailemailYour Email:for/id
#sentry_newsletter_consentcheckboxnone
#installation-dropdown-23select(none)none

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

<select id="installation-dropdown-23">

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback