Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

10 PASS 6 REVIEW 8 FIX

Heading Hierarchy

Action

22 headings

FIX

22 headings

No H1 heading found

Every page should have one H1 that describes the page content.

12 empty heading(s)

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

H2 The ultimate gifts
H3 Create special pentru tine și afacerea ta
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 Agende și Plannere
H3 Pentru Căsuța Ta
H3 Cupe și Trofee
H3 Pentru Copilul Tău
H3 Produse speciale
H4 Login
H4 Register
H3 Search

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

Alt Text Quality

Action

13 of 110 images have issues

FIX

13 of 110 images have issues

13 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

13 image-in-link without alt text

An image inside a link with no alt creates an empty link.

2 image(s) with alt text over 125 characters

48 decorative image(s) correctly marked

47 image(s) with good alt text

110 images 47 good alt text 48 decorative 13 missing

Issue	Count
missing	13 image(s)
too long	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

37 issue(s) across 324 links and 15 buttons

FIX

37 issue(s) across 324 links and 15 buttons

31 link(s) with no accessible text

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

Got: /wishlist/; javascript:void(0);; javascript:void(0);; /; javascript:void(0);; #; #; #; #; # (+21 more)

4 link(s) open in new tab without warning

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

Got: https://www.facebook.com/profile.php?id=61560766116851; https://instagram.com/evaprints.ro; https://tiktok.com/@evaprints.ro; https://www.s-sols.com/products/wordpress/accelerator?utm_source=usersite&utm…

6 button(s) with no accessible text

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

Got: button (#258 on page); button (#316 on page); button.btn-sub-menu (#2595 on page); button.btn-sub-menu (#2634 on page); button.btn-sub-menu (#2652 on page); button.searchsubmit (#2698 on page)

289 link(s) with descriptive text

324 links

31 empty

0 generic text

4 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
/wishlist/	(empty)	empty	Add link text or aria-label
javascript:void(0);	(empty)	empty	Add link text or aria-label
javascript:void(0);	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
javascript:void(0);	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
/	(empty)	empty	Add link text or aria-label
https://www.facebook.com/profile.php?id=…	Facebook	new tab	Add '(opens in new tab)' to text
https://instagram.com/evaprints.ro	Instagram	new tab	Add '(opens in new tab)' to text
https://tiktok.com/@evaprints.ro	Tiktok	new tab	Add '(opens in new tab)' to text
https://anpc.ro/ce-este-sal/	(empty)	empty	Add link text or aria-label
https://ec.europa.eu/consumers/odr/main/…	(empty)	empty	Add link text or aria-label
https://anpc.ro/ce-este-sal/	(empty)	empty	Add link text or aria-label
https://ec.europa.eu/consumers/odr/main/…	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
https://www.s-sols.com/products/wordpres…	Optimized by Seraphinite Accel…	new tab	Add '(opens in new tab)' to text
/	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
#	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

298 links and buttons have descriptive text

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

/wishlist/; javascript:void(0);; javascript:void(0);; /; javascript:void(0);; #; #; #; #; # (+21 more)

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://www.facebook.com/profile.php?id=61560766116851; https://instagram.com/evaprints.ro; https://tiktok.com/@evaprints.ro; https://www.s-sols.com/products/wordpress/accelerator?utm_source=usersite&utm…

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 (#258 on page); button (#316 on page); button.btn-sub-menu (#2595 on page); button.btn-sub-menu (#2634 on page); button.btn-sub-menu (#2652 on page); button.searchsubmit (#2698 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

Tabindex Anti-Patterns

Action

0 positive, 131 -1-on-focusable

FIX

0 positive, 131 -1-on-focusable

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

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

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

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.

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 ✗

Landmark Structure

4 landmarks

REVIEW

4 landmarks

<main> landmark present

No <nav> landmark 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

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="submit" name="wp-submit">

3 control(s) rely on placeholder only

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

Got: <input type="text" name="log">; <input type="password" name="pwd">; <input type="text" name="s">

1 control(s) properly labeled

5 controls

1 labeled

3 placeholder only

1 unlabeled

Control	Type	Label	Method
#popupRememberme	checkbox		none
pwd	password	(Password)	placeholder only
log	text	(Username or email)	placeholder only
s	text	(Search...)	placeholder only
wp-submit	submit	(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

Form Input Quality

2 input-semantic issue(s) across 5 form control(s)

REVIEW

2 input-semantic issue(s) across 5 form control(s)

1 password field(s) missing or with invalid `autocomplete`

Password managers fill / save passwords only when `autocomplete` is exactly `current-password` (login) or `new-password` (registration / change). Empty, `off`, `password`, or other values silently disable the manager UX. Sample: <input type="password" name="pwd">.

1 login form field(s) missing `autocomplete=username` (or `email`)

On a page with a password input, the matching username / email field needs `autocomplete="username"` or `autocomplete="email"` -- otherwise the password manager can't identify which field carries the login identifier and silently skips autofill on the whole form. Sample: <input type="text" name="log">.

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 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

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h2 The ultimate gifts

1.65:1

#000000

#32323A

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Create special pentru tine și afacerea …

1.65:1

#000000

#32323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Agende și Plannere

1.65:1

#000000

#32323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Pentru Căsuța Ta

1.65:1

#000000

#32323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Cupe și Trofee

1.65:1

#000000

#32323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Pentru Copilul Tău

1.65:1

#000000

#32323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Produse speciale

1.65:1

#000000

#32323A

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Search

1.65:1

#000000

#32323A

needs 3.0:1 (large text)

19px · bottom of viewport

span Carduri de loialitate

1.18:1

#000000

#15181F

needs 4.5:1 (normal text)

16px · top of page (header area)

span Cărți de vizită

1.19:1

#000000

#22160B

needs 4.5:1 (normal text)

16px · above the fold

span Etichete autocolante

1.16:1

#000000

#201307

needs 4.5:1 (normal text)

16px · above the fold

span Etichete cartonate

1.10:1

#000000

#170E03

needs 4.5:1 (normal text)

16px · above the fold

span Flyere

1.11:1

#000000

#190F07

needs 4.5:1 (normal text)

16px · above the fold

span Listă Prețuri

1.34:1

#000000

#2A221C

needs 4.5:1 (normal text)

16px · above the fold

span Plannere și Agende

1.57:1

#000000

#372D29

needs 4.5:1 (normal text)

16px · above the fold

span Social Cards

1.26:1

#000000

#251C17

needs 4.5:1 (normal text)

16px · above the fold

span Stickere

1.08:1

#000000

#100C09

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 The ultimate gifts	1.65:1	3.0:1	#000000	#32323A	Fail
h3 Create special pentr…	1.65:1	3.0:1	#000000	#32323A	Fail
h3 Agende și Plannere	1.65:1	3.0:1	#000000	#32323A	Fail
h3 Pentru Căsuța Ta	1.65:1	3.0:1	#000000	#32323A	Fail
h3 Cupe și Trofee	1.65:1	3.0:1	#000000	#32323A	Fail
h3 Pentru Copilul Tău	1.65:1	3.0:1	#000000	#32323A	Fail
h3 Produse speciale	1.65:1	3.0:1	#000000	#32323A	Fail
h3 Search	1.65:1	3.0:1	#000000	#32323A	Fail
title Acasa - Eva Prints	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Business	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Carduri cadou	8.25:1	4.5:1	#000000	#9DA3AA	Pass
span Carduri de loialitat…	1.18:1	4.5:1	#000000	#15181F	Fail
span Cărți de vizită	1.19:1	4.5:1	#000000	#22160B	Fail
span Etichete autocolante	1.16:1	4.5:1	#000000	#201307	Fail
span Etichete cartonate	1.10:1	4.5:1	#000000	#170E03	Fail
span Flyere	1.11:1	4.5:1	#000000	#190F07	Fail
span Listă Prețuri	1.34:1	4.5:1	#000000	#2A221C	Fail
span Plannere și Agende	1.57:1	4.5:1	#000000	#372D29	Fail
span Social Cards	1.26:1	4.5:1	#000000	#251C17	Fail
span Stickere	1.08:1	4.5:1	#000000	#100C09	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 Text Quality

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

PASS

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

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

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 "log" should use type="email" (currently type="text")

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

Input "s" should use type="search" (currently type="text")

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

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 "ro-RO"

PASS

Lang attribute set to "ro-RO"

<html lang="ro-RO"> is set and valid

Got: ro-RO

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

PASS

All 49 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 93/100 — 2 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.

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
LIVRARE GRATUITĂ `div.elementor-element > div.elementor-widget-container > p > span`
119.00 lei `span.price > del > span.woocommerce-Price-amount > bdi`
lei `del > span.woocommerce-Price-amount > bdi > span.woocommerce-Price-currencySymbol`
149.00 lei `span.price > del > span.woocommerce-Price-amount > bdi`
lei `del > span.woocommerce-Price-amount > bdi > span.woocommerce-Price-currencySymbol`
89.00 lei `span.price > del > span.woocommerce-Price-amount > bdi`
lei `del > span.woocommerce-Price-amount > bdi > span.woocommerce-Price-currencySymbol`

These are opportunities to improve the legibility of your content.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a`
div.elementor-widget-container > div.jws-offcanvas-action-wrap > div.jws-button-wrapper > a.jws-offcanvas-trigger `div.elementor-widget-container > div.jws-offcanvas-action-wrap > div.jws-button-wrapper > a.jws-offcanvas-trigger`
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a`
div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn `div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn`
div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn `div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn`
div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn `div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn`
div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn `div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn`
div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn `div.buttton-inner > ul.ct_ul_ol > li.btn-wishlist > a.jws-wishlist-btn`
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a`
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a`
div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a `div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > a`
body.home > a.backToTop `body.home > a.backToTop`

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

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

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

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

●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

○`[accesskey]` values are unique

○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

○Buttons have an accessible name

○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

○Heading elements appear in a sequentially-descending order

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

○Form elements have associated labels

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

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