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 4 REVIEW 5 FIX

Mobile-Readable Font Sizes

Action

59% of visible text renders at >= 12 CSS px (287 below threshold)

FIX

59% of visible text renders at >= 12 CSS px (287 below threshold)

287 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> 10.5px ("Trusted by 600K+ security researchers"); <div> 10.0px ("Datasets"); <div> 10.0px ("Domains"); <div> 10.0px ("Categories"); <div> 10.0px ("ASNs").

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

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 Missing

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Not found

FIX

Not found

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.

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.

Link & Button Quality

Action

2 issue(s) across 111 links and 7 buttons

REVIEW

2 issue(s) across 111 links and 7 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /

8 link(s) open in new tab without warning

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

Got: https://wa.me/16477810204/; https://app.marketxy.com/login; https://wa.me/16477810204?text=I%20have%20a%20query%20regarding%20MarketXY; https://wa.me/61417556478?text=I%20have%20query%20regarding%20MarketXY; https://x.com/MarketXy277/; https://www.instagram.com/marketxyofficial/; https://www.facebook.com/marketxy/; https://www.linkedin.com/company/marketxy/

1 button(s) with no accessible text

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

Got: button.lg:hidden (#102 on page)

102 link(s) with descriptive text

111 links

1 empty

0 generic text

8 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
/	(empty)	empty	Add link text or aria-label
https://wa.me/16477810204/	+1 (647) 781-0204	new tab	Add '(opens in new tab)' to text
https://app.marketxy.com/login	Account	new tab	Add '(opens in new tab)' to text
https://wa.me/16477810204?text=I%20have%…	WhatsApp us	new tab	Add '(opens in new tab)' to text
https://wa.me/61417556478?text=I%20have%…	InstantWhatsAppQuick questions…	new tab	Add '(opens in new tab)' to text
https://x.com/MarketXy277/	Twitter	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/marketxyoffici…	Instagram	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/marketxy/	Facebook	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/marketx…	LinkedIn	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label

108 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://wa.me/16477810204/; https://app.marketxy.com/login; https://wa.me/16477810204?text=I%20have%20a%20query%20regarding%20MarketXY; https://wa.me/61417556478?text=I%20have%20query%20regarding%20MarketXY; https://x.com/MarketXy277/; https://www.instagram.com/marketxyofficial/; https://www.facebook.com/marketxy/; https://www.linkedin.com/company/marketxy/

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.lg:hidden (#102 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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Domain Categories for Every Industry | MarketXY ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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

h2 Built for

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One domain.

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Everything you need in

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 270 Million

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Websites by

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 230M+ Companies

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 What Data You Can

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One indicator,

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Research Data at

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 WHOIS, DNS, Email & CMS

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 See Patterns Across

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Why Teams Choose

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 One-time 25% discount for research teams…

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Built for Data Research

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Help when you

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Enterprise security

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 From scrappy startups to

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 — research runs on

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h2 MarketXY

1.73:1

#000000

#153660

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Cybersecurity

1.73:1

#000000

#153660

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Built for	1.73:1	3.0:1	#000000	#153660	Fail
h2 One domain.	1.73:1	3.0:1	#000000	#153660	Fail
h2 Everything you need …	1.73:1	3.0:1	#000000	#153660	Fail
h2 270 Million	1.73:1	3.0:1	#000000	#153660	Fail
h2 Websites by	1.73:1	3.0:1	#000000	#153660	Fail
h2 230M+ Companies	1.73:1	3.0:1	#000000	#153660	Fail
h2 What Data You Can	1.73:1	3.0:1	#000000	#153660	Fail
h2 One indicator,	1.73:1	3.0:1	#000000	#153660	Fail
h2 Research Data at	1.73:1	3.0:1	#000000	#153660	Fail
h2 WHOIS, DNS, Email & …	1.73:1	3.0:1	#000000	#153660	Fail
h2 See Patterns Across	1.73:1	3.0:1	#000000	#153660	Fail
h2 Why Teams Choose	1.73:1	3.0:1	#000000	#153660	Fail
h2 One-time 25% discoun…	1.73:1	3.0:1	#000000	#153660	Fail
h2 Built for Data Resea…	1.73:1	3.0:1	#000000	#153660	Fail
h2 Help when you	1.73:1	3.0:1	#000000	#153660	Fail
h2 Enterprise security	1.73:1	3.0:1	#000000	#153660	Fail
h2 From scrappy startup…	1.73:1	3.0:1	#000000	#153660	Fail
h2 — research runs on	1.73:1	3.0:1	#000000	#153660	Fail
h2 MarketXY	1.73:1	3.0:1	#000000	#153660	Fail
h3 Cybersecurity	1.73:1	3.0:1	#000000	#153660	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

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

Heading Hierarchy

28 headings, 1 skip(s)

PASS

28 headings, 1 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 MarketXY: Data Research Platform
H2 Built for Research Teams
H3 Cybersecurity
H3 Market Research
H3 Due Diligence
H3 Sales Intelligence
H3 Investment Research
H3 Domain Industry
H2 One domain. Six connected datasets.
H2 Everything you need in One Platform
H2 270 Million Websites by Categories
H2 230M+ Companies Database
H2 What Data You Can Research
H2 One indicator, an entire threat graph.
H3 From one seed to full actor infrastructure.
H2 Research Data at Global Scale
H2 WHOIS, DNS, Email & CMS Intelligence
H2 See Patterns Across the Internet
H2 Why Teams Choose MarketXY
H2 One-time 25% discount for research teams.
H2 Built for Data Research Workflows
H3 Plug into your existing stack.
H2 Help when you need it.
H2 Enterprise security by default.
H2 From scrappy startups to Fortune 500 — research runs on MarketXY.
H4 Support skipped
H4 About
H4 Legal

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

A+

Heading Text Quality

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

PASS

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

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

A+

Alt Text Quality

No images

PASS

No images

No images on this page

No images on this page.

Form Accessibility

1 of 2 controls have issues

PASS

1 of 2 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="text">

1 control(s) properly labeled

2 controls

1 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
input	text	Search intelligence	aria-label
input	text	(Search domain, email, IP, CMS...)	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

Form Input Types

2 input(s) using type=text where a specific type would help

PASS

2 input(s) using type=text where a specific type would help

Input "Search domain, email, IP, CMS..." should use type="email" (currently type="text")

Field name "Search domain, email, IP, CMS..." suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.

Input "Search intelligence" should use type="email" (currently type="text")

Field name "Search intelligence" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.

A+

Form Input Quality

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

PASS

2 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

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

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

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 90/100 — 3 failing, 25 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
header.relative > nav.fixed > div.flex > button.lg:hidden `header.relative > nav.fixed > div.flex > button.lg:hidden`

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
Research Teams `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
MarketXY supports industries that rely on data, intelligence, discovery, and an… `section.sect > div.mxy-container > div.sect-hd > p.sect-sub`
One Platform `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
Five core workflows replace the stack of tools your research team is paying for… `section.sect > div.mxy-container > div.sect-hd > p.sect-sub`
Unlimited exports `div.mxy-container > div.wyc-grid > div.wyc-card > div.wyc-meta`
4,800 categories `div.mxy-container > div.wyc-grid > div.wyc-card > div.wyc-meta`
230M+ companies `div.mxy-container > div.wyc-grid > div.wyc-card > div.wyc-meta`
Categories `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
206 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
299 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
254 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
235 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
176 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
50 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
85 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
112 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
71 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
10 `table.mxy-tbl > tbody > tr.cat-parent > td.tbl-rank`
34 subs `td > div.cat-name-cell > div.cat-name-main > span.cat-sub-count`
Database `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
200 million tracked companies across industries, geographies, and business type… `section#companyDatabaseSection > div.mxy-container > div.sect-hd > p.sect-sub`
10 `table.mxy-tbl > tbody > tr > td.tbl-rank`
Research `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
10 `div.dtype-grid > div.dtype-card > div.dtype-top > span.dtype-count`
10 `div.dtype-grid > div.dtype-card > div.dtype-top > span.dtype-count`
10 `div.dtype-grid > div.dtype-card > div.dtype-top > span.dtype-count`
Global Scale `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
Intelligence `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
Historical growth, infrastructure mapping, email provider distribution, and CMS… `section#emailCmsSection > div.mxy-container > div.sect-hd > p.sect-sub`
the Internet `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
Track where growth, registration, and company density are shifting month to mon… `section.sect-sm > div.mxy-container > div.sect-hd > p.sect-sub`
MarketXY `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
Six reasons data teams standardize on MarketXY for everyday research workflows. `section.sect > div.mxy-container > div.sect-hd > p.sect-sub`
Workflows `div.api-split > div > h2.sect-h2 > em`
# Search websites in a category `div.api-split > div.code-card > pre.code-body > span.c`
need it `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
Fortune 500 `div.mxy-container > div.sect-hd > h2.sect-h2 > em`
10,000+ research teams `section.sect > div.mxy-container > div.logos-stats > div.logos-stat`
4,200+ companies `section.sect > div.mxy-container > div.logos-stats > div.logos-stat`
148 countries `section.sect > div.mxy-container > div.logos-stats > div.logos-stat`

These are opportunities to improve the legibility of your content.

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
SUPPORT `div.jsx-894fd3c66fa3085b > div.jsx-894fd3c66fa3085b > div.jsx-894fd3c66fa3085b > h4.jsx-894fd3c66fa3085b`

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

●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

●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

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

●Touch targets have sufficient size and spacing.

●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

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

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

○Elements with visible text labels have matching accessible names.

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