Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 7 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

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

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.

Favicon & Branding

Action

3 icon(s) detected

FIX

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✓ Manifest Icons Present

✗ Multiple Sizes Missing

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

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 ModePartial Dark Mode

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

2 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 2 <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.

Landmark Structure

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

Link & Button Quality

1 issue(s) across 32 links and 8 buttons

REVIEW

1 issue(s) across 32 links and 8 buttons

2 link(s) open in new tab without warning

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

Got: https://bni.com/; https://moseslakechamber.chambermaster.com/list/member/meisterhoff-associates…

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.md:hidden (#94 on page)

30 link(s) with descriptive text

32 links

0 empty

0 generic text

2 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://bni.com/	BNI	new tab	Add '(opens in new tab)' to text
https://moseslakechamber.chambermaster.c…	Moses Lake Chamber of Commerce…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

37 links and buttons have descriptive text

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

https://bni.com/; https://moseslakechamber.chambermaster.com/list/member/meisterhoff-associates…

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

Icon-only buttons need an aria-label so screen readers can announce them.

button.md:hidden (#94 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Tap Target Adequacy

Action

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

REVIEW

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

4 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.

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (4 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (4 below threshold)

4 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 10.0px ("Professional Disclaimer"); <span> 9.0px ("Associates"); <span> 9.0px ("Associates"); <span> 9.0px ("Associates").

Web Manifest

Valid manifest

REVIEW

Valid manifest

Name present: MeisterHoff & Associates

No 192x192 icon

A 192px icon is required for PWA installation.

512x512 icon present

Display mode: standalone

PWA Install Criteria Not Installable

Name MeisterHoff & Associates ✓192×192 icon ✗512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name MeisterHoff & Associates Display Mode standalone Theme Color #1F3D34 Background Color #F2EFE6 Icons 1 icon(s)

Color Contrast (Screenshot)

Action

20 text elements analyzed, 20 fail WCAG AA

REVIEW

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

0 pass 20 fail WCAG AA

h1 A good bookkeeper

1.65:1

#000000

#20372E

needs 3.0:1 (large text)

32px · mid-page

h2 What a bookkeeper

1.89:1

#000000

#2D4034

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Really good bookkeepers.

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Results worth

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

24px · bottom of viewport

h2 See where your business

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Records every transaction

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Reconciles your accounts

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Tracks invoices & bills

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Runs payroll

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Organizes receipts & expenses

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Prepares financial statements

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Keeps books tax-ready all year

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Catches errors early

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We know our stuff

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We talk plain

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We are there when you need us

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

h3 You will love us

1.48:1

#000000

#2B2B2B

needs 3.0:1 (large text)

19px · bottom of viewport

title Bookkeeping That Changes Everything — …

1.74:1

#000000

#363635

needs 4.5:1 (normal text)

16px · top of page (header area)

div You agree to receive information message…

1.72:1

#000000

#363535

needs 4.5:1 (normal text)

16px · top of page (header area)

span MeisterHoff

1.72:1

#000000

#233A31

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 A good bookkeeper	1.65:1	3.0:1	#000000	#20372E	Fail
h2 What a bookkeeper	1.89:1	3.0:1	#000000	#2D4034	Fail
h2 Really good bookkeep…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h2 Results worth	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h2 See where your busin…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 Records every transa…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 Reconciles your acco…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 Tracks invoices & bi…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 Runs payroll	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 Organizes receipts &…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 Prepares financial s…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 Keeps books tax-read…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 Catches errors early	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 We know our stuff	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 We talk plain	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 We are there when yo…	1.48:1	3.0:1	#000000	#2B2B2B	Fail
h3 You will love us	1.48:1	3.0:1	#000000	#2B2B2B	Fail
title Bookkeeping That Cha…	1.74:1	4.5:1	#000000	#363635	Fail
div You agree to receive…	1.72:1	4.5:1	#000000	#363535	Fail
span MeisterHoff	1.72:1	4.5:1	#000000	#233A31	Fail

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.

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 17 passed

REVIEW

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
THE ROLE `div.max-w-7xl > div.max-w-2xl > div.flex > span.text-bronze`
does for your business `div.max-w-7xl > div.max-w-2xl > h2.font-serif > span.text-honey`
WHY US `div.max-w-7xl > div.max-w-2xl > div.flex > span.text-bronze`
We are good at bookkeeping — and we are good at people. That combination is why… `section.py-24 > div.max-w-7xl > div.max-w-2xl > p.text-foam/50`
Over 25 years in corporate leadership — CEOs, COOs, CFOs, controllers, and acco… `div.max-w-7xl > div.grid > div.border-l-2 > p.text-foam/50`
No jargon, no confusion. We explain your numbers in language you actually under… `div.max-w-7xl > div.grid > div.border-l-2 > p.text-foam/50`
Real people, real answers. We are responsive, reliable, and we treat your busin… `div.max-w-7xl > div.grid > div.border-l-2 > p.text-foam/50`
MeisterHoff & ASSOCIATES may be a new company here in Moses Lake, but our team … `div.max-w-7xl > div.grid > div.border-l-2 > p.text-foam/50`
ASSOCIATES `div.border-l-2 > p.text-foam/50 > span.whitespace-nowrap > span.font-sans`
TWO-YEAR FINANCIAL CLEAN-UP & OPERATIONAL TURNAROUND `div.relative > div.min-h-[280px] > div.w-full > p.text-foam/50`
We keep the books straight, so you can get back to running the business. `div.max-w-7xl > div.grid > div > p.text-foam/40`
— Good Rich Bookkeeping `div.grid > div > div.flex > a.text-taupe/60`
— Business Services Overview `div.grid > div > div.flex > a.text-taupe/60`
accountant@meisterhoff.com `div > div.flex > p > a`
(509) 761-9988 `div > div.flex > p > a`
PO Box 420 Moses Lake, WA 98837 `div.grid > div > div.flex > p`
PROFESSIONAL DISCLAIMER `div.min-h-screen > footer.bg-[#2B2B2B] > div.max-w-7xl > p.text-foam/40`
MeisterHoff & ASSOCIATES provides accounting, bookkeeping, payroll, and executi… `footer.bg-[#2B2B2B] > div.max-w-7xl > div.text-foam/25 > p`
We do help clients answer audits and examinations from state agencies and insur… `footer.bg-[#2B2B2B] > div.max-w-7xl > div.text-foam/25 > p`
Under our active PTIN, we can prepare and sign federal and state tax returns fo… `footer.bg-[#2B2B2B] > div.max-w-7xl > div.text-foam/25 > p`
© 2026 MeisterHoff & ASSOCIATES. All rights reserved. `footer.bg-[#2B2B2B] > div.max-w-7xl > div.flex > p.text-foam/30`
Terms & Conditions `div.max-w-7xl > div.flex > div.flex > a.text-foam/40`
Privacy Policy `div.max-w-7xl > div.flex > div.flex > a.text-foam/40`
Proud Member of `footer.bg-[#2B2B2B] > div.max-w-7xl > div.flex > p.text-foam/40`
Structured Clarity™ `div.min-h-screen > footer.bg-[#2B2B2B] > div.max-w-7xl > span.text-xs`
SERVICES `nav.md:hidden > div.flex > a.flex > span.text-[10px]`
CONTACT `nav.md:hidden > div.flex > a.flex > span.text-[10px]`
BOOK `nav.md:hidden > div.flex > a.flex > span.text-[10px]`

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
NAVIGATION `div.max-w-7xl > div.grid > div > h4.text-xs`

These are opportunities to improve keyboard navigation in your application.

Best practices

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
Go to testimonial 2 `div.relative > div.flex > div.flex > button.h-2`
Go to testimonial 3 `div.relative > div.flex > div.flex > button.h-2`
Go to testimonial 4 `div.relative > div.flex > div.flex > button.h-2`
Go to testimonial 5 `div.relative > div.flex > div.flex > button.h-2`

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

●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.

●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 have a discernible name

●No element has a `[tabindex]` value greater than 0

●Document has a main landmark.

●Elements with visible text labels have matching accessible names.

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

○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

○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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○Identical links have the same purpose.

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

Heading Hierarchy

19 headings, 1 skip(s)

PASS

19 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

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

H1 A good bookkeeperchanges everything.
H2 What a bookkeeper does for your business
H3 Records every transaction
H3 Reconciles your accounts
H3 Tracks invoices & bills
H3 Runs payroll
H3 Organizes receipts & expenses
H3 Prepares financial statements
H3 Keeps books tax-ready all year
H3 Catches errors early
H2 Really good bookkeepers. You will love us.
H3 We know our stuff
H3 We talk plain
H3 We are there when you need us
H3 You will love us
H2 Results worth talking about.
H2 See where your businessactually stands.
H4 Navigation skipped
H4 Get in Touch

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

All 19 heading(s) have substantive, well-formed text

PASS

All 19 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 6 images OK

PASS

All 6 images OK

6 image(s) with good alt text

6 images 6 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

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

A+

Form Input Quality

No form controls on this page

PASS

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

No form controls on this page

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

2 explicit tabindex attribute(s) checked, no anti-patterns

PASS

2 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

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