Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 3 REVIEW 6 FIX

Form Accessibility

Action

4 of 4 controls have issues

FIX

4 of 4 controls have issues

3 control(s) without accessible label

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

Got: <select name="property_type">; <select name="price_range">; <select name="bedrooms">

1 control(s) rely on placeholder only

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

Got: <input type="text" name="location">

4 controls

0 labeled

1 placeholder only

3 unlabeled

Control	Type	Label	Method
location	text	(City or area)	placeholder only
property_type	select	(none)	none
price_range	select	(none)	none
bedrooms	select	(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

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

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.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://foryouproperty.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://foryouproperty.com/manifest.json

Manifest contains invalid JSON.

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.

Got: #0c0e10

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

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

Mobile-Readable Font Sizes

93% of visible text renders at >= 12 CSS px (15 below threshold)

REVIEW

93% of visible text renders at >= 12 CSS px (15 below threshold)

15 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> 11.0px ("International property platform"); <p> 11.0px ("Our vision"); <p> 11.0px ("Browse by intent"); <p> 11.0px ("International destinations"); <p> 11.0px ("Browse by type").

Favicon & Branding

5 icon(s) detected

REVIEW

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

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA

h1 Find Your Property.

1.51:1

#000000

#262E2B

needs 3.0:1 (large text)

32px · above the fold

h1 Find Your Opportunity.

2.79:1

#000000

#465668

needs 3.0:1 (large text)

32px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Find Your Property.	1.51:1	3.0:1	#000000	#262E2B	Fail
h1 Find Your Opportunit…	2.79:1	3.0:1	#000000	#465668	Fail
h2 Property Without Bor…	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Buy, rent or stay	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Explore the World	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Properties for sale	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Long-term rentals	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Holiday stays	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Find Your Style	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 How It Works	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Why FORYOU?	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Have a Property to S…	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Partner With FORYOU	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Built on Trust and T…	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h2 Before you continue	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h3 Buy	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h3 Rent	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h3 Stay	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h3 Discover	4.81:1	3.0:1	#000000	#6D7A8C	Pass
h3 Explore	4.81:1	3.0:1	#000000	#6D7A8C	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Heading Hierarchy

53 headings

PASS

53 headings

Single H1 present

H1 Find Your Property.Find Your Opportunity.Find it with FORYOU.
H2 Property Without Borders
H2 Buy, rent or stay
H3 Buy
H3 Rent
H3 Stay
H2 Explore the World
H2 Properties for sale
H2 Long-term rentals
H2 Holiday stays
H2 Find Your Style
H2 How It Works
H3 Discover
H3 Explore
H3 Enquire
H3 Move Forward
H2 Why FORYOU?
H3 Global Opportunities
H3 Curated Properties
H3 Verified Features
H3 Professional Support
H2 Have a Property to Sell?
H2 Partner With FORYOU
H3 Become a FORYOU Broker
H3 Become a Property Partner
H2 Built on Trust and Transparency
H3 Properties
H3 Destinations
H3 Sell With Us
H3 Partners
H3 Company
H3 Legal
H2 Before you continue
H3 1. About FORYOU
H3 2. Eligibility
H3 3. User accounts
H3 4. Property providers
H3 5. Broker and partner accounts
H3 6. Property submissions and verification
H3 7. Listing requirements
H3 8. Prohibited conduct
H3 9. Enquiries and viewings
H3 10. User-generated content and intellectual property
H3 11. Reporting and complaints
H3 12. Anti-fraud measures
H3 13. International users
H3 14. Payments and advertising
H3 15. No guarantees
H3 16. Limitation of liability
H3 17. Account termination
H3 18. Changes to terms
H3 19. Governing law
H3 20. Contact

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 21 images OK

PASS

All 21 images OK

6 decorative image(s) correctly marked

15 image(s) with good alt text

21 images 15 good alt text 6 decorative

All images have appropriate alt text.

Link & Button Quality

68 links, 11 buttons — all OK

PASS

68 links, 11 buttons — all OK

3 link(s) open in new tab without warning

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

Got: https://www.pexels.com; /legal/terms; /legal/privacy

65 link(s) with descriptive text

68 links

0 empty

0 generic text

3 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	FORYOU — home	img no alt	Add alt attribute to the image
/buy	BuyHomes, apartments and devel…	img no alt	Add alt attribute to the image
/rent	RentLong-term rentals with cle…	img no alt	Add alt attribute to the image
/stays	StayHoliday homes and short-te…	img no alt	Add alt attribute to the image
https://www.pexels.com	Pexels	new tab	Add '(opens in new tab)' to text
/	FORYOU — home	img no alt	Add alt attribute to the image
/legal/terms	Terms & Conditions	new tab	Add '(opens in new tab)' to text
/legal/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text

76 links and buttons have descriptive text

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

https://www.pexels.com; /legal/terms; /legal/privacy

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

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

4 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

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+

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+

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

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.

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 31 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
FORYOU `div.container-brand > div.flex > a.inline-flex > span.font-display`
LIST YOUR PROPERTY `div.bg-sand-50 > div.container-brand > div.mt-10 > a.inline-flex`
RENT `div.rounded-2xl > div.w-full > div.mb-0 > button.rounded-t-lg`
STAYS `div.rounded-2xl > div.w-full > div.mb-0 > button.rounded-t-lg`
LIST YOUR PROPERTY `div.container-brand > div.max-w-xl > div.mt-8 > a.inline-flex`
Photography from Pexels. Hero by Senfoni Real Estate; vision image by Daniel Po… `div.flex > main.flex-1 > div > p.container-brand`
Pexels `main.flex-1 > div > p.container-brand > a.underline`
FORYOU `div.grid > div.col-span-2 > a.inline-flex > span.font-display`
Foryouu.as1@gmail.com `div.grid > div.col-span-2 > div.mt-5 > a.flex`
+44 7749935799 `div.grid > div.col-span-2 > div.mt-5 > a.flex`
International `div.grid > div.col-span-2 > div.mt-5 > p.flex`
PROPERTIES `div.container-brand > div.grid > div > h3.text-2xs`
DESTINATIONS `div.container-brand > div.grid > div > h3.text-2xs`
SELL WITH US `div.container-brand > div.grid > div > h3.text-2xs`
PARTNERS `div.container-brand > div.grid > div > h3.text-2xs`
COMPANY `div.container-brand > div.grid > div > h3.text-2xs`
LEGAL `div.container-brand > div.grid > div > h3.text-2xs`
© 2026 FORYOU. All rights reserved. `div.container-brand > div.mt-14 > div.flex > p`
FORYOU does not guarantee property ownership, transaction safety, or listing ac… `div.container-brand > div.mt-14 > div.flex > p.max-w-xl`
Version 1.0 `div.fixed > div.flex > div#legal-document-panel > p.mb-5`
To read in a separate tab: Terms & Conditions and Privacy Policy `div.fixed > div.flex > div.border-t > p.text-xs`
Terms & Conditions `div.flex > div.border-t > p.text-xs > a.underline`

These are opportunities to improve the legibility of your content.

Names and labels

Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Any type Apartment House Villa Land Commercial Development Townhouse Penthouse … `form.rounded-r-xl > div.grid > div > select.input-field`
Any price Up to 100K 100K — 500K 500K — 1M Over 1M `form.rounded-r-xl > div.grid > div > select.input-field`
Any 1+ 2+ 3+ 4+ 5+ `form.rounded-r-xl > div.grid > div > select.input-field`

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

●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

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

●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

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

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

○`[accesskey]` values are unique

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

○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

○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

○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

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