Skip to content
https://s-sols.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
5
PASS
3
INFO
0
Checks
13
3 PASS 5 REVIEW 5 FIX
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
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::
2 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 2 <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.
B
Landmark Structure
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <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 CONTENTINFO footer

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 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: <select>
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">
2 controls
0 labeled
1 placeholder only
1 unlabeled
ControlTypeLabelMethod
stext(Search…)placeholder only
selectselect(none)none

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

<select>

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

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

<input type="text" name="s">

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

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Seraphinite Solutions ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Lighthouse Accessibility Audits
Action
Score 77/100 — 6 failing, 20 passed
REVIEW
77

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.navbar-items > div.dropdown > a.dropdown-toggle div.row > div.navbar-items > div.dropdown > a.dropdown-toggle
div.row > div.navbar-items > div.dropdown > a.dropdown-toggle div.row > div.navbar-items > div.dropdown > a.dropdown-toggle
en div.row > div.navbar-items > div.dropdown > a.dropdown-toggle

These are opportunities to improve the usage of ARIA in your application which 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
December 24, 2024 div > div.rpwe-block > article.col-md-4 > time.rpwe-time
November 5, 2021 div > div.rpwe-block > article.col-md-4 > time.rpwe-time
June 15, 2021 div > div.rpwe-block > article.col-md-4 > time.rpwe-time
February 27, 2021 div > div.rpwe-block > article.col-md-4 > time.rpwe-time
May 1, 2020 div > div.rpwe-block > article.col-md-4 > time.rpwe-time
April 16, 2020 div > div.rpwe-block > article.col-md-4 > time.rpwe-time

These are opportunities to improve the legibility of your content.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
We make your life more convenient, productive and simpler article#post-17 > div.entry-content > div.page_block_like_container > h3

These are opportunities to improve keyboard navigation in your application.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Euro (€) United States (US) dollar ($) div#pgc-w60b3f73facb5c-0-0 > div#panel-w60b3f73facb5c-0-0-0 > div.textwidget > select

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
ul.products > li.product > div.product_sub_title > a.woocommerce-LoopProduct-link ul.products > li.product > div.product_sub_title > a.woocommerce-LoopProduct-link
ul.products > li.product > div.product_sub_title > a.woocommerce-LoopProduct-link ul.products > li.product > div.product_sub_title > a.woocommerce-LoopProduct-link
ul.products > li.product > div.product_sub_title > a.woocommerce-LoopProduct-link ul.products > li.product > div.product_sub_title > a.woocommerce-LoopProduct-link
ul.products > li.product > div.product_sub_title > a.woocommerce-LoopProduct-link ul.products > li.product > div.product_sub_title > a.woocommerce-LoopProduct-link
body.home > div.areacontent > a.support body.home > div.areacontent > a.support

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Google My Business nav#social > ul#menu-social-items > li.menu-item > a.social-follow-link
YouTube nav#social > ul#menu-social-items > li.menu-item > a.social-follow-link
Facebook nav#social > ul#menu-social-items > li.menu-item > a.social-follow-link
Twitter nav#social > ul#menu-social-items > li.menu-item > a.social-follow-link
Instagram nav#social > ul#menu-social-items > li.menu-item > a.social-follow-link
ReddIt nav#social > ul#menu-social-items > li.menu-item > a.social-follow-link
for WordPress ul.products > li.product > div.product_sub_title > a
for WordPress ul.products > li.product > div.product_sub_title > a
for WordPress ul.products > li.product > div.product_sub_title > a
for Windows ul.products > li.product > div.product_sub_title > a

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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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 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
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[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
○Buttons have an accessible name
○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
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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
38 headings, 1 skip(s)
PASS
38 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 IT solutions to streamline your business and life
  • H3 We make your life more convenient, productive and simpler skipped
  • H2 Awards
  • H3 Recognition and high grade
  • H2 Why from us
  • H3 Trust proven by our users and authorized parties
  • H3 Trusted and loved by our customers
  • H4 Renault Group
  • H4 Brandlift
  • H4 Texas Worker
  • H4 Cubiq
  • H4 GDPR Planet
  • H4 Russian Food
  • H4 EBAU
  • H4 Expleo Group
  • H4 CCOO convenios
  • H4 Cahn Litigation Services
  • H4 Advanced Living
  • H4 Web Valasz
  • H4 Axell Training
  • H4 Jobs3
  • H4 Waterfront Digital
  • H4 Dunatis
  • H4 Preevo
  • H2 Featured Software Products
  • H3 We provide a set of useful software products to you.
  • H2 Accelera­tor
  • H2 Post .DOCX Source
  • H2 Bulk Discounts for Woo­Commerce
  • H2 Wi-Fi Hotspot
  • H2 Helpful Advice and 'How To'
  • H3 Also we provide publications that consist of advice and 'How To' to help in different situations.
  • H3 Currency
  • H3 Cart
  • H3 Recent News
  • H3 Partners
  • H2 Please wait
  • H3 Data is processing...

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

A+
Alt Text Quality
All 37 images OK
PASS
All 37 images OK
Info::
37 image(s) with good alt text
37 images 37 good alt text
All images have appropriate alt text.
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 IT solutions to stre…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Awards21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Why from us21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Featured Software Pr…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Accelera­tor21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Post .DOCX Source21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Bulk Discounts for W…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Wi-Fi Hotspot21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Helpful Advice and '…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Please wait21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We make your life mo…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Recognition and high…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Trust proven by our …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Trusted and loved by…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We provide a set of …21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Also we provide publ…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Currency21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Cart21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Recent News21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Partners21.00:13.0:1
#000000
#FFFFFF
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