Skip to content
https://openid.net

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
67
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation 4 <nav> element(s)
Back to Top
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.
B
Landmark Structure
10 landmarks
REVIEW
10 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
2 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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.
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV "Menu" SEARCH MAIN CONTENTINFO footer

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

B
Heading Hierarchy
26 headings
REVIEW
26 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 DISCOVER
  • H3 DISCOVER
  • H3 HOW
  • H3 HOW
  • H3 JOIN
  • H3 JOIN
  • H3 Our mission is to lead the global community in creating identity standards that are secure, interoperable and privacy-preserving.
  • H3 Enable real-world identity use cases
  • H3 FIND A WORKING GROUP
  • H3 FIND A WORKING GROUP
  • H3 EXPLORE SPECIFICATIONS
  • H3 EXPLORE SPECIFICATIONS
  • H3 CERTIFY YOUR IMPLEMENTATION
  • H3 CERTIFY YOUR IMPLEMENTATION
  • H3 Stay up to-date and engage with community experts
  • H3 NEWS
  • H3 NEWS
  • H3 EVENTS
  • H3 EVENTS
  • H3 PAPERS
  • H3 PAPERS
  • H4 Connect with us
  • H4 REACH THE FOUNDATION
  • H4 ABOUT
  • H4 EXPLORE
  • H4 ENGAGE:

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h3 DISCOVER
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 DISCOVER
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 HOW
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 HOW
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 JOIN
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 JOIN
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Our mission is to lead the global commun…
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Enable real-world identity use cases
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 FIND A WORKING GROUP
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 FIND A WORKING GROUP
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 EXPLORE SPECIFICATIONS
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 EXPLORE SPECIFICATIONS
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CERTIFY YOUR IMPLEMENTATION
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 CERTIFY YOUR IMPLEMENTATION
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Stay up to-date and engage with communit…
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 NEWS
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 NEWS
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 EVENTS
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 EVENTS
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PAPERS
2.66:1
#000000
on
#A0025C
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 DISCOVER2.66:13.0:1
#000000
#A0025C
Fail
h3 DISCOVER2.66:13.0:1
#000000
#A0025C
Fail
h3 HOW2.66:13.0:1
#000000
#A0025C
Fail
h3 HOW2.66:13.0:1
#000000
#A0025C
Fail
h3 JOIN2.66:13.0:1
#000000
#A0025C
Fail
h3 JOIN2.66:13.0:1
#000000
#A0025C
Fail
h3 Our mission is to le…2.66:13.0:1
#000000
#A0025C
Fail
h3 Enable real-world id…2.66:13.0:1
#000000
#A0025C
Fail
h3 FIND A WORKING GROUP2.66:13.0:1
#000000
#A0025C
Fail
h3 FIND A WORKING GROUP2.66:13.0:1
#000000
#A0025C
Fail
h3 EXPLORE SPECIFICATIO…2.66:13.0:1
#000000
#A0025C
Fail
h3 EXPLORE SPECIFICATIO…2.66:13.0:1
#000000
#A0025C
Fail
h3 CERTIFY YOUR IMPLEME…2.66:13.0:1
#000000
#A0025C
Fail
h3 CERTIFY YOUR IMPLEME…2.66:13.0:1
#000000
#A0025C
Fail
h3 Stay up to-date and …2.66:13.0:1
#000000
#A0025C
Fail
h3 NEWS2.66:13.0:1
#000000
#A0025C
Fail
h3 NEWS2.66:13.0:1
#000000
#A0025C
Fail
h3 EVENTS2.66:13.0:1
#000000
#A0025C
Fail
h3 EVENTS2.66:13.0:1
#000000
#A0025C
Fail
h3 PAPERS2.66:13.0:1
#000000
#A0025C
Fail

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+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
A+
Form Accessibility
All 6 controls labeled
PASS
All 6 controls labeled
Info::
6 control(s) properly labeled
6 controls
6 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cmplz-functional-optincheckboxFunctionalfor/id
#cmplz-preferences-optincheckboxPreferencesfor/id
#cmplz-statistics-optincheckboxStatisticsfor/id
#cmplz-marketing-optincheckboxMarketingfor/id
#elementor-search-form-eb7055asearchSearchfor/id
#elementor-search-form-eb7055asearchSearchfor/id
A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found – OpenID Foundation ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A
Lighthouse Accessibility Audits
Score 94/100 — 2 failing, 31 passed
PASS
94

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
Accept div#cmplz-cookiebanner-container > div.cmplz-cookiebanner > div.cmplz-buttons > button.cmplz-btn
search > form.elementor-search-form > div.elementor-search-form__container > input#elementor-search-form-eb7055a search > form.elementor-search-form > div.elementor-search-form__container > input#elementor-search-form-eb7055a
Sign-In div.elementor-button-wrapper > a.elementor-button > span.elementor-button-content-wrapper > span.elementor-button-text
Founded in 2007, the OpenID Foundation (OIDF) is a global open standards body c… div.elementor-element > div.elementor-widget-container > p > span
Find an existing working group, explore all the specifications you can develop … div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p
Expand your knowledge base through our news, whitepapers, and presentations plu… div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p
More News div.elementor-flip-box__layer__overlay > div.elementor-flip-box__layer__inner > div.elementor-flip-box__layer__description > a.more_info_button
More Events div.elementor-flip-box__layer__overlay > div.elementor-flip-box__layer__inner > div.elementor-flip-box__layer__description > a.more_info_button
More Papers div.elementor-flip-box__layer__overlay > div.elementor-flip-box__layer__inner > div.elementor-flip-box__layer__description > a.more_info_button
CONNECT WITH US div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > h4.elementor-heading-title
Adjust Cookie Setting div.elementor-widget-wrap > div.elementor-element > div.elementor-widget-container > p

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
div.cmplz-documents > ul > li > a.cmplz-link div.cmplz-documents > ul > li > a.cmplz-link

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
●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
●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.
●`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.
●`[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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●`[lang]` attributes have a valid value
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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
○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.
○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.
○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.

Send Feedback