Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 5 REVIEW 6 FIX

Landmark Structure

Action

11 landmarks

FIX

11 landmarks

No <main> landmark found

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

11 <nav> landmark(s) found

11 of 11 <nav> elements are unlabeled

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

No banner (header) landmark

No contentinfo (footer) landmark

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

Favicon & Branding

Action

2 icon(s) detected

FIX

2 icon(s) detected

favicon.ico present at site root

HTML icon links detected

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✓ PNG Icons Present

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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

11 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 11 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Link & Button Quality

Action

29 issue(s) across 82 links and 0 buttons

REVIEW

29 issue(s) across 82 links and 0 buttons

29 link(s) with no accessible text

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

Got: projects.html; agencies-new-business-hub.html; agencies-agency-hub.html; legal.html; business.html; wikis.html; education.html; http://dokkio.com/pb; index.html; https://plans.pbworks.com/network/premium_21 (+19 more)

6 link(s) open in new tab without warning

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

Got: http://www.pbworks.com/privacy-policy.html; http://dokkio.com/pb; webinars.html; https://my.pbworks.com; webinars.html; http://dokkio.com

47 link(s) with descriptive text

82 links

29 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
http://www.pbworks.com/privacy-policy.ht…	learn more about cookies	new tab	Add '(opens in new tab)' to text
projects.html	(empty)	empty	Add link text or aria-label
agencies-new-business-hub.html	(empty)	empty	Add link text or aria-label
agencies-agency-hub.html	(empty)	empty	Add link text or aria-label
legal.html	(empty)	empty	Add link text or aria-label
business.html	(empty)	empty	Add link text or aria-label
wikis.html	(empty)	empty	Add link text or aria-label
education.html	(empty)	empty	Add link text or aria-label
http://dokkio.com/pb	(empty)	empty	Add link text or aria-label
http://dokkio.com/pb	LEARN MORE ››	new tab	Add '(opens in new tab)' to text
webinars.html	WEBINARS	new tab	Add '(opens in new tab)' to text
index.html	(empty)	empty	Add link text or aria-label
https://plans.pbworks.com/network/premiu…	(empty)	empty	Add link text or aria-label
https://plans.pbworks.com/network/premiu…	(empty)	empty	Add link text or aria-label
https://plans.pbworks.com/network/premiu…	(empty)	empty	Add link text or aria-label
https://plans.pbworks.com/network/premiu…	(empty)	empty	Add link text or aria-label
https://plans.pbworks.com/network/premiu…	(empty)	empty	Add link text or aria-label
https://plans.pbworks.com/academic	(empty)	empty	Add link text or aria-label
https://my.pbworks.com	LOGIN	new tab	Add '(opens in new tab)' to text
agencies-agency-hub.html	(empty)	empty	Add link text or aria-label
agencies-new-business-hub.html	(empty)	empty	Add link text or aria-label
projects.html	(empty)	empty	Add link text or aria-label
legal.html	(empty)	empty	Add link text or aria-label
education.html	(empty)	empty	Add link text or aria-label
wikis.html	(empty)	empty	Add link text or aria-label
business.html	(empty)	empty	Add link text or aria-label
http://fb.com/pbworks	(empty)	empty	Add link text or aria-label
http://twitter.com/pbworks	(empty)	empty	Add link text or aria-label
http://blog.pbworks.com/	(empty)	empty	Add link text or aria-label
index.html	(empty)	empty	Add link text or aria-label
https://docs.pbworks.com/w/page/42027927…	(empty)	empty	Add link text or aria-label
http://edumanual.pbworks.com/w/page/5800…	(empty)	empty	Add link text or aria-label
terms-of-service.html	(empty)	empty	Add link text or aria-label
webinars.html	WEBINARS	new tab	Add '(opens in new tab)' to text
http://dokkio.com	Learn about our new product - …	new tab	Add '(opens in new tab)' to text

47 links and buttons have descriptive text

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

projects.html; agencies-new-business-hub.html; agencies-agency-hub.html; legal.html; business.html; wikis.html; education.html; http://dokkio.com/pb; index.html; https://plans.pbworks.com/network/premium_21 (+19 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.

http://www.pbworks.com/privacy-policy.html; http://dokkio.com/pb; webinars.html; https://my.pbworks.com; webinars.html; http://dokkio.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

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

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA 1 pass AA only

title Capture knowledge, share files, and mana…

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

span PBworks uses cookies to ensure you get t…

1.32:1

#000000

#222222

needs 4.5:1 (normal text)

16px · top of page (header area)

a Our Privacy Policy

3.97:1

#000000

#9B5A4E

needs 4.5:1 (normal text)

16px · top of page (header area)

a Got it!

4.01:1

#000000

#9D5A51

needs 4.5:1 (normal text)

16px · top of page (header area)

p Capture knowledge, share files, and mana…

2.95:1

#000000

#814846

needs 4.5:1 (normal text)

16px · above the fold

p LEARN MORE

1.22:1

#000000

#201A1B

needs 4.5:1 (normal text)

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

span ››

4.18:1

#000000

#6F6F70

needs 4.5:1 (normal text)

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

p Go beyond simple task management with co…

1.14:1

#000000

#141417

needs 4.5:1 (normal text)

16px · above the fold

p LEARN MORE ››

1.15:1

#000000

#151518

needs 4.5:1 (normal text)

16px · above the fold

p Pitch more business.

2.26:1

#000000

#45474B

needs 4.5:1 (normal text)

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

p Win more business.

1.22:1

#000000

#181B1F

needs 4.5:1 (normal text)

16px · above the fold

p Organize and improve each stage of the n…

1.48:1

#000000

#272B32

needs 4.5:1 (normal text)

16px · above the fold

p LEARN MORE ››

1.49:1

#000000

#272C33

needs 4.5:1 (normal text)

16px · mid-page

p Connect your team.

2.37:1

#000000

#434B53

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

p Build your business.

2.30:1

#000000

#404955

needs 4.5:1 (normal text)

16px · mid-page

p Transform how your people and clients wo…

1.66:1

#000000

#333333

needs 4.5:1 (normal text)

16px · mid-page

span LEARN MORE

2.22:1

#000000

#464646

needs 4.5:1 (normal text)

16px · mid-page · over background image/gradient

5 contrast failures on background images/gradients

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

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Capture knowledge, s…	1.32:1	4.5:1	#000000	#222222	Fail
span PBworks uses cookies…	1.32:1	4.5:1	#000000	#222222	Fail
a Our Privacy Policy	3.97:1	4.5:1	#000000	#9B5A4E	Fail
a Got it!	4.01:1	4.5:1	#000000	#9D5A51	Fail
p Capture knowledge, s…	2.95:1	4.5:1	#000000	#814846	Fail
p LEARN MORE	1.22:1	4.5:1	#000000	#201A1B	Fail
span ››	4.18:1	4.5:1	#000000	#6F6F70	Fail
p Your next project ca…	4.50:1	4.5:1	#000000	#747476	Pass
p Go beyond simple tas…	1.14:1	4.5:1	#000000	#141417	Fail
p LEARN MORE ››	1.15:1	4.5:1	#000000	#151518	Fail
p Pitch more business.	2.26:1	4.5:1	#000000	#45474B	Fail
p Win more business.	1.22:1	4.5:1	#000000	#181B1F	Fail
p Organize and improve…	1.48:1	4.5:1	#000000	#272B32	Fail
p LEARN MORE ››	1.49:1	4.5:1	#000000	#272C33	Fail
p Connect your team.	2.37:1	4.5:1	#000000	#434B53	Fail
p Build your business.	2.30:1	4.5:1	#000000	#404955	Fail
p Transform how your p…	1.66:1	4.5:1	#000000	#333333	Fail
span LEARN MORE	2.22:1	4.5:1	#000000	#464646	Fail
span ››	10.34:1	4.5:1	#000000	#52C0FF	Pass
p Less matter issues.	10.34:1	4.5:1	#000000	#52C0FF	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 88/100 — 4 failing, 21 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
Our Privacy Policy `body.initialized > div.cc-window > span#cookieconsent:desc > a.cc-link`
Got it! `body.initialized > div.cc-window > div.cc-compliance > a.cc-btn`
“I can’t imagine managing a team-based project without the kind of online colla… `div#u2036 > div#u2036_align_to_page > div#u2037-9 > p#u2037-2`
Alex Seropian `div#u2036 > div#u2036_align_to_page > div#u2037-9 > p#u2037-5`
©2020 PBworks, Inc. Project Hub, Agency Hub, New Business Hub, Legal Hub, Busin… `div#page > div#pu8935 > div#u8936-4 > p`
HOME `div#u8941-5 > p#u8941-3 > a.nonblock > span#u8941`
PRO `div#pu8935 > a#u8943-5 > p#u8943-3 > span#u8943`
DUCTS `div#pu8935 > a#u8943-5 > p#u8943-3 > span#u8943-2`
SUPPORT: `div#pu8935 > a#u8944-5 > p#u8944-3 > span#u8944`
GDPR `div#u25286-5 > p#u25286-3 > a.nonblock > span#u25286`
ARTICLES `div#pu8935 > a#u8947-4 > p#u8947-2 > span#u8947`
WEBINARS `div#pu8935 > a#u8949-4 > p#u8949-2 > span#u8949`
ABOUT US `div#pu8935 > a#u8951-4 > p#u8951-2 > span#u8951`
DMCA `div#pu8935 > a#u8952-4 > p#u8952-2 > span#u8952`
NEWS `div#pu8935 > a#u8953-4 > p#u8953-2 > span#u8953`
API `div#pu8935 > a#u8954-4 > p#u8954-2 > span#u8954`
CONTACT US `div#pu8935 > a#u8955-4 > p#u8955-2 > span#u8955`
Contact us for a custom price quote. `div#page > div#pu8935 > div#u11474-18 > p#u11474-6`
Sales line: (800) 326-6506 `div#page > div#pu8935 > div#u11474-18 > p#u11474-8`
Email: `div#pu8935 > div#u11474-18 > p > span#u11474-9`
sales@pbworks.com `div#u11474-18 > p > a.nonblock > span#u11474-10`
Learn about our new product - Dokkio `div#u11474-18 > p > a.nonblock > span#u11474-14`

These are opportunities to improve the legibility of your content.

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
body.initialized > div#page > div#ppamphletu1189 > a#u11476 `body.initialized > div#page > div#ppamphletu1189 > a#u11476`
div#pamphletu2330 > div#u2353 > div#u2354popup > a#u2354 `div#pamphletu2330 > div#u2353 > div#u2354popup > a#u2354`
div#pamphletu2330 > div#u2353 > div#u13373popup > a#u13373 `div#pamphletu2330 > div#u2353 > div#u13373popup > a#u13373`
div#pamphletu2330 > div#u2353 > div#u13386popup > a#u13386 `div#pamphletu2330 > div#u2353 > div#u13386popup > a#u13386`
div#pamphletu2330 > div#u2353 > div#u13399popup > a#u13399 `div#pamphletu2330 > div#u2353 > div#u13399popup > a#u13399`
div#pamphletu2330 > div#u2353 > div#u13411popup > a#u13411 `div#pamphletu2330 > div#u2353 > div#u13411popup > a#u13411`
div#pamphletu2330 > div#u2353 > div#u13428popup > a#u13428 `div#pamphletu2330 > div#u2353 > div#u13428popup > a#u13428`
div#pamphletu2330 > div#u2353 > div#u13440popup > a#u13440 `div#pamphletu2330 > div#u2353 > div#u13440popup > a#u13440`
body.initialized > div#page > div#pu8935 > a#u8937 `body.initialized > div#page > div#pu8935 > a#u8937`
body.initialized > div#page > div#pu8935 > a#u8939 `body.initialized > div#page > div#pu8935 > a#u8939`
body.initialized > div#page > div#pu8935 > a#u13991 `body.initialized > div#page > div#pu8935 > a#u13991`
div#page > div#pu8935 > div#u8941-5 > a.block `div#page > div#pu8935 > div#u8941-5 > a.block`
div#page > div#pu8935 > div#u25280-5 > a.block `div#page > div#pu8935 > div#u25280-5 > a.block`
div#page > div#pu8935 > div#u25283-5 > a.block `div#page > div#pu8935 > div#u25283-5 > a.block`
div#page > div#pu8935 > div#u25286-5 > a.block `div#page > div#pu8935 > div#u25286-5 > a.block`

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
Online Team Collaboration `div#page > div#ppamphletu1189 > div#u7337 > a#u7340-4`
HOME `div#pu8935 > div#u8941-5 > p#u8941-3 > a.nonblock`
SUPPORT: BUSINESS `body.initialized > div#page > div#pu8935 > a#u8942-4`
DATA BREACH POLICY `div#pu8935 > div#u25280-5 > p#u25280-3 > a.nonblock`
PRODUCTS `body.initialized > div#page > div#pu8935 > a#u8943-5`
CASE STUDIES `body.initialized > div#page > div#pu8935 > a#u8945-4`
TERMS OF SERVICE `body.initialized > div#page > div#pu8935 > a#u8946-5`
GDPR `div#pu8935 > div#u25286-5 > p#u25286-3 > a.nonblock`
ARTICLES `body.initialized > div#page > div#pu8935 > a#u8947-4`
WEBINARS `body.initialized > div#page > div#pu8935 > a#u8949-4`
SECURITY `body.initialized > div#page > div#pu8935 > a#u8950-4`
ABOUT US `body.initialized > div#page > div#pu8935 > a#u8951-4`
DMCA `body.initialized > div#page > div#pu8935 > a#u8952-4`
NEWS `body.initialized > div#page > div#pu8935 > a#u8953-4`
API `body.initialized > div#page > div#pu8935 > a#u8954-4`
CONTACT US `body.initialized > div#page > div#pu8935 > a#u8955-4`

These items highlight common accessibility best practices.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Our Privacy Policy `body.initialized > div.cc-window > span#cookieconsent:desc > a.cc-link`
Got it! `body.initialized > div.cc-window > div.cc-compliance > a.cc-btn`

○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

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

●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

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

●Document has a main landmark.

●Deprecated ARIA roles were not used

●The page contains a heading, skip link, or landmark region

●Uses ARIA roles only on compatible elements

○`[accesskey]` values are unique

○`[aria-hidden="true"]` elements do not contain focusable descendents

○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

○Buttons have an accessible name

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

○Heading elements appear in a sequentially-descending order

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

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

○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

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

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

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

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

○Identical links have the same purpose.

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

Alt Text Quality

All 24 images OK

PASS

All 24 images OK

24 decorative image(s) correctly marked

24 images 24 decorative

All images have appropriate alt text.

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.