Accessibility
· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.DLandmark StructureAction4 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
F404 Error PageActionSoft 404 detectedFIX
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.
FFavicon & BrandingAction1 icon(s) detectedFIX
FWeb ManifestActionInvalid JSONFIX
Manifest contains invalid JSON.
DDark Mode SupportActionNo dark mode signalsFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BHeading Hierarchy23 headings, 2 skip(s)REVIEW
- H1 Composite Bonding London
- H2 Transform Your Smile with Latest Composite Bonding Deals & Offers
- H2 Why Choose Composite Bonding London?
- H2 Expert Dental Artisans:
- H2 Advanced Techniques & Technology:
- H2 Comfort-First Experience:
- H2 Tailored Solutions for Every Smile:
- H2 Benefits of Composite Bonding in London
- H4 Immediate Results: skipped
- H4 Minimally Invasive:
- H4 Cost-Effective Enhancement:
- H4 Long-Lasting Outcomes:
- H2 Procedure of Composite Bonding Treatment
- H2 Ready to Elevate Your Smile with our Composite bonding Package?
- H2 How Much Does Composite Bonding Cost in London?
- H5 Package 1: Composite Edge Bonding Full Mouth (16 teeth) skipped
- H5 Package 2: Composite Edge Bonding single Arch (8 teeth)
- H5 Package 3: Composite Veneers Full Mouth (16 teeth)
- H5 Package 4: Composite Veneers Single Arch (8 teeth)
- H5 Package 5: Composite Edge Bonding (Single tooth)
- H5 Package 6: Composite Veneer (Single tooth)
- H2 Questions About Composite Bonding
- H2 Book Your Free Composite Bonding Consultation Today
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
CLink & Button QualityAction6 issue(s) across 33 links and 3 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| tel:02030516447 | 020 3051 6447 | img no alt | Add alt attribute to the image |
| # | (empty) | empty | Add link text or aria-label |
| tel:02030516447 | 020 3051 6447 | img no alt | Add alt attribute to the image |
| https://thousand-smiles.dentr.net/ | Book An Appointment | new tab | Add '(opens in new tab)' to text |
| https://thousand-smiles.dentr.net/ | Thousand Smiles Group | new tab | Add '(opens in new tab)' to text |
| https://thousand-smiles.dentr.net/ | Book An Appointment | new tab | Add '(opens in new tab)' to text |
| https://thousand-smiles.dentr.net/ | Book Your Free Consultation To… | new tab | Add '(opens in new tab)' to text |
| tel:02030516447 | (empty) | empty | Add link text or aria-label |
| mailto:hello@compositebonding.london | (empty) | empty | Add link text or aria-label |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label | |
| (empty) | empty | Add link text or aria-label |
Links without text are announced as raw URLs by screen readers.
#; tel:02030516447; mailto:hello@compositebonding.london; a (#374 on page); a.ftr-twitter (#376 on page); a.ftr-linkedin (#378 on page)
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
Add '(opens in new tab)' to link text or aria-label.
https://thousand-smiles.dentr.net/; https://thousand-smiles.dentr.net/; 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
BLighthouse Accessibility AuditsScore 89/100 — 4 failing, 21 passedREVIEW
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 |
|---|
Thousand Smiles Group div.tyswcb-london-content > p > strong > a |
Book An Appointment div.container > div.ready-to-elevate > div.dilBtn-row > a.btn |
full mouth bonding div.benfts-cmpst-bndg-content > p > a > strong |
Package 1: div.pckofrsSec > div.pkgebx > h5 > span |
Package 2: div.pckofrsSec > div.pkgebx > h5 > span |
Package 3: div.pckofrsSec > div.pkgebx > h5 > span |
Package 4: div.pckofrsSec > div.pkgebx > h5 > span |
Package 5: div.pckofrsSec > div.pkgebx > h5 > span |
Package 6: div.pckofrsSec > div.pkgebx > h5 > span |
Book Your Free Consultation Today div.col-md-6 > div.bkyfre-cnslt-todya > div.dilBtn-row > a.btn |
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 |
|---|
Immediate Results: div.benfts-cmpst-bndg-content > ul.benfts-cmpst-list > li > h4 |
Package 1:
Composite Edge Bonding Full Mouth (16 teeth) div.container- > div.pckofrsSec > div.pkgebx > h5 |
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.
Performance issues directly impact user engagement and conversion rates.
| Failing Elements |
|---|
header#header > div.container > div.topHeader > a.btn header#header > div.container > div.topHeader > a.btn |
div.col-md-4 > div.ftr-info-list > div.ftr-icon > a div.col-md-4 > div.ftr-info-list > div.ftr-icon > a |
div.col-md-4 > div.ftr-info-list > div.ftr-icon > a div.col-md-4 > div.ftr-info-list > div.ftr-icon > a |
div.container > div.ftr__social__link > div.top-link > a div.container > div.ftr__social__link > div.top-link > a |
div.container > div.ftr__social__link > div.top-link > a.ftr-twitter div.container > div.ftr__social__link > div.top-link > a.ftr-twitter |
div.container > div.ftr__social__link > div.top-link > a.ftr-linkedin div.container > div.ftr__social__link > div.top-link > 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.
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.
A+Heading Text QualityAll 23 heading(s) have substantive, well-formed textPASS
A+Alt Text QualityAll 17 images OKPASS
A+Form AccessibilityNo form controlsPASS
A+Form Input TypesNo form controls on this pagePASS
A+Form Input QualityNo form controls on this pagePASS
A+Mobile Keyboard & AutofillNo form controls -- mobile keyboard check is N/APASS
A+Document LanguageLang attribute set to "en-GB"PASS
A+Tabindex Anti-Patterns1 explicit tabindex attribute(s) checked, no anti-patternsPASS
A+Iframe AccessibilityNo iframes on this pagePASS
A+Tap Target AdequacyAll tap targets meet WCAG 2.5.5/2.5.8 sizingPASS
A+Mobile-Readable Font SizesAll 140 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
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
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 London | 18.90:1 | 3.0:1 | #000000 | #F7F2EF | Pass |
| h2 Transform Your Smil… | 20.18:1 | 3.0:1 | #000000 | #FCFAF9 | Pass |
| h2 Deals & Offers | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Why Choose | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 London? | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Expert Dental Artisa… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Advanced Techniques … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Comfort-First Experi… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Tailored Solutions f… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Benefits of | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 in London | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Procedure of | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Treatment | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Ready to Elevate You… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 How Much Does | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Cost in London? | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Questions About | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Bonding | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Book Your Free Compo… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Composite Bonding Lo… | 18.90:1 | 4.5:1 | #000000 | #F7F2EF | 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.