Skip to content
https://zend.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
3
REVIEW
6
PASS
4
INFO
0
Checks
13
4 PASS 6 REVIEW 3 FIX
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: #4c00ff
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.
B
Form Accessibility
2 of 7 controls have issues
REVIEW
2 of 7 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="checkbox" id="menu-toggle">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="keys">
Info::
5 control(s) properly labeled
7 controls
5 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
#solutions-togglecheckboxSolutionsfor/id
#products-togglecheckboxProductsfor/id
#support-togglecheckboxSupportfor/id
#services-togglecheckboxServicesfor/id
#resources-togglecheckboxResourcesfor/id
keystext(Search...)placeholder only
#menu-togglecheckbox(none)none

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

<input type="checkbox" id="menu-toggle">

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

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

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

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

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 404: Not Found | Zend ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
10 icon(s) detected
REVIEW
10 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ 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, 14 fail WCAG AA
REVIEW

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

6 pass 14 fail WCAG AA 1 pass AA only
h1 Made Possible
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Secondary Navigation
2.75:1
#000000
on
#4C00FF
needs 3.0:1 (large text)
24px · top of page (header area)
h2 Mega Menu
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Enterprise-Grade PHP Platform Developmen…
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Meet the Zend Enterprise Web Platform
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 See Why Zend Is the Top Choice for PHP
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Secure, Scale, and Optimize Mission-Crit…
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Footer
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Keep Critical PHP Apps Secure and Suppor…
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Instant Application Insight and Orchestr…
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 On-Demand PHP Expertise
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
h3 mittwald Managed Hosting Customers Stay …
1.66:1
#000000
on
#333333
needs 3.0:1 (large text)
19px · bottom of viewport
title Enterprise PHP Development Platform | Ex…
2.75:1
#000000
on
#4C00FF
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to main content
2.75:1
#000000
on
#4C00FF
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Made Possible1.66:13.0:1
#000000
#333333
Fail
h2 Secondary Navigation2.75:13.0:1
#000000
#4C00FF
Fail
h2 Sitewide Search4.31:13.0:1
#000000
#7F52EB
Pass
h2 Mega Menu1.66:13.0:1
#000000
#333333
Fail
h2 Enterprise-Grade PHP…1.66:13.0:1
#000000
#333333
Fail
h2 Meet the Zend Enterp…1.66:13.0:1
#000000
#333333
Fail
h2 See Why Zend Is the …1.66:13.0:1
#000000
#333333
Fail
h2 Secure, Scale, and O…1.66:13.0:1
#000000
#333333
Fail
h2 Footer1.66:13.0:1
#000000
#333333
Fail
h3 Keep Critical PHP Ap…1.66:13.0:1
#000000
#333333
Fail
h3 Instant Application …1.66:13.0:1
#000000
#333333
Fail
h3 On-Demand PHP Expert…1.66:13.0:1
#000000
#333333
Fail
h3 mittwald Managed Hos…1.66:13.0:1
#000000
#333333
Fail
title Enterprise PHP Devel…2.75:14.5:1
#000000
#4C00FF
Fail
a Skip to main content2.75:14.5:1
#000000
#4C00FF
Fail
button ✖21.00:14.5:1
#000000
#FFFFFF
Pass
a Partners21.00:14.5:1
#000000
#FFFFFF
Pass
span Downloads21.00:14.5:1
#000000
#FFFFFF
Pass
a Downloads21.00:14.5:1
#000000
#FFFFFF
Pass
a Plugins21.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.

A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 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 "block-p4base-secondarynavigation-menu" 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
16 headings, 1 skip(s)
PASS
16 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Secondary Navigation
  • H2 Sitewide Search
  • H2 Mega Menu
  • H5 Featured Product skipped
  • H5 ZendPHP
  • H5 2026 PHP Landscape Report​
  • H1 Mission-Critical PHP Made Possible
  • H2 Enterprise-Grade PHP Platform Development and Services
  • H3 Keep Critical PHP Apps Secure and Supported
  • H3 Instant Application Insight and Orchestration
  • H3 On-Demand PHP Expertise
  • H2 Meet the Zend Enterprise Web Platform
  • H2 See Why Zend Is the Top Choice for PHP
  • H3 mittwald Managed Hosting Customers Stay Secure With PHP LTS From Zend
  • H2 Secure, Scale, and Optimize Mission-Critical PHP Technologies
  • H2 Footer

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

A+
Alt Text Quality
1 of 13 images have issues
PASS
1 of 13 images have issues
Warning::
1 image(s) with generic alt text
Info::
1 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
13 images 9 good alt text 2 decorative 1 generic
IssueCount
generic1 image(s)
too long1 image(s)
A
Lighthouse Accessibility Audits
Score 93/100 — 3 failing, 26 passed
PASS
93

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
go to promotion div#trd_cta_f417b1fb-88e1-4902-9ed0-5e660bc74e81 > div.component-content > div.container-elements > a.trd-link

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
Go to slide 1 div.flex > div.flex > div.flex > button.mx-1
Go to slide 2 div.flex > div.flex > div.flex > button.mx-1
Go to slide 3 div.flex > div.flex > div.flex > button.mx-1

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
Read our cookie policy. div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-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
●`[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
●ARIA input fields have accessible names
●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.
●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
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○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