Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 8 REVIEW 4 FIX

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

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

Heading Hierarchy

42 headings, 1 skip(s)

REVIEW

42 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: H1 → H3 (missing H2)

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

H3
H2 100% SATISFACTION GUARANTEED
H1 HIGH QUALITY ROOFING SERVICES IN CONNECTICUT
H3 Overall Rating skipped
H3 5.0
H3 Based on 110+ Reviews
H2 LOCAL ROOFING EXPERTS IN CONNECTICUT
H2 Serving Homeowners, Builders, & Contractors with Quality Roofing Services Across all of Connecticut, and parts of New York.
H3 We specialize in roof replacements, repairs, chimney caps, copper flashing, New Roofs, & More.
H3 Licensed & Insured
H3 Family Owned Company
H3 100% Satisfaction Guranteed
H2 Residential Roofing PROS in CT & PARTS OF NY
H2 Roof Installation
H2 New Roof Installations
H2 Roof Replacement
H2 Roof Replacements
H2 Copper Work
H2 Copper Work
H2 Connecticut Roofing SERVICES You Can Trust
H3 Reviews & Testimonials
H2 What Homeowners Are Saying
H2 Rated 5 Stars
H2 Our Roofing Services
H1 Providing Expert Roofing Solutions for Homeowners duplicate H1
H2 Roof Replacements
H2 Roof Repairs
H2 Roof Maintenance
H2 Chimney Caps & Flashing
H2 Copper Work
H2 Have Questions About Our Roofing Services?
H3 REQUEST YOUR FREE ROOFING QUOTE
H2 LOOKING FOR A ROOFING PRO to Fix or Replace Your Roof?
H2 Contact
H2 Hours
H2 CONTACT US!
H2 Services
H2 Roof Types
H2 About Us
H2 Resources
H2 Contact Us
H2 Portfolio

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

Heading Text Quality

3 heading-text-quality issue(s) detected

REVIEW

3 heading-text-quality issue(s) detected

1 heading(s) are too short (≤2 characters) to convey meaning

Headings with 2 or fewer characters are almost always emoji / typos / alignment hacks rather than real headings. Screen readers announce the heading level ("heading 2") and then read the content -- a single-character heading conveys no information. Affected: - H3: "\u200b"

Got: 1 ≤2-char heading(s)

1 heading(s) are over 120 characters -- likely a misformatted paragraph

Headings beyond 120 characters are almost always full sentences or paragraphs that received heading semantics by mistake (e.g., a CMS editor selected the wrong block type, or a template wrapped a body paragraph in `<h2>`). Screen readers will announce these as "heading" and read the entire paragraph at heading prosody. Affected: - H2: 123 chars

Got: 1 >120-char heading(s)

5 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: 5 all-caps heading(s)

Alt Text Quality

5 of 38 images have issues

REVIEW

5 of 38 images have issues

5 image(s) with filename as alt text

10 decorative image(s) correctly marked

23 image(s) with good alt text

38 images 23 good alt text 10 decorative 5 generic

Issue	Count
filename	5 image(s)

Link & Button Quality

Action

7 issue(s) across 124 links and 21 buttons

REVIEW

7 issue(s) across 124 links and 21 buttons

6 link(s) with no accessible text

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

Got: tel:203-202-4234; tel:203-202-4234; tel:203-202-4234; https://www.randaroofing.com/contact; tel:203-202-4234; https://www.randaroofing.com/contact

1 link(s) open in new tab without warning

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

Got: https://www.google.com/search?sca_esv=2a6646da058cd39e&si=AMgyJEtREmoPL4P1I5I…

1 button(s) with no accessible text

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

Got: button#comp-kd5px9q0_r_comp-kkmqi5tc

117 link(s) with descriptive text

124 links

6 empty

0 generic text

1 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
tel:203-202-4234	(empty)	empty	Add link text or aria-label
tel:203-202-4234	(empty)	empty	Add link text or aria-label
https://www.google.com/search?sca_esv=2a…	Based on 110+ Reviews	new tab	Add '(opens in new tab)' to text
tel:203-202-4234	(empty)	empty	Add link text or aria-label
https://www.randaroofing.com/contact	(empty)	empty	Add link text or aria-label
tel:203-202-4234	(empty)	empty	Add link text or aria-label
https://www.randaroofing.com/contact	(empty)	empty	Add link text or aria-label
<button>	(empty)	empty	Add button text or aria-label

137 links and buttons have descriptive text

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

tel:203-202-4234; tel:203-202-4234; tel:203-202-4234; https://www.randaroofing.com/contact; tel:203-202-4234; https://www.randaroofing.com/contact

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.google.com/search?sca_esv=2a6646da058cd39e&si=AMgyJEtREmoPL4P1I5I…

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#comp-kd5px9q0_r_comp-kkmqi5tc

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

Mobile Keyboard & Autofill

Action

3/5 eligible field(s) missing autocomplete or inputmode

REVIEW

3/5 eligible field(s) missing autocomplete or inputmode

3 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, tel, numeric.

Got: <input type="email" name="email" id="input_comp-mh99ypli5">, <input type="tel" name="phone" id="input_comp-mh99yplk">, <input type="number" name="zip-code" id="input_comp-mh9h54yn">

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 404 Error: Page Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

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, 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 HIGH QUALITY ROOFING SERVICES IN CONNECT…

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Providing Expert Roofing Solutions for H…

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

32px · bottom of viewport

h2 100% SATISFACTION GUARANTEED

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 LOCAL ROOFING EXPERTS IN CONNECTICUT

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Serving Homeowners, Builders, & Contract…

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Residential Roofing PROS in

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Roof Installation

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 New Roof Installations

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Roof Replacement

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Roof Replacements

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Copper Work

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Copper Work

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Connecticut Roofing SERVICES You Can Tru…

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Our Roofing Services

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Have Questions About Our Roofing Service…

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 LOOKING FOR A ROOFING PRO to Fix or Repl…

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 CONTACT US!

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Contact Us

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

24px · bottom of viewport

h3 5.0

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

19px · bottom of viewport

h3 We specialize in roof replacements, repa…

2.40:1

#000000

#234E70

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 HIGH QUALITY ROOFING…	2.40:1	3.0:1	#000000	#234E70	Fail
h1 Providing Expert Roo…	2.40:1	3.0:1	#000000	#234E70	Fail
h2 100% SATISFACTION GU…	2.40:1	3.0:1	#000000	#234E70	Fail
h2 LOCAL ROOFING EXPERT…	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Serving Homeowners, …	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Residential Roofing …	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Roof Installation	2.40:1	3.0:1	#000000	#234E70	Fail
h2 New Roof Installatio…	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Roof Replacement	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Roof Replacements	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Copper Work	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Copper Work	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Connecticut Roofing …	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Our Roofing Services	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Have Questions About…	2.40:1	3.0:1	#000000	#234E70	Fail
h2 LOOKING FOR A ROOFIN…	2.40:1	3.0:1	#000000	#234E70	Fail
h2 CONTACT US!	2.40:1	3.0:1	#000000	#234E70	Fail
h2 Contact Us	2.40:1	3.0:1	#000000	#234E70	Fail
h3 5.0	2.40:1	3.0:1	#000000	#234E70	Fail
h3 We specialize in roo…	2.40:1	3.0:1	#000000	#234E70	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

14 landmarks

PASS

14 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

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+

Form Accessibility

All 10 controls labeled

PASS

All 10 controls labeled

10 control(s) properly labeled

10 controls

10 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#input_comp-mh99yplg1	text	First Name	for/id
#input_comp-mh99ypli5	email	Email	for/id
#input_comp-mh9a8c03	text	Street Address	for/id
#input_comp-mh9h4xll	text	City	for/id
#collection_comp-mh9iimer	select	Select A Service	for/id
#textarea_comp-mh99ypll1	textarea	Message	for/id
#input_comp-mh9hb40c	text	Last name	for/id
#input_comp-mh99yplk	tel	Phone	for/id
#input_comp-mh9h54yn	number	Zip Code	for/id
#collection_comp-mh9b77ln	select	How Did You Hear About Us?	for/id

A+

Form Input Types

10 form control(s) checked, no type mismatches

PASS

10 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

10 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

50 explicit tabindex attribute(s) checked, no anti-patterns

PASS

50 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

Mobile-Readable Font Sizes

All 140 visible text node(s) render at >= 12 CSS pixels

PASS

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

A+

Lighthouse Accessibility Audits

Score 95/100 — 2 failing, 27 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.

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
Overall Rating `div#comp-mh55n3062 > div#comp-mh55n30c9 > div#comp-mh55n30f1 > h3.font_3`

These are opportunities to improve keyboard navigation in your application.

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
section#comp-kbgakxea_r_comp-kbgajy18 > div.comp-kbgakxea_r_comp-kbgajy18-container > div#comp-kbgakxea_r_comp-mgz8fzax > a.IT88M3 `section#comp-kbgakxea_r_comp-kbgajy18 > div.comp-kbgakxea_r_comp-kbgajy18-container > div#comp-kbgakxea_r_comp-mgz8fzax > a.IT88M3`
div#comp-mh4vnqd12 > div#comp-mh4vnqd3 > div#comp-mh4vnqd45 > a.IT88M3 `div#comp-mh4vnqd12 > div#comp-mh4vnqd3 > div#comp-mh4vnqd45 > a.IT88M3`
div#comp-mh4vnqd12 > div#comp-mh4vnqde > div#comp-mh4vnqdf7 > a.IT88M3 `div#comp-mh4vnqd12 > div#comp-mh4vnqde > div#comp-mh4vnqdf7 > a.IT88M3`
div#comp-mh9i6d9l9 > div#comp-mh9i6d9n6 > div#comp-mh9i6d9p > a.IT88M3 `div#comp-mh9i6d9l9 > div#comp-mh9i6d9n6 > div#comp-mh9i6d9p > a.IT88M3`
div#comp-mh9i6d9l9 > div#comp-mh9i6dab > div#comp-mh9i6dad > a.IT88M3 `div#comp-mh9i6d9l9 > div#comp-mh9i6dab > div#comp-mh9i6dad > a.IT88M3`
div#comp-kbgakxmn_r_comp-mh282t9z > div#comp-kbgakxmn_r_comp-mh26h5xp > div#comp-kbgakxmn_r_comp-mh26h5xr1 > a.IT88M3 `div#comp-kbgakxmn_r_comp-mh282t9z > div#comp-kbgakxmn_r_comp-mh26h5xp > div#comp-kbgakxmn_r_comp-mh26h5xr1 > a.IT88M3`

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

●Select elements have associated label elements.

●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

●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

●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

●`<video>` elements contain a `<track>` element with `[kind="captions"]`

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

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

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

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