Skip to content
https://dentalkochi.in

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
71
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 FIX
F
Heading Hierarchy
Action
32 headings, 4 skip(s)
FIX
32 headings, 4 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
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: H3 → H6 (missing H4)
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.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Dental Services
  • H4 Expert Doctors skipped
  • H4 20 Years of Experience
  • H4 Latest Technologies
  • H4 Quality Care
  • H3 Trusted Dental Clinic in Kochi Since 1975
  • H3 Services At Our Clinic
  • H3 Tooth Jewels
  • H3 Biomimetic Dentistry
  • H3 Laser Dental Treatment
  • H6 Anita Singh skipped
  • H6 Yedhu Raj
  • H6 Sangeetha Bishnoi
  • H6 Parvathy R S
  • H6 Densil Meyn
  • H3 Need Help? CALL US
  • H3 Latest Dental News
  • H3 Your Trusted Partner in Oral Health
  • H3 Discover the Finest Dental Care with the Best Dentist in Kochi
  • H3 Your Trusted Partner in Oral Health
  • H3 Discover the Finest Dental Care with the Best Dentist in Kochi
  • H3 Welcome to the Premier Dental Clinic in Kochi
  • H3 Book an Appointment
  • H3 Or call us now
  • H3 9446026708 0484-4046708
  • H2 Our Treatments
  • H4 Contact US skipped
  • H4 Locate Us
  • H6 Email: drajithatsomans@gmail.com skipped
  • H6 09446026708
  • H6 +91 8075 301 869
  • H3 Contact Form

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

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

F
Form Accessibility
Action
10 of 11 controls have issues
FIX
10 of 11 controls have issues
Critical::
5 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="tel" name="yout-phone">; <input type="text" name="your-service-requested">; <input type="text" name="time-request">; <input type="submit">; <input type="submit" name="contact-form-submit" id="stickyelements-submit-form">
Warning::
5 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="your-name">; <input type="text" name="contact-form-name" id="contact-form-name">; <input type="tel" name="contact-form-phone" id="contact-form-phone">; <input type="email" name="contact-form-email" id="contact-form-email">; <textarea name="contact-form-message" id="contact-form-message">
Info::
1 control(s) properly labeled
11 controls
1 labeled
5 placeholder only
5 unlabeled
ControlTypeLabelMethod
ssearchSearch for:none
your-nametext(e.g., Jonh Doe)placeholder only
#contact-form-nametext(Name*)placeholder only
#contact-form-phonetel(Phone*)placeholder only
#contact-form-emailemail(Email*)placeholder only
#contact-form-messagetextarea(Message*)placeholder only
your-service-requestedtext(none)none
time-requesttext(none)none
inputsubmit(none)none
yout-phonetel(none)none
#stickyelements-submit-formsubmit(none)none

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

<input type="tel" name="yout-phone">; <input type="text" name="your-service-requested">; <input type="text" name="time-request">; <input type="submit">; <input type="submit" name="contact-form-submit" id="stickyelements-submit-form">

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="your-name">; <input type="text" name="contact-form-name" id="contact-form-name">; <input type="tel" name="contact-form-phone" id="contact-form-phone">; <input type="email" name="contact-form-email" id="contact-form-email">; <textarea name="contact-form-message" id="contact-form-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
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

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::
1 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 1 <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.
C
Landmark Structure
Action
3 landmarks
REVIEW
3 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No contentinfo (footer) landmark
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 (missing!)

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

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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Apple touch icon present
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 19 passed
REVIEW
80

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
Our Treatments div.wpb_wrapper > div#tm-better-custom-menu-6aed41076ee1e > div.widget > h2.widgettitle
K2web Solutions div#tm-heading-6aed4107836d3 > div.heading > a > mark

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control
div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control
div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control div.col-md-6 > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control

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.wpb_wrapper > div.wpb_raw_code > div.wpb_wrapper > iframe.lazyload div.wpb_wrapper > div.wpb_raw_code > div.wpb_wrapper > iframe.lazyload

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
li#mystickyelements-contact-form > div.element-contact-form > h3 > a.element-contact-close li#mystickyelements-contact-form > div.element-contact-form > h3 > a.element-contact-close
ul.mystickyelements-lists > li#mystickyelements-social-whatsapp > span.mystickyelements-social-icon > a ul.mystickyelements-lists > li#mystickyelements-social-whatsapp > span.mystickyelements-social-icon > a
ul.mystickyelements-lists > li#mystickyelements-social-phone > span.mystickyelements-social-icon > a ul.mystickyelements-lists > li#mystickyelements-social-phone > span.mystickyelements-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.

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
Expert Doctors div.content-wrap > div.content > div.box-header > h4.heading
Anita Singh div.testimonial-item > div.testimonial-info > div.testimonial-main-info > h6.testimonial-name
Contact US div.vc_column-inner > div.wpb_wrapper > div#tm-heading-6aed410781f04 > h4.heading
Email: drajithatsomans@gmail.com div.list-item > div.list-header > div.title-wrap > h6.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.

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-*]` attributes match their roles
●`[aria-hidden="true"]` is not present on the document `<body>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●Input buttons have discernible text.
●`[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
●`<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
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[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
○`[role]` values are valid
○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
○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
○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
○`<input type="image">` elements have `[alt]` text
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○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.
○`<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.
○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 32 heading(s) have substantive, well-formed text
PASS
All 32 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
1 of 21 images have issues
PASS
1 of 21 images have issues
Warning::
1 image(s) with generic alt text
Info::
1 decorative image(s) correctly marked
Info::
19 image(s) with good alt text
21 images 19 good alt text 1 decorative 1 generic
IssueCount
generic1 image(s)
A+
Form Input Types
11 form control(s) checked, no type mismatches
PASS
11 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
11 form control(s) checked, no input-semantic issues
PASS
11 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en-US"
PASS
Lang attribute set to "en-US"
Info::
<html lang="en-US"> is set and valid
Got: en-US
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="data:image/svg+xml;base64,PHN2ZyB3aWR0aD0iMSIgaGVpZ2h0PSIxIiB4bWxucz0iaHR0cDovL…")
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 98 visible text node(s) render at >= 12 CSS pixels
PASS
All 98 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.
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Dental Services21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Our Treatments21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Trusted Dental Clini…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Services At Our Clin…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Need Help? CALL US21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Latest Dental News21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Book an Appointment21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Or call us now21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Contact Form4.61:13.0:1
#7761DF
#FFFFFF
Pass
title Dental Services - Dr…21.00:14.5:1
#000000
#FFFFFF
Pass
span CALL FOR APPOINTMENT21.00:14.5:1
#000000
#FFFFFF
Pass
div +91 94460 2670821.00:14.5:1
#000000
#FFFFFF
Pass
div +91 8075 301 86921.00:14.5:1
#000000
#FFFFFF
Pass
span drajithatsomans@gmai…21.00:14.5:1
#000000
#FFFFFF
Pass
span Home21.00:14.5:1
#000000
#FFFFFF
Pass
span About us21.00:14.5:1
#000000
#FFFFFF
Pass
span Our Doctors21.00:14.5:1
#000000
#FFFFFF
Pass
span Our Treatments21.00:14.5:1
#000000
#FFFFFF
Pass
span Dental Tourism21.00:14.5:1
#000000
#FFFFFF
Pass
span Gallery21.00:14.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.

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

Send Feedback