Accessibility

F

Heading Hierarchy

Action

45 headings, 6 skip(s)

FIX

45 headings, 6 skip(s)

Single H1 present

Heading level skipped: H1 → H4 (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.

Heading level skipped: H2 → H4 (missing H3)

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.

Heading level skipped: H2 → H4 (missing H3)

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.

H1 Sorry, content chaos — your time’s up
H4 78% increased CVR via personalization skipped
H4 20+ languages supported
H4 10x increase in content production
H4 5 min release cycles down from 2 weeks
H2 Bring order to your content, and impact to your campaigns
H4 Modular content, max impact skipped
H4 AI that's actually on-brand
H4 Personalization made simple
H4 "Contentful has the capabilities to power and personalize content across customer touchpoints — from kiosks to digital menu boards in the drive-thru. Whether it's one customer looking for a double s
H4 "To be successful, we needed to scale personalized experiences to global audiences. Contentful’s flexible, extensible DXP allows us to build compelling digital experiences for varied personas and ex
H4 "Contentful is like a magnet. It’s really brought us together — marketing, product, engineering. We’re able to go after the blue-sky ideas that sort of demand a stronger cross-functional relatio
H2 Content that works harder, so you can work smarter
H4 More content, more meaningful results skipped
H4 Generate, translate, and personalize content in seconds using contextual AI
H4 Drive higher omnichannel engagement across multiple brands, products, and regions
H4 Measure and optimize performance at the component level
H2 See how brands are building personalized experiences
H3 Ruggable rolls out an efficient way to manage Black Friday and personalization with Contentful
H2 One dynamic content platform, infinite possibilities.
H4 Manage content skipped
H4 Personalize for users
H4 Create smarter content
H4 Design experiences
H4 Take action with insights
H4 All your content, under control
H2 With every team aligned, your impact shines
H4 Growth Marketing skipped
H4 Product
H4 Developers
H4 No-code personalization
H4 Optimize campaigns on the fly
H4 Centralized content management
H4 Faster workflows
H2 Our experts will turn your “can we?” into “we totally did”
H4 Professional Services skipped
H4 Customer Success
H4 Partnerships
H2 Contentful resources to power your digital experiences
H3 Enhancing the digital customer experience: Proven strategies for success
H4 Cutting through content chaos with AI
H4 Contentful leaders on what’s to come in 2025: Leveraging AI to create digital experiences that customers expect
H4 How AI is powering personalized experiences customers expect
H3 Leading brands vibe with Contentful
H2 Your experiences should wow, not wait. Let's talk.

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 ▾

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 ▾

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 ▾

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 ▾

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 ▾

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

F

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

D

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.

D

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.

D

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 ✗

F

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

2 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

Search

Skip Link

Labeled Navigation 2 <nav> element(s)

Back to Top

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.

B

Landmark Structure

17 landmarks

REVIEW

17 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <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

B

Alt Text Quality

4 of 109 images have issues

REVIEW

4 of 109 images have issues

4 image(s) with filename as alt text

4 image(s) with alt text over 125 characters

17 decorative image(s) correctly marked

84 image(s) with good alt text

109 images 84 good alt text 17 decorative 4 generic

Issue	Count
filename	4 image(s)
too long	4 image(s)

C

Link & Button Quality

Action

15 issue(s) across 153 links and 43 buttons

REVIEW

15 issue(s) across 153 links and 43 buttons

15 link(s) with no accessible text

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

Got: /case-studies/kraft-heinz/; /pricing/; https://www.instagram.com/contentful.inc/; https://github.com/contentful/; https://x.com/contentful/; https://www.youtube.com/c/Contentfulinc; https://www.linkedin.com/company/contentful/; /developers/changelog.rss ; /pricing/; https://www.instagram.com/contentful.inc/ (+5 more)

2 link(s) open in new tab without warning

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

Got: /legal/privacy-at-contentful/cookie-notice/; /legal/privacy-at-contentful/privacy-notice/

136 link(s) with descriptive text

153 links

15 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
/legal/privacy-at-contentful/cookie-noti…	Cookie Policy	new tab	Add '(opens in new tab)' to text
/legal/privacy-at-contentful/privacy-not…	Privacy Policy	new tab	Add '(opens in new tab)' to text
/case-studies/kraft-heinz/	(empty)	empty	Add link text or aria-label
/pricing/	(empty)	empty	Add link text or aria-label
https://www.instagram.com/contentful.inc…	(empty)	empty	Add link text or aria-label
https://github.com/contentful/	(empty)	empty	Add link text or aria-label
https://x.com/contentful/	(empty)	empty	Add link text or aria-label
https://www.youtube.com/c/Contentfulinc	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/content…	(empty)	empty	Add link text or aria-label
/developers/changelog.rss	(empty)	empty	Add link text or aria-label
/pricing/	(empty)	empty	Add link text or aria-label
https://www.instagram.com/contentful.inc…	(empty)	empty	Add link text or aria-label
https://github.com/contentful/	(empty)	empty	Add link text or aria-label
https://x.com/contentful/	(empty)	empty	Add link text or aria-label
https://www.youtube.com/c/Contentfulinc	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/content…	(empty)	empty	Add link text or aria-label
/developers/changelog.rss	(empty)	empty	Add link text or aria-label

179 links and buttons have descriptive text

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

/case-studies/kraft-heinz/; /pricing/; https://www.instagram.com/contentful.inc/; https://github.com/contentful/; https://x.com/contentful/; https://www.youtube.com/c/Contentfulinc; https://www.linkedin.com/company/contentful/; /developers/changelog.rss ; /pricing/; https://www.instagram.com/contentful.inc/ (+5 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.

/legal/privacy-at-contentful/cookie-notice/; /legal/privacy-at-contentful/privacy-notice/

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

B

Favicon & Branding

6 icon(s) detected

REVIEW

6 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

C

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 1 pass AA only

title Content that scales. Experiences that co…

1.52:1

#000000

on

#2B2D31

needs 4.5:1 (normal text)

16px · top of page (header area)

span Opens in a new window

1.52:1

#000000

on

#2B2D31

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Sorry, content chaos…	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h2 Bring order to your …	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h2 Content that works h…	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h2 See how brands are b…	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h2 One dynamic content …	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h2 With every team alig…	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h2 Our experts will tur…	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h2 Contentful resources…	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h2 Your experiences sho…	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h3 Ruggable rolls out a…	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h3 Enhancing the digita…	18.70:1	3.0:1	#000000	#EFF2F6	Pass
h3 Leading brands vibe …	18.70:1	3.0:1	#000000	#EFF2F6	Pass
title Content that scales.…	1.52:1	4.5:1	#000000	#2B2D31	Fail
span Opens in a new windo…	1.52:1	4.5:1	#000000	#2B2D31	Fail
span Opens an external we…	5.39:1	4.5:1	#000000	#808183	Pass
span Opens an external we…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span This website utilize…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span You may change your …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span You may close this b…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Cookie Policy	21.00:1	4.5:1	#000000	#FFFFFF	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.

B

Lighthouse Accessibility Audits

Score 85/100 — 5 failing, 26 passed

REVIEW

85

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

Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Loading video... `div > div.media_block_assetWrapper__A9Lft > div.media_block_video_video__UzAmu > div.media_block_video_videoSkeleton__QVovV`

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.

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
Accept All `div.osano-cm-window > div#98c70db7-6ee0-405e-a407-49bbd0750ab0 > div.osano-cm-dialog__buttons > button.osano-cm-accept-all`
Reject Non-Essential `div.osano-cm-window > div#98c70db7-6ee0-405e-a407-49bbd0750ab0 > div.osano-cm-dialog__buttons > button.osano-cm-denyAll`

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
78% increased CVR via personalization `section.logo_metric_root__WDRSB > div.logo_metric_metricsWrapper__aGoT2 > div.logo_metric_metricItem__bQSKp > h4.typography_heading__msTWL`
Modular content, max impact `div.col-span-full > div.copy_block_rootContainer__GVl78 > div.copy_block_container__BcpwE > h4.typography_heading__msTWL`
Manage content `div.icon_with_text_row_root__CPtUb > div.icon_with_text_row_textContainer__RVjUi > span.icon_with_text_row_titleTagContainer__RAwa2 > h4.typography_heading__msTWL`
Growth Marketing `div.icon_with_text_row_root__CPtUb > div.icon_with_text_row_textContainer__RVjUi > span.icon_with_text_row_titleTagContainer__RAwa2 > h4.typography_heading__msTWL`
Professional Services `a.copy_block_link__bsyzV > div.copy_block_rootContainer__GVl78 > div.copy_block_container__BcpwE > h4.typography_heading__msTWL`

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
div.logo_metric_metricsWrapper__aGoT2 > div.logo_metric_metricItem__bQSKp > div.logo_metric_logoContainer__ZNiK9 > a `div.logo_metric_metricsWrapper__aGoT2 > div.logo_metric_metricItem__bQSKp > div.logo_metric_logoContainer__ZNiK9 > a`
div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs `div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs`
div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs `div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs`
div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs `div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs`
div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs `div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs`
div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs `div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs`
div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs `div.mobile_footer_connectSectionMobile__Xsqmn > ul.mobile_footer_linksList__o1OXx > li > a.mobile_footer_link__Gdqbs`

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.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`

These items highlight common accessibility best practices.

○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

●Image elements have `[alt]` attributes

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

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

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

●ARIA IDs are unique

●Image elements do not have `[alt]` attributes that are redundant text.

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

○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

○No form fields have multiple labels

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

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

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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.