Skip to content
https://www.thousandsmiles.co.uk/dental-hygiene

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
9
REVIEW
5
PASS
10
INFO
0
Checks
24
10 PASS 5 REVIEW 9 FIX
D
Landmark Structure
Action
5 landmarks
FIX
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <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 (missing!) CONTENTINFO footer

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

D
Form Accessibility
Action
7 of 7 controls have issues
FIX
7 of 7 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Warning::
5 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="firstname">; <input type="text" name="lname">; <input type="email" name="email">; <input type="text" name="phone">; <textarea name="message">
7 controls
0 labeled
5 placeholder only
2 unlabeled
ControlTypeLabelMethod
firstnametext(First Name)placeholder only
lnametext(Last Name)placeholder only
emailemail(Email)placeholder only
phonetext(Phone No.)placeholder only
messagetextarea(Message)placeholder only
inputsubmit(none)none
#g-recaptcha-response-100000textarea(none)none

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

<input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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="firstname">; <input type="text" name="lname">; <input type="email" name="email">; <input type="text" name="phone">; <textarea name="message">

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

D
Mobile Keyboard & Autofill
Action
3/3 eligible field(s) missing autocomplete or inputmode
FIX
3/3 eligible field(s) missing autocomplete or inputmode
Warning::
2 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: family-name, email.
Got: <input type="text" name="lname">, <input type="email" name="email">
Warning::
1 field(s) would benefit from inputmode attribute
Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: email.
Got: <input type="email" name="email">
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-3ymepo
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
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::
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
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://www.thousandsmiles.co.uk/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://www.thousandsmiles.co.uk/manifest.json

Manifest contains invalid JSON.

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::
3 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 3 <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
Heading Hierarchy
18 headings, 2 skip(s)
REVIEW
18 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Dental Hygiene
  • H1 Dental hygienist in Earls Court, London
  • H2 Benefits of Professional Dental Hygiene
  • H4 Ready to book your hygiene session? Call us today on 020 3773 2280 to schedule your appointment. skipped
  • H2 What to Expect During Your dental hygiene Appointment
  • H2 The Cost of Hygiene Treatment
  • H2 Aftercare and Home Maintenance
  • H2 Who Should See a Dental Hygienist?
  • H2 Alternatives and Complementary Treatments
  • H2 AIR-FLOW Therapy Explained
  • H2 Frequently Asked Questions
  • H2 Book Your Hygiene Appointment
  • H4 Take the first step today—book your consultation and let’s create a smile you’ll love. skipped
  • H3 Opening Hours
  • H3 Treatments
  • H4 Book Now
  • H4 Make an Enquiry
  • H4 Got a Question?

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 ▾

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

B
Iframe Accessibility
2/3 iframe(s) missing title; 0 placeholder(s)
REVIEW
2/3 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d2484.324063603142!2d-0.19…")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA
title Dental Hygienist Earls Court | Dental Hy…
1.47:1
#000000
on
#322825
needs 4.5:1 (normal text)
16px · top of page (header area)
a Home
1.49:1
#000000
on
#322A26
needs 4.5:1 (normal text)
16px · top of page (header area)
a Emergency Dentist
1.65:1
#000000
on
#38312E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Tooth Pain
1.35:1
#000000
on
#2D211E
needs 4.5:1 (normal text)
16px · top of page (header area)
a Broken Tooth
1.57:1
#000000
on
#372D2A
needs 4.5:1 (normal text)
16px · above the fold
a Loose Filling
1.56:1
#000000
on
#352D28
needs 4.5:1 (normal text)
16px · above the fold
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Dental hygienist20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Dental Hygiene20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Benefits of Professi…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 What to Expect Durin…20.47:13.0:1
#000000
#FCFCFC
Pass
h2 The Cost of20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Aftercare and20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Who Should20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Alternatives and20.47:13.0:1
#000000
#FCFCFC
Pass
h2 AIR-FLOW20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Frequently20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Questions20.47:13.0:1
#000000
#FCFCFC
Pass
h2 Book Your20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Opening Hours20.47:13.0:1
#000000
#FCFCFC
Pass
h3 Treatments20.47:13.0:1
#000000
#FCFCFC
Pass
title Dental Hygienist Ear…1.47:14.5:1
#000000
#322825
Fail
a Home1.49:14.5:1
#000000
#322A26
Fail
a Emergency Dentist1.65:14.5:1
#000000
#38312E
Fail
a Tooth Pain1.35:14.5:1
#000000
#2D211E
Fail
a Broken Tooth1.57:14.5:1
#000000
#372D2A
Fail
a Loose Filling1.56:14.5:1
#000000
#352D28
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.

B
Lighthouse Accessibility Audits
Score 82/100 — 5 failing, 16 passed
REVIEW
82

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
Prevention of gum disease div.d-sec-content > ul.ts-listing > li > strong
Cleaner, fresher breath div.d-sec-content > ul.ts-listing > li > strong
Whiter-looking teeth div.d-sec-content > ul.ts-listing > li > strong
Personalised oral health advice div.d-sec-content > ul.ts-listing > li > strong
Support for overall health, div.d-sec-content > ul.ts-listing > li > strong
Book Online div.container > div.tktf-step-info > div.btn-row > a.btn
Polishing div.d-sec-content > ul.ts-listing > li > strong
Stain removal treatments div.d-sec-content > ul.ts-listing > li > strong
Preventive fluoride application div.d-sec-content > ul.ts-listing > li > strong
Tailored home-care guidance div.d-sec-content > ul.ts-listing > li > strong
Teeth whitening div.d-sec-content > ul.ts-listing > li > strong
Restorative dentistry div.d-sec-content > ul.ts-listing > li > strong
Periodontal treatment div.d-sec-content > ul.ts-listing > li > strong
020 3773 2280 section.thousand-smile-bres > div.container > p > a.links
info@tsmile.uk section.thousand-smile-bres > div.container > p > a.links
Privacy Policy div#cookieBanner > div.cookie-content > p > a
Terms and Condition div#cookieBanner > div.cookie-content > p > a

These are opportunities to improve the legibility of your content.

Names and labels

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.row > div.col-lg-12 > div.google-map > iframe div.row > div.col-lg-12 > div.google-map > iframe

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.mob-row > div.mob-logo > div.logoSec > a div.mob-row > div.mob-logo > div.logoSec > a
div.mobile-version > div.mob-row > div.mob-icons > a.mob-info-btn div.mobile-version > div.mob-row > div.mob-icons > a.mob-info-btn
div.mobile-version > div.mob-row > div.mob-icons > a.mob-info-btn div.mobile-version > div.mob-row > div.mob-icons > a.mob-info-btn
div.mobile-version > div.mob-row > div.mob-icons > a.btn div.mobile-version > div.mob-row > div.mob-icons > a.btn
div.ftr-social > ul.ftrSocial > li > a.ftr-facebook div.ftr-social > ul.ftrSocial > li > a.ftr-facebook
div.ftr-social > ul.ftrSocial > li > a.ftr-twitter div.ftr-social > ul.ftrSocial > li > a.ftr-twitter
div.ftr-social > ul.ftrSocial > li > a.ftr-linkedin div.ftr-social > ul.ftrSocial > li > a.ftr-linkedin

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.

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
Ready to book your hygiene session? Call us today on 020 3773 2280 to schedule … section.take-the-first-step > div.container > div.tktf-step-info > h4.mb-4
Take the first step today—book your consultation and let’s create a smile you’l… section.take-the-first-step > div.container > div.tktf-step-info > h4

These are opportunities to improve keyboard navigation in your application.

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
●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-hidden="true"]` elements do not contain focusable descendents
●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
●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 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
○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
○`<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.
○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.
A+
Heading Text Quality
All 18 heading(s) have substantive, well-formed text
PASS
All 18 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 32 images OK
PASS
All 32 images OK
Info::
23 decorative image(s) correctly marked
Info::
9 image(s) with good alt text
32 images 9 good alt text 23 decorative
All images have appropriate alt text.
A+
Form Input Types
1 input(s) using type=text where a specific type would help
PASS
1 input(s) using type=text where a specific type would help
Info::
Input "phone" should use type="tel" (currently type="text")
Field name "phone" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.
A+
Form Input Quality
7 form control(s) checked, no input-semantic issues
PASS
7 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en-GB"
PASS
Lang attribute set to "en-GB"
Info::
<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
Info::
No tabindex anti-patterns detected
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 139 visible text node(s) render at >= 12 CSS pixels
PASS
All 139 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback