Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

7 PASS 2 REVIEW 4 FIX

Web Manifest

Action

Valid manifest

FIX

Valid manifest

No name or short_name

Add a name field to identify the app.

192x192 icon present

512x512 icon present

PWA Install Criteria Not Installable

Name ✗192×192 icon ✓512×512 icon ✓Start URL ✗Display Mode ✗

Icons 2 icon(s)

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 ✗

Form Accessibility

2 of 2 controls have issues

REVIEW

2 of 2 controls have issues

1 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <select id="languages-dropdown">

1 control(s) rely on placeholder only

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

Got: <input type="text" name="s" id="s">

2 controls

0 labeled

1 placeholder only

1 unlabeled

Control	Type	Label	Method
#s	text	(Search)	placeholder only
#languages-dropdown	select	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Why this matters

Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.

Source: WCAG 2.1 SC 3.3.2

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

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 Page not found - Creative Commons ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

A+

Landmark Structure

11 landmarks

PASS

11 landmarks

<main> landmark present

3 <nav> landmark(s) found

All <nav> elements are properly labeled

Skip navigation link present

Page Structure — as a screen reader sees it

A+

Heading Hierarchy

17 headings

PASS

17 headings

Single H1 present

H1 Creative Commons
H2 The commons belongs to us all
H2 Tools for building the commons
H2 Join us in shaping what’s next
H2 Celebrate CC’s 25th Anniversary
H2 Support CC In Style
H2 Empowering access to knowledge
H2 Protecting the Commons in the Age of AI
H2 Support CC and stay connected
H2 Recently from the blog
H3 Celebrating 25 Years of Choosing to Share
H3 CC Hosts Open Heritage Statement Event in Amsterdam
H3 AI’s Infrastructure Era: Reflections from the AI Impact Summit in Delhi
H3 CC Licenses, Data Governance, and the African Context: Conversations and Perspectives
H2 Get the latest CC news, and join the community to empower individuals and communities around the world.
H2 Contact Us
H2 Subscribe to our newsletter

A+

Alt Text Quality

All 18 images OK

PASS

All 18 images OK

2 image(s) with alt text over 125 characters

3 decorative image(s) correctly marked

13 image(s) with good alt text

18 images 13 good alt text 3 decorative

Issue	Count
too long	2 image(s)

Link & Button Quality

100 links, 8 buttons — all OK

PASS

100 links, 8 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://bsky.app/profile/creativecommons.bsky.social; https://mastodon.social/@creativecommons; https://www.linkedin.com/company/creative-commons/; https://fontawesome.com/

96 link(s) with descriptive text

100 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://bsky.app/profile/creativecommons…	Bluesky	new tab	Add '(opens in new tab)' to text
https://mastodon.social/@creativecommons	Mastodon	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/creativ…	LinkedIn	new tab	Add '(opens in new tab)' to text
https://fontawesome.com/	Font Awesome	new tab	Add '(opens in new tab)' to text

104 links and buttons have descriptive text

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

https://bsky.app/profile/creativecommons.bsky.social; https://mastodon.social/@creativecommons; https://www.linkedin.com/company/creative-commons/; https://fontawesome.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

Favicon & Branding

6 icon(s) detected

PASS

6 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

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
h2 The commons belongs …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Tools for building t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Join us in shaping w…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Celebrate CC’s 25t…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Support CC In Style	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Empowering access to…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Protecting the Commo…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Support CC and stay …	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Recently from the bl…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Get the latest CC ne…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Contact Us	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Subscribe to our new…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title The commons belongs …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Skip to content	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Languages available	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option aragonés	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Azərbaycanca	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Bahasa Indonesia	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option Basque	21.00:1	4.5:1	#000000	#FFFFFF	Pass
option català	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.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 23 passed

PASS

100

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.

○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

●Form elements have associated labels

●`[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 use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links are distinguishable without relying on color.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Skip links are focusable.

●Document has a main landmark.

●Identical links have the same purpose.

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

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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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

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

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

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