Skip to content
https://pushy.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
46
GRADE
F
FIX
7
REVIEW
4
PASS
2
INFO
0
Checks
13
2 PASS 4 REVIEW 7 FIX
F
Heading Hierarchy
Action
39 headings, 7 skip(s)
FIX
39 headings, 7 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: H1 → H6 (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: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H1 → H6 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H6 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Lightning-fast, highly-reliablepush notification delivery
  • H6 Worldwide, cross-platform push notification solution skipped
  • H5 Trusted by 15,000+ companies worldwide
  • H3 Mission-critical notification delivery at your service
  • H5 Highly-Reliable skipped
  • H5 Worldwide Delivery
  • H5 Blazing-fast
  • H5 Cross-platform
  • H5 Pay as you grow
  • H5 Auto-Scaling
  • H3 Cross-platform support for popular technologies
  • H6 Persistent connectivity skipped
  • H6 Pub/sub topic messaging
  • H6 Developer-friendly docs
  • H5 Pushy Enterprise
  • H4 Our enterprise-grade, managed/on-premises notification solution, offline-capable and backed by an uptime SLA and 24/7 high priority support
  • H3 Track notification delivery and user activity trends
  • H4 Insightful metrics
  • H4 Powerful tools
  • H3 Some companies we'vehad the pleasure of working with
  • H6 Tim Preuss skipped
  • H6 Brent Dermott
  • H6 Darren Maddock
  • H6 Riky Wijaya
  • H6 Tamir Olpak
  • H6 Chris David
  • H6 Manuel Saleta
  • H4 Reliable notifications at Scale
  • H1 9.7M+ duplicate H1
  • H6 Notifications sent per day skipped
  • H1 48M+ duplicate H1
  • H6 Devices on our platform skipped
  • H3 Try our demo
  • H3 Join over 15,000 companies using the most reliable push notification solution in the world
  • H6 Contact Us skipped
  • H6 Phone
  • H6 Quick Navigation
  • H6 Clients
  • H6 Latest Updates

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

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
Alt Text Quality
Action
66 of 66 images have issues
FIX
66 of 66 images have issues
Critical::
58 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
50 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
3 image(s) with filename as alt text
Warning::
5 image(s) with generic alt text
66 images 8 generic 58 missing
IssueCount
missing58 image(s)
filename3 image(s)
generic5 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

D
Favicon & Branding
Action
5 icon(s) detected
FIX
5 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'>.
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
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
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
2 landmarks
REVIEW
2 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 Pushy ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 11 fail WCAG AA
REVIEW

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

9 pass 11 fail WCAG AA 9 pass AA only
h1 Lightning-fast, highly-reliable
1.75:1
#000000
on
#3E352E
needs 3.0:1 (large text)
32px · above the fold
h1 push notification delivery
1.67:1
#000000
on
#3C312B
needs 3.0:1 (large text)
32px · above the fold
h3 Mission-critical notification delivery a…
1.68:1
#000000
on
#3E312A
needs 3.0:1 (large text)
19px · mid-page
title Pushy - Lightning-Fast & Highly-Reliable…
1.50:1
#000000
on
#2F2B2A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.62:1
#000000
on
#36302C
needs 4.5:1 (normal text)
16px · top of page (header area)
a About
1.83:1
#000000
on
#403831
needs 4.5:1 (normal text)
16px · top of page (header area)
a Pricing
1.65:1
#000000
on
#38312D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Enterprise
2.07:1
#000000
on
#494038
needs 4.5:1 (normal text)
16px · above the fold
a Documentation
1.59:1
#000000
on
#352F2A
needs 4.5:1 (normal text)
16px · above the fold
a Support
2.07:1
#000000
on
#4B3F37
needs 4.5:1 (normal text)
16px · above the fold
a Contact
2.59:1
#000000
on
#584E44
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Lightning-fast, high…1.75:13.0:1
#000000
#3E352E
Fail
h1 push notification de…1.67:13.0:1
#000000
#3C312B
Fail
h1 9.7M+4.23:13.0:1
#000000
#71706B
Pass
h1 48M+4.23:13.0:1
#000000
#71706B
Pass
h3 Mission-critical not…1.68:13.0:1
#000000
#3E312A
Fail
h3 Cross-platform suppo…4.23:13.0:1
#000000
#71706B
Pass
h3 Track notification d…4.23:13.0:1
#000000
#71706B
Pass
h3 Some companies we've4.23:13.0:1
#000000
#71706B
Pass
h3 had the pleasure of …4.23:13.0:1
#000000
#71706B
Pass
h3 Try our demo4.23:13.0:1
#000000
#71706B
Pass
h3 Join over 15,000 com…4.23:13.0:1
#000000
#71706B
Pass
h3 push notification so…4.23:13.0:1
#000000
#71706B
Pass
title Pushy - Lightning-Fa…1.50:14.5:1
#000000
#2F2B2A
Fail
a Home1.62:14.5:1
#000000
#36302C
Fail
a About1.83:14.5:1
#000000
#403831
Fail
a Pricing1.65:14.5:1
#000000
#38312D
Fail
a Enterprise2.07:14.5:1
#000000
#494038
Fail
a Documentation1.59:14.5:1
#000000
#352F2A
Fail
a Support2.07:14.5:1
#000000
#4B3F37
Fail
a Contact2.59:14.5:1
#000000
#584E44
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.

C
Lighthouse Accessibility Audits
Action
Score 78/100 — 4 failing, 14 passed
REVIEW
78

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
MQTT div.col-sm-4 > div.feature > p > a
China div.col-sm-4 > div.feature > p > a
pricing div.col-sm-4 > div.feature > p > a
MQTT div.col-md-4 > div.mb40 > p > a
AOSP div.col-md-4 > div.mb40 > p > a
non-GMS div.col-md-4 > div.mb40 > p > a
Subscribe users div.col-md-4 > div.mb40 > p > a
developer-friendly documentation div.col-md-4 > div.mb40 > p > a
GIVE IT A GO div.container > div.row > div.col-md-4 > a.btn
GET STARTED FOR FREE div.row > div.col-md-4 > a > button.btn

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
WORLDWIDE, CROSS-PLATFORM PUSH NOTIFICATION SOLUTION div.container > div.row > div.col-sm-10 > h6.uppercase
HIGHLY-RELIABLE div.col-sm-4 > div.feature > div.text-center > h5.uppercase
PERSISTENT CONNECTIVITY div.row > div.col-md-4 > div.mb40 > h6.uppercase
TIM PREUSS ul.slides > li.flex-active-slide > div.quote-author > h6.uppercase
NOTIFICATIONS SENT PER DAY div.container > div.row > div.col-sm-6 > h6.uppercase
DEVICES ON OUR PLATFORM div.container > div.row > div.col-sm-6 > h6.uppercase
CONTACT US div.row > div.col-md-4 > div.footer-contact > h6.uppercase

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.js-marquee > div.client > a > img div.js-marquee > div.client > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
div.col-md-12 > div.platform > a > img div.col-md-12 > div.platform > a > img
ul.slides > li.flex-active-slide > div.quote-author > img.rounded ul.slides > li.flex-active-slide > div.quote-author > img.rounded
div.quote-author > span > a > img div.quote-author > span > a > img
ul.slides > li > div.quote-author > img.rounded ul.slides > li > div.quote-author > img.rounded
div.quote-author > span > a > img.rounded div.quote-author > span > a > img.rounded
ul.slides > li > div.quote-author > img.rounded ul.slides > li > div.quote-author > img.rounded
div.quote-author > span > a > img div.quote-author > span > a > img
ul.slides > li > div.quote-author > img.rounded ul.slides > li > div.quote-author > img.rounded
div.quote-author > span > a > img.rounded div.quote-author > span > a > img.rounded
ul.slides > li > div.quote-author > img.rounded ul.slides > li > div.quote-author > img.rounded
div.quote-author > span > a > img.rounded div.quote-author > span > a > img.rounded
ul.slides > li > div.quote-author > img.rounded ul.slides > li > div.quote-author > img.rounded
div.quote-author > span > a > img div.quote-author > span > a > img
ul.slides > li > div.quote-author > img.rounded ul.slides > li > div.quote-author > img.rounded
div.quote-author > span > a > img div.quote-author > span > a > img
div.col-md-4 > div.footer-contact > a > img.gdpr div.col-md-4 > div.footer-contact > a > img.gdpr

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
li.flex-active-slide > div.quote-author > span > a li.flex-active-slide > div.quote-author > span > a
li > div.quote-author > span > a li > div.quote-author > span > a
li > div.quote-author > span > a li > div.quote-author > span > a
li > div.quote-author > span > a li > div.quote-author > span > a
div.row > div.col-md-4 > div.footer-contact > a div.row > div.col-md-4 > div.footer-contact > a
div.col-sm-6 > ul.list-inline > li > a div.col-sm-6 > ul.list-inline > li > a
div.col-sm-6 > ul.list-inline > li > a div.col-sm-6 > ul.list-inline > li > a

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-hidden="true"]` is not present on the document `<body>`
●Buttons have an accessible name
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●Links are distinguishable without relying on color.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA attributes are used as specified for the element's role
○Deprecated ARIA roles were not used
○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 use only permitted ARIA attributes
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○`<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.
○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.
○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+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Pushy Demo
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Pushy Demo ✓192×192 icon ✓512×512 icon ✓Start URL https://pushy.me/docs/resources/demo ✓Display Mode standalone ✓
Name Pushy Demo Display Mode standalone Theme Color #ff5754 Background Color #ffffff Icons 4 icon(s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback