Skip to content
https://fastpanel.direct

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
7
REVIEW
2
PASS
4
INFO
0
Checks
13
4 PASS 2 REVIEW 7 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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

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

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

F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-3kbkva
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://fastpanel.direct/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://fastpanel.direct/manifest.json

Manifest contains invalid JSON.

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::
3 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 3 <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
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 server
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
32px · bottom of viewport
h1 control panel
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Why FASTPANEL
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Key features
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Localization
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 People love us
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 For Providers
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
24px · bottom of viewport
h2 FAQ
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Backup
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Mail
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 File Manager
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 SSL
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Firewall
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Databases
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PHP
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Job scheduler
1.06:1
#000000
on
#09090C
needs 3.0:1 (large text)
19px · bottom of viewport
title FASTPANEL ®
1.06:1
#000000
on
#09090C
needs 4.5:1 (normal text)
16px · top of page (header area)
span Services
1.06:1
#000000
on
#09090C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Get license
2.39:1
#000000
on
#034F77
needs 4.5:1 (normal text)
16px · top of page (header area) · over background image/gradient
a SSL certificates
2.58:1
#000000
on
#01528A
needs 4.5:1 (normal text)
16px · top of page (header area)

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 server1.06:13.0:1
#000000
#09090C
Fail
h1 control panel1.06:13.0:1
#000000
#09090C
Fail
h2 Why FASTPANEL1.06:13.0:1
#000000
#09090C
Fail
h2 Key features1.06:13.0:1
#000000
#09090C
Fail
h2 Localization1.06:13.0:1
#000000
#09090C
Fail
h2 People love us1.06:13.0:1
#000000
#09090C
Fail
h2 For Providers1.06:13.0:1
#000000
#09090C
Fail
h2 FAQ1.06:13.0:1
#000000
#09090C
Fail
h3 Backup1.06:13.0:1
#000000
#09090C
Fail
h3 Mail1.06:13.0:1
#000000
#09090C
Fail
h3 File Manager1.06:13.0:1
#000000
#09090C
Fail
h3 SSL1.06:13.0:1
#000000
#09090C
Fail
h3 Firewall1.06:13.0:1
#000000
#09090C
Fail
h3 Databases1.06:13.0:1
#000000
#09090C
Fail
h3 PHP1.06:13.0:1
#000000
#09090C
Fail
h3 Job scheduler1.06:13.0:1
#000000
#09090C
Fail
title FASTPANEL ®1.06:14.5:1
#000000
#09090C
Fail
span Services1.06:14.5:1
#000000
#09090C
Fail
a Get license2.39:14.5:1
#000000
#034F77
Fail
a SSL certificates2.58:14.5:1
#000000
#01528A
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+
Heading Hierarchy
16 headings
PASS
16 headings
Info::
Single H1 present
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 Free Powerful Secure Reliable server control panel
  • H2 Why FASTPANEL?
  • H2 Key features
  • H3 (empty)
  • H3 Backup
  • H3 Mail
  • H3 File Manager
  • H3 SSL
  • H3 Firewall
  • H3 Databases
  • H3 PHP
  • H3 Job scheduler
  • H2 Localization
  • H2 People love us
  • H2 For Providers
  • H2 FAQ

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

A+
Alt Text Quality
All 162 images OK
PASS
All 162 images OK
Info::
162 image(s) with good alt text
162 images 162 good alt text
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
Lighthouse Accessibility Audits
Score 93/100 — 2 failing, 18 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
section.pb-[100px] > div.container > ins#revive-0-1 > a section.pb-[100px] > div.container > ins#revive-0-1 > 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.

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.overflow-x-hidden html.overflow-x-hidden

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[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 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
●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
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`[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
○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
○Links are distinguishable without relying on color.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback