https://www.commercialcarpetcleaning.london/persian-rugs

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 4 REVIEW 7 FIX

Landmark Structure

Action

4 landmarks

FIX

4 landmarks

No <main> landmark found

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

2 <nav> landmark(s) found

2 of 2 <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

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

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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.commercialcarpetcleaning.london/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.commercialcarpetcleaning.london/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

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

Heading Hierarchy

12 headings, 2 skip(s)

REVIEW

12 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H6 (missing H3)

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

H6 020 3918 4035
H1 Persian Rug Cleaning London
H2 CLEANING PERSIAN RUGS OF ALL KINDS
H2 IS IT SAFE TO DO YOUR OWN PERSIAN RUG CLEANING?
H2 IS STEAM CLEANING A PERSIAN RUG SAFE FOR YOU?
H2 PERSIAN CARPET CLEANING WITH COMPLETE SATISFACTION
H2 100% SATISFIED PERSIA CARPET CLEANING
H5 Our goal at Commercial Carpet Cleaning London is to maintain a high standard of satisfaction for every rug cleaning job. Therefore, for optimal carpet care… skipped
H2 Our Goal is to Wow You With Every Clean
H6 Follow Us On : skipped
H4 Explore
H4 Get In Touch

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Link & Button Quality

11 issue(s) across 90 links and 0 buttons

REVIEW

11 issue(s) across 90 links and 0 buttons

11 link(s) with no accessible text

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

Got: #nav; https://www.facebook.com/commercialcarpetcleaninglondon; https://www.linkedin.com/company/commercial-carpet-cleaning-london/; https://www.youtube.com/@commercialcarpetcleaninglondon; https://www.instagram.com/commercialcarpetcleaning.uk; #; https://www.facebook.com/commercialcarpetcleaninglondon; https://www.youtube.com/@commercialcarpetcleaninglondon; https://www.linkedin.com/company/commercial-carpet-cleaning-london; https://www.instagram.com/commercialcarpetcleaning.uk (+1 more)

79 link(s) with descriptive text

90 links

11 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
#nav	(empty)	empty	Add link text or aria-label
https://www.facebook.com/commercialcarpe…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/commerc…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@commercialcarpe…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/commercialcarp…	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
tel:02039184035	CALL US AT 020 3918 4035	img no alt	Add alt attribute to the image
tel:02039184035	CALL US AT 020 3918 4035	img no alt	Add alt attribute to the image
https://www.facebook.com/commercialcarpe…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/@commercialcarpe…	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/commerc…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/commercialcarp…	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label

79 links and buttons have descriptive text

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

#nav; https://www.facebook.com/commercialcarpetcleaninglondon; https://www.linkedin.com/company/commercial-carpet-cleaning-london/; https://www.youtube.com/@commercialcarpetcleaninglondon; https://www.instagram.com/commercialcarpetcleaning.uk; #; https://www.facebook.com/commercialcarpetcleaninglondon; https://www.youtube.com/@commercialcarpetcleaninglondon; https://www.linkedin.com/company/commercial-carpet-cleaning-london; https://www.instagram.com/commercialcarpetcleaning.uk (+1 more)

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

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

12 pass 8 fail WCAG AA 2 pass AA only

title Persian Rug Cleaning London – Oriental…

1.57:1

#000000

#023723

needs 4.5:1 (normal text)

16px · top of page (header area)

a Office Carpet Cleaning

2.34:1

#000000

#6F3B2E

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a End of Tenancy Cleaning

2.61:1

#000000

#574F47

needs 4.5:1 (normal text)

16px · above the fold

a Carpet Cleaning North London

1.96:1

#000000

#593521

needs 4.5:1 (normal text)

16px · above the fold

a Emergency Carpet Cleaning

1.51:1

#000000

#462312

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

a Woodfloor Polish & Cleaning

1.09:1

#000000

#110E0A

needs 4.5:1 (normal text)

16px · above the fold

a Upholstery Cleaning

1.11:1

#000000

#16100A

needs 4.5:1 (normal text)

16px · above the fold

a Jetwashing

1.02:1

#000000

#060301

needs 4.5:1 (normal text)

16px · above the fold

2 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)

Element	Ratio	Required	FG	BG	Result
h1 Persian Rug Cleaning…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 CLEANING PERSIAN RUG…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 IS IT SAFE TO DO YOU…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 IS STEAM CLEANING A …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 PERSIAN CARPET CLEAN…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 100% SATISFIED PERSI…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Our	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 is to Wow You With	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Persian Rug Cleaning…	1.57:1	4.5:1	#000000	#023723	Fail
a Home	5.33:1	4.5:1	#000000	#67877B	Pass
a About Us	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Our Services	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Office Carpet Cleani…	2.34:1	4.5:1	#000000	#6F3B2E	Fail
a Hard Floor Polish an…	4.69:1	4.5:1	#000000	#72787B	Pass
a End of Tenancy Clean…	2.61:1	4.5:1	#000000	#574F47	Fail
a Carpet Cleaning Nort…	1.96:1	4.5:1	#000000	#593521	Fail
a Emergency Carpet Cle…	1.51:1	4.5:1	#000000	#462312	Fail
a Woodfloor Polish & C…	1.09:1	4.5:1	#000000	#110E0A	Fail
a Upholstery Cleaning	1.11:1	4.5:1	#000000	#16100A	Fail
a Jetwashing	1.02:1	4.5:1	#000000	#060301	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 89/100 — 3 failing, 14 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.

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
Our goal at Commercial Carpet Cleaning London is to maintain a high standard of… `section.urine-removal > div.container > div.urine-removal-text > h5.mt-4`
Follow Us On : `div.row > div.col-md-4 > div.ftr-bx > h6`

These are opportunities to improve keyboard navigation in your application.

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
div.col-auto > div.social-style1 > div.social-icon > a `div.col-auto > div.social-style1 > div.social-icon > a`
div.col-auto > div.social-style1 > div.social-icon > a `div.col-auto > div.social-style1 > div.social-icon > a`
div.col-auto > div.social-style1 > div.social-icon > a `div.col-auto > div.social-style1 > div.social-icon > a`
div.col-auto > div.social-style1 > div.social-icon > a `div.col-auto > div.social-style1 > div.social-icon > a`
div.row > div.col-auto > div.logo-sec > a.btn `div.row > div.col-auto > div.logo-sec > a.btn`
div.ftr-bx > div > div.social-icon > a `div.ftr-bx > div > div.social-icon > a`
div.ftr-bx > div > div.social-icon > a `div.ftr-bx > div > div.social-icon > a`
div.ftr-bx > div > div.social-icon > a `div.ftr-bx > div > div.social-icon > a`
div.ftr-bx > div > div.social-icon > a `div.ftr-bx > div > div.social-icon > 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 `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-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

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

●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

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

●Touch targets have sufficient size and spacing.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

○`[aria-*]` attributes match their roles

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

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

○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 use only permitted 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

○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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

○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

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

Heading Text Quality

2 heading-text-quality issue(s) detected

PASS

2 heading-text-quality issue(s) detected

1 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H5: 156 chars

Got: 1 >120-char heading(s)

5 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 5 all-caps heading(s)

A+

Alt Text Quality

All 12 images OK

PASS

All 12 images OK

2 decorative image(s) correctly marked

10 image(s) with good alt text

12 images 10 good alt text 2 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.

A+

Form Input Types

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

A+

Document Language

Lang attribute set to "en-GB"

PASS

Lang attribute set to "en-GB"

<html lang="en-GB"> is set and valid

Got: en-GB

A+

Tabindex Anti-Patterns

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 61 visible text node(s) render at >= 12 CSS pixels

PASS

All 61 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

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.

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