Skip to content
https://runwayml.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 FIX
F
Heading Hierarchy
Action
22 headings, 5 skip(s)
FIX
22 headings, 5 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
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.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H5 Upload in progress...
  • H1 Building AI to Simulate the World
  • H3 Runway Characters↗ skipped
  • H3 Media and Entertainment↗
  • H3 Robotics and Autonomy↗
  • H3 General World Models↗
  • H5 Upload in progress... skipped
  • H4 Gen-4.5: A New Frontier for Generative Video
  • H4 GWM Robotics: General World Models for Robotics
  • H5 Upload in progress...
  • H4 GWM Worlds: Interactive and Explorable World Models
  • H4 Runway Characters: Real-time Video Agents
  • H5 Upload in progress...
  • H4 GWM-1
  • H4 Gen-4.5
  • H4 General World Models
  • H2 Runway Characters
  • H5 Upload in progress... skipped
  • H2 Introducing GWM-1
  • H5 Upload in progress... skipped
  • H2 Gen-4.5: A new frontier for video generation.
  • H5 Upload in progress... 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

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

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 404 | Runway ✓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
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #0c0c0c
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 ModePartial Dark Mode
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::
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
Color Contrast (Screenshot)
Action
20 text elements analyzed, 15 fail WCAG AA
REVIEW

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

5 pass 15 fail WCAG AA
h1 Building AI to
1.44:1
#000000
on
#002C43
needs 3.0:1 (large text)
32px · mid-page
h1 Simulate the World
1.35:1
#000000
on
#00273B
needs 3.0:1 (large text)
32px · mid-page
h3 Runway Characters
1.24:1
#000000
on
#001F31
needs 3.0:1 (large text)
19px · mid-page
h3 Media and Entertainment
1.19:1
#000000
on
#001B2B
needs 3.0:1 (large text)
19px · mid-page
title Runway | Building AI to Simulate the Wor…
2.43:1
#000000
on
#3E419A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Research
1.79:1
#000000
on
#18376A
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a Product
1.58:1
#000000
on
#00334C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Resources
1.50:1
#000000
on
#002F47
needs 4.5:1 (normal text)
16px · top of page (header area)
a Solutions
1.38:1
#000000
on
#00293C
needs 4.5:1 (normal text)
16px · above the fold
a Company
1.37:1
#000000
on
#00283D
needs 4.5:1 (normal text)
16px · above the fold
a Enterprise Sales
1.46:1
#000000
on
#002D45
needs 4.5:1 (normal text)
16px · above the fold
a Log in
3.56:1
#000000
on
#336B80
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Try Runway
1.76:1
#000000
on
#003B56
needs 4.5:1 (normal text)
16px · above the fold
div Submissions for the AI Festival are open…
1.69:1
#000000
on
#003852
needs 4.5:1 (normal text)
16px · above the fold
a Submit Today
1.64:1
#000000
on
#00364F
needs 4.5:1 (normal text)
16px · above the fold

2 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
h1 Building AI to1.44:13.0:1
#000000
#002C43
Fail
h1 Simulate the World1.35:13.0:1
#000000
#00273B
Fail
h2 Runway Characters21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Introducing GWM-121.00:13.0:1
#000000
#FFFFFF
Pass
h2 Gen-4.5: A new front…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Runway Characters1.24:13.0:1
#000000
#001F31
Fail
h3 Media and Entertainm…1.19:13.0:1
#000000
#001B2B
Fail
h3 Robotics and Autonom…8.17:13.0:1
#000000
#99A3A9
Pass
h3 General World Models21.00:13.0:1
#000000
#FFFFFF
Pass
title Runway | Building AI…2.43:14.5:1
#000000
#3E419A
Fail
a Research1.79:14.5:1
#000000
#18376A
Fail
a Product1.58:14.5:1
#000000
#00334C
Fail
a Resources1.50:14.5:1
#000000
#002F47
Fail
a Solutions1.38:14.5:1
#000000
#00293C
Fail
a Company1.37:14.5:1
#000000
#00283D
Fail
a Enterprise Sales1.46:14.5:1
#000000
#002D45
Fail
a Log in3.56:14.5:1
#000000
#336B80
Fail
a Try Runway1.76:14.5:1
#000000
#003B56
Fail
div Submissions for the …1.69:14.5:1
#000000
#003852
Fail
a Submit Today1.64:14.5:1
#000000
#00364F
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 82/100 — 5 failing, 23 passed
REVIEW
82

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
RUNWAY CHARACTERS ↗ MEDIA AND ENTERTAINMENT ↗ ROBOTICS AND AUTONOMY ↗ GENERAL W… div.!px-0 > div.px-4 > div.md:ml-1/16 > div.flex

Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
RUNWAY CHARACTERS ↗ div.md:ml-1/16 > div.flex > a.group > h3.carousel-title
MEDIA AND ENTERTAINMENT ↗ div.md:ml-1/16 > div.flex > a.group > h3.carousel-title
ROBOTICS AND AUTONOMY ↗ div.md:ml-1/16 > div.flex > a.group > h3.carousel-title
GENERAL WORLD MODELS ↗ div.md:ml-1/16 > div.flex > a.group > h3.carousel-title

These are opportunities to improve the usage of ARIA in your application which 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
We partner with the world's leading organizations to advance their industries: div.w-11/12 > div.flex > div.w-full > div.opacity-50
Product div#footer > div.grid > div > div.rw-bodycopy3
Initiatives div#footer > div.grid > div > div.rw-bodycopy3
Company div#footer > div.grid > div > div.rw-bodycopy3
Get Started div#footer > div.grid > div > div.rw-bodycopy3
Connect div#footer > div.grid > div > div.rw-bodycopy3

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
Gen-4.5: A New Frontier for Generative Video div.mt-9 > div.relative > a.group > h4.mb-2

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
div.rw-container > div.static > div.relative > a.relative div.rw-container > div.static > div.relative > a.relative

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
●`[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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[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
○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
○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
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
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 CONTENTINFO footer

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

A+
Alt Text Quality
All 12 images OK
PASS
All 12 images OK
Info::
8 decorative image(s) correctly marked
Info::
4 image(s) with good alt text
12 images 4 good alt text 8 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback