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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
63
GRADE
D
FIX
5
REVIEW
2
PASS
6
INFO
0
Checks
13
6 PASS 2 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 404, bare page
FIX
HTTP 404, bare page
Info::
Correct 404 status code returned
Got: HTTP 404
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 404 ✓Page Title Not Found \ Anthropic ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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::
11 navigation landmark(s) detected
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 11 <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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A
Landmark Structure
16 landmarks
PASS
16 landmarks
Info::
<main> landmark present
Info::
11 <nav> landmark(s) found
Warning::
3 of 11 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
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

A
Heading Hierarchy
26 headings, 1 skip(s)
PASS
26 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 AI research and products that put safety at the frontierAI research and products that put safety at the frontier
  • H2 Project Glasswing
  • H2 Latest releases
  • H2 Claude Opus 4.6
  • H2 Claude is a space to think
  • H2 Claude on Mars
  • H2 At Anthropic, we build AI to serve humanity’s long-term well-being.
  • H2 ‍
  • H3 Core views on AI safety
  • H3 Anthropic’s Responsible Scaling Policy
  • H3 Anthropic Academy: Build and Learn with Claude
  • H3 Anthropic’s Economic Index
  • H3 Claude’s Constitution
  • H2 Footer
  • H3 Products
  • H3 Models
  • H3 Solutions
  • H3 Claude Platform
  • H3 Resources
  • H3 Help and security
  • H3 Company
  • H3 Terms and policies
  • H3 Cookie Settings
  • H6 Necessary skipped
  • H6 Analytics
  • H6 Marketing

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 1 images OK
PASS
All 1 images OK
Info::
1 decorative image(s) correctly marked
1 images 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 3 controls labeled
PASS
All 3 controls labeled
Info::
3 control(s) properly labeled
3 controls
3 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputcheckboxnone
#analytics-consentcheckboxnone
#marketing-consentcheckboxnone
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
h2 Project Glasswing18.08:13.0:1
#000000
#F0EEE6
Pass
h2 Latest releases18.08:13.0:1
#000000
#F0EEE6
Pass
h2 Claude Opus 4.618.08:13.0:1
#000000
#F0EEE6
Pass
h2 Claude is a space to…18.08:13.0:1
#000000
#F0EEE6
Pass
h2 Claude on Mars18.08:13.0:1
#000000
#F0EEE6
Pass
h2 At Anthropic, we bui…18.08:13.0:1
#000000
#F0EEE6
Pass
h2 ‍18.08:13.0:1
#000000
#F0EEE6
Pass
h2 Footer18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Core views on AI saf…18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Anthropic’s Respon…18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Anthropic Academy: B…18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Anthropic’s Econom…18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Claude’s Constitut…18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Products18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Models18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Solutions18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Claude Platform18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Resources18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Help and security18.08:13.0:1
#000000
#F0EEE6
Pass
h3 Company18.08:13.0:1
#000000
#F0EEE6
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 93/100 — 2 failing, 26 passed
PASS
93

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
Accept dialog#consent-container > div#consent-banner > div#simple-options > button#accept-btn

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link
ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link ul.w-list-unstyled > li > div.article-list-item > a.g_clickable_link
div#w-node-_1f7589da-b35f-83df-c217-2c60daf900d4-b8ec2927 > ul.footer_bottom_list > li.footer_bottom_item > a.footer_bottom_link_wrap div#w-node-_1f7589da-b35f-83df-c217-2c60daf900d4-b8ec2927 > ul.footer_bottom_list > li.footer_bottom_item > a.footer_bottom_link_wrap

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
●Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
●`[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.
●`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
●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.
●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
●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
○`[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
○Form elements have associated labels
○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.
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback