Skip to content
https://www.prefect.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) 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.
Page Structure — as a screen reader sees it
BANNER (missing!) NAV MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

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

B
Alt Text Quality
2 of 21 images have issues
REVIEW
2 of 21 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
19 image(s) with good alt text
21 images 19 good alt text 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page Not Found | Prefect ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
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 Automation for
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
32px · mid-page
h1 the context era
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
32px · mid-page
h2 Orchestrate workflows. Build AI applicat…
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · mid-page
h2 The standards for Python automation.
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Two platforms.
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted in
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 production
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 What teams are saying
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Start building today
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Product
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Resources
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Company
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Social
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy Preference Center
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy Preference Center
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Prefect
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 FastMCP
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Prefect Cloud
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Prefect Horizon
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Your Privacy
1.06:1
#000000
on
#0A0A0A
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Automation for1.06:13.0:1
#000000
#0A0A0A
Fail
h1 the context era1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Orchestrate workflow…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 The standards for Py…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Two platforms.1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Trusted in1.06:13.0:1
#000000
#0A0A0A
Fail
h2 production1.06:13.0:1
#000000
#0A0A0A
Fail
h2 What teams are sayin…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Start building today1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Product1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Resources1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Company1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Social1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Privacy Preference C…1.06:13.0:1
#000000
#0A0A0A
Fail
h2 Privacy Preference C…1.06:13.0:1
#000000
#0A0A0A
Fail
h3 Prefect1.06:13.0:1
#000000
#0A0A0A
Fail
h3 FastMCP1.06:13.0:1
#000000
#0A0A0A
Fail
h3 Prefect Cloud1.06:13.0:1
#000000
#0A0A0A
Fail
h3 Prefect Horizon1.06:13.0:1
#000000
#0A0A0A
Fail
h3 Your Privacy1.06:13.0:1
#000000
#0A0A0A
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.

A+
Heading Hierarchy
39 headings
PASS
39 headings
Info::
Single H1 present
  • H1 Automation forthe context era
  • H2 Orchestrate workflows. Build AI applications. Open-source foundations, production-ready platforms.
  • H2 The standards for Python automation.
  • H3 Prefect
  • H3 FastMCP
  • H2 Two platforms.One mission.
  • H3 Prefect Cloud
  • H3 Prefect Horizon
  • H2 Trusted inproduction
  • H2 What teams are saying
  • H2 Start building today
  • H2 Product
  • H2 Resources
  • H2 Company
  • H2 Social
  • H2 Privacy Preference Center
  • H3 Your Privacy
  • H3 Performance Cookies
  • H3 Targeting Cookies
  • H3 Functional Cookies
  • H3 Strictly Necessary Cookies
  • H4 Your Privacy
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H4 Functional Cookies
  • H4 Strictly Necessary Cookies
  • H3 Cookie List
  • H2 Privacy Preference Center
  • H3 Your Privacy
  • H3 Performance Cookies
  • H3 Targeting Cookies
  • H3 Functional Cookies
  • H3 Strictly Necessary Cookies
  • H4 Your Privacy
  • H4 Performance Cookies
  • H4 Targeting Cookies
  • H4 Functional Cookies
  • H4 Strictly Necessary Cookies
  • H3 Back
A
Form Accessibility
1 of 16 controls have issues
PASS
1 of 16 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="vendor-search-handler" id="vendor-search-handler">
Info::
15 control(s) properly labeled
16 controls
15 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
#ot-group-id-C0002checkboxPerformance Cookiesfor/id
#ot-group-id-C0004checkboxTargeting Cookiesfor/id
#ot-group-id-C0003checkboxFunctional Cookiesfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#chkbox-idcheckboxcheckbox labelfor/id
#vendor-search-handlertext(none)none

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

<input type="text" name="vendor-search-handler" id="vendor-search-handler">

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

A+
Lighthouse Accessibility Audits
Score 96/100 — 1 failing, 27 passed
PASS
96

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
Trusted in Production section.w-full > div.mx-auto > div.flex > p.text-xs
One mission. div.max-w-7xl > div.max-w-3xl > h2.text-4xl > span.text-foreground/30
Reject All div#onetrust-button-group-parent > div#onetrust-button-group > div.banner-actions-container > button#onetrust-reject-all-handler

These are opportunities to improve the legibility of your content.

○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
●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○No form fields have multiple labels
○`<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
○Links are distinguishable without relying on color.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback