Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

17 PASS 4 REVIEW 3 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-knkpco

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.

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

Hamburger menu detected (responsive design)

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)

2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

6 landmarks

REVIEW

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

No banner (header) landmark

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

3 issue(s) across 41 links and 12 buttons

REVIEW

3 issue(s) across 41 links and 12 buttons

1 link(s) open in new tab without warning

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

Got: mailto:Feng Shui Bedroom <support@fengshuibedroom.app>

3 button(s) with no accessible text

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

Got: button.peer (#194 on page); button.peer (#197 on page); button.peer (#203 on page)

40 link(s) with descriptive text

41 links

0 empty

0 generic text

1 new tab

3 empty buttons

Element	Text	Issue	Suggested Fix
mailto:Feng Shui Bedroom <support@fengsh…	Email	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

49 links and buttons have descriptive text

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

mailto:Feng Shui Bedroom <support@fengshuibedroom.app>

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.peer (#194 on page); button.peer (#197 on page); button.peer (#203 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

Favicon & Branding

6 icon(s) detected

REVIEW

6 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 Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

A+

Heading Hierarchy

52 headings

PASS

52 headings

Single H1 present

H1 Feng Shui Bedroom Analyzer: Check Your Bedroom Layout From One Photo
H2 Feng shui bedroom analyzer
H2 Instant bedroom layout clarity
H2 How it works
H3 Upload a photo
H3 Confirm what we see
H3 Get your report
H3 Save and compare
H2 Sample report: before and after
H3 Before
H3 After the suggested changes
H2 Five feng shui tools in one place
H3 Bedroom photo analyzer
H3 Kua number calculator
H3 Wealth corner finder
H3 Front door check
H3 Flying star chart
H2 What we check
H2 What is a feng shui bedroom check?
H2 Why your bedroom layout matters
H2 Methodology you can check
H3 Rule-based, then explained
H3 No invented data
H3 Privacy by default
H3 No promises about luck
H2 Who uses Feng Shui Bedroom
H3 Renters
H3 Moving into a new home
H3 Small bedrooms and studios
H3 Couples’ bedrooms
H3 Interior designers & stagers
H3 Curious beginners
H2 Example scenarios
H2 Simple credit pricing
H3 Free trial
H3 Credit pack
H3 Monthly
H3 Yearly
H2 Feng shui bedroom FAQ
H3 What is the best bed position in feng shui?
H3 How does the AI bedroom analyzer work?
H3 Is it free?
H3 What photo should I upload?
H3 I rent and can’t move furniture. Is it still useful?
H3 Is a mirror facing the bed bad feng shui?
H3 Do you promise better sleep, health or money?
H3 What happens to my photos?
H2 From the feng shui bedroom blog
H3 Bed Placement Feng Shui: How to Find the Commanding Position in Any Bedroom
H3 Bedroom Feng Shui Colors: How to Choose Calm, Restful Tones
H3 Feng Shui Bedroom Checklist: 12 Layout Rules You Can Check Tonight
H2 Ready to check your bedroom?

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 9 images OK

PASS

All 9 images OK

1 image(s) with alt text over 125 characters

8 image(s) with good alt text

9 images 8 good alt text

Issue	Count
too long	1 image(s)

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

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

Got: <input type="file">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
input	file	(none)	none

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

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

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"

PASS

Lang attribute set to "en"

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

Got: en

A+

Tabindex Anti-Patterns

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

PASS

1 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+

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

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

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

PASS

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

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

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Feng Shui Bedroom

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Feng Shui Bedroom ✓192×192 icon ✓512×512 icon ✓Start URL /?utm_source=pwa&utm_medium=install ✓Display Mode standalone ✓

Name Feng Shui Bedroom Display Mode standalone Theme Color #0f3e17 Background Color #fffefc Icons 2 icon(s)

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

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)

Element	Ratio	Required	FG	BG	Result
h1 Feng Shui Bedroom An…	20.83:1	3.0:1	#000000	#FFFEFC	Pass
h2 Feng shui bedroom an…	20.38:1	3.0:1	#000000	#FBFCF8	Pass
h2 Instant bedroom layo…	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 How it works	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 Sample report: befor…	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 Five feng shui tools…	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 What we check	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 What is a feng shui …	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 Why your bedroom lay…	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 Methodology you can …	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 Who uses Feng Shui B…	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 Example scenarios	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 Simple credit pricin…	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 Feng shui bedroom FA…	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 From the feng shui b…	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h2 Ready to check your …	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h3 Upload a photo	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h3 Confirm what we see	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h3 Get your report	20.12:1	3.0:1	#000000	#F8FBF6	Pass
h3 Save and compare	20.12:1	3.0:1	#000000	#F8FBF6	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.

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 24 passed

PASS

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.space-y-4 > div.space-y-3 > div.flex > button.peer `div.space-y-4 > div.space-y-3 > div.flex > button.peer`
div.space-y-4 > div.space-y-3 > div.flex > button.peer `div.space-y-4 > div.space-y-3 > div.flex > button.peer`
div.space-y-4 > div.space-y-3 > div.flex > button.peer `div.space-y-4 > div.space-y-3 > div.flex > button.peer`

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.

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
01 `div.mx-auto > ol.mt-10 > li.rounded-3xl > span.font-serif`
02 `div.mx-auto > ol.mt-10 > li.rounded-3xl > span.font-serif`
03 `div.mx-auto > ol.mt-10 > li.rounded-3xl > span.font-serif`
04 `div.mx-auto > ol.mt-10 > li.rounded-3xl > span.font-serif`
Layout score: 54/100 `div.mt-10 > div.rounded-3xl > div.flex > span.rounded-full`
Scores describe layout rules only. They do not predict health, money or relatio… `div.flex > section#samples > div.mx-auto > p.mt-6`

These are opportunities to improve the legibility of your content.

○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]` values are valid

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

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

●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 are distinguishable without relying on color.

●Links have a discernible name

●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

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

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

○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

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

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