Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 5 REVIEW 6 FIX

Mobile Keyboard & Autofill

Action

2/2 eligible field(s) missing autocomplete or inputmode

FIX

2/2 eligible field(s) missing autocomplete or inputmode

1 field(s) missing recommended autocomplete attribute

WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: tel.

Got: <input type="tel">

1 field(s) would benefit from inputmode attribute

Mobile browsers pick the on-screen keyboard layout from `inputmode=` when present (numeric pad, tel dialpad, email keyboard). Without it, users see the default text keyboard and must mode-switch -- 2-3 extra taps per phone-number or numeric-ID field. Type-based defaults exist (`type=tel` shows the tel keyboard on most browsers) but `inputmode` is the explicit, cross-browser way to control this. Affected types: tel.

Got: <input type="tel">

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

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

2 icon(s) detected

FIX

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

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://share.google/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://share.google/manifest.json

Manifest contains invalid JSON.

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

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

3 landmarks

REVIEW

3 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

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

Form Accessibility

Action

4 of 5 controls have issues

REVIEW

4 of 5 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="text">

3 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">; <input type="tel">; <textarea>

1 control(s) properly labeled

5 controls

1 labeled

3 placeholder only

1 unlabeled

Control	Type	Label	Method
input	checkbox		none
input	tel	(56 458 564)	placeholder only
textarea	textarea	(Enter your message here...)	placeholder only
input	text	(Full Name)	placeholder only
input	text	(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

Placeholder text disappears on focus and is not a reliable label.

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

Link & Button Quality

1 issue(s) across 12 links and 9 buttons

REVIEW

1 issue(s) across 12 links and 9 buttons

4 link(s) open in new tab without warning

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

Got: https://www.linkedin.com/in/brickyard-real-estate-4180b0321/; https://www.instagram.com/brickyardrealestatellc/; https://www.tiktok.com/@brickyardrealestate?; https://www.facebook.com/people/Brickyard-Real-Estate-LLC/61562999425109/

1 button(s) with no accessible text

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

Got: button.px-5 (#40 on page)

8 link(s) with descriptive text

12 links

0 empty

0 generic text

4 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
https://www.linkedin.com/in/brickyard-re…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/brickyardreale…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@brickyardrealest…	TikTok	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/people/Brickyar…	Facebook	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

16 links and buttons have descriptive text

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

https://www.linkedin.com/in/brickyard-real-estate-4180b0321/; https://www.instagram.com/brickyardrealestatellc/; https://www.tiktok.com/@brickyardrealestate?; https://www.facebook.com/people/Brickyard-Real-Estate-LLC/61562999425109/

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.px-5 (#40 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

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.

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 Creation & confidence.

1.99:1

#000000

#463D3A

needs 3.0:1 (large text)

32px · above the fold

h1 Without compromise.

1.61:1

#000000

#3E2D27

needs 3.0:1 (large text)

32px · above the fold

h2 FX's Interior Design Practice of the Yea…

1.67:1

#000000

#3C312E

needs 3.0:1 (large text)

24px · above the fold · over background image/gradient

h2 Luxury Sales

1.73:1

#000000

#40332D

needs 3.0:1 (large text)

24px · above the fold

h2 Residential Buying

1.37:1

#000000

#2D2320

needs 3.0:1 (large text)

24px · mid-page

h2 Urban Rentals

1.45:1

#000000

#302822

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Commercial Leasing

1.45:1

#000000

#302822

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Exclusive Portfolios

1.45:1

#000000

#302822

needs 3.0:1 (large text)

24px · bottom of viewport

h2 We Work With

1.45:1

#000000

#302822

needs 3.0:1 (large text)

24px · bottom of viewport

h2 LEADING REAL ESTATE BROKERAGE YOU CAN TR…

1.45:1

#000000

#302822

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our Brokerage Services

1.45:1

#000000

#302822

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Maximize Your Property Value

1.45:1

#000000

#302822

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Looking For Expert Advice For Your Prope…

1.45:1

#000000

#302822

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Property Buying and Selling

1.45:1

#000000

#302822

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Brokerage Services

1.45:1

#000000

#302822

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Rental Services

1.45:1

#000000

#302822

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Real Estate Investment Consulting

1.45:1

#000000

#302822

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Property Management

1.45:1

#000000

#302822

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Luxury Property Management

1.45:1

#000000

#302822

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Long-Term Rental Plan

1.45:1

#000000

#302822

needs 3.0:1 (large text)

19px · bottom of viewport

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

Element	Ratio	Required	FG	BG	Result
h1 Creation & confidenc…	1.99:1	3.0:1	#000000	#463D3A	Fail
h1 Without compromise.	1.61:1	3.0:1	#000000	#3E2D27	Fail
h2 FX's Interior Design…	1.67:1	3.0:1	#000000	#3C312E	Fail
h2 Luxury Sales	1.73:1	3.0:1	#000000	#40332D	Fail
h2 Residential Buying	1.37:1	3.0:1	#000000	#2D2320	Fail
h2 Urban Rentals	1.45:1	3.0:1	#000000	#302822	Fail
h2 Commercial Leasing	1.45:1	3.0:1	#000000	#302822	Fail
h2 Exclusive Portfolios	1.45:1	3.0:1	#000000	#302822	Fail
h2 We Work With	1.45:1	3.0:1	#000000	#302822	Fail
h2 LEADING REAL ESTATE …	1.45:1	3.0:1	#000000	#302822	Fail
h2 Our Brokerage Servic…	1.45:1	3.0:1	#000000	#302822	Fail
h2 Maximize Your Proper…	1.45:1	3.0:1	#000000	#302822	Fail
h3 Looking For Expert A…	1.45:1	3.0:1	#000000	#302822	Fail
h3 Property Buying and …	1.45:1	3.0:1	#000000	#302822	Fail
h3 Brokerage Services	1.45:1	3.0:1	#000000	#302822	Fail
h3 Rental Services	1.45:1	3.0:1	#000000	#302822	Fail
h3 Real Estate Investme…	1.45:1	3.0:1	#000000	#302822	Fail
h3 Property Management	1.45:1	3.0:1	#000000	#302822	Fail
h3 Luxury Property Mana…	1.45:1	3.0:1	#000000	#302822	Fail
h3 Long-Term Rental Pla…	1.45:1	3.0:1	#000000	#302822	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+

Heading Hierarchy

26 headings

PASS

26 headings

Single H1 present

H1 Creation & confidence.Without compromise.
H2 FX's Interior Design Practice of the Year
H2 Luxury Sales
H2 Residential Buying
H2 Urban Rentals
H2 Commercial Leasing
H2 Exclusive Portfolios
H2 We Work With
H2 LEADING REAL ESTATE BROKERAGE YOU CAN TRUST
H3 Looking For Expert Advice For Your Property? Leave Your Message Here.
H2 Our Brokerage Services
H3 Property Buying and Selling
H3 Brokerage Services
H3 Rental Services
H3 Real Estate Investment Consulting
H3 Property Management
H3 Luxury Property Management
H2 Maximize Your Property Value
H3 Long-Term Rental Plan
H3 Short-Term Rental Plan
H3 You've scrolled 1m
H4 Find us
H4 Email
H4 Phone
H4 Follow us
H4 Explore

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

1 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: 1 all-caps heading(s)

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

3 image(s) with good alt text

3 images 3 good alt text

All images have appropriate alt text.

A+

Form Input Types

5 form control(s) checked, no type mismatches

PASS

5 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

5 form control(s) checked, no input-semantic issues

PASS

5 form control(s) checked, no input-semantic issues

All form input semantics look correct

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

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <input>

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

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 150 visible text node(s) render at >= 12 CSS pixels

PASS

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

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

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

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.

Lighthouse Accessibility Audits

Score 91/100 — 2 failing, 23 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.

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
Book Now `div.absolute > div.absolute > div.flex > button.bg-gold-500`
CHOOSE YOUR PLAN `div.max-w-7xl > div.w-full > div.mb-12 > span.font-sans`
01 `div.flex > div.group > div.flex > span.font-sans`

These are opportunities to improve the legibility of your content.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
form.space-y-5 > div.flex > div.flex > input.w-1/3 `form.space-y-5 > div.flex > div.flex > input.w-1/3`

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]` 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.

●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

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

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

○Links are distinguishable without relying on color.

○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

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

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