Skip to content
https://activestate.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
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 ✗
D
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
4 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search role='search' landmark
Skip Link
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.
B
Landmark Structure
19 landmarks
REVIEW
19 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
No contentinfo (footer) 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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Top-Bar Menu" SEARCH MAIN CONTENTINFO (missing!)

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
Heading Hierarchy
68 headings, 1 skip(s)
REVIEW
68 headings, 1 skip(s)
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Overview
  • H3 Service Status
  • H2 Featured
  • H2 The 2026 State of Vulnerability Management & Remediation
  • H2 Read post
  • H2 Featured
  • H2 Introducing ActiveState’s Secure, Custom Container Images
  • H2 Read post
  • H2 Featured
  • H2 The 2026 State of Vulnerability Management & Remediation
  • H2 Read post
  • H2 Featured
  • H2 Introducing ActiveState’s Secure, Custom Container Images
  • H2 Read post
  • H2 ActiveState Library
  • H2 Managed Distros
  • H2 Supported Languages
  • H2 USE CASES
  • H2 Container Security
  • H2 Vulnerability Management and Remediation
  • H2 Software Supply Chain Security
  • H2 Compliance and SBOM
  • H2 Beyond End-of-Life Support
  • H2 RESOURCES
  • H2 Read
  • H2 Watch
  • H2 Attend
  • H2 Academy
  • H2 FEATURED
  • H2 The 2026 State of Vulnerability Management & Remediation​
  • H2 Read More
  • H2 FEATURED
  • H2 Introducing ActiveState’s Secure, Custom Container Images
  • H2 Read More
  • H2 Docs
  • H2 Support Overview
  • H2 Service Status
  • H2 Login
  • H1 Tame Open Source Complexity
  • H1 Fuss-free Open Source duplicate H1
  • H2 Open source doesn't mean open risk.
  • H2 STRENGTHEN SECURITY
  • H3 Access Over 79M Secure Components
  • H2 ACCELERATE DEVELOPMENT
  • H3 Open Source Packaged For Any Tech Stack
  • H2 REDUCE ENGINEERING TOIL
  • H3 AI Powered Vulnerability Remediation
  • H3 Discover ActiveState
  • H2 Why ActiveState?
  • H3 Strengthen Security Posture
  • H3 Reduce Costly Engineering Toil
  • H3 Simplify Compliance
  • H3 Streamline open source management across your organization​
  • H2 Improve efficiency
  • H2 Drive innovation
  • H2 Maintain robust security
  • H2 What our clients say
  • H2 Your One Stop For Secure, Trusted Open Source
  • H2 Tame the complexities of your open source
  • H6 PRODUCT skipped
  • H6 LANGUAGES
  • H6 SOLUTIONS
  • H6 RESOURCES
  • H6 COMPANY
  • H2 © 2026 ActiveState Software Inc. All rights reserved. ActiveState®, ActivePerl®, ActiveTcl®, ActivePython®, Komodo®, ActiveGo™, ActiveRuby™, ActiveNode™, ActiveLua™, and The Open Source
  • H2 Legal
  • H2 Privacy Policy
  • H2 Accessibility

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

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 - ActiveState ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
6 icon(s) detected
REVIEW
6 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
C
Web Manifest
Action
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
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 Tame Open Source Complexity
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
32px · bottom of viewport
h1 Fuss-free Open Source
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Featured
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The 2026 State of Vulnerability Manageme…
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Read post
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Introducing ActiveState’s Secure, Cust…
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Read post
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 The 2026 State of Vulnerability Manageme…
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Read post
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Featured
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Introducing ActiveState’s Secure, Cust…
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Read post
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ActiveState Library
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Managed Distros
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Supported Languages
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 USE CASES
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Container Security
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Vulnerability Management and Remediation
2.00:1
#000000
on
#71136A
needs 3.0:1 (large text)
24px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Tame Open Source Com…2.00:13.0:1
#000000
#71136A
Fail
h1 Fuss-free Open Sourc…2.00:13.0:1
#000000
#71136A
Fail
h2 Featured2.00:13.0:1
#000000
#71136A
Fail
h2 The 2026 State of Vu…2.00:13.0:1
#000000
#71136A
Fail
h2 Read post2.00:13.0:1
#000000
#71136A
Fail
h2 Featured2.00:13.0:1
#000000
#71136A
Fail
h2 Introducing ActiveSt…2.00:13.0:1
#000000
#71136A
Fail
h2 Read post2.00:13.0:1
#000000
#71136A
Fail
h2 Featured2.00:13.0:1
#000000
#71136A
Fail
h2 The 2026 State of Vu…2.00:13.0:1
#000000
#71136A
Fail
h2 Read post2.00:13.0:1
#000000
#71136A
Fail
h2 Featured2.00:13.0:1
#000000
#71136A
Fail
h2 Introducing ActiveSt…2.00:13.0:1
#000000
#71136A
Fail
h2 Read post2.00:13.0:1
#000000
#71136A
Fail
h2 ActiveState Library2.00:13.0:1
#000000
#71136A
Fail
h2 Managed Distros2.00:13.0:1
#000000
#71136A
Fail
h2 Supported Languages2.00:13.0:1
#000000
#71136A
Fail
h2 USE CASES2.00:13.0:1
#000000
#71136A
Fail
h2 Container Security2.00:13.0:1
#000000
#71136A
Fail
h2 Vulnerability Manage…2.00:13.0:1
#000000
#71136A
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.

A+
Alt Text Quality
All 39 images OK
PASS
All 39 images OK
Info::
9 decorative image(s) correctly marked
Info::
30 image(s) with good alt text
39 images 30 good alt text 9 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 10 controls labeled
PASS
All 10 controls labeled
Info::
10 control(s) properly labeled
10 controls
10 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optoutcheckboxFunctionalfor/id
#cmplz-preferences-optoutcheckboxPreferencesfor/id
#cmplz-statistics-optoutcheckboxStatisticsfor/id
#cmplz-marketing-optoutcheckboxMarketingfor/id
#cmplz-functional-optincheckboxFunctionalfor/id
#cmplz-preferences-optincheckboxPreferencesfor/id
#cmplz-statistics-optincheckboxStatisticsfor/id
#cmplz-marketing-optincheckboxMarketingfor/id
#search-4deceae6searchSearchfor/id
#search-65a87dc5searchSearchfor/id
A
Lighthouse Accessibility Audits
Score 94/100 — 3 failing, 30 passed
PASS
94

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.

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.elementor-element > div.elementor-element > div.elementor-widget-container > a div.elementor-element > div.elementor-element > div.elementor-widget-container > a
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon
div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Curate your catalog with direct access to open source packages, runtimes, and s… div.e-con-inner > div.elementor-element > div.elementor-widget-container > ul
Access secure open source directly from the tools your team already uses. Pull … div.e-con-inner > div.elementor-element > div.elementor-widget-container > ul

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Read more about these purposes div.cmplz-links > ul > li > a.cmplz-link
○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
●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
●`[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.
●`button`, `link`, and `menuitem` elements have accessible names
●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
●Background and foreground colors have a sufficient contrast ratio
●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.
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback