Skip to content
https://apache.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
66
GRADE
D
FIX
4
REVIEW
4
PASS
5
INFO
0
Checks
13
5 PASS 4 REVIEW 4 FIX
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Apache
Info::
192x192 icon present
PWA Install Criteria Not Installable
Name Apache ✓192×192 icon ✓512×512 icon ✗Start URL ✗Display Mode ✗
Name Apache Icons 6 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
Theme-color present but no dark variant
A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.
Got: #282661
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 ModePartial Dark Mode
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
Breadcrumbs
Search role='search' landmark
Skip Link
Labeled Navigation
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.
B
Landmark Structure
5 landmarks
REVIEW
5 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 SEARCH MAIN CONTENTINFO footer

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
404 Error Page
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
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title 404 | Apache Software Foundation ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Favicon & Branding
22 icon(s) detected
REVIEW
22 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 Present
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 17 fail WCAG AA
REVIEW

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

3 pass 17 fail WCAG AA
h1 Software For The Public Good
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
32px · bottom of viewport
h2 Our Impact
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Open Source Projects
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Incubating Projects
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Incubate a Project
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Everyone is Welcome
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Upcoming Events
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Thank You, Sponsors
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ASF Plus One
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Growing Together
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Subscribe to ASF Plus One, Our Monthly N…
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Flink Forward 2026
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Iceberg Summit 2026
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Most Recent Blog Posts
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Plus One Newsletter
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Plus One Podcast
1.53:1
#000000
on
#28265E
needs 3.0:1 (large text)
19px · bottom of viewport
title Welcome to The Apache Software Foundatio…
2.47:1
#000000
on
#7C297D
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Software For The Pub…1.53:13.0:1
#000000
#28265E
Fail
h2 Our Impact1.53:13.0:1
#000000
#28265E
Fail
h2 Our Open Source Proj…1.53:13.0:1
#000000
#28265E
Fail
h2 Our Incubating Proje…1.53:13.0:1
#000000
#28265E
Fail
h2 Incubate a Project1.53:13.0:1
#000000
#28265E
Fail
h2 Everyone is Welcome1.53:13.0:1
#000000
#28265E
Fail
h2 Upcoming Events1.53:13.0:1
#000000
#28265E
Fail
h2 Thank You, Sponsors1.53:13.0:1
#000000
#28265E
Fail
h2 ASF Plus One1.53:13.0:1
#000000
#28265E
Fail
h2 Growing Together1.53:13.0:1
#000000
#28265E
Fail
h2 Subscribe to ASF Plu…1.53:13.0:1
#000000
#28265E
Fail
h3 Flink Forward 20261.53:13.0:1
#000000
#28265E
Fail
h3 Iceberg Summit 20261.53:13.0:1
#000000
#28265E
Fail
h3 Most Recent Blog Pos…1.53:13.0:1
#000000
#28265E
Fail
h3 Plus One Newsletter1.53:13.0:1
#000000
#28265E
Fail
h3 Plus One Podcast1.53:13.0:1
#000000
#28265E
Fail
title Welcome to The Apach…2.47:14.5:1
#000000
#7C297D
Fail
p Introducing The ASF…10.08:14.5:1
#000000
#CBA9CB
Pass
a Read Now21.00:14.5:1
#000000
#FFFFFF
Pass
span Toggle navigation19.60:14.5:1
#000000
#F7F7F7
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
Heading Hierarchy
35 headings, 1 skip(s)
PASS
35 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Software For The Public Good¶
  • H2 Our Impact¶
  • H2 Our Open Source Projects¶
  • H2 Our Incubating Projects¶
  • H2 Incubate a Project¶
  • H2 Everyone is Welcome¶
  • H2 Upcoming Events¶
  • H3 Flink Forward 2026¶
  • H4 Shenzen, China¶
  • H5 July 11-12, 2026
  • H3 Iceberg Summit 2026¶
  • H4 San Francisco, CA, USA¶
  • H5 April 8 - April 9 2026
  • H2 Thank You, Sponsors¶
  • H2 ASF Plus One¶
  • H3 Most Recent Blog Posts¶
  • H4 The Apache Software Foundation Welcomes 45 New Members¶
  • H4 The Apache Software Foundation Launches $10M Responsible AI Initiative with Initial $1.75M Donation¶
  • H4 The Apache Software Foundation Announces $1.5M Donation from Anthropic¶
  • H3 Plus One Newsletter¶
  • H4 ASF Plus One Newsletter: March 2026¶
  • H4 ASF Plus One Newsletter: February 2026¶
  • H4 ASF Plus One Newsletter: January 2026¶
  • H3 Plus One Podcast¶
  • H4 Chris Dutz, new Director at the ASF¶
  • H4 Apache Grails: James Fredley and James Daugherty¶
  • H4 Airflow 3.x and beyond¶
  • H2 Growing Together¶
  • H2 Subscribe to ASF Plus One, Our Monthly Newsletter
  • H5 Community skipped
  • H5 Learn
  • H5 Projects
  • H5 Resources & Tools
  • H5 Downloads
  • H5 About

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

A
Alt Text Quality
8 of 54 images have issues
PASS
8 of 54 images have issues
Warning::
8 image(s) with generic alt text
Info::
46 image(s) with good alt text
54 images 46 good alt text 8 generic
IssueCount
generic8 image(s)
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text">
1 controls
0 labeled
1 placeholder only
0 unlabeled
ControlTypeLabelMethod
inputtext(Search)placeholder only

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

<input type="text">

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

A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 20 passed
PASS
98

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

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
Community div.flex-1 > div.footer-nav-col > div.footer-nav-group > h5.white

These are opportunities to improve keyboard navigation in your application.

○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
●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-hidden="true"]` elements do not contain focusable descendents
●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
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`[aria-*]` attributes match their roles
○`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 input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○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
○`[aria-*]` attributes have valid values
○`[aria-*]` attributes are valid and not misspelled
○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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○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.
○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