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

Landmark Structure

Action

5 landmarks

FIX

5 landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

3 <nav> landmark(s) found

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

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

34 headings, 1 skip(s)

FIX

34 headings, 1 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.

9 empty heading(s)

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

H3 Built With Directus
H3 Directus TV
H1 Your backend.Everyone's workspace.
H3 A production-ready backend before your second coffee. skipped
H2 Model your data visually
H2 Instant GraphQL + REST APIs
H2 Bring any SQL database
H2 Policy-based access control
H2 Extend with custom code
H2 AI-ready from day one
H2 Your backend is a black box.That's the problem.
H2 (empty)
H2 Give your team the controls.Keep your guardrails.
H3 Let workflows do the busywork
H3 Tailor the view per role
H3 Dashboards anyone can build
H3 Extend every surface
H2 AI that works with your data. Not a copy of it.
H3 AI Assistant
H3 Native MCP Server
H3 Governed by default
H2 Fits your stack. Not the other way around.
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H3 (empty)
H2 Stop drowning in tickets. Start shipping together.
H3 1000+ Employees, 1 Data Platform
H3 How Ripley Entertainment Used Directus to Revamp Their Digital Presence
H3 How Copa Airlines is Elevating Their Passenger Experience

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

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

Link & Button Quality

Action

13 issue(s) across 82 links and 5 buttons

FIX

13 issue(s) across 82 links and 5 buttons

13 link(s) with no accessible text

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

Got: https://directus.is/site/nextjs; https://directus.is/site/nuxt; https://directus.is/site/astro; https://directus.is/site/sveltekit; https://directus.is/site/solidstart; https://directus.is/site/11ty; https://github.com/directus; https://directus.chat; https://www.youtube.com/c/DirectusVideos; https://hub.docker.com/r/directus/directus (+3 more)

7 image-only link(s) without alt text

12 link(s) open in new tab without warning

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

Got: https://directus.io/blog/100-tools-apps-and-platforms-you-can-build-with-directus; https://community.directus.io/; https://testimonial.to/directus/all; /docs; https://github.com/directus/directus; https://directus.is/cms; https://directus.is/backend/data-modeling; https://directus.is/backend/apis; https://directus.is/backend/dbs; https://directus.is/backend/auth (+2 more)

50 link(s) with descriptive text

82 links

13 empty

0 generic text

12 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://directus.io/blog/100-tools-apps-…	100+ More Use CasesBuild anyth…	new tab	Add '(opens in new tab)' to text
https://community.directus.io/	Community ForumQuestions and c…	new tab	Add '(opens in new tab)' to text
https://testimonial.to/directus/all	Wall of LoveSee what others ar…	new tab	Add '(opens in new tab)' to text
/docs	Developers	new tab	Add '(opens in new tab)' to text
https://github.com/directus/directus	34,630	new tab	Add '(opens in new tab)' to text
https://directus.is/cms	See the Studio	new tab	Add '(opens in new tab)' to text
https://hub.docker.com/r/directus/direct…	41M+Downloads	img no alt	Add alt attribute to the image
https://github.com/directus/directus	32K+Stars	img no alt	Add alt attribute to the image
https://directus.io/built-with-directus	500K+Projects	img no alt	Add alt attribute to the image
https://directus.chat	16K+Members	img no alt	Add alt attribute to the image
https://directus.is/backend/data-modelin…	Model your data visuallyDefine…	new tab	Add '(opens in new tab)' to text
https://directus.is/backend/apis	Instant GraphQL + REST APIsCon…	new tab	Add '(opens in new tab)' to text
https://directus.is/backend/dbs	Bring any SQL databasePostgres…	new tab	Add '(opens in new tab)' to text
https://directus.is/backend/auth	Policy-based access controlGra…	new tab	Add '(opens in new tab)' to text
https://directus.is/backend/extensions	Extend with custom codeBuild c…	new tab	Add '(opens in new tab)' to text
https://directus.io/mcp	AI-ready from day oneBuilt-in …	new tab	Add '(opens in new tab)' to text
https://directus.is/site/nextjs	(empty)	empty	Add link text or aria-label
https://directus.is/site/nuxt	(empty)	empty	Add link text or aria-label
https://directus.is/site/astro	(empty)	empty	Add link text or aria-label
https://directus.is/site/sveltekit	(empty)	empty	Add link text or aria-label
https://directus.is/site/solidstart	(empty)	empty	Add link text or aria-label
https://directus.is/site/11ty	(empty)	empty	Add link text or aria-label
/case-studies/prusa3d	Case Study1000+ Employees, 1 D…	img no alt	Add alt attribute to the image
/case-studies/ripley-entertainment	Case StudyHow Ripley Entertain…	img no alt	Add alt attribute to the image
/case-studies/copa-airlines	Case StudyHow Copa Airlines is…	img no alt	Add alt attribute to the image
https://github.com/directus	(empty)	empty	Add link text or aria-label
https://directus.chat	(empty)	empty	Add link text or aria-label
https://www.youtube.com/c/DirectusVideos	(empty)	empty	Add link text or aria-label
https://hub.docker.com/r/directus/direct…	(empty)	empty	Add link text or aria-label
https://www.npmjs.com/package/directus	(empty)	empty	Add link text or aria-label
https://x.com/directus	(empty)	empty	Add link text or aria-label
https://www.linkedin.com/company/directu…	(empty)	empty	Add link text or aria-label

55 links and buttons have descriptive text

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

https://directus.is/site/nextjs; https://directus.is/site/nuxt; https://directus.is/site/astro; https://directus.is/site/sveltekit; https://directus.is/site/solidstart; https://directus.is/site/11ty; https://github.com/directus; https://directus.chat; https://www.youtube.com/c/DirectusVideos; https://hub.docker.com/r/directus/directus (+3 more)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://directus.io/blog/100-tools-apps-and-platforms-you-can-build-with-directus; https://community.directus.io/; https://testimonial.to/directus/all; /docs; https://github.com/directus/directus; https://directus.is/cms; https://directus.is/backend/data-modeling; https://directus.is/backend/apis; https://directus.is/backend/dbs; https://directus.is/backend/auth (+2 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

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.

Alt Text Quality

2 of 150 images have issues

REVIEW

2 of 150 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

90 decorative image(s) correctly marked

58 image(s) with good alt text

150 images 58 good alt text 90 decorative 2 missing

Issue	Count
missing	2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

Learn more ▾

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

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

404 Error Page

Action

Could not test

REVIEW

Could not test

404 page could not be tested

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

404 page quality check not available.

Favicon & Branding

Action

4 icon(s) detected

REVIEW

4 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

SVG favicon detected — scales perfectly to any size

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 1 fail WCAG AA

REVIEW

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

19 pass 1 fail WCAG AA

title The Headless CMS + Backend for Every Cus…

1.23:1

#000000

#0E1C2F

needs 4.5:1 (normal text)

16px · top of page (header area)

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Model your data visu…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Instant GraphQL + RE…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Bring any SQL databa…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Policy-based access …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Extend with custom c…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 AI-ready from day on…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title The Headless CMS + B…	1.23:1	4.5:1	#000000	#0E1C2F	Fail
span Learn more about our…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Product	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Use Cases and Featur…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Headless CMS	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Manage and deliver c…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Backend-as-a-Service	20.65:1	4.5:1	#000000	#FDFDFD	Pass
div Build and ship appli…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Headless Commerce	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div A single source of t…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div 100+ More Use Cases	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Build anything (or e…	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Instant APIs	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Connect a database, …	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.

Lighthouse Accessibility Audits

Score 84/100 — 4 failing, 18 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
Downloads `div.block-container > div.block-metric-group > a#metric-d312e27c-9363-4c59-adc3-3730e29572c5 > div.description`
Stars `div.block-container > div.block-metric-group > a#metric-aa39c25f-c070-4aa1-a656-3ad6e7c204cd > div.description`
Projects `div.block-container > div.block-metric-group > a#metric-16e2611f-315b-48d8-b525-801c8162ff98 > div.description`
Members `div.block-container > div.block-metric-group > a#metric-cccdac53-dfd9-449c-91af-cc80debb90af > div.description`
Every project needs APIs, auth, and admin tooling. Directus gives you all of it… `div.header > div.base-text-container > div.base-text > p`
Product Lead, Rescue.org `div.base-quote > address.base-byline > div > p.title`
Your content team needs a field renamed. Marketing wants a campaign. PM is aski… `div.header > div.base-text-container > div.base-text > p`
A visual workspace where content teams, business users, and AI work on live dat… `div.base-text-container > div.base-text > div.section-header > p`
Build automations that trigger on data changes, schedules, or manual input. Con… `div.header > div.base-text-container > div.base-text > p`
Content editors see what they need. Developers see what they need. Nobody gets … `div.header > div.base-text-container > div.base-text > p`
Real-time visibility into what matters. No SQL required. Drag, drop, and share … `div.header > div.base-text-container > div.base-text > p`
Custom interfaces, layouts, modules, and hooks. When the defaults aren't enough… `div.header > div.base-text-container > div.base-text > p`
Directus treats AI as another member of your team. Same permissions. Same gover… `div.header > div.base-text-container > div.base-text > p`
Writes, translates, and takes action on your content directly `div.direction-vertical > div.base-card > div.content > p.description`
Connect any AI tool to your Directus data in seconds `div.direction-vertical > div.base-card > div.content > p.description`
Same access policies apply to AI as to humans `div.direction-vertical > div.base-card > div.content > p.description`
Tech Lead, The Shift Network `div.base-quote > address.base-byline > div > p.title`
Directus works with whatever you're already building with. Bring your favorite … `div.base-text-container > div.base-text > div.section-header > p`
Jan 31, 2025 `div.direction-vertical > a.base-card > div.content > p.description`
Jul 2, 2024 `div.direction-vertical > a.base-card > div.content > p.description`
Nov 17, 2023 `div.direction-vertical > a.base-card > div.content > p.description`
Co-Founder, Rolley.io `div.base-quote > address.base-byline > div > p.title`
A composable backend to build your Headless CMS, BaaS, and more. `ul > li.logo > div.description > p`
Headless CMS `li > ul.children > li > a`
Backend-as-a-Service `li > ul.children > li > a`
Product Information `li > ul.children > li > a`
100+ Things to Build `li > ul.children > li > a`
Documentation `li > ul.children > li > a`
Guides `li > ul.children > li > a`
Community `li > ul.children > li > a`
Release Notes `li > ul.children > li > a`
Issue Tracker `li > ul.children > li > a`
Feature Requests `li > ul.children > li > a`
Community Chat `li > ul.children > li > a`
Cloud Dashboard `li > ul.children > li > a`
About `li > ul.children > li > a`
Careers `li > ul.children > li > a`
Brand Assets `li > ul.children > li > a`
Contact `li > ul.children > li > a`
©2026 Monospace Inc `div.base-container > footer.footer > nav.secondary > small`
Cloud Policies `nav.secondary > ul.links > li > a`
License `nav.secondary > ul.links > li > a`
Terms `nav.secondary > ul.links > li > a`
Privacy `nav.secondary > ul.links > li > a`

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
A production-ready backend before your second coffee. `div.block-container > div.header > div.base-heading-container > h3.base-heading`

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.base-container > div.block-container > div.direction-horizontal > a.base-card `div.base-container > div.block-container > div.direction-horizontal > a.base-card`
div.base-container > div.block-container > div.direction-horizontal > a.base-card `div.base-container > div.block-container > div.direction-horizontal > a.base-card`
div.base-container > div.block-container > div.direction-horizontal > a.base-card `div.base-container > div.block-container > div.direction-horizontal > a.base-card`
div.base-container > div.block-container > div.direction-horizontal > a.base-card `div.base-container > div.block-container > div.direction-horizontal > a.base-card`
div.base-container > div.block-container > div.direction-horizontal > a.base-card `div.base-container > div.block-container > div.direction-horizontal > a.base-card`
div.base-container > div.block-container > div.direction-horizontal > a.base-card `div.base-container > div.block-container > div.direction-horizontal > a.base-card`
nav.secondary > ul.socials > li > a `nav.secondary > ul.socials > li > a`
nav.secondary > ul.socials > li > a `nav.secondary > ul.socials > li > a`
nav.secondary > ul.socials > li > a `nav.secondary > ul.socials > li > a`
nav.secondary > ul.socials > li > a `nav.secondary > ul.socials > li > a`
nav.secondary > ul.socials > li > a `nav.secondary > ul.socials > li > a`
nav.secondary > ul.socials > li > a `nav.secondary > ul.socials > li > a`
nav.secondary > ul.socials > li > a `nav.secondary > ul.socials > li > a`

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

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Close `div#header > div.base-container > div.banner-content > button.dismiss`

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

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

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

●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

●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

●Document has a main landmark.

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

●All heading elements contain content.

○`[accesskey]` values are unique

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

○Deprecated ARIA roles were not used

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

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

○No element has a `[tabindex]` value greater than 0

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

○Uses ARIA roles only on compatible elements

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

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