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

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
5
REVIEW
4
PASS
4
INFO
0
Checks
13
4 PASS 4 REVIEW 5 FIX
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: #5a1ba9
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
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 | Heroku Custom Styling Navigation Homepage Link Search Form
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 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 Missing
Multiple Sizes Present
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 The AI PaaS For Deploying, Managing, and…
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
32px · bottom of viewport
h2 A streamlined platform for building AI a…
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Powerful platform, unparalleled ecosyste…
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Developers, teams, and businesses of all…
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
24px · bottom of viewport
h2 A powerful and innovative feature set
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Your data on Heroku
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The platform developers trust
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Heroku Enterprise
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Ready to Get Started?
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
24px · bottom of viewport
h3 How Heroku Helps PixieBrix Accelerate AI…
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Heroku Runtime
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Heroku Postgres
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Heroku Key-Value Store
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Scalability
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Heroku Elements
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Heroku Teams
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Fast Rollback
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 App Metrics
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Continuous Delivery
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
h3 GitHub Integration
1.29:1
#000000
on
#2C0D53
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 The AI PaaS For Depl…1.29:13.0:1
#000000
#2C0D53
Fail
h2 A streamlined platfo…1.29:13.0:1
#000000
#2C0D53
Fail
h2 Powerful platform, u…1.29:13.0:1
#000000
#2C0D53
Fail
h2 Developers, teams, a…1.29:13.0:1
#000000
#2C0D53
Fail
h2 A powerful and innov…1.29:13.0:1
#000000
#2C0D53
Fail
h2 Your data on Heroku1.29:13.0:1
#000000
#2C0D53
Fail
h2 The platform develop…1.29:13.0:1
#000000
#2C0D53
Fail
h2 Heroku Enterprise1.29:13.0:1
#000000
#2C0D53
Fail
h2 Ready to Get Started…1.29:13.0:1
#000000
#2C0D53
Fail
h3 How Heroku Helps Pix…1.29:13.0:1
#000000
#2C0D53
Fail
h3 Heroku Runtime1.29:13.0:1
#000000
#2C0D53
Fail
h3 Heroku Postgres1.29:13.0:1
#000000
#2C0D53
Fail
h3 Heroku Key-Value Sto…1.29:13.0:1
#000000
#2C0D53
Fail
h3 Scalability1.29:13.0:1
#000000
#2C0D53
Fail
h3 Heroku Elements1.29:13.0:1
#000000
#2C0D53
Fail
h3 Heroku Teams1.29:13.0:1
#000000
#2C0D53
Fail
h3 Fast Rollback1.29:13.0:1
#000000
#2C0D53
Fail
h3 App Metrics1.29:13.0:1
#000000
#2C0D53
Fail
h3 Continuous Delivery1.29:13.0:1
#000000
#2C0D53
Fail
h3 GitHub Integration1.29:13.0:1
#000000
#2C0D53
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 89/100 — 3 failing, 26 passed
REVIEW
89

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
Heroku March 2026 Update NEWS Last Updated: March 19, 2026 KESHAV POKKULURI We… div.e-con-inner > div.elementor-element > div.elementor-widget-container > div.elementor-loop-container

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
All Heroku Buildpacks div.elementor-element > div.elementor-widget-container > p > a.cta-link
Explore Heroku Solutions div.elementor-element > div.elementor-widget-container > p > a.cta-link
slug size div.elementor-element > div.elementor-widget-container > p > a

These are opportunities to improve the legibility of your content.

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
Heroku Platform li#menu-item-275 > ul.sub-menu > li#menu-item-219 > a
Heroku AI li#menu-item-275 > ul.sub-menu > li#menu-item-13878 > a
Heroku Managed Inference and Agents li#menu-item-275 > ul.sub-menu > li#menu-item-13881 > a
pgvector for Heroku Postgres li#menu-item-275 > ul.sub-menu > li#menu-item-13879 > a
MCP on Heroku li#menu-item-275 > ul.sub-menu > li#menu-item-13880 > a
Heroku Data Services li#menu-item-275 > ul.sub-menu > li#menu-item-220 > a
Heroku Postgres li#menu-item-275 > ul.sub-menu > li#menu-item-221 > a
Heroku Key-Value Store li#menu-item-275 > ul.sub-menu > li#menu-item-229 > a
Apache Kafka on Heroku li#menu-item-275 > ul.sub-menu > li#menu-item-228 > a
Heroku Enterprise li#menu-item-275 > ul.sub-menu > li#menu-item-230 > a
Heroku Private Spaces li#menu-item-275 > ul.sub-menu > li#menu-item-12268 > a
Heroku Connect li#menu-item-275 > ul.sub-menu > li#menu-item-232 > a
Heroku Shield li#menu-item-275 > ul.sub-menu > li#menu-item-233 > a
Heroku Success li#menu-item-275 > ul.sub-menu > li#menu-item-2240 > a
Heroku Teams li#menu-item-275 > ul.sub-menu > li#menu-item-234 > a
Elements Marketplace li#menu-item-275 > ul.sub-menu > li#menu-item-235 > a
Python li#menu-item-2241 > ul.sub-menu > li#menu-item-2242 > a
.NET li#menu-item-2241 > ul.sub-menu > li#menu-item-14019 > a
Java li#menu-item-2241 > ul.sub-menu > li#menu-item-2244 > a
Node.js li#menu-item-2241 > ul.sub-menu > li#menu-item-2245 > a
Go li#menu-item-2241 > ul.sub-menu > li#menu-item-2248 > a
PHP li#menu-item-2241 > ul.sub-menu > li#menu-item-2247 > a
Ruby li#menu-item-2241 > ul.sub-menu > li#menu-item-2246 > a
Scala li#menu-item-2241 > ul.sub-menu > li#menu-item-18612 > a
Clojure li#menu-item-2241 > ul.sub-menu > li#menu-item-18611 > a
Dev Center div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2253 > a
Training & Education div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2254 > a
Get Started div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2255 > a
Pricing div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2257 > a
Blog div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2258 > a
Customers div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2259 > a
Partners div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2260 > a
Compliance Center div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2261 > a
Solutions div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2262 > a
Podcasts div.menu-footer-3-container > ul#menu-footer-3 > li#menu-item-2263 > a
What is Heroku? li#menu-item-2264 > ul.sub-menu > li#menu-item-2267 > a
Heroku & Salesforce li#menu-item-2264 > ul.sub-menu > li#menu-item-2270 > a
Careers li#menu-item-2264 > ul.sub-menu > li#menu-item-2271 > a

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]`s are contained by their required parent element
`[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
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
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
No element has a `[tabindex]` value greater than 0
Heading elements appear in a sequentially-descending order
Skip links are focusable.
Document has a main landmark.
Deprecated ARIA roles were not used
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements 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
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
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.
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
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 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+
Heading Hierarchy
40 headings
PASS
40 headings
Info::
Single H1 present
  • H3 Heroku March 2026 Update
  • H3 Heroku March 2026 Update
  • H3 How Heroku Helps PixieBrix Accelerate AI Innovation and Growth
  • H3 Heroku March 2026 Update
  • H1 The AI PaaS For Deploying, Managing, and Scaling Apps
  • H2 A streamlined platform for building AI applications and agents
  • H3 Heroku Managed Inference and Agents
  • H3 Model Context Protocol (MCP) on Heroku
  • H3 pgvector for Heroku Postgres
  • H2 Powerful platform, unparalleled ecosystem
  • H3 Officially supported languages
  • H2 Developers, teams, and businesses of all sizes use Heroku to deploy, manage, and scale apps.
  • H2 A powerful and innovative feature set
  • H3 Heroku Runtime
  • H3 Heroku Postgres
  • H3 Heroku Key-Value Store
  • H3 Scalability
  • H3 Heroku Elements
  • H3 Heroku Teams
  • H3 Fast Rollback
  • H3 App Metrics
  • H3 Continuous Delivery
  • H3 GitHub Integration
  • H3 Extensibility
  • H3 Security and Compliance
  • H2 Your data on Heroku
  • H2 The platform developers trust
  • H2 Heroku Enterprise
  • H3 Private Spaces
  • H3 Heroku Shield
  • H3 SSO for Heroku
  • H3 Team and Resource Oversight
  • H3 Heroku Connect
  • H3 Enterprise-grade Support
  • H2 Recent Posts
  • H3 Heroku March 2026 Update
  • H3 Modernizing the Command Line: Heroku CLI v11
  • H3 Bigger Slugs and Greater Build Timeout Flexibility
  • H2 Upcoming Events
  • H2 Ready to Get Started?
A+
Alt Text Quality
All 37 images OK
PASS
All 37 images OK
Info::
16 decorative image(s) correctly marked
Info::
21 image(s) with good alt text
37 images 21 good alt text 16 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#stextSearch For:for/id
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

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

Send Feedback