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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
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
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::
1 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 1 <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
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
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 (missing!) CONTENTINFO footer

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | Replicate ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light dark
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 light dark ✓Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

B
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

20 pass 6 pass AA only
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Run and fine-tune mo…4.94:13.0:1
#000000
#E3326C
Pass
h2 Run4.82:13.0:1
#000000
#DE356A
Pass
h2 with an4.81:13.0:1
#000000
#DF326C
Pass
h2 Thousands of models …5.03:13.0:1
#000000
#E43668
Pass
h2 How it works5.03:13.0:1
#000000
#E43668
Pass
h2 Scale on Replicate5.03:13.0:1
#000000
#E43668
Pass
h2 Imagine what you can…5.03:13.0:1
#000000
#E43668
Pass
h3 Run models5.03:13.0:1
#000000
#E43668
Pass
h3 Fine-tune models wit…5.03:13.0:1
#000000
#E43668
Pass
h3 Deploy custom models5.03:13.0:1
#000000
#E43668
Pass
title Replicate - Run AI w…21.00:14.5:1
#000000
#FFFFFF
Pass
span Get access to Seedan…21.00:14.5:1
#000000
#FFFFFF
Pass
kbd ctrl+k21.00:14.5:1
#000000
#FFFFFF
Pass
span Explore13.12:14.5:1
#000000
#F5B9F3
Pass
span Pricing6.45:14.5:1
#000000
#E54EDC
Pass
span Enterprise6.34:14.5:1
#000000
#E54DD4
Pass
span Docs6.22:14.5:1
#000000
#E54BCD
Pass
span Blog6.13:14.5:1
#000000
#E54AC6
Pass
span Sign in6.04:14.5:1
#000000
#E549BF
Pass
span Try for free5.95:14.5:1
#000000
#E548B8
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 5 failing, 24 passed
REVIEW
86

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#_R_cr655_ > div.group > div.absolute > button.r8-btn div#_R_cr655_ > div.group > div.absolute > button.r8-btn
div.code-snippet > div.group > div.absolute > button.r8-btn div.code-snippet > div.group > div.absolute > button.r8-btn
div.code-snippet > div.group > div.absolute > button.r8-btn div.code-snippet > div.group > div.absolute > button.r8-btn
div.code-snippet > div.group > div.absolute > button.r8-btn div.code-snippet > div.group > div.absolute > button.r8-btn
div.code-snippet > div.group > div.absolute > button.r8-btn div.code-snippet > div.group > div.absolute > button.r8-btn
div.code-snippet > div.group > div.absolute > button.r8-btn div.code-snippet > div.group > div.absolute > button.r8-btn
div.site-footer-bottom-content > div.site-footer-dark-mode-toggle > div > button.r8-btn div.site-footer-bottom-content > div.site-footer-dark-mode-toggle > div > button.r8-btn
div.site-footer-bottom-content > div.site-footer-dark-mode-toggle > div > button.r8-btn div.site-footer-bottom-content > div.site-footer-dark-mode-toggle > div > button.r8-btn
div.site-footer-bottom-content > div.site-footer-dark-mode-toggle > div > button.r8-btn div.site-footer-bottom-content > div.site-footer-dark-mode-toggle > div > button.r8-btn

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
import div.flex > pre.lowlight > code.hljs > span.hljs-keyword
from div.flex > pre.lowlight > code.hljs > span.hljs-keyword
const div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
new div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
const div.flex > pre.lowlight > code.hljs > span.hljs-keyword
"google/nano-banana div.bg-r8-gray-1 > div.min-w-max > div.flex > span.font-mono
const div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
"a soft armchair sh div.bg-r8-gray-1 > div.min-w-max > div.flex > span.font-mono
const div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
await div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
console div.min-w-max > pre.lowlight > code.hljs > span.hljs-variable
8.3m runs div.grid > div.flex-1 > div.flex > p.text-r8-xs
735.6k runs div.grid > div.flex-1 > div.flex > p.text-r8-xs
5.3m runs div.grid > div.flex-1 > div.flex > p.text-r8-xs
Explore models div.top-0 > div.flex-1 > div.mt-4 > a.r8-btn
import div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
input div.min-w-max > pre.lowlight > code.hljs > span.hljs-built_in
print div.min-w-max > pre.lowlight > code.hljs > span.hljs-built_in
Fine-tune image models div.border-t > div.flex-1 > div.mb-4 > a.r8-btn
input div.min-w-max > pre.lowlight > code.hljs > span.hljs-built_in
0 runs div.min-h-[8.75rem] > div.p-4 > div.flex > p.text-r8-xs
input div.min-w-max > pre.lowlight > code.hljs > span.hljs-built_in
Learn more div.lg:border-l > div.flex-1 > div.mt-4 > a.r8-btn
from div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
import div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
import div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
class div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
def div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
self div.min-w-max > pre.lowlight > code.hljs > span.hljs-variable
def div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
self div.min-w-max > pre.lowlight > code.hljs > span.hljs-variable
return div.min-w-max > pre.lowlight > code.hljs > span.hljs-keyword
Learn more about our enterprise plans div.bg-r8-gray-12 > div.px-6 > div.text-center > a.r8-btn
Learn more about pricing ul.divide-y > li.pb-0 > a.hover:underline > span.font-mono

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
Automatic scale div.border-l > div.p-4 > div.text-branding-red > h4

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
black-forest-labs / flux-2-pro High-quality image generation and editing wit… div.-mt-4 > div > div.marquee > ul.marquee__group
inworld / tts-1.5-max Highest-quality text-to-speech with <200ms latency, em… div.my-16 > div.space-y-8 > div.marquee > ul.marquee__group
google / gemini-3-flash Google's most intelligent model built for speed with… div.my-16 > div.space-y-8 > div.marquee > ul.marquee__group
Autonomous Robots Zero-shot autonomous robots with open source models Paint wit… div.pt-16 > div.pb-16 > div.block > ul.space-y-8

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

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.light html.light

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
●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
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[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
○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
○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.
○Identical links have the same purpose.
○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
Heading Hierarchy
13 headings, 1 skip(s)
PASS
13 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Run AIwith an API.
  • H1 Run and fine-tune models. Deploy custom models. All with one line of code.
  • H2 Thousands of models contributed by our community
  • H2 How it works
  • H3 Run models
  • H3 Fine-tune models with your own data
  • H3 Deploy custom models
  • H2 Scale on Replicate
  • H4 Automatic scale skipped
  • H4 Pay for what you use
  • H4 Forget about infrastructure
  • H4 Logging & monitoring
  • H2 Imagine what you can build

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 124 images OK
PASS
All 124 images OK
Info::
124 image(s) with good alt text
124 images 124 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input id="_R_9rd555_">
Info::
1 control(s) properly labeled
2 controls
1 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#_R_4pa55_radionone
#_R_9rd555_input(Search 'best image models' or 'text to image')placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input id="_R_9rd555_">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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

Send Feedback