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 2 REVIEW 9 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: email.

Got: <input type="email">

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: email.

Got: <input type="email">

Tap Target Adequacy

Action

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

FIX

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

26 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

Action

50% of visible text renders at >= 12 CSS px (110 below threshold)

FIX

50% of visible text renders at >= 12 CSS px (110 below threshold)

110 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: <span> 11.0px ("HOMEX"); <span> 11.0px ("HOMEX"); <span> 11.0px ("HOMEX"); <span> 11.0px ("HOMEX"); <span> 11.0px ("HOMEX").

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

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

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://www.homex.ae/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://www.homex.ae/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

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 ModeNo Dark Mode Detected

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.

Form Accessibility

2 of 6 controls have issues

REVIEW

2 of 6 controls have issues

2 control(s) rely on placeholder only

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

Got: <input>; <input type="email">

4 control(s) properly labeled

6 controls

4 labeled

2 placeholder only

0 unlabeled

Control	Type	Label	Method
#home-location	input	Location	for/id
#home-min-price	text	Minimum price	for/id
#home-max-price	text	Maximum price	for/id
#home-bedrooms	input	Bedrooms	for/id
input	input	(Full Name)	placeholder only
input	email	(Email Address)	placeholder only

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

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 Find Your Perfect Property in Dubai

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Newest listings

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Project of the month

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What our clients say about us on Google.

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Market intelligence.

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Seven services, one trusted partner.

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Properties by Category

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Where should you buy in Dubai?

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Make your next Dubai property decision w…

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Dubai property, explained.

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Your next move, personally guided.

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Trust

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Build

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Future

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Semi Furnished 1BR | Mid Floor | Pool & …

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Fully Furnished 1BR | Prime Location | P…

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Shell & Core Retail | Mirdif Hills | 7 P…

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Luxury 2BR|Burj Khalifa View |Furnished|…

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Shell & Core Retail | Mirdif Hills | 7 P…

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Luxury 2BR|Burj Khalifa View |Furnished|…

1.43:1

#000000

#24292D

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Find Your Perfect Pr…	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Newest listings	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Project of the month	1.43:1	3.0:1	#000000	#24292D	Fail
h2 What our clients say…	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Market intelligence.	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Seven services, one …	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Properties by Catego…	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Where should you buy…	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Make your next Dubai…	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Dubai property, expl…	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Your next move, pers…	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Trust	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Build	1.43:1	3.0:1	#000000	#24292D	Fail
h2 Future	1.43:1	3.0:1	#000000	#24292D	Fail
h3 Semi Furnished 1BR \|…	1.43:1	3.0:1	#000000	#24292D	Fail
h3 Fully Furnished 1BR …	1.43:1	3.0:1	#000000	#24292D	Fail
h3 Shell & Core Retail …	1.43:1	3.0:1	#000000	#24292D	Fail
h3 Luxury 2BR\|Burj Khal…	1.43:1	3.0:1	#000000	#24292D	Fail
h3 Shell & Core Retail …	1.43:1	3.0:1	#000000	#24292D	Fail
h3 Luxury 2BR\|Burj Khal…	1.43:1	3.0:1	#000000	#24292D	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.

Landmark Structure

9 landmarks

PASS

9 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

39 headings

PASS

39 headings

Single H1 present

H1 Find Your Perfect Property in Dubai
H2 Newest listings
H3 Semi Furnished 1BR | Mid Floor | Pool & Gym
H3 Fully Furnished 1BR | Prime Location | Pool & Gym
H3 Shell & Core Retail | Mirdif Hills | 7 Parkings
H3 Luxury 2BR|Burj Khalifa View |Furnished|High Floor
H2 Project of the month
H3 Shell & Core Retail | Mirdif Hills | 7 Parkings
H3 Luxury 2BR|Burj Khalifa View |Furnished|High Floor
H2 What our clients say about us on Google.
H2 Market intelligence.
H3 How to Compare Dubai Property Opportunities
H3 IPS 2026 Dubai: The Global Real Estate Marketplace Returns
H2 Seven services, one trusted partner.
H3 Off-Plan Sales
H3 Secondary Market
H3 Leasing
H3 Land Joint Venture
H3 Construction
H3 Holiday Homes
H3 Property Management
H2 Properties by Category
H3 Apartments
H3 Villas
H3 Office Spaces
H3 Townhouses
H3 Retail
H3 shop
H2 Where should you buy in Dubai?
H3 Downtown Dubai
H2 Make your next Dubai property decision with clarity.
H2 Dubai property, explained.
H2 Your next move, personally guided.
H2 Trust • Build • Future
H3 Contact
H3 Explore
H3 Areas
H3 Services
H3 Connect

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

All 66 images OK

PASS

All 66 images OK

4 decorative image(s) correctly marked

62 image(s) with good alt text

66 images 62 good alt text 4 decorative

All images have appropriate alt text.

Link & Button Quality

120 links, 40 buttons — all OK

PASS

120 links, 40 buttons — all OK

12 link(s) open in new tab without warning

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

Got: https://www.instagram.com/homexproperties.ae/; https://www.google.com/search?q=HomeX+Properties+LLC+Dubai+reviews; https://www.google.com/maps/search/?api=1&query=Office+811%2C+Metropolis+Towe…; https://www.instagram.com/homexproperties.ae; https://www.tiktok.com/@homexproperties.ae; https://www.facebook.com/share/1Ee8jZF9sZ/?mibextid=wwXIfr; https://api.whatsapp.com/send/?phone=%2B971501648293&text=Hi%2C+I%E2%80%99m+c…; https://www.linkedin.com/company/homex-properties/mycompany/; https://x.com/homeXProperties; https://www.youtube.com/@HomexProperties (+2 more)

108 link(s) with descriptive text

120 links

0 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/	HomeX Properties LLC home	img no alt	Add alt attribute to the image
https://www.instagram.com/homexpropertie…	Follow Homex Properties on Ins…	new tab	Add '(opens in new tab)' to text
https://www.google.com/search?q=HomeX+Pr…	Read Our Google Reviews	new tab	Add '(opens in new tab)' to text
https://www.google.com/maps/search/?api=…	Office 811, Metropolis Tower, …	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/homexpropertie…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.tiktok.com/@homexproperties.…	TikTok	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/share/1Ee8jZF9s…	Facebook	new tab	Add '(opens in new tab)' to text
https://api.whatsapp.com/send/?phone=%2B…	WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/homex-p…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://x.com/homeXProperties	X	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@HomexProperties	YouTube	new tab	Add '(opens in new tab)' to text
https://dubailand.gov.ae/en/#/	Open DLD Verification	new tab	Add '(opens in new tab)' to text
https://wa.me/971501648293	WhatsApp	new tab	Add '(opens in new tab)' to text

148 links and buttons have descriptive text

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

https://www.instagram.com/homexproperties.ae/; https://www.google.com/search?q=HomeX+Properties+LLC+Dubai+reviews; https://www.google.com/maps/search/?api=1&query=Office+811%2C+Metropolis+Towe…; https://www.instagram.com/homexproperties.ae; https://www.tiktok.com/@homexproperties.ae; https://www.facebook.com/share/1Ee8jZF9sZ/?mibextid=wwXIfr; https://api.whatsapp.com/send/?phone=%2B971501648293&text=Hi%2C+I%E2%80%99m+c…; https://www.linkedin.com/company/homex-properties/mycompany/; https://x.com/homeXProperties; https://www.youtube.com/@HomexProperties (+2 more)

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

6 form control(s) checked, no type mismatches

PASS

6 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

6 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

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

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 93/100 — 3 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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
View Azizi `div.mt-5 > div.market-ticker > div.market-ticker-track > div.flex`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
Increase minimum price `form.mx-auto > div.relative > div.price-stepper > button.price-stepper-button`
Decrease minimum price `form.mx-auto > div.relative > div.price-stepper > button.price-stepper-button`
Increase maximum price `form.mx-auto > div.relative > div.price-stepper > button.price-stepper-button`
Decrease maximum price `form.mx-auto > div.relative > div.price-stepper > button.price-stepper-button`
Increase bedrooms `form.mx-auto > div.relative > div.price-stepper > button.price-stepper-button`
Decrease bedrooms `form.mx-auto > div.relative > div.price-stepper > button.price-stepper-button`
Properties `div.mx-auto > div.grid > div > a.mb-1.5`
Services `div.mx-auto > div.grid > div > a.mb-1.5`
Journal `div.mx-auto > div.grid > div > a.mb-1.5`
Team `div.mx-auto > div.grid > div > a.mb-1.5`
About `div.mx-auto > div.grid > div > a.mb-1.5`
Contact `div.mx-auto > div.grid > div > a.mb-1.5`
Business Bay `div.mx-auto > div.grid > div > a.mb-1.5`
Downtown Dubai `div.mx-auto > div.grid > div > a.mb-1.5`
Dubai Marina `div.mx-auto > div.grid > div > a.mb-1.5`
Palm Jumeirah `div.mx-auto > div.grid > div > a.mb-1.5`
Jumeirah Village Circle `div.mx-auto > div.grid > div > a.mb-1.5`
Dubai Hills Estate `div.mx-auto > div.grid > div > a.mb-1.5`
Land Joint Venture `div.mx-auto > div.grid > div > a.mb-1.5`
Construction `div.mx-auto > div.grid > div > a.mb-1.5`
Property Management `div.mx-auto > div.grid > div > a.mb-1.5`
Holiday Homes `div.mx-auto > div.grid > div > a.mb-1.5`
Off-Plan Sales `div.mx-auto > div.grid > div > a.mb-1.5`
Secondary Market `div.mx-auto > div.grid > div > a.mb-1.5`
Leasing `div.mx-auto > div.grid > div > a.mb-1.5`
Sell With Us `div.mx-auto > div.grid > div > a.mb-1.5`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AED `div.mx-auto > div.flex > div.relative > button.flex`
Follow Us `div.cinematic-home > section.border-t > div.mx-auto > a.mt-5`
DLD VERIFICATION `div.mx-auto > div.grid > div > a.mt-4`

○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

●Elements use only permitted ARIA attributes

●ARIA `tooltip` elements have accessible names

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

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

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

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

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

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