Skip to content
https://www.warp.dev

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
51
GRADE
F
FIX
6
REVIEW
5
PASS
2
INFO
0
Checks
13
2 PASS 5 REVIEW 6 FIX
F
Heading Hierarchy
Action
40 headings, 6 skip(s)
FIX
40 headings, 6 skip(s)
Warning::
Multiple H1 headings (3 found)
A page should have only one H1. Multiple H1s dilute the document outline.
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.
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 Warp unveils new software for collaborative AI coding
  • H2 Fastcompany
  • H5 Transforming the Command Line at Warp Speed skipped
  • H2 Sequoia Capital
  • H5 Start with a prompt: Warps AI coding mandate skipped
  • H2 First Round
  • H5 Warp's new agentic development environment helps developers work with Al coding agents skipped
  • H2 Fastcompany
  • H5 Vibe coding is dead: Agentic swarm coding is the new enterprise moat skipped
  • H2 Venture Beat
  • H5 AI Won't Replace Developers, It Will Make the Best Ones Indispensable skipped
  • H2 DevOps Digest
  • H5 Goodbye IDE. Hello ADE? skipped
  • H2 Turing Post
  • H3 Analytics Engineer
  • H3 Growth Marketing Lead
  • H3 Implementation Engineer
  • H3 Software Engineer
  • H1 All Downloads
  • H1 Get Warp today duplicate H1
  • H1 Get early access to unreleased and experimental features with Warp Preview duplicate H1
  • H2 Mac
  • H2 Linux
  • H2 .deb
  • H2 x64
  • H2 ARM64
  • H2 .rpm
  • H2 x64
  • H2 ARM64
  • H2 .tar.zst
  • H2 Arch Linux
  • H2 x64
  • H2 ARM64
  • H2 AppImage
  • H2 x64
  • H2 ARM64
  • H2 Windows
  • H2 .exe
  • H2 x64
  • H2 ARM64

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

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
Favicon & Branding
Action
2 icon(s) detected
FIX
2 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
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 (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

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 Warp ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
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 Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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 All Downloads
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Get Warp today
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Get early access to unreleased and exper…
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Fastcompany
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Sequoia Capital
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 First Round
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Fastcompany
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Venture Beat
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 DevOps Digest
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Turing Post
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Mac
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Linux
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 .deb
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 x64
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ARM64
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 .rpm
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 x64
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ARM64
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 .tar.zst
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Arch Linux
1.12:1
#000000
on
#121212
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 All Downloads1.12:13.0:1
#000000
#121212
Fail
h1 Get Warp today1.12:13.0:1
#000000
#121212
Fail
h1 Get early access to …1.12:13.0:1
#000000
#121212
Fail
h2 Fastcompany1.12:13.0:1
#000000
#121212
Fail
h2 Sequoia Capital1.12:13.0:1
#000000
#121212
Fail
h2 First Round1.12:13.0:1
#000000
#121212
Fail
h2 Fastcompany1.12:13.0:1
#000000
#121212
Fail
h2 Venture Beat1.12:13.0:1
#000000
#121212
Fail
h2 DevOps Digest1.12:13.0:1
#000000
#121212
Fail
h2 Turing Post1.12:13.0:1
#000000
#121212
Fail
h2 Mac1.12:13.0:1
#000000
#121212
Fail
h2 Linux1.12:13.0:1
#000000
#121212
Fail
h2 .deb1.12:13.0:1
#000000
#121212
Fail
h2 x641.12:13.0:1
#000000
#121212
Fail
h2 ARM641.12:13.0:1
#000000
#121212
Fail
h2 .rpm1.12:13.0:1
#000000
#121212
Fail
h2 x641.12:13.0:1
#000000
#121212
Fail
h2 ARM641.12:13.0:1
#000000
#121212
Fail
h2 .tar.zst1.12:13.0:1
#000000
#121212
Fail
h2 Arch Linux1.12:13.0:1
#000000
#121212
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 86/100 — 5 failing, 23 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.

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
ALL RIGHTS RESERVED ©️ 2026 div.framer-164kh0p > div.framer-2wihu9 > div.framer-eh4v7r > p.framer-text
SOC 2 CERTIFIED div.framer-4c4s84 > div.framer-1n541he > p.framer-text > a.framer-text

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Warp Preview div.framer-1fisnf > div.framer-1pmlury > h1.framer-text > a.framer-text

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
Transforming the Command Line at Warp Speed div.framer-1ei4ldk-container > a.framer-yyoHr > div.framer-1d4966p > h5.framer-text
Start with a prompt: Warps AI coding mandate div.framer-1ei4ldk-container > a.framer-yyoHr > div.framer-1d4966p > h5.framer-text
Warp's new agentic development environment helps developers work with Al coding… div.framer-1ei4ldk-container > a.framer-yyoHr > div.framer-1d4966p > h5.framer-text
Vibe coding is dead: Agentic swarm coding is the new enterprise moat div.framer-1ei4ldk-container > a.framer-yyoHr > div.framer-1d4966p > h5.framer-text
AI Won't Replace Developers, It Will Make the Best Ones Indispensable div.framer-1ei4ldk-container > a.framer-yyoHr > div.framer-1d4966p > h5.framer-text
Goodbye IDE. Hello ADE? div.framer-1ei4ldk-container > a.framer-yyoHr > div.framer-1d4966p > h5.framer-text

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
nav.framer-jmTFF > div.framer-s8scol > div.framer-1lerno > a.framer-m93mzv nav.framer-jmTFF > div.framer-s8scol > div.framer-1lerno > a.framer-m93mzv
div.framer-17nkchd > div.framer-dgamls > div.ssr-variant > a.framer-1c5gzcb div.framer-17nkchd > div.framer-dgamls > div.ssr-variant > a.framer-1c5gzcb
div.framer-ey2l67 > div.framer-vqy38n > div.ssr-variant > a.framer-1qi3wzx div.framer-ey2l67 > div.framer-vqy38n > div.ssr-variant > a.framer-1qi3wzx
div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-rxl5pj div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-rxl5pj
div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-zsl0bg div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-zsl0bg
div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-35hmci div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-35hmci
div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-1ftlme div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-1ftlme
div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-btf37c div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-btf37c
div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-1u0s1lj div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-1u0s1lj
div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-3yeqm0 div.framer-gk62e4 > div.framer-164kh0p > div.framer-996bjj > a.framer-3yeqm0

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.

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 html

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
●Buttons have an accessible name
●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
●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.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
●Elements with visible text labels have matching accessible names.
○`[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 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 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
○`<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.
○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 9 images OK
PASS
All 9 images OK
Info::
9 decorative image(s) correctly marked
9 images 9 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
Emailemailnone
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback