Skip to content
https://engelcoatings.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
79
GRADE
C
FIX
6
REVIEW
2
PASS
16
INFO
0
Checks
24
16 PASS 2 REVIEW 6 FIX
D
Landmark Structure
Action
2 landmarks
FIX
2 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
2 <nav> landmark(s) found
Warning::
1 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
No banner (header) landmark
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 (missing!) NAV "Main" 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

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

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::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
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 2 <nav> element(s)
Back to Top
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.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 - Page not found - Engel Coatings Inc ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
A
Heading Hierarchy
39 headings, 1 skip(s)
PASS
39 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 LAS CRUCES, NM: 575-642-5481
  • H5 Stucco Services skipped
  • H5 Flat Roof Services
  • H5 Painting Services
  • H5 Other Services
  • H2 ENGEL COATINGS INC.
  • H1 Stucco Repair in Las Cruces, NM
  • H2 PROFESSIONAL LAS CRUCES STUCCO CONTRACTOR
  • H3 Careful  Inspections
  • H3 We're  Insured!
  • H3 Quality  Preparations
  • H3 Skilled Stucco Repair, Restoration, & Painting
  • H2 DO YOU HAVE AN ISSUE WITH YOUR STUCCO?
  • H2 Have Stucco Problems?
  • H2 OUR SERVICES
  • H3 STUCCO REPAIR AND RESTORATION
  • H3 EXTERIOR PAINTING
  • H3 INTERIOR PAINTING
  • H3 ROOF COATINGS
  • H3 WINDOW AND DOOR REPLACEMENT
  • H2 AREAS SERVED
  • H3 El Paso, TX
  • H3 Las Cruces, NM
  • H3 Deming, NM
  • H3 Alamogordo, NM
  • H2 why choose engel coatings inc. for your stucco restoration and painting projects?
  • H2 why choose engel coatings inc. for your stucco restoration and painting projects?
  • H2 EXTERIOR REMODELING SERVICES
  • H2 Frequently Asked Questions
  • H2 Frequently Asked Questions
  • H3 What are the benefits of stucco for exterior walls?
  • H3 Can you put new stucco over old stucco?
  • H3 How long does an elastomeric roof coating last?
  • H3 Does stucco help with insulation or energy efficiency?
  • H2 CONTACT US TODAY
  • H3 If you are looking for a Las Cruces Stucco Repair or a Las Cruces Painting Contractor you can:
  • H4 CONTACT
  • H4 QUICK LINKS
  • H4 SERVICE AREAS

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
1 heading-text-quality issue(s) detected
PASS
1 heading-text-quality issue(s) detected
Info::
16 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: 16 all-caps heading(s)
A+
Alt Text Quality
All 84 images OK
PASS
All 84 images OK
Info::
70 decorative image(s) correctly marked
Info::
14 image(s) with good alt text
84 images 14 good alt text 70 decorative
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
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
1 explicit tabindex attribute(s) checked, no anti-patterns
PASS
1 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
All 1 iframe(s) have descriptive titles
PASS
All 1 iframe(s) have descriptive titles
Info::
All 1 iframe(s) have title attributes
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 108 visible text node(s) render at >= 12 CSS pixels
PASS
All 108 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
h1 Stucco Repair in Las…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 ENGEL COATINGS INC.21.00:13.0:1
#000000
#FFFFFF
Pass
h2 PROFESSIONAL LAS CRU…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Have Stucco Problems…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 OUR SERVICES21.00:13.0:1
#000000
#FFFFFF
Pass
h2 AREAS SERVED21.00:13.0:1
#000000
#FFFFFF
Pass
h2 EXTERIOR REMODELING …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Frequently Asked Que…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CONTACT US TODAY21.00:13.0:1
#000000
#FFFFFF
Pass
h3 LAS CRUCES, NM:21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Careful  Inspection…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 We're  Insured!21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Quality  Preparatio…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Skilled Stucco Repai…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 STUCCO REPAIR AND RE…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 EXTERIOR PAINTING21.00:13.0:1
#000000
#FFFFFF
Pass
h3 INTERIOR PAINTING21.00:13.0:1
#000000
#FFFFFF
Pass
h3 ROOF COATINGS21.00:13.0:1
#000000
#FFFFFF
Pass
h3 WINDOW AND DOOR REPL…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 El Paso, TX21.00:13.0: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
Lighthouse Accessibility Audits
Score 90/100 — 2 failing, 13 passed
PASS
90

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
GET A FREE ESTIMATE div.ct-section-inner-wrap > div#div_block-3-14 > div#div_block-6-14 > a#link_button-9-14
CONTACT US FOR A FREE ESTIMATE div.ct-section-inner-wrap > div#div_block-3-11 > div#div_block-8-11 > a#link_button-9-11
LEARN MORE ABOUT US section#section-33-11 > div.ct-section-inner-wrap > div#div_block-34-11 > a#link_button-46-11
Have Stucco Problems? div#div_block-61-11 > div#div_block-62-11 > div#div_block-63-11 > h2#headline-610-11
Let us come out, properly inspect the problem, and give you a free estimate. Ju… div#div_block-61-11 > div#div_block-62-11 > div#div_block-63-11 > div#text_block-71-11
EXPLORE STUCCO REPAIR div.ct-section-inner-wrap > div#div_block-94-11 > div#div_block-95-11 > a#link_button-111-11
EXPLORE EXTERIOR PAINTING div.ct-section-inner-wrap > div#div_block-94-11 > div#div_block-114-11 > a#link_button-118-11
EXPLORE INTERIOR PAINTING div.ct-section-inner-wrap > div#div_block-94-11 > div#div_block-119-11 > a#link_button-123-11
EXPLORE ROOF COATINGS div.ct-section-inner-wrap > div#div_block-94-11 > div#div_block-128-11 > a#link_button-132-11
EXPLORE WINDOWS & DOORS div.ct-section-inner-wrap > div#div_block-94-11 > div#div_block-133-11 > a#link_button-137-11
LEARN MORE ABOUT US div.ct-section-inner-wrap > div#div_block-312-11 > div#div_block-313-11 > a#link_button-339-11
EXPLORE EXTERIOR REMODELING div.ct-section-inner-wrap > div#div_block-263-11 > div#div_block-265-11 > a#link_button-280-11
Disclaimer div.ct-section-inner-wrap > div#div_block-54-14 > div#text_block-55-14 > 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.

○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●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 are distinguishable without relying on color.
●Links have a discernible name
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Identical links have the same purpose.
○`[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 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
○`<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
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback