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 5 REVIEW 5 FIX

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

1 navigation landmark(s) detected

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

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.

Lighthouse Accessibility Audits

Action

Score 52/100 — 7 failing, 7 passed

FIX

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
210.920.8481 `div#top-header > div.container > div#et-info > span#et-info-phone`
infovilladental@gmail.com `div.container > div#et-info > a > span#et-info-email`
Want a Straighter Smile? `div.et_pb_slider_container_inner > div.et_pb_slide_description > h2.et_pb_slide_title > a`
Learn About Invisalign Today `div.et_pb_slider_container_inner > div.et_pb_slide_description > div.et_pb_button_wrapper > a.et_pb_button`
Request an Appointment for Dental Services in San Antonio, TX `div.et_pb_module > div.et_pb_text_inner > h2 > span`
Villa Dental is a provider for the most popular insurance companies. `div.et_pb_fullwidth_header_container > div.header-content-container > div.header-content > h2.et_pb_module_header`
Don't see your insurance here? Give us a call! `div.et_pb_fullwidth_header_container > div.header-content-container > div.header-content > span.et_pb_fullwidth_header_subhead`
Call Villa Dental to Learn More `div.et_pb_fullwidth_header_container > div.header-content-container > div.header-content > a.et_pb_button`
What Our Customers Are Saying `div.et_pb_module > div.et_pb_text_inner > span > span`
Look No Further. `div.et_pb_promo_description > div > p > span`
Contact Us Today `div.et_pb_promo_description > div > p > span`
Contact Villa Dental `div.et_pb_column > div.et_pb_module > div.et_pb_button_wrapper > a.et_pb_button`
© Copyright - Villa Dental 2019 \| General Dentist \| Family Dentist \| San Antoni… `footer#main-footer > div#footer-bottom > div.container > div#footer-info`

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
Our team `div.et_pb_module > div.et_pb_text_inner > p > a`
dental care `div.et_pb_module > div.et_pb_text_inner > p > 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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
About Villa Dental `div.et_pb_module > div.et_pb_blurb_content > div.et_pb_blurb_container > h4.et_pb_module_header`
Contact Villa Dental `div#footer-widgets > div.footer-widget > div#text-7 > h4.title`

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.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.et_pb_section > div.et_pb_module > div.et-pb-slider-arrows > a.et-pb-arrow-prev `div.et_pb_section > div.et_pb_module > div.et-pb-slider-arrows > a.et-pb-arrow-prev`
div.et_pb_section > div.et_pb_module > div.et-pb-slider-arrows > a.et-pb-arrow-next `div.et_pb_section > div.et_pb_module > div.et-pb-slider-arrows > a.et-pb-arrow-next`
div.et_pb_module > div.et_pb_portfolio_items > div.et-pb-slider-arrows > a.et-pb-arrow-prev `div.et_pb_module > div.et_pb_portfolio_items > div.et-pb-slider-arrows > a.et-pb-arrow-prev`
div.et_pb_module > div.et_pb_portfolio_items > div.et-pb-slider-arrows > a.et-pb-arrow-next `div.et_pb_module > div.et_pb_portfolio_items > div.et-pb-slider-arrows > a.et-pb-arrow-next`
div#post-6679 > div.et_pb_portfolio_image > div.meta > a `div#post-6679 > div.et_pb_portfolio_image > div.meta > 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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
1 `div.et_pb_section > div.et_pb_module > div.et-pb-controllers > a.et-pb-active-control`
2 `div.et_pb_section > div.et_pb_module > div.et-pb-controllers > a`
3 `div.et_pb_section > div.et_pb_module > div.et-pb-controllers > a`

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.js `html.js`

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

●Image elements have `[alt]` attributes

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

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

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○`[aria-hidden="true"]` elements do not contain focusable descendents

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements use only permitted ARIA attributes

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

○`[aria-*]` attributes have valid values

○`[aria-*]` attributes are valid and not misspelled

○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

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

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

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

○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

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

○`<td>` elements in a large `<table>` have one or more table headers.

Landmark Structure

Action

3 landmarks

REVIEW

3 landmarks

No <main> landmark found

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

1 <nav> landmark(s) found

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

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

Heading Hierarchy

27 headings, 2 skip(s)

REVIEW

27 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H2 → H4 (missing H3)

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

H2 Want a Straighter Smile?
H2 Need a Pediatric Dentist?
H2 A Family Dentist
H1 Villa Dental is Your Extraordinary Home for Family Dentistry!
H4 About Villa Dental skipped
H4 Dental Services
H4 Contact Villa Dental
H2 Request an Appointment for Dental Services in San Antonio, TX
H2 Villa Dental is a provider for the most popular insurance companies.
H3 Tricare
H3 Metlife
H3 Humana
H3 Guardian
H3 Delta Dental
H3 Cigna
H3 Boon Chapman
H3 Blue Cross Blue Shield
H3 Assurant
H3 Ameritas
H3 Aetna
H3 United Healthcare
H3 MCNA
H3 Dentequest
H3 United Concordia
H2 About Us
H4 Contact Villa Dental skipped
H4 Villa Dental Office Hours

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Tap Target Adequacy

3 tap target(s) too small or too close together

REVIEW

3 tap target(s) too small or too close together

3 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Favicon & Branding

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 16 fail WCAG AA

REVIEW

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

4 pass 16 fail WCAG AA

h2 Villa Dental is a provider for the most …

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Tricare

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Metlife

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Humana

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Guardian

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Delta Dental

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cigna

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Boon Chapman

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Blue Cross Blue Shield

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Assurant

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Ameritas

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Aetna

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 United Healthcare

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 MCNA

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Dentequest

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 United Concordia

1.60:1

#000000

#27323A

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Villa Dental is a pr…	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Tricare	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Metlife	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Humana	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Guardian	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Delta Dental	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Cigna	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Boon Chapman	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Blue Cross Blue Shie…	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Assurant	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Ameritas	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Aetna	1.60:1	3.0:1	#000000	#27323A	Fail
h3 United Healthcare	1.60:1	3.0:1	#000000	#27323A	Fail
h3 MCNA	1.60:1	3.0:1	#000000	#27323A	Fail
h3 Dentequest	1.60:1	3.0:1	#000000	#27323A	Fail
h3 United Concordia	1.60:1	3.0:1	#000000	#27323A	Fail
title A Family Dentistry \|…	7.64:1	4.5:1	#000000	#2EA3F2	Pass
span 210.920.8481	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span infovilladental@gmai…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	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 Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 1 all-caps heading(s)

A+

Alt Text Quality

All 30 images OK

PASS

All 30 images OK

3 decorative image(s) correctly marked

27 image(s) with good alt text

30 images 27 good alt text 3 decorative

All images have appropriate alt text.

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search" name="s">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
s	search	(Search …)	placeholder only

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

Link & Button Quality

91 links, 0 buttons — all OK

PASS

91 links, 0 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://www.google.com/maps/contrib/111580059433134021862/reviews/@29.4291222…; https://www.google.com/maps/contrib/111897390295511549771/reviews; https://www.google.com/maps/contrib/108887378343000002989/reviews/@29.4291222…

88 link(s) with descriptive text

91 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.google.com/maps/contrib/1115…	Diana Martinez	new tab	Add '(opens in new tab)' to text
https://www.google.com/maps/contrib/1118…	Shane Hopkins	new tab	Add '(opens in new tab)' to text
https://www.google.com/maps/contrib/1088…	Travis Gloeckler	new tab	Add '(opens in new tab)' to text

88 links and buttons have descriptive text

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

https://www.google.com/maps/contrib/111580059433134021862/reviews/@29.4291222…; https://www.google.com/maps/contrib/111897390295511549771/reviews; https://www.google.com/maps/contrib/108887378343000002989/reviews/@29.4291222…

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 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

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

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

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"

<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

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Mobile-Readable Font Sizes

All 63 visible text node(s) render at >= 12 CSS pixels

PASS

All 63 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

404 Error Page

HTTP 404, custom page

PASS

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

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Villa Dental ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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.

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