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

Link & Button Quality

Action

13 issue(s) across 55 links and 13 buttons

FIX

13 issue(s) across 55 links and 13 buttons

3 link(s) with no accessible text

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

Got: https://www.acecelebrations.com; https://www.facebook.com/acecelebrationslondon/; https://www.instagram.com/ace_celebrations/

10 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://www.acecelebrations.com/party-balloon-decorations ("Read More"); https://www.acecelebrations.com/anniversary-balloon-decorations ("Read More"); https://www.acecelebrations.com/corporate-balloon-decoration ("Read More"); https://www.acecelebrations.com/graduate-balloon-decorations ("Read More"); https://www.acecelebrations.com/engagement-party-balloon ("Read More"); https://www.acecelebrations.com/baby-shower-balloon-decorations ("Read More"); https://www.acecelebrations.com/dinner-table-setup ("Read More"); https://www.acecelebrations.com/wedding-backdrops ("Read More"); https://www.acecelebrations.com/gender-reveal-balloon-decoration ("Read More"); https://www.acecelebrations.com/birthday-party-decorations ("Read More")

13 link(s) open in new tab without warning

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

Got: https://api.whatsapp.com/send?phone=442080982514; https://www.facebook.com/acecelebrationslondon/; https://www.instagram.com/ace_celebrations/; http://www.youtube.com/@acecelebrations; https://api.whatsapp.com/send?phone=442080982514; https://www.facebook.com/acecelebrationslondon/; https://www.instagram.com/ace_celebrations; https://api.whatsapp.com/send?phone=442080982514; https://api.whatsapp.com/send?phone=442080982514; http://www.youtube.com/@acecelebrations (+3 more)

29 link(s) with descriptive text

55 links

3 empty

10 generic text

13 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.acecelebrations.com	(empty)	empty	Add link text or aria-label
https://api.whatsapp.com/send?phone=4420…	Whatsapp	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/acecelebrations…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/ace_celebratio…	Instagram	new tab	Add '(opens in new tab)' to text
http://www.youtube.com/@acecelebrations	Youtube	new tab	Add '(opens in new tab)' to text
https://api.whatsapp.com/send?phone=4420…	WhatsApp	new tab	Add '(opens in new tab)' to text
https://www.acecelebrations.com/party-ba…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Party Balloon Decorations
https://www.acecelebrations.com/annivers…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Anniversary Balloon Decorations
https://www.acecelebrations.com/corporat…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Corporate Balloon Decoration
https://www.acecelebrations.com/graduate…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Graduate Balloon Decorations
https://www.acecelebrations.com/engageme…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Engagement Party Balloon
https://www.acecelebrations.com/baby-sho…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Baby Shower Balloon Decorations
https://www.acecelebrations.com/dinner-t…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Dinner Table Setup
https://www.acecelebrations.com/wedding-…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Wedding Backdrops
https://www.acecelebrations.com/gender-r…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Gender Reveal Balloon Decoration
https://www.acecelebrations.com/birthday…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Birthday Party Decorations
https://www.facebook.com/acecelebrations…	(empty)	empty	Add link text or aria-label
https://www.facebook.com/acecelebrations…	Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/ace_celebratio…	(empty)	empty	Add link text or aria-label
https://www.instagram.com/ace_celebratio…	Instagram	new tab	Add '(opens in new tab)' to text
https://api.whatsapp.com/send?phone=4420…	ftr-whatsapp-icon.webp	new tab	Add '(opens in new tab)' to text
https://api.whatsapp.com/send?phone=4420…	WhatsApp	new tab	Add '(opens in new tab)' to text
http://www.youtube.com/@acecelebrations	ftr-youtube-icon.webp	new tab	Add '(opens in new tab)' to text
http://www.youtube.com/@acecelebrations	YouTube	new tab	Add '(opens in new tab)' to text
https://www.acecelebrations.com/	Ace Celebrations	new tab	Add '(opens in new tab)' to text
/store-policy	Privacy Policy	new tab	Add '(opens in new tab)' to text

42 links and buttons have descriptive text

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

https://www.acecelebrations.com; https://www.facebook.com/acecelebrationslondon/; https://www.instagram.com/ace_celebrations/

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

Generic link text like 'click here' doesn't describe the destination.

https://www.acecelebrations.com/party-balloon-decorations ("Read More"); https://www.acecelebrations.com/anniversary-balloon-decorations ("Read More"); https://www.acecelebrations.com/corporate-balloon-decoration ("Read More"); https://www.acecelebrations.com/graduate-balloon-decorations ("Read More"); https://www.acecelebrations.com/engagement-party-balloon ("Read More"); https://www.acecelebrations.com/baby-shower-balloon-decorations ("Read More"); https://www.acecelebrations.com/dinner-table-setup ("Read More"); https://www.acecelebrations.com/wedding-backdrops ("Read More"); https://www.acecelebrations.com/gender-reveal-balloon-decoration ("Read More"); https://www.acecelebrations.com/birthday-party-decorations ("Read More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://api.whatsapp.com/send?phone=442080982514; https://www.facebook.com/acecelebrationslondon/; https://www.instagram.com/ace_celebrations/; http://www.youtube.com/@acecelebrations; https://api.whatsapp.com/send?phone=442080982514; https://www.facebook.com/acecelebrationslondon/; https://www.instagram.com/ace_celebrations; https://api.whatsapp.com/send?phone=442080982514; https://api.whatsapp.com/send?phone=442080982514; http://www.youtube.com/@acecelebrations (+3 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

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" id="form-field-input-5a5210ab-8031-4ca2-95e0-97473746af2a-comp-lxmoi753-">

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" id="form-field-input-5a5210ab-8031-4ca2-95e0-97473746af2a-comp-lxmoi753-">

404 Error Page

Action

HTTP 404, custom page

FIX

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 ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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 ✗

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.

Heading Hierarchy

27 headings, 1 skip(s)

REVIEW

27 headings, 1 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H2 → H5 (missing H3)

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

H5 Picture Perfect
H5 BALLOON
H5 DECOR
H1 & More!
H1 Balloon Decoration in London for Event, Parties and Corporate duplicate H1
H2 Balloon Decoration for Occasions
H2 Party and Event Decorations:
H2 Anniversary Decorations:
H2 Corporate Event Decorations:
H2 Graduation Party Decorations:
H2 Engagement Party Decorations :
H2 Baby Shower Balloon Decorations :
H2 Dining Table Setups :
H2 Wedding Backdrops and Decorations :
H2 Gender Reveal Balloon Decorations :
H2 1st Birthday Balloon Decorations :
H2 Benefits of Balloon Decorations
H2 Why Choose us for Balloon Decoration?
H2 Cost of Balloon Decoration in London
H5 FAQS skipped
H3 What services does Ace Celebrations offer?
H3 How do I book Ace Celebrations for my event?
H3 Do you serve all event types and sizes?
H3 What makes Ace Celebrations different?
H3 Can I get a quote before booking?
H2 Contact Us For Balloon Decoration in London
H2 ©2026 by Ace Celebrations.

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Alt Text Quality

14 of 30 images have issues

REVIEW

14 of 30 images have issues

14 image(s) with filename as alt text

10 decorative image(s) correctly marked

6 image(s) with good alt text

30 images 6 good alt text 10 decorative 14 generic

Issue	Count
filename	14 image(s)

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 4 fail WCAG AA

REVIEW

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

16 pass 4 fail WCAG AA 5 pass AA only

span Home

2.02:1

#000000

#543B20

needs 4.5:1 (normal text)

16px · above the fold

span About

1.91:1

#000000

#4D3823

needs 4.5:1 (normal text)

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

span Services & Designs

2.13:1

#000000

#52402A

needs 4.5:1 (normal text)

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

span Wedding Balloon Decoration

4.11:1

#000000

#816B3F

needs 4.5:1 (normal text)

16px · above the fold

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h3 What services does A…	16.21:1	3.0:1	#000000	#E2E2E2	Pass
h3 How do I book Ace Ce…	16.21:1	3.0:1	#000000	#E2E2E2	Pass
h3 Do you serve all eve…	16.21:1	3.0:1	#000000	#E2E2E2	Pass
h3 What makes Ace Celeb…	16.21:1	3.0:1	#000000	#E2E2E2	Pass
h3 Can I get a quote be…	16.21:1	3.0:1	#000000	#E2E2E2	Pass
title Balloon Decoration L…	17.84:1	4.5:1	#000000	#F8EBD5	Pass
span top of page	17.84:1	4.5:1	#000000	#F8EBD5	Pass
button Skip to Main Content	17.84:1	4.5:1	#000000	#F8EBD5	Pass
span info@acecelebrations…	17.84:1	4.5:1	#000000	#F8EBD5	Pass
span 020 8098 2514	17.84:1	4.5:1	#000000	#F8EBD5	Pass
span Home	2.02:1	4.5:1	#000000	#543B20	Fail
span About	1.91:1	4.5:1	#000000	#4D3823	Fail
span Services & Designs	2.13:1	4.5:1	#000000	#52402A	Fail
span Wedding Balloon Deco…	4.11:1	4.5:1	#000000	#816B3F	Fail
span Event Decoration Lon…	5.09:1	4.5:1	#000000	#867C67	Pass
span Party Balloon Decora…	6.08:1	4.5:1	#000000	#808C92	Pass
span Engagement Party Bal…	6.93:1	4.5:1	#000000	#919594	Pass
span Corporate Balloon De…	7.06:1	4.5:1	#000000	#949695	Pass
span Baby Shower Balloon …	6.57:1	4.5:1	#000000	#8F9092	Pass
span Wedding Venue Setup	5.78:1	4.5:1	#000000	#82878A	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

13 landmarks

PASS

13 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 Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

3 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 3 all-caps heading(s)

A+

Form Accessibility

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#form-field-input-a64b9da2-2b7d-42a4-5fff-b4fb19a448e2-comp-lxmoi753-	text	Full Name	aria-label
#form-field-input-5a5210ab-8031-4ca2-95e0-97473746af2a-comp-lxmoi753-	email	Email	aria-label
#form-field-input-dfaa7486-a00e-4259-3b2b-1ab03fd4456c-comp-lxmoi753-	phone	Contact Number. Phone	aria-label
#form-field-input-d631cafb-ad95-47a9-7b82-d3cad4717425-comp-lxmoi753-	text	Event Location	aria-label
#form-field-input-7c03c505-91a5-4bfe-3abd-6e86e0b9f726-comp-lxmoi753-	text	Number of Guests	aria-label
#form-field-input-6eecbf1c-e405-445e-aaf6-475132d16cce-comp-lxmoi753-	textarea	Any further details or enquiries	aria-label

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-GB"

PASS

Lang attribute set to "en-GB"

<html lang="en-GB"> is set and valid

Got: en-GB

A+

Tabindex Anti-Patterns

0 positive, 1 -1-on-focusable

PASS

0 positive, 1 -1-on-focusable

tabindex="-1" on naturally-focusable <input id="form-field-input-f541c744-8c8f-4e4a-ca7d-c59b50f7b2ea-comp-lxmoi753-">

tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

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

PASS

All 132 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

2 mobile-depth signal(s) detected

PASS

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

iOS auto-link for phone numbers disabled (`format-detection: telephone=no`)

The page sets `<meta name="format-detection" content="telephone=no">`, which prevents iOS Safari from auto-converting phone-number-shaped strings into clickable `tel:` links. Common reason: the auto-detection rewrites mid-paragraph DOM and breaks CSS selectors / JS that depended on the specific text. If you want clickable phone numbers, declare them with explicit `<a href="tel:+1234567890">` and keep auto-detection disabled.

Lighthouse Accessibility Audits

Score 91/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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Select Date `div.htcADB > div > div.sOV3ab8 > div`
Select Date `div.slP6sMf > div.svEXDbE > span.sYLLh5P > button.sqaxP2l`

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.

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 > div > div#comp-lxmr04o9 > a.apPOZK `div > div > div#comp-lxmr04o9 > a.apPOZK`
div > div > div#comp-lxmr04ni > a.apPOZK `div > div > div#comp-lxmr04ni > a.apPOZK`

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

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

●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

●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

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

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

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