Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

1 PASS 6 REVIEW 6 FIX

Alt Text Quality

Action

14 of 102 images have issues

FIX

14 of 102 images have issues

14 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

10 image-in-link without alt text

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

55 decorative image(s) correctly marked

33 image(s) with good alt text

102 images 33 good alt text 55 decorative 14 missing

Issue	Count
missing	14 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

9 issue(s) across 168 links and 3 buttons

FIX

9 issue(s) across 168 links and 3 buttons

5 link(s) with no accessible text

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

Got: #section-1-tab-1; #section-1-tab-2; #section-1-tab-3; /customers/amc; /customers/neiman-marcus

2 link(s) with generic text

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

Got: https://cloudinary.com/integrations ("Learn More"); https://cloudinary.com/customers ("LEARN MORE")

8 image-only link(s) without alt text

4 link(s) open in new tab without warning

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

Got: https://cloudinary.com/documentation/figma_integration#banner; /integrations/wordpress; https://app-gallery.cloudinary.com/; https://ai.cloudinary.com/

2 button(s) with no accessible text

149 link(s) with descriptive text

168 links

5 empty

2 generic text

4 new tab

2 empty buttons

Element	Text	Issue	Suggested Fix
https://cloudinary.com/documentation/fig…	Figma	new tab	Add '(opens in new tab)' to text
/integrations/wordpress	WordPress	new tab	Add '(opens in new tab)' to text
https://app-gallery.cloudinary.com/	App Gallery	new tab	Add '(opens in new tab)' to text
#section-1-tab-1	(empty)	empty	Add link text or aria-label
#section-1-tab-2	(empty)	empty	Add link text or aria-label
#section-1-tab-3	(empty)	empty	Add link text or aria-label
https://ai.cloudinary.com/	TRY OUR GENERATIVE AI DEMOS �…	new tab	Add '(opens in new tab)' to text
https://cloudinary.com/integrations	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Integrations
https://cloudinary.com/customers	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Customers
/customers/paul-smith	45% higher video-enabled sales	img no alt	Add alt attribute to the image
/customers/amc	(empty)	empty	Add link text or aria-label
/customers/neiman-marcus	(empty)	empty	Add link text or aria-label
/customers/puma	Uptime rateof 99.95% …	img no alt	Add alt attribute to the image
/customers/rapha	90% faster image delivery …	img no alt	Add alt attribute to the image
https://lp.cloudinary.com/wod.lp.25q2-cl…	Need-to-Know Guide to Scale Vi…	new tab	Add '(opens in new tab)' to text
https://cloudinary-marketing-res.cloudin…	Modernizing the Visual Stack …	new tab	Add '(opens in new tab)' to text
https://lp.cloudinary.com/wnr.lp.cloudin…	Take the Work Out of Workflows…	new tab	Add '(opens in new tab)' to text
https://cloudinary.com/solutions/retail/…	The Trends Reshaping Retail …	new tab	Add '(opens in new tab)' to text
https://cloudinary.com/blog/heavy-images…	Heavy Images Are Costing You S…	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

150 links and buttons have descriptive text

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

#section-1-tab-1; #section-1-tab-2; #section-1-tab-3; /customers/amc; /customers/neiman-marcus

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://cloudinary.com/integrations ("Learn More"); https://cloudinary.com/customers ("LEARN 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://cloudinary.com/documentation/figma_integration#banner; /integrations/wordpress; https://app-gallery.cloudinary.com/; https://ai.cloudinary.com/

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

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

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

Landmark Structure

10 landmarks

REVIEW

10 landmarks

<main> landmark present

7 <nav> landmark(s) found

7 of 7 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

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

Action

20 headings, 2 skip(s)

REVIEW

20 headings, 2 skip(s)

Single H1 present

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H2 → H4 (missing H3)

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

2 empty heading(s)

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

H1 IMAGE AND VIDEO API PLATFORMVisualize Engaging Experiences
H3 Trusted by 3 million developers and 11,000 enterprise and hyper-growth companies as a critical part of their tech stack. skipped
H3 Image and Video APIs for Fast, Scalable Media Management
H3 AI-Powered Image & Video Transformation at Scale
H3 Create, Manage, and Deliver Dynamic Visual Experiences
H2 Integrations
H2 The Cloudinary Difference
H3 45% higher video-enabled sales
H3 (empty)
H3 (empty)
H3 Uptime rateof 99.95%
H3 90% faster image delivery
H2 Analysts and  Customers Agree
H4 Resources skipped
H4 Need-to-Know Guide to Scale Video Experiences
H4 Modernizing the Visual Stack
H4 Take the Work Out of Workflows
H4 The Trends Reshaping Retail
H4 Heavy Images Are Costing You Sales
H2 Ready to start using Cloudinary?

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

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 ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Cloudinary - Page not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

11 icon(s) detected

REVIEW

11 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 16 fail WCAG AA

REVIEW

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

4 pass 16 fail WCAG AA

h2 Integrations

1.34:1

#000000

#162436

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Cloudinary Difference

1.34:1

#000000

#162436

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Analysts and

1.34:1

#000000

#162436

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Customers Agree

1.34:1

#000000

#162436

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Image and Video APIs for Fast, Scalable …

1.34:1

#000000

#162436

needs 3.0:1 (large text)

19px · bottom of viewport

h3 AI-Powered Image & Video Transformation …

1.34:1

#000000

#162436

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Create, Manage, and Deliver Dynamic Visu…

1.34:1

#000000

#162436

needs 3.0:1 (large text)

19px · bottom of viewport

h3 % higher video-enabled sales

1.34:1

#000000

#162436

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Uptime rate

1.34:1

#000000

#162436

needs 3.0:1 (large text)

19px · bottom of viewport

h3 % faster image delivery

1.34:1

#000000

#162436

needs 3.0:1 (large text)

19px · bottom of viewport

a Platform Overview

1.19:1

#000000

#0C163B

needs 4.5:1 (normal text)

16px · top of page (header area)

span Create, personalize, and transcode video…

1.19:1

#000000

#0C163B

needs 4.5:1 (normal text)

16px · top of page (header area)

div Products

1.19:1

#000000

#0C163B

needs 4.5:1 (normal text)

16px · above the fold

a Video

1.19:1

#000000

#0C163B

needs 4.5:1 (normal text)

16px · above the fold

span Scale high-performing video faster with …

1.19:1

#000000

#0C163B

needs 4.5:1 (normal text)

16px · above the fold

a Image

1.19:1

#000000

#0C163B

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Integrations	1.34:1	3.0:1	#000000	#162436	Fail
h2 The Cloudinary Diffe…	1.34:1	3.0:1	#000000	#162436	Fail
h2 Analysts and	1.34:1	3.0:1	#000000	#162436	Fail
h2 Customers Agree	1.34:1	3.0:1	#000000	#162436	Fail
h2 Ready to start using…	15.67:1	3.0:1	#FFFFFF	#162436	Pass
h3 Trusted by 3 million…	15.67:1	3.0:1	#FFFFFF	#162436	Pass
h3 Image and Video APIs…	1.34:1	3.0:1	#000000	#162436	Fail
h3 AI-Powered Image & V…	1.34:1	3.0:1	#000000	#162436	Fail
h3 Create, Manage, and …	1.34:1	3.0:1	#000000	#162436	Fail
h3 % higher video-enabl…	1.34:1	3.0:1	#000000	#162436	Fail
h3 Uptime rate	1.34:1	3.0:1	#000000	#162436	Fail
h3 % faster image deliv…	1.34:1	3.0:1	#000000	#162436	Fail
title Image and Video Uplo…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Platform	8.15:1	4.5:1	#000000	#9DA1AF	Pass
a Platform Overview	1.19:1	4.5:1	#000000	#0C163B	Fail
span Create, personalize,…	1.19:1	4.5:1	#000000	#0C163B	Fail
div Products	1.19:1	4.5:1	#000000	#0C163B	Fail
a Video	1.19:1	4.5:1	#000000	#0C163B	Fail
span Scale high-performin…	1.19:1	4.5:1	#000000	#0C163B	Fail
a Image	1.19:1	4.5:1	#000000	#0C163B	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.

Lighthouse Accessibility Audits

Score 87/100 — 4 failing, 26 passed

REVIEW

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
LEARN MORE `main#general > section#LogoMarquee-Home > div.logo-marquee-mod_container > a.logo-marquee-mod_cta`
LEARN MORE `section#bentogrid > div.BentoGrid__intro > div.BentoGrid__intro-buttons > a.BentoGrid__intro-buttons-primary`
DOWNLOAD `div.resources_feed_module--item-wrapper > a.resources_feed_module--item--link > div.resources_feed_module--item--content > div.resources_feed_module--item--read-more`
GET STARTED `div.text-wrapper > div.text > div.buttons > a.btn`
Cookies Settings `div.ot-sdk-row > div#onetrust-button-group-parent > div#onetrust-button-group > button#onetrust-pc-btn-handler`
Accept All Cookies `div#onetrust-button-group-parent > div#onetrust-button-group > div.onetrust-banner-options > button#onetrust-accept-btn-handler`

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
Trusted by 3 million developers and 11,000 enterprise and hyper-growth companie… `div.wrapper > div.text > div.subtitle > h3`
Resources `div.container > div.resources_feed_module_wrap > div.resources_feed_module_heading > h4.resources_feed_module_heading--title`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img.wp-post-0 `a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img.wp-post-0`
div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0 `div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0`
a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img `a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img`
div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0 `div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0`
a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img.wp-post-0 `a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img.wp-post-0`
div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0 `div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0`
a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img.wp-post-0 `a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img.wp-post-0`
div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0 `div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0`
a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img.wp-post-0 `a.BentoGrid__item > div.BentoGrid__item-content > div.BentoGrid__item-logo > img.wp-post-0`
div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0 `div.BentoGrid__grid > a.BentoGrid__item > div.BentoGrid__item-thumbnail > img.wp-post-0`
div.aw-grid > div.item > div.item-img > img.idc-logo `div.aw-grid > div.item > div.item-img > img.idc-logo`
div.aw-grid > div.item > div.item-img > img `div.aw-grid > div.item > div.item-img > img`
div.aw-grid > div.item > div.item-img > img `div.aw-grid > div.item > div.item-img > img`
div.aw-grid > div.item > div.item-img > img `div.aw-grid > div.item > div.item-img > img`

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
ul#sync-nav-1 > li#tab-1 > p > a `ul#sync-nav-1 > li#tab-1 > p > a`
ul#sync-nav-1 > li#tab-2 > p > a `ul#sync-nav-1 > li#tab-2 > p > a`
ul#sync-nav-1 > li#tab-3 > p > a `ul#sync-nav-1 > li#tab-3 > p > a`
main#general > section#bentogrid > div.BentoGrid__grid > a.BentoGrid__item `main#general > section#bentogrid > div.BentoGrid__grid > a.BentoGrid__item`
main#general > section#bentogrid > div.BentoGrid__grid > a.BentoGrid__item `main#general > section#bentogrid > div.BentoGrid__grid > a.BentoGrid__item`

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

●Buttons have an accessible name

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

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

●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

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

○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

○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

○Form elements have associated labels

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

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

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) rely on placeholder only

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

Got: <input type="search" id="autocomplete-0-input">

1 controls

0 labeled

1 placeholder only

0 unlabeled

Control	Type	Label	Method
#autocomplete-0-input	search	(Search for...)	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

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