Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

6 landmarks

FIX

6 landmarks

No <main> landmark found

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

4 <nav> landmark(s) found

4 of 4 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Link & Button Quality

Action

7 issue(s) across 42 links and 5 buttons

FIX

7 issue(s) across 42 links and 5 buttons

4 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: #; #; #; #

2 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: /wordpress-hosting-features.php ("Learn More"); /wordpress-hosting-features.php ("Learn More")

3 link(s) open in new tab without warning

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

Got: https://digital.mondadori.it/docs/digital/privacy-notice-mondadori-digital-sp…; https://www.mondadorigroup.com/privacy-policy-eng; https://digital.mondadori.it/docs/digital/cookie-policy-mondadori-digital-spa…

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.btn--search (#93 on page)

33 link(s) with descriptive text

42 links

4 empty

2 generic text

3 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/wordpress-hosting-features.php	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Wordpress Hosting Features.Php
/wordpress-hosting-features.php	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Wordpress Hosting Features.Php
https://digital.mondadori.it/docs/digita…	Privacy Notice	new tab	Add '(opens in new tab)' to text
https://www.mondadorigroup.com/privacy-p…	Privacy Policy	new tab	Add '(opens in new tab)' to text
https://digital.mondadori.it/docs/digita…	Cookie Policy	new tab	Add '(opens in new tab)' to text
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

37 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

#; #; #; #

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Generic link text like 'click here' doesn't describe the destination.

/wordpress-hosting-features.php ("Learn More"); /wordpress-hosting-features.php ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://digital.mondadori.it/docs/digital/privacy-notice-mondadori-digital-sp…; https://www.mondadorigroup.com/privacy-policy-eng; https://digital.mondadori.it/docs/digital/cookie-policy-mondadori-digital-spa…

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.btn--search (#93 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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-hcziwc

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://altervista.org/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://altervista.org/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

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

4 navigation landmark(s) detected

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 4 <nav> element(s)

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.

Alt Text Quality

Action

18 of 18 images have issues

REVIEW

18 of 18 images have issues

17 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

1 image(s) with generic alt text

18 images 1 generic 17 missing

Issue	Count
missing	17 image(s)
generic	1 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

Favicon & Branding

9 icon(s) detected

REVIEW

9 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

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 Create your site and start earning

2.35:1

#000000

#7C3138

needs 3.0:1 (large text)

32px · above the fold

h2 Pick Up A Design

2.82:1

#000000

#54507D

needs 3.0:1 (large text)

24px · mid-page

h2 Manage The Site

2.82:1

#000000

#54507D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your Story Is More Than A Showcase

2.82:1

#000000

#54507D

needs 3.0:1 (large text)

24px · bottom of viewport

title Create a blog or website for free and ma…

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · top of page (header area)

a Start Now

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · top of page (header area)

a Features

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · top of page (header area)

a Earn

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · top of page (header area)

a Hosting

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · above the fold

span Login

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · above the fold

span Login

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · above the fold

span Menu

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · above the fold

p Open

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · above the fold

span free of charge

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · above the fold

p a site

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · above the fold

span .altervista.org

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · mid-page

p or choose the name you want:

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · mid-page

span .com

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · mid-page

span .net

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · mid-page

p and other available extensions!

2.35:1

#000000

#7C3138

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Create your site and…	2.35:1	3.0:1	#000000	#7C3138	Fail
h2 Pick Up A Design	2.82:1	3.0:1	#000000	#54507D	Fail
h2 Manage The Site	2.82:1	3.0:1	#000000	#54507D	Fail
h2 Your Story Is More T…	2.82:1	3.0:1	#000000	#54507D	Fail
title Create a blog or web…	2.35:1	4.5:1	#000000	#7C3138	Fail
a Start Now	2.35:1	4.5:1	#000000	#7C3138	Fail
a Features	2.35:1	4.5:1	#000000	#7C3138	Fail
a Earn	2.35:1	4.5:1	#000000	#7C3138	Fail
a Hosting	2.35:1	4.5:1	#000000	#7C3138	Fail
span Login	2.35:1	4.5:1	#000000	#7C3138	Fail
span Login	2.35:1	4.5:1	#000000	#7C3138	Fail
span Menu	2.35:1	4.5:1	#000000	#7C3138	Fail
p Open	2.35:1	4.5:1	#000000	#7C3138	Fail
span free of charge	2.35:1	4.5:1	#000000	#7C3138	Fail
p a site	2.35:1	4.5:1	#000000	#7C3138	Fail
span .altervista.org	2.35:1	4.5:1	#000000	#7C3138	Fail
p or choose the name y…	2.35:1	4.5:1	#000000	#7C3138	Fail
span .com	2.35:1	4.5:1	#000000	#7C3138	Fail
span .net	2.35:1	4.5:1	#000000	#7C3138	Fail
p and other available …	2.35:1	4.5:1	#000000	#7C3138	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.

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 23 passed

REVIEW

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.

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
form.domainSearch > div.formGroup > div.formField > input `form.domainSearch > div.formGroup > div.formField > input`
Open free of charge a site .altervista.org or choose the name you want: .com, .… `div.transitionWrapper > div.domainListWrapper > div.domainsList > p.tld-info`

These are opportunities to improve the legibility of your content.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax `div.av-grid-two-col > div.av-elem > div.av-image-composition > img.rellax`
section#section-4 > div.av-section-inner > div.av-cover-image > img.av-cover-image `section#section-4 > div.av-section-inner > div.av-cover-image > img.av-cover-image`
section#section-4 > div.av-section-inner > div.food-blogger-badge > img `section#section-4 > div.av-section-inner > div.food-blogger-badge > img`
div.av-testimonial-slide > div.author-content > div.author-image > img `div.av-testimonial-slide > div.author-content > div.author-image > img`
div.av-testimonial-slide > div.author-content > div.author-image > img `div.av-testimonial-slide > div.author-content > div.author-image > img`
div.av-testimonial-slide > div.author-content > div.author-image > img `div.av-testimonial-slide > div.author-content > div.author-image > img`
div.av-testimonial-slide > div.author-content > div.author-image > img `div.av-testimonial-slide > div.author-content > div.author-image > img`
div.av-testimonial-slide > div.author-content > div.author-image > img `div.av-testimonial-slide > div.author-content > div.author-image > img`

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
ALTERVISTA News Hosting WordPress managed hosting Make money blogging Forum `footer#site-footer > div.av-container > nav.footer-navigation > ul.footer-menu`
COMPANY About Us Contacts `footer#site-footer > div.av-container > nav.footer-navigation > ul.footer-menu`
TERMS OF SERVICE Disclaimer Privacy Notice Privacy Policy Cookie Policy Trackin… `footer#site-footer > div.av-container > nav.footer-navigation > ul.footer-menu`
COMMUNITY FAQ Support Thanks Brand `footer#site-footer > div.av-container > nav.footer-navigation > ul.footer-menu`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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

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

●`button`, `link`, and `menuitem` elements have accessible names

●ARIA attributes are used as specified for the element's role

●Elements use only permitted ARIA attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●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

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

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

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

A+

Heading Hierarchy

4 headings

PASS

4 headings

Single H1 present

H1 Create your site and start earning
H2 Pick Up A Design
H2 Manage The Site
H2 Your Story Is More Than A Showcase

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text" name="siteName">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
siteName	text	(Choose the domain name)	placeholder only

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

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

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