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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark 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 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

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 Ona - AI software engineers Custom Styling Navigation Homepage Link Search Form
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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Favicon & Branding
15 icon(s) detected
REVIEW
15 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
favicon.ico Present
PNG Icons Present
Apple Touch Present
SVG Favicon Missing
Manifest Icons Present
Multiple Sizes Present
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
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 #ffffff CSS indicators Detected

Detection limited to meta tags and inline styles.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 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
Top 100 global company div.overflow-y-clip > section.container > div.bg-grey-450 > p.text-body-160
productivity increase section.container > div.grid > div.bg-grey-400 > p.text-body-110
of PRs co-authored by Ona section.container > div.grid > div.bg-grey-400 > p.text-body-110
Python repos modernized in 6 months section.container > div.grid > div.bg-grey-400 > p.text-body-110
Compliant, certified, and trusted by Fortune 500 companies. section.container > div.flex > h2.text-[1.125rem] > span.text-grey-700
The adversary can reason now, and our security tools weren't built for that. section.container > div.flex > a.flex > p.text-body-160
Background agents that write, test, and ship code on a schedule. Ona Automation… section.container > div.flex > a.flex > p.text-body-160
The companies winning with background agents didn't start with better models. T… section.container > div.flex > a.flex > p.text-body-160

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.flex > div.flex > div.w-full > input.cursor-pointer div.flex > div.flex > div.w-full > input.cursor-pointer

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1x div.text-white > div.flex > div.flex > button.flex
Unmute div.text-white > div.flex > div.flex > button.flex
Fullscreen div.text-white > div.flex > div.flex > button.flex
Automations div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Environments div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Governance div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Pricing div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
AI code review div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Code migration div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
CVE remediation div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Standardization div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Devin div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Codex div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Factory div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Blog div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Docs div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Changelog div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Events div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Newsletter div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Templates div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Videos div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Reports div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
About div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Careers div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Media div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Contact div.col-span-1 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Status div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Security div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Imprint div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Terms of service div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Terms of use div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Privacy policy div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]
Cookie policy div.col-span-3 > ul.text-[0.75rem] > li.flex > a.leading-[1]

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
`[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
Links are distinguishable without relying on color.
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
Heading elements appear in a sequentially-descending order
Deprecated ARIA roles were not used
`<video>` elements contain a `<track>` element with `[kind="captions"]`
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.
No element has a `[tabindex]` value greater than 0
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.
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
20 headings
PASS
20 headings
Info::
Single H1 present
  • H1 The platform forbackground agents
  • H2 The AI engineering workforce.Set the direction. Ona runs the execution. Continuously and autonomously.
  • H3 Background agents
  • H3 Automations
  • H3 Connected environments
  • H3 Governance with guarantees
  • H3 Code migration & modernization
  • H3 AI code review
  • H3 Automated CVE remediation
  • H2 Enterprise-ready.Compliant, certified, and trusted by Fortune 500 companies.
  • H2 Recent highlights from our blog
  • H3 How Claude Code escapes its own denylist and sandbox
  • H3 Ona Automations: proactive background agents
  • H3 The last year of localhost
  • H2 Start shipping with Ona
  • H3 Platform
  • H3 Use cases
  • H3 Compare Ona
  • H3 Resources
  • H3 Company
A+
Alt Text Quality
All 24 images OK
PASS
All 24 images OK
Info::
1 decorative image(s) correctly marked
Info::
23 image(s) with good alt text
24 images 23 good alt text 1 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 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="range">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputrange(none)none

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

<input type="range">

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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Ona (formerly Gitpod)
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Installable
Name Ona (formerly Gitpod) 192×192 icon 512×512 icon Start URL / Display Mode standalone
Name Ona (formerly Gitpod) Display Mode standalone Theme Color #0A0E19 Background Color #ffffff Icons 5 icon(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 The AI engineering w…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Enterprise-ready.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Recent highlights fr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Start shipping with …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Background agents21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Automations21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Connected environmen…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Governance with guar…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Code migration & mod…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 AI code review21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Automated CVE remedi…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 How Claude Code esca…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Ona Automations: pro…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 The last year of loc…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Platform21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Use cases21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Compare Ona21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Resources21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Company21.00:13.0:1
#000000
#FFFFFF
Pass
title Ona · Run backgroun…21.00:14.5:1
#000000
#FFFFFF
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.

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

Send Feedback