Skip to content
https://blogastico.it

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
80
GRADE
B
FIX
5
REVIEW
3
PASS
16
INFO
0
Checks
24
16 PASS 3 REVIEW 5 FIX
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-iy0fic
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.

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
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'>.
✓ favicon.ico Present
✗ PNG Icons Missing
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://blogastico.it/manifest.webmanifest contains invalid JSON. Browsers cannot parse it.
Got: https://blogastico.it/manifest.webmanifest

Manifest contains invalid JSON.

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 ✗
D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 3 <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
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
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.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA 1 pass AA only
a Auto
4.13:1
#000000
on
#6E6E70
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a Il sottovalutato coprivolante
4.26:1
#000000
on
#72706F
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
time March 30, 2026
1.21:1
#000000
on
#1C1A17
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

3 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
h2 Posts navigation11.77:13.0:1
#000000
#E2BAA1
Pass
h2 You May Also Like:11.77:13.0:1
#000000
#E2BAA1
Pass
h3 Categories11.77:13.0:1
#000000
#E2BAA1
Pass
title Blogastico.it – Le…21.00:14.5:1
#000000
#FFFFFF
Pass
a Skip to content21.00:14.5:1
#000000
#FFFFFF
Pass
span Shuffle21.00:14.5:1
#000000
#FFFFFF
Pass
span Menu21.00:14.5:1
#000000
#FFFFFF
Pass
span Switch color mode21.00:14.5:1
#000000
#FFFFFF
Pass
span Search21.00:14.5:1
#000000
#FFFFFF
Pass
div Monday, August 24 20…21.00:14.5:1
#000000
#FFFFFF
Pass
a Blogastico.it21.00:14.5:1
#000000
#FFFFFF
Pass
span Le ultime notizie da…21.00:14.5:1
#000000
#FFFFFF
Pass
span Close21.00:14.5:1
#000000
#FFFFFF
Pass
span Search for:21.00:14.5:1
#000000
#FFFFFF
Pass
span Close search11.81:14.5:1
#000000
#C2C2C4
Pass
a Auto4.13:14.5:1
#000000
#6E6E70
Fail
a Il sottovalutato cop…4.26:14.5:1
#000000
#72706F
Fail
span Posted on5.83:14.5:1
#000000
#868787
Pass
time March 30, 20261.21:14.5:1
#000000
#1C1A17
Fail
time March 30, 202617.02:14.5:1
#000000
#E7E7EA
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
35 landmarks
PASS
35 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Info::
All <nav> elements are properly labeled
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #primary
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Primary" SEARCH MAIN ASIDE CONTENTINFO footer

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

A+
Heading Hierarchy
26 headings
PASS
26 headings
Info::
Single H1 present
  • H1 Blogastico.it
  • H2 Il sottovalutato coprivolante
  • H2 Massaggio riflessologico plantare: racconti di piedi in viaggio
  • H2 Quanto si risparmia davvero passando all’infrarosso
  • H2 Perché le pastiglie dei freni di qualità sono così importanti
  • H2 Il sottovalutato coprivolante
  • H2 Massaggio riflessologico plantare: racconti di piedi in viaggio
  • H2 Massaggio riflessologico plantare: racconti di piedi in viaggio
  • H2 Quanto si risparmia davvero passando all’infrarosso
  • H2 Perché le pastiglie dei freni di qualità sono così importanti
  • H2 Il sottovalutato coprivolante
  • H2 Il tuo dizionario personale dei sogni: come creare un riferimento basato sulle tue esperienze
  • H2 Il pastore tedesco come compagno caotico e soffice
  • H2 Trovare il miglior negozio online di ricambi auto
  • H2 Tipi popolari di alimenti senza glutine
  • H2 L’ascesa dell’Ayurveda nelle esperienze termali slovene
  • H2 Lettera d’amore ai tergicristalli dell’auto
  • H2 Posts navigation
  • H3 Categories
  • H2 You May Also Like:
  • H3 Massaggio riflessologico plantare: racconti di piedi in viaggio
  • H3 Quanto si risparmia davvero passando all’infrarosso
  • H3 Perché le pastiglie dei freni di qualità sono così importanti
  • H3 Il sottovalutato coprivolante
  • H3 Il tuo dizionario personale dei sogni: come creare un riferimento basato sulle tue esperienze
  • H3 Il pastore tedesco come compagno caotico e soffice
A+
Heading Text Quality
All 26 heading(s) have substantive, well-formed text
PASS
All 26 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 16 images OK
PASS
All 16 images OK
Info::
10 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
16 images 6 good alt text 10 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 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="submit">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
ssearchSearch for:none
inputsubmit(none)none

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

<input type="submit">

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

A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
6 explicit tabindex attribute(s) checked, no anti-patterns
PASS
6 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
No iframes on this page
A+
Tap Target Adequacy
All tap targets meet WCAG 2.5.5/2.5.8 sizing
PASS
All tap targets meet WCAG 2.5.5/2.5.8 sizing
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 153 visible text node(s) render at >= 12 CSS pixels
PASS
All 153 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
No `<meta name="theme-color">` -- browser chrome falls back to default
Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.
A
Lighthouse Accessibility Audits
Score 92/100 — 2 failing, 23 passed
PASS
92

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
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text
1 min read div.article-block-wrapper > div.entry-image > div.blogmotive-meta > span.meta-text

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link
[…] div.article-block-wrapper > div.entry-summary > p > a.read-more-link

These are opportunities to improve the legibility of your content.

○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
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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
●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
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○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.
○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.

Send Feedback