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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
41
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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 Raycast - Your shortcut to everything Custom Styling Navigation Homepage Link Search Form
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
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
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Heading Hierarchy
Action
20 headings, 3 skip(s)
REVIEW
20 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Your shortcut to everything.
  • H2 It’s not about saving time.
  • H2 There’s an extension for that.
  • H3 Plus thousands more...
  • H2 Your Mac just got smarter.
  • H2 Built for professionals like you.
  • H2 Don't repeat yourself.
  • H5 Snippets skipped
  • H5 Quicklinks
  • H5 Hotkeys and Aliases
  • H2 Stay in the loop.
  • H5 Slack skipped
  • H5 X/Twitter
  • H3 Build the perfect tools.
  • H4 React to macOS
  • H4 Built-in UI
  • H4 Batteries included
  • H4 Publish to the Store
  • H2 Take the short way.
  • H5 Subscribe to our newsletter. skipped

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

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

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input>; <input type="submit">
2 controls
0 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
inputinput(none)none
inputsubmit(none)none

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

<input>; <input type="submit">

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

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 Your shortcut to everything.
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
32px · above the fold
h2 It’s not about saving time.
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 There’s an extension for that.
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your Mac just got smarter.
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built for professionals like you.
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Don't repeat yourself.
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stay in the loop.
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Take the short way.
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Plus thousands more...
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Build the perfect tools.
1.05:1
#000000
on
#07080A
needs 3.0:1 (large text)
19px · bottom of viewport
title Raycast - Your shortcut to everything
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Store
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Pro
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · top of page (header area)
a iOS
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Windows
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · above the fold
a Teams
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · above the fold
a Developers
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · above the fold
a Blog
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · above the fold
a Pricing
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · above the fold
a Log in
1.05:1
#000000
on
#07080A
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Your shortcut to eve…1.05:13.0:1
#000000
#07080A
Fail
h2 It’s not about sav…1.05:13.0:1
#000000
#07080A
Fail
h2 There’s an extensi…1.05:13.0:1
#000000
#07080A
Fail
h2 Your Mac just got sm…1.05:13.0:1
#000000
#07080A
Fail
h2 Built for profession…1.05:13.0:1
#000000
#07080A
Fail
h2 Don't repeat yoursel…1.05:13.0:1
#000000
#07080A
Fail
h2 Stay in the loop.1.05:13.0:1
#000000
#07080A
Fail
h2 Take the short way.1.05:13.0:1
#000000
#07080A
Fail
h3 Plus thousands more.…1.05:13.0:1
#000000
#07080A
Fail
h3 Build the perfect to…1.05:13.0:1
#000000
#07080A
Fail
title Raycast - Your short…1.05:14.5:1
#000000
#07080A
Fail
a Store1.05:14.5:1
#000000
#07080A
Fail
a Pro1.05:14.5:1
#000000
#07080A
Fail
a iOS1.05:14.5:1
#000000
#07080A
Fail
a Windows1.05:14.5:1
#000000
#07080A
Fail
a Teams1.05:14.5:1
#000000
#07080A
Fail
a Developers1.05:14.5:1
#000000
#07080A
Fail
a Blog1.05:14.5:1
#000000
#07080A
Fail
a Pricing1.05:14.5:1
#000000
#07080A
Fail
a Log in1.05:14.5:1
#000000
#07080A
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 85/100 — 5 failing, 22 passed
REVIEW
85

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.ExtensionHighlight_container__aojC1 > div.ExtensionHighlight_bottom__fmUy9 > div.ExtensionHighlight_pagination__m71T_ > button.ExtensionHighlight_previous__vaBCj div.ExtensionHighlight_container__aojC1 > div.ExtensionHighlight_bottom__fmUy9 > div.ExtensionHighlight_pagination__m71T_ > button.ExtensionHighlight_previous__vaBCj
div.ExtensionHighlight_container__aojC1 > div.ExtensionHighlight_bottom__fmUy9 > div.ExtensionHighlight_pagination__m71T_ > button.ExtensionHighlight_next__yGcNX div.ExtensionHighlight_container__aojC1 > div.ExtensionHighlight_bottom__fmUy9 > div.ExtensionHighlight_pagination__m71T_ > button.ExtensionHighlight_next__yGcNX
div.SnippetsShowcase_snippetsShowcase__fglRC > div.SnippetsShowcase_addressSnippet__76DsF > div.SnippetsShowcase_controls__fR6_T > button.SnippetsShowcase_emojiPicker__94s1h div.SnippetsShowcase_snippetsShowcase__fglRC > div.SnippetsShowcase_addressSnippet__76DsF > div.SnippetsShowcase_controls__fR6_T > button.SnippetsShowcase_emojiPicker__94s1h

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
div#navbar > div.Navbar_navbar__XlgWY > div.Navbar_logoContainer__enocR > a div#navbar > div.Navbar_navbar__XlgWY > div.Navbar_logoContainer__enocR > a
div#root > div.CommunitySection_container__8ZibF > div.CommunitySection_footer__9b00k > a.ArrowLink_link__WKebC div#root > div.CommunitySection_container__8ZibF > div.CommunitySection_footer__9b00k > a.ArrowLink_link__WKebC

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.

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
One interface, everything you need. div.page_sectionContainer__86OJv > div.Features_container__cNA2k > div.SectionTitle_container__qvIRZ > p
Use your favorite tools without even opening them. div.ExtensionHighlight_top__Nem0f > div.ExtensionHighlight_text__gMfVY > div.SectionTitle_container__qvIRZ > p
AI where it’s most useful - on your OS. div.page_sectionContainer__86OJv > div.AIShowCase_title__JqKIV > div.SectionTitle_container__qvIRZ > p
Used by seriously productive people. div.page_sectionContainer__86OJv > div > div.SectionTitle_container__qvIRZ > p
Creator, MKBHD div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Founder, Framer div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Designer & Iconograph div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Creator, Tailwind CSS div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Co-host, SyntaxFM div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Creator, Dive Club div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
CEO, Stellate div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Angel Investor div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Founding Engineer div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Founder div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Design Engineer div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Design Engineer div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Student div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Designer div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Designer div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Student div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Developer Advocate div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Runway AI div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Design Advocate div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Designer, OpenAI div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Designer div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Founder, Dub div.Testimonials_embla__oOmX5 > div.Testimonials_embla__container__QZsiM > div.Testimonials_embla__slide__fUmrA > span.Testimonials_title__echp9
Automate the things you do all the time. div.page_sectionContainer__86OJv > div.Automation_container__39AlV > div.SectionTitle_container__qvIRZ > p
Track your flights. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Convert anything. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Search files. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Run scripts. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Manage your windows. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Plan your day. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Remind you of stuff. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Translate into any language. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Block distractions. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Find text in screenshots. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
Insert Emojis. div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > span > span.FeatureWall_text__KtcCg
And much, much more. div.FeatureWall_container__ealcz > div.FeatureWall_left__5x6NB > div.FeatureWall_wall__BRIeA > a.FeatureWall_text__KtcCg
Join the community and learn how other people get the most out of Raycast. div.CommunitySection_container__8ZibF > div.CommunitySection_socials___HNIF > div.SectionTitle_container__qvIRZ > p
Download and use Raycast for free. div.CommandYourTime_container__S_HJo > div.CommandYourTime_action__EYknz > div.SectionTitle_container__qvIRZ > p

These are opportunities to improve the legibility of your content.

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
Snippets div.Automation_card__7Lygc > div.Automation_top__n4uSt > div.Automation_description__gITAR > h5
Slack div.CommunitySection_socials___HNIF > a.CommunitySection_socialCard__Grpqk > div.CommunitySection_header__52zZJ > h5
Subscribe to our newsletter. div.Footer_content__WG3KU > div.Footer_newsletter__wZsad > div.Footer_text__UYcCR > h5

These are opportunities to improve keyboard navigation in your application.

Best practices

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.__variable_f367f3 html.__variable_f367f3

These items highlight common accessibility best practices.

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
Image elements have `[alt]` attributes
Input buttons have discernible text.
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.
`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.
No element has a `[tabindex]` value greater than 0
Touch targets have sufficient size and spacing.
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
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 type="image">` elements have `[alt]` text
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
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.
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+
Alt Text Quality
All 97 images OK
PASS
All 97 images OK
Info::
39 decorative image(s) correctly marked
Info::
58 image(s) with good alt text
97 images 58 good alt text 39 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback