Skip to content
https://progress.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
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 Present
✓ 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
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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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
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
Info::
Skip navigation link present
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

C
Heading Hierarchy
Action
46 headings, 3 skip(s)
REVIEW
46 headings, 3 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
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 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 AI Enable Your Business
  • H4 How can we help you today? skipped
  • H2 You Need The Right AI Infrastructure Software
  • H5 Digital Experience skipped
  • H5 Artificial Intelligence
  • H5 Progress Federal Solutions
  • H5 Kendo UI
  • H5 Telerik
  • H5 Sitefinity
  • H5 ThemeBuilder Pro
  • H5 Agentic RAG
  • H5 Data Platform
  • H5 Digital Experience
  • H5 Artificial Intelligence
  • H5 Progress Federal Solutions
  • H5 Agentic RAG
  • H5 ShareFile
  • H5 MarkLogic
  • H5 Sitefinity
  • H5 Semaphore
  • H5 Sitefinity Insight
  • H5 Corticon
  • H5 OpenEdge
  • H5 Data Platform
  • H5 Artificial Intelligence
  • H5 Progress Federal Solutions
  • H5 Agentic RAG
  • H5 MarkLogic
  • H5 DataDirect
  • H5 Semaphore
  • H5 OpenEdge
  • H5 MOVEit
  • H5 Infrastructure Management
  • H5 Artificial Intelligence
  • H5 Progress Federal Solutions
  • H5 Chef
  • H5 WhatsUp Gold
  • H5 LoadMaster
  • H5 Flowmon
  • H2 Latest from Progress
  • H2 Trusted Software Built for What’s Next
  • H2 Trust Progress for Innovation and Results
  • H4 80% skipped
  • H4 200K
  • H4 100%
  • H2 Progress Insights & Perspective

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

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 16 fail WCAG AA
REVIEW

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

4 pass 16 fail WCAG AA
h1 AI Enable Your Business
1.29:1
#000000
on
#151950
needs 3.0:1 (large text)
32px · bottom of viewport
h2 You Need The Right AI Infrastructure Sof…
1.29:1
#000000
on
#151950
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest from Progress
1.29:1
#000000
on
#151950
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trusted Software Built for What’s Next
1.29:1
#000000
on
#151950
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Trust Progress for Innovation and Result…
1.29:1
#000000
on
#151950
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Progress Insights & Perspective
1.29:1
#000000
on
#151950
needs 3.0:1 (large text)
24px · bottom of viewport
div New
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · above the fold
a Progress Data Platform
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · above the fold
div New
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · above the fold
a AI Product Overview
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · above the fold
a AI Thought Leadership
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · above the fold
button Solutions
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · above the fold
a Artificial Intelligence
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · above the fold
p Develop the responsible AI-powered appli…
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · above the fold
a Data Platform
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · above the fold
p Accelerate data, AI and analytics projec…
1.29:1
#000000
on
#151950
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 AI Enable Your Busin…1.29:13.0:1
#000000
#151950
Fail
h2 You Need The Right A…1.29:13.0:1
#000000
#151950
Fail
h2 Latest from Progress1.29:13.0:1
#000000
#151950
Fail
h2 Trusted Software Bui…1.29:13.0:1
#000000
#151950
Fail
h2 Trust Progress for I…1.29:13.0:1
#000000
#151950
Fail
h2 Progress Insights & …1.29:13.0:1
#000000
#151950
Fail
title Unleash the Power of…14.92:14.5:1
#000000
#90EF8E
Pass
a Deploy Trusted AI Fa…14.92:14.5:1
#000000
#90EF8E
Pass
a skip navigation18.25:14.5:1
#000000
#D3F9D2
Pass
a Progress Agentic RAG21.00:14.5:1
#000000
#FFFFFF
Pass
div New1.29:14.5:1
#000000
#151950
Fail
a Progress Data Platfo…1.29:14.5:1
#000000
#151950
Fail
div New1.29:14.5:1
#000000
#151950
Fail
a AI Product Overview1.29:14.5:1
#000000
#151950
Fail
a AI Thought Leadershi…1.29:14.5:1
#000000
#151950
Fail
button Solutions1.29:14.5:1
#000000
#151950
Fail
a Artificial Intellige…1.29:14.5:1
#000000
#151950
Fail
p Develop the responsi…1.29:14.5:1
#000000
#151950
Fail
a Data Platform1.29:14.5:1
#000000
#151950
Fail
p Accelerate data, AI …1.29:14.5:1
#000000
#151950
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 18 images OK
PASS
All 18 images OK
Info::
2 decorative image(s) correctly marked
Info::
16 image(s) with good alt text
18 images 16 good alt text 2 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 3 controls have issues
PASS
1 of 3 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q">
Info::
2 control(s) properly labeled
3 controls
2 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
#js-search-inputsearchSite searchfor/id
#js-search-mobinputsearchSite searchfor/id
qtext(Ask anything)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="q">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

A+
Lighthouse Accessibility Audits
Score 97/100 — 3 failing, 23 passed
PASS
97

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.

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
How can we help you today? section.Section > div#Content_C1290_Col00 > div#Content_C1291_Col00 > h4.-c-black
80% div#Content_C1321_Col00 > div.row > div#Content_C1322_Col00 > h4.-c-green1

These are opportunities to improve keyboard navigation in your application.

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 html#html

These items highlight common accessibility best practices.

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
WATCH VIDEO div#Content_C1309_Col01 > div.row > div#Content_C1310_Col00 > a.Btn
○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
●Background and foreground colors have a sufficient contrast ratio
●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
●Touch targets have sufficient size and spacing.
●Deprecated ARIA roles were not used
○`[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
○`<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.
○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