Skip to content
https://housebeautiful.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
62
GRADE
D
FIX
4
REVIEW
6
PASS
3
INFO
0
Checks
13
3 PASS 6 REVIEW 4 FIX
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
Theme color only
FIX
Theme color only
Info::
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.
Got: #000000
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 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.

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
Landmark Structure
7 landmarks
REVIEW
7 landmarks
Info::
<main> landmark present
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.
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 header NAV MAIN CONTENTINFO footer

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

C
Heading Hierarchy
Action
66 headings, 2 skip(s)
REVIEW
66 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H1 (empty)
  • H3 Quartz vs. Quartzite: Here's the One Experts Say Is Best for Your Home skipped
  • H3 How to Organize Your Closet Like a Designer
  • H3 The “British-Inspired” Living Room Trend to Try
  • H3 Experts Say Collectors Want THESE Antiques in 2026
  • H3 10 Fresh Ways to Use Zellige Tiles All Over Your Home
  • H2 TOURS
  • H3 This New York Home Marries Two Dueling Aesthetics
  • H3 This Mountain Retreat Has So Many “Secret” Spaces
  • H3 This Cottage Nods to the Owner’s Love of Florals
  • H3 A Hyper-Personal California Family Home
  • H2 WELLNESS
  • H3 The New Home Gym: Fitness Experts Say "Recovery Zones" Will Be Huge in 2026
  • H3 This Missouri Home Prioritizes Slowing Down
  • H3 The Most Extravagent Hotel Spas Around the World
  • H3 A Lakeside Retreat Gets a Light-Filled Second Life
  • H3 "Invisible Wellness" Is the Next Big Home Trend
  • H2 REAL ESTATE
  • H3 5 Features That Make Homes More Desirable in 2026
  • H3 JFK's Former D.C. Home Is on the Market
  • H3 This Feature Can Make Your Home Sell Faster
  • H3 Drew Barrymore Just Listed Her Westchester Home
  • H2 ANTIQUES
  • H3 13 Vintage Home Features That Don’t Exist Anymore
  • H3 5 Vintage Chairs That Are Worth a LOT of Money
  • H3 This Unexpected Antique Is Making a Comeback
  • H3 5 “Tacky" Antiques That Are Cool Again
  • H2 SHOPPING
  • H3 8 Daybeds to Elevate Any Living Room IMMEDIATELY
  • H3 “Gossip Benches” Are Having a Surprising Comeback
  • H3 Jonathan Adler’s Michaels Collab Made My Jaw Drop
  • H3 It's a Great Time to Shop Big-Ticket Appliances
  • H2 ADVICE
  • H3 Psychologists Reveal Why You Love Antiques
  • H3 8 “Tacky” Things Designers NEVER Have in Kitchens
  • H3 This Is the “Magic Number” of Bed Pillows to Have
  • H3 The "5-4-3-2-1 Method" Is Great for New Gardeners
  • H3 12 Paint Colors That HGTV Stars ALWAYS Use
  • H2 WANT MORE?
  • H4 Get House Beautiful's newsletter for the latest interior design inspo, trends, and everything in between. skipped
  • H2 GOODS
  • H2 An Upcycled Solid Wood Lounge Chair
  • H2 A Colorful Shoe Rack to Display Your Best Pairs
  • H2 A Patterned Ottoman for Extra Whimsy
  • H2 A Zero-Waste Yarn Wall Hanging
  • H3 How Artist Malene Barnett Tells The Stories of Her Ancestors Through Clay
  • H2 DESIGN INSPO
  • H3 Psychologists Explain Why You Should Avoid a “Hostility Color Palette” in Your Home
  • H3 How to Design an “Expensive-looking” Kitchen
  • H3 The ONLY Way to Decorate With Antiques
  • H3 Vintage Finds That Work Perfectly in Modern Homes
  • H3 Stop Chasing Trends and Buy “Heirloom” Designs
  • H2 We are a community of design obsessives, but we happily welcome the design curious.
  • H2 Latest
  • H3 This New York Home Marries Two Dueling Aesthetics
  • H3 How to Reduce Your Carbon Footprint During a Reno
  • H3 Jennifer Lawrence’s Mansion Hits The Market Again
  • H3 You Might Be Mulching Your Garden All Wrong
  • H3 5 Early Spring Plants to Prune Right Now
  • H3 The Best Garden Plants to Attract Hummingbirds
  • H3 You Need to Try This Japanese Cleaning Method
  • H3 California is Home to the Nation’s Happiest City
  • H3 30 Elegant White Flowers You Should Plant Now
  • H3 20 Thrift Store Finds That Are Actually Worth a Lot
  • H3 87 Inspiring Designer Dining Rooms
  • H3 These Kitchen Hardware Trends Will Be Everywhere

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 ▾

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

B
Alt Text Quality
6 of 83 images have issues
REVIEW
6 of 83 images have issues
Warning::
6 image(s) with generic alt text
Info::
3 image(s) with alt text over 125 characters
Info::
2 decorative image(s) correctly marked
Info::
72 image(s) with good alt text
83 images 72 good alt text 2 decorative 6 generic
IssueCount
generic6 image(s)
too long3 image(s)
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 6 fail WCAG AA
REVIEW

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

14 pass 6 fail WCAG AA 1 pass AA only
a Design Inspiration
1.51:1
#000000
on
#242D39
needs 4.5:1 (normal text)
16px · above the fold
a Follow
3.53:1
#000000
on
#825C36
needs 4.5:1 (normal text)
16px · above the fold
a About Us
3.41:1
#000000
on
#7F5A34
needs 4.5:1 (normal text)
16px · mid-page
a House Beautiful Shop
3.33:1
#000000
on
#7A593F
needs 4.5:1 (normal text)
16px · mid-page
a Other Editions
2.04:1
#000000
on
#463F3D
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient
a Privacy Notice
1.31:1
#000000
on
#2E1E15
needs 4.5:1 (normal text)
16px · mid-page · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 WANT MORE?20.16:13.0:1
#000000
#FBFAFA
Pass
h2 We are a community o…20.16:13.0:1
#000000
#FBFAFA
Pass
title Home Decorating Idea…21.00:14.5:1
#000000
#FFFFFF
Pass
span Search21.00:14.5:1
#000000
#FFFFFF
Pass
a Subscribe21.00:14.5:1
#000000
#FFFFFF
Pass
a Leanne Ford x Feel F…21.00:14.5:1
#000000
#FFFFFF
Pass
a Design Inspiration1.51:14.5:1
#000000
#242D39
Fail
a Room Ideas20.16:14.5:1
#000000
#FBFAFA
Pass
a How to Renovate20.16:14.5:1
#000000
#FBFAFA
Pass
a Lifestyle20.16:14.5:1
#000000
#FBFAFA
Pass
a Entertaining16.68:14.5:1
#000000
#E6E5E3
Pass
a Shopping Guides17.27:14.5:1
#000000
#E9E9E7
Pass
a News10.48:14.5:1
#000000
#BAB7AF
Pass
a Newsletter6.51:14.5:1
#000000
#9D8D77
Pass
a Follow3.53:14.5:1
#000000
#825C36
Fail
a About Us3.41:14.5:1
#000000
#7F5A34
Fail
a House Beautiful Shop3.33:14.5:1
#000000
#7A593F
Fail
a Promotions15.63:14.5:1
#000000
#DEDEE0
Pass
a Other Editions2.04:14.5:1
#000000
#463F3D
Fail
a Privacy Notice1.31:14.5:1
#000000
#2E1E15
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.

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
#global-nav-search-input-inputtextSearchfor/id
#EmailemailEmail*for/id
A
404 Error Page
HTTP 404, custom page
PASS
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
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | House Beautiful ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 29 passed
PASS
98

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.

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
Quartz vs. Quartzite: Here's the One Experts Say Is Best for Your Home div.css-wgm1ip > a.ee4ms354 > div.css-1lzj3p3 > h3.css-cbnquu
Get House Beautiful's newsletter for the latest interior design inspo, trends, … section > div.css-1dcnzpc > div.css-131rjty > h4.css-7mmjvp

These are opportunities to improve keyboard navigation in your application.

○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
●Buttons have an accessible name
●Image elements have `[alt]` attributes
●Form elements have associated labels
●`[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
●Background and foreground colors have a sufficient contrast ratio
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●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
○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
○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.
○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