Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 3 REVIEW 2 FIX

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 ✗

Link & Button Quality

14 links, 2 buttons — all OK

REVIEW

14 links, 2 buttons — all OK

4 image-only link(s) without alt text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

Got: a[href="https://www.g2.com/products/padlet/reviews"]; a[href="https://apps.apple.com/us/app/padlet/id834618886?see-all=reviews"]; a[href="https://padlet.link/capterra"]; a[href="https://play.google.com/store/apps/details?id=com.wallwisher.Padlet"]

10 link(s) with descriptive text

14 links

0 empty

0 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.g2.com/products/padlet/revie…	See reviews of Padlet in G2.co…	img no alt	Add alt attribute to the image
https://apps.apple.com/us/app/padlet/id8…	See reviews of Padlet in App S…	img no alt	Add alt attribute to the image
https://padlet.link/capterra	See reviews of Padlet in Capte…	img no alt	Add alt attribute to the image
https://play.google.com/store/apps/detai…	See reviews of Padlet in Googl…	img no alt	Add alt attribute to the image

12 links and buttons have descriptive text

Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.

a[href="https://www.g2.com/products/padlet/reviews"]; a[href="https://apps.apple.com/us/app/padlet/id834618886?see-all=reviews"]; a[href="https://padlet.link/capterra"]; a[href="https://play.google.com/store/apps/details?id=com.wallwisher.Padlet"]

Why this matters

Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.

Source: WCAG 2.1 SC 2.4.4

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 404 – Not found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

Dark-specific theme-color detected

A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.

prefers-color-scheme CSS detected in inline styles

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark Mode✓ Dark Mode Supported

color-scheme meta Not set ✗Dark theme-color rgb(17,17,17) ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

Landmark Structure

2 landmarks

PASS

2 landmarks

<main> landmark present

No <nav> landmark found

No contentinfo (footer) landmark

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 Visual collaboration for creative work and education
H2 We have boards
H2 We have sandboxes
H2 Thanks to the academy... 🏆
H2 40 million users worldwide
H2 Get started

Alt Text Quality

1 of 7 images have issues

PASS

1 of 7 images have issues

1 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

6 decorative image(s) correctly marked

7 images 6 decorative 1 missing

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

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Favicon & Branding

12 icon(s) detected

PASS

12 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

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✓ SVG Favicon Present

✓ Manifest Icons Present

✓ Multiple Sizes Present

Web Manifest

Valid manifest

PASS

Valid manifest

Name present: Padlet

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name Padlet ✓192×192 icon ✓512×512 icon ✓Start URL https://padlet.com/dashboard?utm_source=pwa ✓Display Mode browser ✗

Name Padlet Display Mode browser Theme Color white Background Color #F8F8F8 Icons 8 icon(s)

A+

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

PASS

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

20 pass

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Visual collaboration	16.92:1	3.0:1	#000000	#C0EEFF	Pass
h1 for creative work	16.92:1	3.0:1	#000000	#C0EEFF	Pass
h1 and education	16.92:1	3.0:1	#000000	#C0EEFF	Pass
h2 We have boards	16.92:1	3.0:1	#000000	#C0EEFF	Pass
h2 We have sandboxes	16.92:1	3.0:1	#000000	#C0EEFF	Pass
h2 Thanks to the academ…	15.01:1	3.0:1	#000000	#C3E776	Pass
h2 40 million users wor…	15.01:1	3.0:1	#000000	#C3E776	Pass
h2 Get started	15.01:1	3.0:1	#000000	#C3E776	Pass
title Padlet - Visual Coll…	16.92:1	4.5:1	#000000	#C0EEFF	Pass
span Skip to content	16.92:1	4.5:1	#000000	#C0EEFF	Pass
span Get a quote	16.92:1	4.5:1	#000000	#C0EEFF	Pass
span Log in	16.92:1	4.5:1	#000000	#C0EEFF	Pass
span Sign up	16.92:1	4.5:1	#000000	#C0EEFF	Pass
p Used by 40 million b…	16.92:1	4.5:1	#000000	#C0EEFF	Pass
span Sign up - it’s fre…	16.92:1	4.5:1	#000000	#C0EEFF	Pass
p Collect, organize, a…	16.92:1	4.5:1	#000000	#C0EEFF	Pass
span Make a board	16.92:1	4.5:1	#000000	#C0EEFF	Pass
span Explore more	16.92:1	4.5:1	#000000	#C0EEFF	Pass
p Digital canvases for…	16.92:1	4.5:1	#000000	#C0EEFF	Pass
span Make a sandbox	16.92:1	4.5:1	#000000	#C0EEFF	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.

A+

Lighthouse Accessibility Audits

Score 96/100 — 2 failing, 24 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

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
Log in `div.relative > div.flex > a.no-underline > span.flex-1`
Sign up `div.relative > div.flex > a.no-underline > span.flex-1`
Sign up - it’s free `div.flex > div.flex > a.no-underline > span.flex-1`
Make a board `div.flex > div.flex > a.no-underline > span.flex-1`
Explore more `div.flex > div.flex > a.no-underline > span.flex-1`
Make a sandbox `div.flex > div.flex > a.no-underline > span.flex-1`
Explore more `div.flex > div.flex > a.no-underline > span.flex-1`
Sign up for free `div.flex > div.flex > a.no-underline > span.flex-1`
Product `nav.px-2 > button.select-none > div.flex > h2#ProductFooterSectionTitle`
Solutions `nav.px-2 > button.select-none > div.flex > h2#SolutionsFooterSectionTitle`
Support `nav.px-2 > button.select-none > div.flex > h2#SupportFooterSectionTitle`
Company `nav.px-2 > button.select-none > div.flex > h2#CompanyFooterSectionTitle`
Legal `nav.px-2 > button.select-none > div.flex > h2#LegalFooterSectionTitle`
English (US) `section > div > button.select-none > span.me-1.5`

These are opportunities to improve the legibility of your content.

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
G2.com 4.9 Padlet has a rating of 4.9 out of 5 on G2.com `div.w-full > article.flex > div.flex > a.no-underline`
App Store 4.6 Padlet has a rating of 4.6 out of 5 on App Store `div.w-full > article.flex > div.flex > a.no-underline`
Capterra 4.9 Padlet has a rating of 4.9 out of 5 on Capterra `div.w-full > article.flex > div.flex > a.no-underline`
Google Play 4.8 Padlet has a rating of 4.8 out of 5 on Google Play `div.w-full > article.flex > div.flex > a.no-underline`

○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

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

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

●Links have a discernible name

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○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

○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

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

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

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

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

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