Skip to content
https://www.jenkins.io

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
4
REVIEW
7
PASS
2
INFO
0
Checks
13
2 PASS 7 REVIEW 4 FIX
D
Landmark Structure
Action
No landmarks
FIX
No landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Warning::
No <nav> landmark found
Info::
No banner (header) landmark
Info::
No contentinfo (footer) landmark
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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Heading Hierarchy
24 headings, 2 skip(s)
REVIEW
24 headings, 2 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.
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 Jenkins
  • H2 Redesigned Jenkins header and UI
  • H2 Jenkins 2025 Community Awards
  • H2 Jenkins wins DevOps Dozen award
  • H2 Announcing the new Jenkins Bug Bounty Program!
  • H2 Meet the driving forces
  • H2 Jenkins Stories!
  • H2 Participate and Contribute!
  • H5 Continuous Integration and Continuous Delivery skipped
  • H5 Easy installation
  • H5 Easy configuration
  • H5 Plugins
  • H5 Extensible
  • H5 Distributed
  • H2 Recent posts
  • H5 Plugin of the Month – April 2026: Pipeline Graph View skipped
  • H5 JetBrains Report Highlights Jenkins as a Popular CI/CD Tool in 2026
  • H5 Redesigned Credentials in Jenkins
  • H5 Introducing the Chinese Workday Plugin
  • H5 Revamped Build Monitor plugin
  • H5 Introducing the Jenkins Plugin of the Month
  • H5 Jenkins Contributor Summit: Officers View on the Present and Future
  • H5 Jenkins Contributor Awards 2026 - Nominations are Open
  • H5 Impressions from Jenkins Contributor Summit in Brussels

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

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✗Homepage Link ✓Search Form ✗
B
Favicon & Branding
7 icon(s) detected
REVIEW
7 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
B
Web Manifest
Valid manifest
REVIEW
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name ✗192×192 icon ✓512×512 icon ✓Start URL https://jenkins.io/ ✓Display Mode standalone ✓
Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 2 icon(s)
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
Dark-specific theme-color detected
A theme-color with media='(prefers-color-scheme: dark)' adapts the browser toolbar for dark mode.
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color jenkins ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Jenkins
1.36:1
#000000
on
#212529
needs 4.5:1 (normal text)
16px · top of page (header area)
span Jenkins
1.36:1
#000000
on
#212529
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Redesigned Jenkins h…19.96:13.0:1
#000000
#F9F9FA
Pass
h2 Jenkins 2025 Communi…19.96:13.0:1
#000000
#F9F9FA
Pass
h2 Jenkins wins DevOps …19.96:13.0:1
#000000
#F9F9FA
Pass
h2 Announcing the new J…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Meet the driving for…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Jenkins Stories!21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Participate and Cont…5.86:13.0:1
#000000
#ED5321
Pass
h2 Recent posts5.86:13.0:1
#000000
#ED5321
Pass
title Jenkins1.36:14.5:1
#000000
#212529
Fail
span Jenkins1.36:14.5:1
#000000
#212529
Fail
strong Build great things a…19.96:13.0:1
#000000
#F9F9FA
Pass
p The leading open sou…19.96:14.5:1
#000000
#F9F9FA
Pass
a Download19.96:14.5:1
#000000
#F9F9FA
Pass
a Documentation19.96:14.5:1
#000000
#F9F9FA
Pass
p Jenkins' UI has been…19.96:14.5:1
#000000
#F9F9FA
Pass
a Read here19.96:14.5:1
#000000
#F9F9FA
Pass
p The Jenkins 2025 Com…19.96:14.5:1
#000000
#F9F9FA
Pass
a Read more about the …19.96:14.5:1
#000000
#F9F9FA
Pass
p Jenkins has been awa…21.00:14.5:1
#000000
#FFFFFF
Pass
a More info21.00:14.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.

C
Lighthouse Accessibility Audits
Action
Score 71/100 — 8 failing, 18 passed
REVIEW
71

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.

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#ProjectCarousel_590 > div.container > div.carousel-indicators > button.active div#ProjectCarousel_590 > div.container > div.carousel-indicators > button.active
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > button
div#ProjectCarousel_590 > div.container > div.carousel-indicators > button div#ProjectCarousel_590 > div.container > div.carousel-indicators > 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.container > div.row > div.col-md-5 > img div.container > div.row > div.col-md-5 > img

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container > div.section > div.video > iframe div.container > div.section > div.video > iframe

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.container > div.row > div.col-md-12 > a div.container > div.row > div.col-md-12 > a
div.sponsors > ul > li > a div.sponsors > ul > li > a
div.sponsors > ul > li > a div.sponsors > ul > li > a
div.sponsors > ul > li > a div.sponsors > ul > li > a
div.sponsors > ul > li > a div.sponsors > ul > li > a
div.sponsors > ul > li > a div.sponsors > ul > li > 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
Download div.row > div.col-md-5 > div > a.app-button
Atlassian div.supporters > ul > li > a
Datadog div.supporters > ul > li > a
DigitalOcean div.supporters > ul > li > a
Discourse div.supporters > ul > li > a
Fastly div.supporters > ul > li > a
IBM div.supporters > ul > li > a
Netlify div.supporters > ul > li > a
PagerDuty div.supporters > ul > li > a
Sentry div.supporters > ul > li > a
Tsinghua University div.supporters > ul > li > a
XMission div.supporters > ul > li > a
Belnet div.supporters > ul > li > a
RWTH Aachen University div.supporters > ul > li > a
Hostico div.supporters > ul > li > a
FreeDif div.supporters > ul > li > a
Servana div.supporters > ul > li > a
Yamagata University div.supporters > ul > li > a
ProthamD div.contributor-data > div.desc-div > p > a
contributor-spotlight div.contributor-data > div.desc-div > p > a

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
Continuous Integration and Continuous Delivery div.row > div.col-md-6 > div.box > h5
Plugin of the Month – April 2026: Pipeline Graph View ul.app-cards > li.app-card > a > h5.app-card__title

These are opportunities to improve keyboard navigation in your application.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Plugins div.div-mar > ul.resources > li > a
Security div.div-mar > ul.resources > li > a
Roadmap div.div-mar > ul.project > li > a
GitHub div.div-mar > ul.project > li > a
Forum div.div-mar > ul.community > li > a
Events div.div-mar > ul.community > li > a
LinkedIn div.div-mar > ul.community > li > a
Bluesky div.div-mar > ul.community > li > a
Mastodon div.div-mar > ul.community > li > a
Youtube div.div-mar > ul.community > li > a
Reddit div.div-mar > ul.community > li > a
Artwork div.div-mar > ul.other > li > a
Awards div.div-mar > ul.other > li > a

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html.hydrated html.hydrated

These items highlight common accessibility best practices.

○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
●`[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
●`[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
●Deprecated ARIA roles were not used
●Image elements do not have `[alt]` attributes that are redundant text.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○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
○`<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
○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.
○Uses ARIA roles only on compatible elements
○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.
A
Alt Text Quality
1 of 27 images have issues
PASS
1 of 27 images have issues
Critical::
1 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
7 decorative image(s) correctly marked
Info::
19 image(s) with good alt text
27 images 19 good alt text 7 decorative 1 missing
IssueCount
missing1 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

A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback