Skip to content
https://ispmanager.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
60
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
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
3 landmarks
REVIEW
3 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
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 header 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 Error 404 - ispmanager ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Lighthouse Accessibility Audits
Action
Score 71/100 — 5 failing, 12 passed
REVIEW
71

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

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
header#header > div.container > div.flex > button.bg-light-purple4 header#header > div.container > div.flex > button.bg-light-purple4
header#header > div.container > div.flex > button.bg-light-purple4 header#header > div.container > div.flex > button.bg-light-purple4
header#header > div.container > div.flex > button.ml-10 header#header > div.container > div.flex > button.ml-10

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.bg-main-bg > iframe#r4H8FYfj00C7Cy-z body.bg-main-bg > iframe#r4H8FYfj00C7Cy-z

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
header#header > div.container > div.flex > a.mr-auto header#header > div.container > div.flex > a.mr-auto
div.flex > div.text-18 > div.flex > a.w-50 div.flex > div.text-18 > div.flex > a.w-50
div.flex > div.text-18 > div.flex > a.w-50 div.flex > div.text-18 > div.flex > a.w-50
div.flex > div.text-18 > div.flex > a.w-50 div.flex > div.text-18 > div.flex > a.w-50
div.flex > div.text-18 > div.flex > a.w-50 div.flex > div.text-18 > div.flex > a.w-50

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.

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
Our partner providers div.bg-white > div.tw-base-html > p > a
Email to technical support div.bg-white > div.flex-1 > a.tw-btn > span.relative
Go to the Community div.bg-white > div.tw-base-html > p > a
Go to the Help Center div.bg-white > div.tw-base-html > p > a
Up to 10 websites div.bg-white > div > div.text-16 > p
10 div > div.text-16 > p > span
Up to 50 websites div.bg-white > div > div.text-16 > p
50 div > div.text-16 > p > span
Unlimited websites div.bg-white > div > div.text-16 > p
Unlimited div > div.text-16 > p > span
Upgrade anytime inside your ispmanager panel - no reinstallation needed div.relative > div.mt-15 > div.raw-html-embed > p.text-14
We use cookies on the site div.container > div.flex > div > p.text-28
privacy policy div > div.mt-10 > p > a
Accept div.js-cookie-policy > div.container > div.flex > button.js-cookie-policy-btn

These are opportunities to improve the legibility of your content.

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

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-hidden="true"]` is not present on the document `<body>`
●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.
●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
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[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-hidden="true"]` elements do not contain focusable descendents
○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
○`<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.
○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
Heading Hierarchy
23 headings
PASS
23 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H1 A panel to manage hosting, server, websites, mail
  • H2 Everything you need to host and maintain your websites on the server
  • H3 Website management
  • H3 Security Support
  • H3 Configure mail server
  • H3 Manage SSL certificates
  • H2 Try ispmanager in action
  • H3 Run the ispmanager
  • H2 Who is ispmanager for?
  • H3 For web developers
  • H3 For website managers
  • H3 For system administrators
  • H3 For hosting providers
  • H2 ispmanager is in use worldwide
  • H2 We will support and help
  • H3 Technical support 24/7
  • H3 Community
  • H3 Help Center
  • H2 Become our partner and get benefits
  • H3 01
  • H3 02
  • H3 03
  • H1 Ready to launch ispmanager in 3 steps? duplicate H1

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

A+
Alt Text Quality
All 61 images OK
PASS
All 61 images OK
Info::
1 decorative image(s) correctly marked
Info::
60 image(s) with good alt text
61 images 60 good alt text 1 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 A panel to manage …15.25:13.0:1
#000000
#CCDCFF
Pass
h1 Ready to launch isp…15.25:13.0:1
#000000
#CCDCFF
Pass
h2 Everything you need …15.25:13.0:1
#000000
#CCDCFF
Pass
h2 Try ispmanager in ac…15.25:13.0:1
#000000
#CCDCFF
Pass
h2 Who is ispmanager fo…15.25:13.0:1
#000000
#CCDCFF
Pass
h2 ispmanager is in use…15.25:13.0:1
#000000
#CCDCFF
Pass
h2 We will support and …15.25:13.0:1
#000000
#CCDCFF
Pass
h2 Become our partner a…15.25:13.0:1
#000000
#CCDCFF
Pass
h3 Website management15.25:13.0:1
#000000
#CCDCFF
Pass
h3 Security Support15.25:13.0:1
#000000
#CCDCFF
Pass
h3 Configure mail serve…15.25:13.0:1
#000000
#CCDCFF
Pass
h3 Manage SSL certifica…15.25:13.0:1
#000000
#CCDCFF
Pass
h3 Run the ispmanager15.25:13.0:1
#000000
#CCDCFF
Pass
h3 For web developers15.25:13.0:1
#000000
#CCDCFF
Pass
h3 For website managers15.25:13.0:1
#000000
#CCDCFF
Pass
h3 For system administr…15.25:13.0:1
#000000
#CCDCFF
Pass
h3 For hosting provider…15.25:13.0:1
#000000
#CCDCFF
Pass
h3 Technical support 24…15.25:13.0:1
#000000
#CCDCFF
Pass
h3 Community15.25:13.0:1
#000000
#CCDCFF
Pass
h3 Help Center15.25:13.0:1
#000000
#CCDCFF
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.

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

Send Feedback