Skip to content
https://lagunatools.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
76
GRADE
C
FIX
6
REVIEW
4
PASS
14
INFO
0
Checks
24
14 PASS 4 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-iugwqn
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

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.

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
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
6 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 6 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
C
Landmark Structure
Action
19 landmarks
REVIEW
19 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
6 <nav> landmark(s) found
Warning::
2 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) CONTENTINFO footer

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

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

B
Alt Text Quality
16 of 82 images have issues
REVIEW
16 of 82 images have issues
Warning::
16 image(s) with filename as alt text
Info::
1 decorative image(s) correctly marked
Info::
65 image(s) with good alt text
82 images 65 good alt text 1 decorative 16 generic
IssueCount
filename16 image(s)
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
B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 30 passed
REVIEW
88

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
// AUTOMATED IQ SERIES Big Performance with a Small Footprint for only $15,495 … div#e-n-tab-content-1640652571 > div.elementor-element > div.elementor-widget-container > div.swiper
The did a great job on the SmartShop 2 Elite. It cuts a lot of parts! Ryan Jepp… div.elementor-element > div.elementor-element > div.elementor-widget-container > div.swiper
Hugh Saffel August 6, 2025, 6:47 pm I bought a Laguna 15/24 lathe about 2 year… div.elementor-element > div.elementor-element > div.elementor-widget-container > div.swiper

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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 Quote div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
CUSTOMER SERVICE div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Join Our Email List div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Accept All div#wpconsent-banner-holder > div.wpconsent-banner > div.wpconsent-banner-footer > button#wpconsent-accept-all
Reject div#wpconsent-banner-holder > div.wpconsent-banner > div.wpconsent-banner-footer > button#wpconsent-cancel-all

These are opportunities to improve the legibility of your content.

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.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon div.elementor-element > div.elementor-widget-container > div.elementor-icon-wrapper > a.elementor-icon

Including a skip link can help users skip to the main content to save time. Learn more about skip links.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Skip to content body.home > a.skip-link

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.

○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>`
●`[role]`s have all required `[aria-*]` attributes
●`[role]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●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.
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○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
○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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
○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 Hierarchy
98 headings
PASS
98 headings
Warning::
Multiple H1 headings (2 found)
A page should have only one H1. Multiple H1s dilute the document outline.
  • H2 Automated Machinery
  • H2 Industrial Machinery
  • H2 Classic Machinery
  • H2 Metal Machinery
  • H2 Application
  • H2 Laguna Care
  • H2 Warranty Registration
  • H2 Resaw King Blade Resharpening
  • H2 Financing
  • H2 Blog
  • H2 Events
  • H2 Laguna Outlet
  • H2 Product Manuals
  • H2 CNC Software
  • H2 About Us
  • H2 Customer Stories
  • H2 School Programs
  • H2 Careers
  • H2 Automated Machinery
  • H2 Industrial Machinery
  • H2 Classic Machinery
  • H2 Metal Machinery
  • H2 Application
  • H2 Laguna Care
  • H2 Warranty Registration
  • H2 Resaw King Blade Resharpening
  • H2 Financing
  • H2 Blog
  • H2 Events
  • H2 CNC Resources & Education
  • H2 Product Manuals
  • H2 CNC Software
  • H2 About Us
  • H2 Customer Stories
  • H2 School Programs
  • H2 Careers
  • H2 Automated Machinery
  • H2 Industrial Machinery
  • H2 Classic Machinery
  • H2 Metal Machinery
  • H2 Application
  • H2 Laguna Care
  • H2 Warranty Registration
  • H2 Resaw King Blade Resharpening
  • H2 Financing
  • H2 Blog
  • H2 Events
  • H2 Laguna Outlet
  • H2 Product Manuals
  • H2 CNC Software
  • H2 About Us
  • H2 Customer Stories
  • H2 School Programs
  • H2 Careers
  • H2 Automated Machinery
  • H2 Industrial Machinery
  • H2 Classic Machinery
  • H2 Metal Machinery
  • H2 Application
  • H2 Laguna Care
  • H2 Warranty Registration
  • H2 Resaw King Blade Resharpening
  • H2 Financing
  • H2 Blog
  • H2 Events
  • H2 CNC Resources & Education
  • H2 Product Manuals
  • H2 CNC Software
  • H2 About Us
  • H2 Customer Stories
  • H2 School Programs
  • H2 Careers
  • H2 Flexible financing available - get the tools you need today!
  • H2 Laguna Tools Fall Savings Are in Full Swing! Get 10% off Classic & Metal Machines And Accessories
  • H1 Precision CNC Machines And Equipment For Every Job
  • H2 Laguna Tools goes beyond machinery—we’re your partner when precision, productivity and creativity are the goals. Whether you’re a first-time builder or an industry leader, our CNC routers and eq
  • H2 OCT 21 - 23 BOOTH #C1551
  • H2 Your Metalworking Upgrade is ready
  • H2 FABTECH Specials are live on metalworking machinery, including Dake. Unlock special pricing to see what you can save.
  • H2 10% OFF
  • H2 ALL CLASSIC & METAL MACHINES AND ACCESSORIES*
  • H2 PROMO ENDS 10.31
  • H1 Precision CNC Machines And Equipment For Every Job duplicate H1
  • H2 Laguna Tools goes beyond machinery—we’re your partner when precision, productivity and creativity are the goals. Whether you’re a first-time builder or an industry leader, our CNC routers and eq
  • H2 OCT 21 - 23 BOOTH #C1551
  • H2 Your Metalworking Upgrade is ready
  • H2 FABTECH Specials are live on metalworking machinery, including Dake. Unlock special pricing to see what you can save.
  • H2 Sign Making
  • H2 Education
  • H2 Metalworking
  • H2 Woodworking
  • H2 Furniture Making
  • H2 Cabinet Making
  • H2 Sign Making
  • H2 Education
  • H2 Metalworking
  • H2 Woodworking
  • H2 Flexible Financing Available

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A
Heading Text Quality
2 heading-text-quality issue(s) detected
PASS
2 heading-text-quality issue(s) detected
Warning::
2 heading(s) are over 120 characters -- likely a misformatted paragraph
Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 194 chars - H2: 194 chars
Got: 2 >120-char heading(s)
Info::
5 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: 5 all-caps heading(s)
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#ysm-smart-search-1-6adf19333d7b0searchSearch...none
#ysm-smart-search-1-6adf19333d7b0searchSearch...none
A+
Form Input Types
2 form control(s) checked, no type mismatches
PASS
2 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
2 form control(s) checked, no input-semantic issues
PASS
2 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
0 positive, 3 -1-on-focusable
PASS
0 positive, 3 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1640652572">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1640652573">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <button id="e-n-tab-title-1640652574">
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
A+
Iframe Accessibility
All 3 iframe(s) have descriptive titles
PASS
All 3 iframe(s) have descriptive titles
Info::
All 3 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 6 visible text node(s) render at >= 12 CSS pixels
PASS
All 6 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 Precision CNC Machin…21.00:13.0:1
#000000
#FFFFFF
Pass
h1 Precision CNC Machin…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Application21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Laguna Care21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Warranty Registratio…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Resaw King Blade Res…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Financing21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Blog21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Events21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Laguna Outlet21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Product Manuals21.00:13.0:1
#000000
#FFFFFF
Pass
h2 CNC Software21.00:13.0:1
#000000
#FFFFFF
Pass
h2 About Us21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Customer Stories21.00:13.0:1
#000000
#FFFFFF
Pass
h2 School Programs21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Careers21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Application21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Application21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Laguna Care21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Warranty Registratio…21.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.

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

Send Feedback