Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction8 landmarksFIX
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
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.
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.
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
DForm AccessibilityAction6 of 6 controls have issuesFIX
| Control | Type | Label | Method |
|---|---|---|---|
| fname | text | (Full Name) | placeholder only |
| email-939 | (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.
<input type="submit">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
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="fname">; <input type="email" name="email-939">; <input type="text" name="phone">; <textarea name="textarea-427">
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
DMobile Keyboard & AutofillAction2/2 eligible field(s) missing autocomplete or inputmodeFIX
FFavicon & BrandingAction1 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy7 headings, 2 skip(s)REVIEW
- H5 Call Us:
- H5 Mail Us:
- H1 Composite Veneer & Bonding Cost London, UK
- H3 Treatments skipped
- 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.
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.
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
B404 Error PageHTTP 404, custom pageREVIEW
CColor Contrast (Screenshot)Action20 text elements analyzed, 1 fail WCAG AAREVIEW
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Composite Veneer & B… | 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 Composite Veneers Co… | 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… | 14.38:1 | 4.5:1 | #000000 | #D4D6D5 | Pass |
| a Home | 12.62:1 | 4.5:1 | #000000 | #C7C9C8 | Pass |
| a Emergency Dentist | 12.55:1 | 4.5:1 | #000000 | #C8C8C8 | Pass |
| a Tooth Pain | 12.04:1 | 4.5:1 | #000000 | #C4C4C4 | Pass |
| a Broken Tooth | 12.64:1 | 4.5:1 | #000000 | #C8C9C8 | Pass |
| a Loose Filling | 12.01:1 | 4.5:1 | #000000 | #C3C4C4 | Pass |
| a Dental Infection | 7.01:1 | 4.5:1 | #000000 | #959595 | Pass |
| a Dental Trauma | 15.02:1 | 4.5:1 | #000000 | #DADADA | Pass |
| a Treatments | 10.68:1 | 4.5:1 | #000000 | #C4B89B | Pass |
| a GENERAL | 6.15:1 | 4.5:1 | #000000 | #9D8958 | Pass |
| a Dental Examination | 6.15:1 | 4.5:1 | #000000 | #9D8958 | Pass |
| a Dental Hygiene | 6.15:1 | 4.5:1 | #000000 | #9D8958 | Pass |
| a Periodontics | 6.15:1 | 4.5:1 | #000000 | #9D8958 | Pass |
| a Root Canal Treatment | 21.00:1 | 4.5: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.
A+Heading Text QualityAll 7 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityAll 10 images OKPASS
ALink & Button Quality342 links, 4 buttons — all OKPASS
| 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 |
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/
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 Types1 input(s) using type=text where a specific type would helpPASS
A+Form Input Quality6 form control(s) checked, no input-semantic issuesPASS
A+Document LanguageLang attribute set to "en-GB"PASS
A+Tabindex Anti-Patterns2 explicit tabindex attribute(s) checked, no anti-patternsPASS
AIframe Accessibility1/2 iframe(s) missing title; 0 placeholder(s)PASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 67 visible text node(s) render at >= 12 CSS pixelsPASS
A+PWA DepthNo PWA depth issues detectedPASS
A+Mobile UX Depth1 mobile-depth signal(s) detectedPASS
ALighthouse Accessibility AuditsScore 93/100 — 4 failing, 24 passedPASS
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.
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 |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Treatments div.row > div.col-lg-3 > section#nav_menu-2 > h3.widget-title |
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.
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
Let's start
Start body.wp-singular > button#botbutton |