https://www.thousandsmiles.uk/e-max-veneers/

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 2 REVIEW 8 FIX

Landmark Structure

Action

8 landmarks

FIX

8 landmarks

No <main> landmark found

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

5 <nav> landmark(s) found

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

Form Accessibility

Action

6 of 6 controls have issues

FIX

6 of 6 controls have issues

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

4 control(s) rely on placeholder only

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

Got: <input type="text" name="fname">; <input type="email" name="email-939">; <input type="text" name="phone">; <textarea name="textarea-427">

6 controls

0 labeled

4 placeholder only

2 unlabeled

Control	Type	Label	Method
fname	text	(Full Name)	placeholder only
email-939	email	(Email)	placeholder only
phone	text	(Phone No.)	placeholder only
textarea-427	textarea	(Message)	placeholder only
input	submit	(none)	none
#g-recaptcha-response-100000	textarea	(none)	none

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

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.

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

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 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: given-name.

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

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-939">

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

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

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

5 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Thousand Smiles ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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

a 020 8050 0280

1.23:1

#000000

#1C1C1A

needs 4.5:1 (normal text)

16px · top of page (header area)

a hello@thousandsmiles.uk

1.40:1

#000000

#3E1E0D

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.79:1

#000000

#572D15

needs 4.5:1 (normal text)

16px · above the fold

a Emergency Dentist

1.53:1

#000000

#49230E

needs 4.5:1 (normal text)

16px · above the fold

a Tooth Pain

1.37:1

#000000

#3E1C09

needs 4.5:1 (normal text)

16px · above the fold

a Broken Tooth

1.22:1

#000000

#311207

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Porcelain Emax Venee…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Cosmetic dentistry	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Benefits of E-max ve…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Disadvantages of the…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 E-max application pr…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 What is the cost of …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 An overview of E-max…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Highly experienced d…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Highly experienced d…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Highly experienced d…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Treatments	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Treatments	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h3 Quick Links	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Emax Veneers Cost UK…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a 020 8050 0280	1.23:1	4.5:1	#000000	#1C1C1A	Fail
a hello@thousandsmiles…	1.40:1	4.5:1	#000000	#3E1E0D	Fail
a Home	1.79:1	4.5:1	#000000	#572D15	Fail
a Emergency Dentist	1.53:1	4.5:1	#000000	#49230E	Fail
a Tooth Pain	1.37:1	4.5:1	#000000	#3E1C09	Fail
a Broken Tooth	1.22:1	4.5:1	#000000	#311207	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.

Heading Hierarchy

16 headings, 1 skip(s)

PASS

16 headings, 1 skip(s)

Single H1 present

Heading level skipped: H3 → H5 (missing H4)

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

H5 Call Us:
H5 Mail Us:
H1 Porcelain Emax Veneers UK
H2 Cosmetic dentistry
H3 An overview of E-max porcelain veneers
H3 Highly experienced dentists offering advanced dental treatments at Thousand Smiles.
H2 Benefits of E-max veneers
H3 Highly experienced dentists offering advanced dental treatments at Thousand Smiles.
H2 Disadvantages of the E-max veneers
H2 E-max application procedure
H3 Highly experienced dentists offering advanced dental treatments at Thousand Smiles.
H2 What is the cost of an E-max veneer?
H3 Treatments
H3 Treatments
H3 Quick Links
H5 Book a Consultation skipped

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+

Heading Text Quality

All 16 heading(s) have substantive, well-formed text

PASS

All 16 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 14 images OK

PASS

All 14 images OK

14 image(s) with good alt text

14 images 14 good alt text

All images have appropriate alt text.

Link & Button Quality

349 links, 4 buttons — all OK

PASS

349 links, 4 buttons — all OK

9 link(s) open in new tab without warning

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

Got: https://www.facebook.com/thousandsmilesuk; https://www.linkedin.com/company/thousandsmilesuk/; #; https://www.instagram.com/thousandsmilesuk; https://thousand-smiles.dentr.net/; https://thousand-smiles.dentr.net/; https://thousand-smiles.dentr.net; https://thousand-smiles.dentr.net; https://thousand-smiles.dentr.net

340 link(s) with descriptive text

349 links

0 empty

0 generic text

9 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/thousandsmilesu…	Visit Thousand Smiles on Faceb…	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/thousan…	Visit Thousand Smiles on Linke…	new tab	Add '(opens in new tab)' to text
#	Visit Thousand Smiles on Twitt…	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/thousandsmiles…	Visit Thousand Smiles on Insta…	new tab	Add '(opens in new tab)' to text
https://thousand-smiles.dentr.net/	Book a consultation	new tab	Add '(opens in new tab)' to text
https://thousand-smiles.dentr.net/	Book Now	new tab	Add '(opens in new tab)' to text
https://thousand-smiles.dentr.net	book a consultation	new tab	Add '(opens in new tab)' to text
https://thousand-smiles.dentr.net	book a consultation	new tab	Add '(opens in new tab)' to text
https://thousand-smiles.dentr.net	book a consultation	new tab	Add '(opens in new tab)' to text

344 links and buttons have descriptive text

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

https://www.facebook.com/thousandsmilesuk; https://www.linkedin.com/company/thousandsmilesuk/; #; https://www.instagram.com/thousandsmilesuk; https://thousand-smiles.dentr.net/; https://thousand-smiles.dentr.net/; https://thousand-smiles.dentr.net; https://thousand-smiles.dentr.net; https://thousand-smiles.dentr.net

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

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

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

6 form control(s) checked, no input-semantic issues

PASS

6 form control(s) checked, no input-semantic issues

All form input semantics look correct

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

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

PASS

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

No tabindex anti-patterns detected

Iframe Accessibility

1/2 iframe(s) missing title; 0 placeholder(s)

PASS

1/2 iframe(s) missing title; 0 placeholder(s)

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.

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 77 visible text node(s) render at >= 12 CSS pixels

PASS

All 77 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.

Lighthouse Accessibility Audits

Score 91/100 — 4 failing, 24 passed

PASS

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
BOOK A CONSULTATION `div.row > div.col-lg-4 > div.btn > a`
BOOK NOW `body.wp-singular > div.float_button > a`
BOOK A CONSULTATION `div.row > div.col-md-5 > div.pqad_btns > a.button`
BOOK A CONSULTATION `div.row > div.col-md-5 > div.pqad_btns > a.button`
020 8050 0280 `div.row > div.col-md-12 > p > a`

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
020 8050 0280 `div.row > div.col-md-12 > p > a`

These are opportunities to improve the legibility of your content.

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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Let's start Start `body.wp-singular > button#botbutton`

○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

●`<frame>` or `<iframe>` elements have a title

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

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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Deprecated ARIA roles were not used

●ARIA IDs are unique

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

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

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