Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 5 REVIEW 3 FIX

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

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'>.

Multiple icon sizes detected

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

Action

2 landmarks

REVIEW

2 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

1 <nav> landmark(s) found

No banner (header) landmark

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Vesta Control Panel | Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Web Manifest

Action

Valid manifest

REVIEW

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

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)

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Color Contrast (Screenshot)

Action

20 text elements analyzed, 15 fail WCAG AA

REVIEW

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

5 pass 15 fail WCAG AA 1 pass AA only

h2 Simple installation from a single comman…

1.35:1

#000000

#490336

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Efficient with Low Resource Usage

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Internationalization

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Secure

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Firewall

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Linux Passwords

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Open Source

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Monitoring & logging

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Backups

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Data loss prevention

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Backup Schedules

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 External FTP backups

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 CLI interface

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Start working with Vesta

1.31:1

#000000

#450233

needs 3.0:1 (large text)

24px · bottom of viewport

title Vesta Control Panel

1.40:1

#000000

#4E033B

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Simple Hosting	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h1 Control Panel	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Works with your favo…	20.47:1	3.0:1	#000000	#FCFCFC	Pass
h2 Fast	20.29:1	3.0:1	#000000	#FBFBFB	Pass
h2 Ultra Fast Web Inter…	4.45:1	3.0:1	#000000	#8F6785	Pass
h2 Simple installation …	1.35:1	3.0:1	#000000	#490336	Fail
h2 Efficient with Low R…	1.31:1	3.0:1	#000000	#450233	Fail
h2 Internationalization	1.31:1	3.0:1	#000000	#450233	Fail
h2 Secure	1.31:1	3.0:1	#000000	#450233	Fail
h2 Firewall	1.31:1	3.0:1	#000000	#450233	Fail
h2 Linux Passwords	1.31:1	3.0:1	#000000	#450233	Fail
h2 Open Source	1.31:1	3.0:1	#000000	#450233	Fail
h2 Monitoring & logging	1.31:1	3.0:1	#000000	#450233	Fail
h2 Backups	1.31:1	3.0:1	#000000	#450233	Fail
h2 Data loss prevention	1.31:1	3.0:1	#000000	#450233	Fail
h2 Backup Schedules	1.31:1	3.0:1	#000000	#450233	Fail
h2 External FTP backups	1.31:1	3.0:1	#000000	#450233	Fail
h2 CLI interface	1.31:1	3.0:1	#000000	#450233	Fail
h2 Start working with V…	1.31:1	3.0:1	#000000	#450233	Fail
title Vesta Control Panel	1.40:1	4.5:1	#000000	#4E033B	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

18 headings

PASS

18 headings

Single H1 present

H1 Simple Hosting Control Panel
H2 Works with your favorite stack
H2 Fast
H2 Ultra Fast Web Interface
H2 Simple installation from a single command:
H2 Efficient with Low Resource Usage
H2 Internationalization
H2 Secure
H2 Firewall
H2 Linux Passwords
H2 Open Source
H2 Monitoring & logging
H2 Backups
H2 Data loss prevention
H2 Backup Schedules
H2 External FTP backups
H2 CLI interface
H2 Start working with Vesta

A+

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

5 decorative image(s) correctly marked

7 image(s) with good alt text

12 images 7 good alt text 5 decorative

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

31 links, 2 buttons — all OK

PASS

31 links, 2 buttons — all OK

4 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://github.com/outroll/vesta; https://github.com/outroll/vesta; https://x.com/vestacp/; https://x.com/vestacp/

27 link(s) with descriptive text

31 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://github.com/outroll/vesta	GitHub Respository Link	new tab	Add '(opens in new tab)' to text
https://github.com/outroll/vesta	GitHub Respository Link	new tab	Add '(opens in new tab)' to text
/	Homepage link	img no alt	Add alt attribute to the image
https://x.com/vestacp/	Vesta X profile link	new tab	Add '(opens in new tab)' to text
https://x.com/vestacp/	Vesta X profile link	new tab	Add '(opens in new tab)' to text

29 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://github.com/outroll/vesta; https://github.com/outroll/vesta; https://x.com/vestacp/; https://x.com/vestacp/

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 18 passed

PASS

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.

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-*]` 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

●`[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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

○`[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 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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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.

○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.