Skip to content
https://www.stability.ai

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
56
GRADE
D
FIX
6
REVIEW
4
PASS
3
INFO
0
Checks
13
3 PASS 4 REVIEW 6 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
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
Heading Hierarchy
Action
38 headings, 3 skip(s)
REVIEW
38 headings, 3 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.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 We’ll help you make it like nobody’s business.
  • H2 It starts with real creatives.
  • H4 Marketing skipped
  • H4 Gaming
  • H4 Entertainment
  • H2 Solve practical problems without creating new ones.
  • H2 Power your vision. Protect your craft.
  • H2 News
  • H3 Trusted by the world’s most innovative businesses.
  • H2 Your next production requires more than a prompt.
  • H3 The control you’ve been looking for.
  • H3 Ready for business.
  • H2 The flexible deployment you need to get to the outcomes you want.
  • H4 Self-Host skipped
  • H4 API
  • H4 Cloud Service
  • H2 Electronic Arts Partners With James Cameron-Backed Stability AI for Game Developer Tools That Serve as Smarter Paintbrushes”
  • H2 WPP Makes Next Big AI Bet With Investment in Stability AI”
  • H2 UMG Partners With Stability AI to Develop Music Creation Tools for Artists, Producers”
  • H2 HubSpot accelerates creative production with professional-quality images.
  • H2 Enterprise retailers choose Stability AI to create high-quality product visuals that convert.
  • H2 Innovative brands bring ideas to market faster with state-of-the-art generation tools.
  • H2 News
  • H2 Less busywork. More great work.
  • H4 Company skipped
  • H4 Models
  • H4 Deployment
  • H4 ResourceS
  • H4 Contact Us
  • H4 Legal
  • H4 Applications
  • H4 Join the Mailing List
  • H2 Privacy Preference Center
  • H3 Manage Consent Preferences
  • H4 Strictly Necessary Cookies
  • H4 Advertising Cookies
  • H4 Analytics Cookies
  • H3 Cookie List

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
Alt Text Quality
35 of 56 images have issues
REVIEW
35 of 56 images have issues
Warning::
35 image(s) with filename as alt text
Info::
3 decorative image(s) correctly marked
Info::
18 image(s) with good alt text
56 images 18 good alt text 3 decorative 35 generic
IssueCount
filename35 image(s)
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 404 — Stability AI ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA
h2 lectronic Arts Partners With James Camer…
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 PP Makes Next Big AI Bet With Investment…
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 MG Partners With Stability AI to Develop…
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 HubSpot accelerates creative production …
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Enterprise retailers choose Stability AI…
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Innovative brands bring ideas to market …
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Privacy Preference Center
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Manage Consent Preferences
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Cookie List
1.21:1
#000000
on
#1A1A1A
needs 3.0:1 (large text)
19px · bottom of viewport
title Stability AI
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to Content
1.26:1
#000000
on
#1E1E1E
needs 4.5:1 (normal text)
16px · top of page (header area)
span Models
3.89:1
#000000
on
#706A58
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 lectronic Arts Partn…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 PP Makes Next Big AI…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 MG Partners With Sta…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 HubSpot accelerates …1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Enterprise retailers…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Innovative brands br…1.21:13.0:1
#000000
#1A1A1A
Fail
h2 Privacy Preference C…1.21:13.0:1
#000000
#1A1A1A
Fail
h3 Manage Consent Prefe…1.21:13.0:1
#000000
#1A1A1A
Fail
h3 Cookie List1.21:13.0:1
#000000
#1A1A1A
Fail
title Stability AI1.26:14.5:1
#000000
#1E1E1E
Fail
a Skip to Content1.26:14.5:1
#000000
#1E1E1E
Fail
span Models3.89:14.5:1
#000000
#706A58
Fail
span Image8.12:14.5:1
#000000
#AAA181
Pass
span Video8.27:14.5:1
#000000
#ADA283
Pass
span Audio8.23:14.5:1
#000000
#ABA283
Pass
span Solutions8.10:14.5:1
#000000
#A9A181
Pass
span Enterprise Solutions8.28:14.5:1
#000000
#ADA284
Pass
span Brand Style8.16:14.5:1
#000000
#ABA183
Pass
span Product Photography8.25:14.5:1
#000000
#ACA283
Pass
span Customer Stories8.17:14.5:1
#000000
#ACA182
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
Landmark Structure
12 landmarks
PASS
12 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
4 of 4 <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
Form Accessibility
1 of 10 controls have issues
PASS
1 of 10 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="submit">
Info::
9 control(s) properly labeled
10 controls
9 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#email-296f89b5-3f8a-4eab-add9-5153aa2cc2b4emailEmail*for/id
#which_of_our_products_or_services_are_you_interested_in_-296f89b5-3f8a-4eab-add9-5153aa2cc2b4selectWhich of our products or services are you interested in?*for/id
#ot-group-id-C0004checkboxAdvertising Cookiesfor/id
#ot-group-id-C0002checkboxAnalytics Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
inputsubmit(none)none

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

<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

A
Lighthouse Accessibility Audits
Score 92/100 — 3 failing, 29 passed
PASS
92

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
View all news div.sqs-text-block-container > div.sqs-html-content > p > a

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
Marketing div.video-cards__row > div.video-cards__col > div.video-cards__col-copy > h4
Self-Host div.fcc > a.card > div.content > h4
COMPANY div.sqs-block-content > div.sqs-text-block-container > div.sqs-html-content > h4

These are opportunities to improve keyboard navigation in your application.

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
Stability AI Joins the Tech Coalition div#yui_3_17_2_1_1775594115121_307 > div#yui_3_17_2_1_1775594115121_312 > div.summary-thumbnail-outer-container > a.summary-thumbnail-container
Warner Music Group and Stability AI Join Forces To Build The Next Generation Of… div#yui_3_17_2_1_1775594115121_307 > div#yui_3_17_2_1_1775594115121_314 > div.summary-thumbnail-outer-container > a.summary-thumbnail-container
Universal Music Group and Stability AI Announce Strategic Alliance to Co-Develo… div#yui_3_17_2_1_1775594115121_307 > div#yui_3_17_2_1_1775594115121_316 > div.summary-thumbnail-outer-container > a.summary-thumbnail-container

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
●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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○`<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
○Links are distinguishable without relying on color.
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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.
○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