Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

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

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

Skip Link

Labeled Navigation 2 <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.

Heading Hierarchy

19 headings, 1 skip(s)

REVIEW

19 headings, 1 skip(s)

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H4 (missing H2)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H2 Growing the impact of Open Source around the world
H3 Supported by the whole Open Source ecosystem
H2 Open Source licenses: The cornerstone of an 8.8 trillion dollar industry
H1 THE open source ai definition 1.0
H4 We have released the first stable version of the Definition. skipped
H2 OSI News
H2 Welcoming the New Executive Director!
H2 Welcoming Duane O’Brien as Executive Director of the Open Source Initiative
H2 Open Source Initiative Appoints Duane O’Brien as Executive Director
H2 ClearlyDefined: A Three-Year Roadmap for Sustainability and Growth
H2 OSI Newsletter
H2 Subscribe to our newsletter
H2 About
H2 Licenses
H2 Open Source AI
H2 Community
H1 Search results duplicate H1
H2 No results found
H2 Filter options

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

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

Form Accessibility

2 of 8 controls have issues

REVIEW

2 of 8 controls have issues

2 control(s) without accessible label

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

Got: <input type="email" name="email">; <input type="submit">

6 control(s) properly labeled

8 controls

6 labeled

0 placeholder only

2 unlabeled

Control	Type	Label	Method
#cmplz-functional-optin	checkbox	Functional	for/id
#cmplz-preferences-optin	checkbox	Preferences	for/id
#cmplz-statistics-optin	checkbox	Statistics	for/id
#cmplz-marketing-optin	checkbox	Marketing	for/id
_wpcf7_ak_hp_textarea	textarea	Δ	none
#jetpack-instant-search__box-input-1	search	Magnifying Glass	none
email	email	(none)	none
input	submit	(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

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Open Source Initiative ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

4 icon(s) detected

REVIEW

4 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

Landmark Structure

8 landmarks

PASS

8 landmarks

<main> landmark present

2 <nav> landmark(s) found

All <nav> elements are properly labeled

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

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

Alt Text Quality

32 of 40 images have issues

PASS

32 of 40 images have issues

32 image(s) with generic alt text

6 decorative image(s) correctly marked

2 image(s) with good alt text

40 images 2 good alt text 6 decorative 32 generic

Issue	Count
generic	32 image(s)

Link & Button Quality

67 links, 13 buttons — all OK

PASS

67 links, 13 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://cookiedatabase.org/tcf/purposes/; https://wordpress.com/wp/?partner_domain=opensource.org&utm_source=Automattic…; https://pressable.com/?utm_source=Automattic&utm_medium=rpc&utm_campaign=Conc…; https://jetpack.com/upgrade/search/?utm_source=poweredby

63 link(s) with descriptive text

67 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://cookiedatabase.org/tcf/purposes/	Read more about TCF purposes o…	new tab	Add '(opens in new tab)' to text
https://wordpress.com/wp/?partner_domain…	Proudly powered by WordPress.	new tab	Add '(opens in new tab)' to text
https://pressable.com/?utm_source=Automa…	Hosted by Pressable.	new tab	Add '(opens in new tab)' to text
https://jetpack.com/upgrade/search/?utm_…	Search powered by Jetpack	new tab	Add '(opens in new tab)' to text

76 links and buttons have descriptive text

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

https://cookiedatabase.org/tcf/purposes/; https://wordpress.com/wp/?partner_domain=opensource.org&utm_source=Automattic…; https://pressable.com/?utm_source=Automattic&utm_medium=rpc&utm_campaign=Conc…; https://jetpack.com/upgrade/search/?utm_source=poweredby

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

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 THE	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 definition 1.0	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h1 Search results	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Growing the impact o…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Open Source licenses…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 OSI News	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 OSI Newsletter	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Subscribe to our new…	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 About	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Licenses	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Open Source AI	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Community	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 No results found	21.00:1	3.0:1	#000000	#FFFFFF	Pass
h2 Filter options	21.00:1	3.0:1	#000000	#FFFFFF	Pass
title Open Source Initiati…	18.88:1	4.5:1	#000000	#F2F3F2	Pass
div Manage Cookie Consen…	18.88:1	4.5:1	#000000	#F2F3F2	Pass
div To provide the best …	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Functional	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Functional	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Always active	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 91/100 — 3 failing, 26 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.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`
Image `div.has-carousel > div.swiper-wrapper > div.swiper-slide > div.coblocks-gallery--item`

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
We have released the first stable version of the Definition. `article#post-136840 > div.entry-content > section.wp-block-group > h4.wp-block-heading`

These are opportunities to improve keyboard navigation in your application.

Names and labels

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#newsletter > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control `div#newsletter > p > span.wpcf7-form-control-wrap > input.wpcf7-form-control`

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.

○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

●Input buttons have discernible text.

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

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

●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

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

●`[lang]` attributes have a valid value

●Document has a main landmark.

●Deprecated ARIA roles were not used

○`[accesskey]` values are unique

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

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

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

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

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