Skip to content
https://www.linuxfoundation.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
35
GRADE
F
FIX
8
REVIEW
4
PASS
1
INFO
0
Checks
13
1 PASS 4 REVIEW 8 FIX
F
Heading Hierarchy
Action
33 headings, 6 skip(s)
FIX
33 headings, 6 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H6 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H4 Search
  • H1 Decentralized innovation.Built on trust.
  • H2 1300+
  • H2 4M+
  • H2 855K
  • H2 89M
  • H2 21K+
  • H2 229+
  • H2 100+
  • H2 Getting started is easy.
  • H3 Become a Member
  • H3 Host a Project
  • H2 Explore our projects.
  • H2 Management & Best Practices
  • H2 Security
  • H2 Digital Trust
  • H2 Sustainability
  • H6 LF EDUCATION skipped
  • H2 Live instructor learning is the gold standard
  • H2 From Linux and Kubernetes to Cybersecurity, PyTorch, Rust, and more, we offer the expert-led courses you need.
  • H2 Open Source Summit North America
  • H4 May 18-20, 2026 | Minneapolis, Minnesota skipped
  • H6 FEATURED RESEARCH skipped
  • H2 ROI for Open Source Software Contribution
  • H2 The latest from the Linux Foundation
  • H6 Announcement skipped
  • H4 Linux Foundation Announces the FAIR Package Manager Project for Open Source Content Management System Stability
  • H6 Announcement skipped
  • H4 Linux Foundation Wins Not-For-Profit and Education Team of the Year at 2025 World Trademark Review Industry Awards
  • H6 Announcement skipped
  • H4 Linux Foundation and OpenSSF Release Cybersecurity Skills Framework to Strengthen Enterprise Readiness
  • H3 Stay Connected with the Linux Foundation
  • H3 (empty)

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

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

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

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

F
Alt Text Quality
Action
26 of 34 images have issues
FIX
26 of 34 images have issues
Critical::
25 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
25 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Warning::
1 image(s) with filename as alt text
Info::
8 image(s) with good alt text
34 images 8 good alt text 1 generic 25 missing
IssueCount
missing25 image(s)
filename1 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

F
Favicon & Branding
Action
1 icon(s) detected
FIX
1 icon(s) detected
Info::
favicon.ico present at site root
Info::
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 Missing
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
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
No navigation patterns
FIX
No navigation patterns
Info::
19 navigation landmark(s) detected
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 19 <nav> element(s)
Back to Top
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.
C
Landmark Structure
Action
23 landmarks
REVIEW
23 landmarks
Info::
<main> landmark present
Warning::
Multiple <main> landmarks (2 found)
A page should have only one <main> landmark.
Info::
19 <nav> landmark(s) found
Warning::
1 of 19 <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.
Page Structure — as a screen reader sees it
BANNER header NAV "Navigation Menu" MAIN CONTENTINFO footer

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

C
Form Accessibility
Action
17 of 21 controls have issues
REVIEW
17 of 21 controls have issues
Critical::
17 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <select>; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="submit"> (+7 more)
Info::
4 control(s) properly labeled
21 controls
4 labeled
0 placeholder only
17 unlabeled
ControlTypeLabelMethod
termtextSearcharia-label
#firstname-e5c83800-1206-402c-9050-decfe094cca8_5878textFirst namefor/id
#lastname-e5c83800-1206-402c-9050-decfe094cca8_5878textLast namefor/id
#email-e5c83800-1206-402c-9050-decfe094cca8_5878emailEmail*for/id
#menu_arrowcheckbox(none)none
#menu_arrowcheckbox(none)none
#menu_arrowcheckbox(none)none
#menu_arrowcheckbox(none)none
#menu_arrowcheckbox(none)none
#menu_arrowcheckbox(none)none
selectselect(none)none
#menu_arrowcheckbox(none)none
#menu_arrowcheckbox(none)none
inputsubmit(none)none
#footer_menu_arrowcheckbox(none)none
#footer_menu_arrowcheckbox(none)none
#footer_menu_arrowcheckbox(none)none
#footer_menu_arrowcheckbox(none)none
#footer_menu_arrowcheckbox(none)none
#footer_menu_arrowcheckbox(none)none
#footer_menu_arrowcheckbox(none)none

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

<select>; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="checkbox" name="menu_arrow" id="menu_arrow">; <input type="submit"> (+7 more)

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
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
404 Page Quality Custom 404 Page
Status Code HTTP 404 Custom Styling Navigation Homepage Link Search Form
C
Lighthouse Accessibility Audits
Action
Score 76/100 — 7 failing, 24 passed
REVIEW
76

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.

ARIA

Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
PROJECTS div.footer__right-content-menu > div.footer__row-list > div.menu-group > div.child-menu_links
NEWSROOM div.footer__right-content-menu > div.footer__row-list > div.menu-group > div.child-menu_links
LF RESEARCH div.footer__right-content-menu > div.footer__row-list > div.menu-group > div.child-menu_links
LFX PLATFORM div.footer__right-content-menu > div.footer__row-list > div.menu-group > div.child-menu_links
RESOURCES div.footer__right-content-menu > div.footer__row-list > div.menu-group > div.child-menu_links
LF EVENTS div.footer__right-content-menu > div.footer__row-list > div.menu-group > div.child-menu_links
LF EDUCATION div.footer__right-content-menu > div.footer__row-list > div.menu-group > div.child-menu_links

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header__row > div.header_content > div.header-left > button.burger-button div.header__row > div.header_content > div.header-left > button.burger-button

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.header__row > div.header_branding > a > img div.header__row > div.header_branding > a > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.slick-track > div.slick-slide > div > img div.slick-track > div.slick-slide > div > img
div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img
div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img
div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img
div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img
div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img
div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image > img

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
header#js-top-header > div.header__row > div.header_branding > a header#js-top-header > div.header__row > div.header_branding > a
div.two-col-blocks__inner-content > div.two-col-blocks__supporting-content > p > a div.two-col-blocks__inner-content > div.two-col-blocks__supporting-content > p > a
div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image
div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image
div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image
div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image
div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image
div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image div.projects-tabs-col__container > div.flex-row > div.projects-tabs-col__wrapper-item > a.project__image
div.footer__container > div.footer__left > div.footer__social-links > a div.footer__container > div.footer__left > div.footer__social-links > a
div.footer__container > div.footer__left > div.footer__social-links > a div.footer__container > div.footer__left > div.footer__social-links > a
div.footer__container > div.footer__left > div.footer__social-links > a div.footer__container > div.footer__left > div.footer__social-links > a
div.footer__container > div.footer__left > div.footer__social-links > a div.footer__container > div.footer__left > div.footer__social-links > a
div.footer__container > div.footer__left > div.footer__social-links > a div.footer__container > div.footer__left > div.footer__social-links > a

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.

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
Privacy Policy div.osano-cm-window > div#1f02a6bf-3841-4e67-8d91-9a16514f037a > div.osano-cm-dialog__content > a.osano-cm-storage-policy
Storage Preferences div#1f02a6bf-3841-4e67-8d91-9a16514f037a > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link
Save div.osano-cm-window > div#1f02a6bf-3841-4e67-8d91-9a16514f037a > div.osano-cm-dialog__buttons > button.osano-cm-save
Accept All div.osano-cm-window > div#1f02a6bf-3841-4e67-8d91-9a16514f037a > div.osano-cm-dialog__buttons > button.osano-cm-accept-all
Reject Non-Essential div.osano-cm-window > div#1f02a6bf-3841-4e67-8d91-9a16514f037a > div.osano-cm-dialog__buttons > button.osano-cm-denyAll
LEARN MORE div.hero-img-mask__container > div.col6 > div.hero-img-mask__cta > a.hs-button
open source projects  div.counter-col__inner > div.counter-col__counter > div.counter-col__content > a.counter-col__link
developers trained  div.counter-col__inner > div.counter-col__counter > div.counter-col__content > a.counter-col__link
developers contributing code  div.counter-col__inner > div.counter-col__counter > div.counter-col__content > a.counter-col__link
lines of code added weekly  div.counter-col__inner > div.counter-col__counter > div.counter-col__content > a.counter-col__link
contributing organizations  div.counter-col__inner > div.counter-col__counter > div.counter-col__content > a.counter-col__link
upcoming events  div.counter-col__inner > div.counter-col__counter > div.counter-col__content > a.counter-col__link
standards and specifications  div.counter-col__inner > div.counter-col__counter > div.counter-col__content > a.counter-col__link
Meet our members. div.slider > div.slider > div.slider > a
Open Hardware div.projects-tabs-col > ul.filter-menu > li.filter-menu__link > label
Open Standards div.projects-tabs-col > ul.filter-menu > li.filter-menu__link > label
Open Data div.projects-tabs-col > ul.filter-menu > li.filter-menu__link > label
See all open software projects. div.projects-tabs-col__rich-text > div.projects-tabs-col__rich-link > p > a
SEE ALL PROJECTS section.section--widget_1662844101751 > div.projects-tabs-col > div.align--center > a.projects-tabs-col__button
Learn more p > span > strong > a
Learn more p > span > strong > a
SAVE NOW div.simple-img-mask__container > div.col6 > div.simple-img-mask__cta > a.hs-button
REGISTER NOW div.banner-img-mask__container > div.col6 > div.banner-img-mask__cta > a.hs-button
READ NOW div.banner-img-mask__container > div.col6 > div.banner-img-mask__cta > a.hs-button
NEWSROOM div.resources-cards > div.section-title__wrapper > div.section-title__link > a.section-title__link-text
fieldset.form-columns-3 > div.hs_firstname > div.input > input#firstname-e5c83800-1206-402c-9050-decfe094cca8_5878 fieldset.form-columns-3 > div.hs_firstname > div.input > input#firstname-e5c83800-1206-402c-9050-decfe094cca8_5878
fieldset.form-columns-3 > div.hs_lastname > div.input > input#lastname-e5c83800-1206-402c-9050-decfe094cca8_5878 fieldset.form-columns-3 > div.hs_lastname > div.input > input#lastname-e5c83800-1206-402c-9050-decfe094cca8_5878
fieldset.form-columns-3 > div.hs_email > div.input > input#email-e5c83800-1206-402c-9050-decfe094cca8_5878 fieldset.form-columns-3 > div.hs_email > div.input > input#email-e5c83800-1206-402c-9050-decfe094cca8_5878
Privacy Policy div.hs-richtext > p > u > a
form#hsForm_e5c83800-1206-402c-9050-decfe094cca8_5878 > div.hs_submit > div.actions > input.hs-button form#hsForm_e5c83800-1206-402c-9050-decfe094cca8_5878 > div.hs_submit > div.actions > input.hs-button

These are opportunities to improve the legibility of your content.

Navigation

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
LF EDUCATION div.simple-img-mask__wrapper > div.simple-img-mask__container > div.col6 > h6.simple-img-mask__pre-title
May 18-20, 2026 | Minneapolis, Minnesota div.banner-img-mask__container > div.col6 > div.banner-img-mask__supporting-content > h4
FEATURED RESEARCH div.banner-img-mask__wrapper > div.banner-img-mask__container > div.col6 > h6.banner-img-mask__pre-title
ANNOUNCEMENT div.resources-cards__container > a.box-widget_1661719294883 > div.resources-cards__content > h6.resources-cards__tagline
ANNOUNCEMENT div.resources-cards__container > a.box-widget_1661719294883 > div.resources-cards__content > h6.resources-cards__tagline
ANNOUNCEMENT div.resources-cards__container > a.box-widget_1661719294883 > div.resources-cards__content > h6.resources-cards__tagline

These are opportunities to improve keyboard navigation in your application.

Internationalization and localization

If a page doesn't specify a `lang` attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more about the `lang` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html html

These are opportunities to improve the interpretation of your content by users in different locales.

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-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
Input buttons have discernible text.
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 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
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.
Document has a main landmark.
Deprecated ARIA roles were not used
All heading elements contain content.
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
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
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has a valid value for its `[lang]` attribute
`<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.
`[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>`.
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.
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)
ElementRatioRequiredFGBGResult
h1 Decentralized innova…18.26:13.0:1
#000000
#EFEFEF
Pass
h1 Built on trust.18.26:13.0:1
#000000
#EFEFEF
Pass
h2 1300+18.26:13.0:1
#000000
#EFEFEF
Pass
h2 4M+18.26:13.0:1
#000000
#EFEFEF
Pass
h2 855K18.26:13.0:1
#000000
#EFEFEF
Pass
h2 89M18.26:13.0:1
#000000
#EFEFEF
Pass
h2 21K+18.26:13.0:1
#000000
#EFEFEF
Pass
h2 229+18.26:13.0:1
#000000
#EFEFEF
Pass
h2 100+18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Getting started is e…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Explore our projects…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Management & Best Pr…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Security18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Digital Trust18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Sustainability18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Live instructor lear…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 From Linux and Kuber…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 Open Source Summit N…18.26:13.0:1
#000000
#EFEFEF
Pass
h2 ROI for Open Source …18.26:13.0:1
#000000
#EFEFEF
Pass
h2 The latest from the …18.26:13.0:1
#000000
#EFEFEF
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.

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

Send Feedback