Skip to content
https://openjdk.org

Accessibility

· 12 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
6
REVIEW
2
PASS
4
INFO
0
Checks
12
4 PASS 2 REVIEW 6 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

F
Favicon & Branding
Action
No icons detected
FIX
No icons detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
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'>.
Critical::
No favicon or icon links detected
Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.
✗ favicon.ico Missing
✗ 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
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.
D
Lighthouse Accessibility Audits
Action
Score 57/100 — 5 failing, 8 passed
FIX
57

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
(overview, archive) body > div#sidebar > div.links > div.link
(overview, archive) body > div#sidebar > div.links > div.link
JDK (…, 25, 26, 27) body > div#sidebar > div.links > div.link
© 2026 Oracle Corporation and/or its affiliates Terms of Use · License: GPLv2 ·… body > div#footer
Terms of Use body > div#footer > a
GPLv2 body > div#footer > a
Privacy body > div#footer > a
Trademarks body > div#footer > a

These are opportunities to improve the legibility of your content.

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.

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
OpenJDK logo body > div#sidebar > div#openjdk-sidebar-logo > 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.

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
Installing div#sidebar > div.links > div.link > a
Contributing div#sidebar > div.links > div.link > a
Sponsoring div#sidebar > div.links > div.link > a
Developers' Guide div#sidebar > div.links > div.link > a
Vulnerabilities div#sidebar > div.links > div.link > a
JDK GA/EA Builds div#sidebar > div.links > div.link > a
Mailing lists div#sidebar > div.links > div.links > a
Mastodon div#sidebar > div.links > div.link > a
Bluesky div#sidebar > div.links > div.link > a
Workshop div#sidebar > div.links > div.links > a
JEP Process div#sidebar > div.links > div.links > a
GitHub div#sidebar > div.links > div.link > a
Mercurial div#sidebar > div.links > div.link > a
Git div#sidebar > div.links > div.link > a
Adoption div#sidebar > div.links > div.link > a
Build div#sidebar > div.links > div.link > a
Client Libraries div#sidebar > div.links > div.link > a
Compiler div#sidebar > div.links > div.link > a
Conformance div#sidebar > div.links > div.link > a
Core Libraries div#sidebar > div.links > div.link > a
Governing Board div#sidebar > div.links > div.link > a
HotSpot div#sidebar > div.links > div.link > a
IDE Tooling & Support div#sidebar > div.links > div.link > a
Internationalization div#sidebar > div.links > div.link > a
Members div#sidebar > div.links > div.link > a
Networking div#sidebar > div.links > div.link > a
Porters div#sidebar > div.links > div.link > a
Quality div#sidebar > div.links > div.link > a
Security div#sidebar > div.links > div.link > a
Serviceability div#sidebar > div.links > div.link > a
Vulnerability div#sidebar > div.links > div.link > a
Web div#sidebar > div.links > div.link > a
Amber div#sidebar > div.links > div.link > a
Babylon div#sidebar > div.links > div.link > a
Brisbane div#sidebar > div.links > div.link > a
CRaC div#sidebar > div.links > div.link > a
Code Tools div#sidebar > div.links > div.link > a
Coin div#sidebar > div.links > div.link > a
Common VM Interface div#sidebar > div.links > div.link > a
Detroit div#sidebar > div.links > div.link > a
Duke div#sidebar > div.links > div.link > a
Graal div#sidebar > div.links > div.link > a
IcedTea div#sidebar > div.links > div.link > a
JDK 8 Updates div#sidebar > div.links > div.link > a
JDK 9 div#sidebar > div.links > div.link > a
JDK Updates div#sidebar > div.links > div.link > a
JMC div#sidebar > div.links > div.link > a
Jigsaw div#sidebar > div.links > div.link > a
Lanai div#sidebar > div.links > div.link > a
Leyden div#sidebar > div.links > div.link > a
Lilliput div#sidebar > div.links > div.link > a
Loom div#sidebar > div.links > div.link > a
Memory Model Update div#sidebar > div.links > div.link > a
Metropolis div#sidebar > div.links > div.link > a
Multi-Language VM div#sidebar > div.links > div.link > a
Nashorn div#sidebar > div.links > div.link > a
New I/O div#sidebar > div.links > div.link > a
OpenJFX div#sidebar > div.links > div.link > a
Panama div#sidebar > div.links > div.link > a
Port: AArch32 div#sidebar > div.links > div.link > a
Port: AArch64 div#sidebar > div.links > div.link > a
Port: BSD div#sidebar > div.links > div.link > a
Port: Haiku div#sidebar > div.links > div.link > a
Port: MIPS div#sidebar > div.links > div.link > a
Port: Mobile div#sidebar > div.links > div.link > a
Port: PowerPC/AIX div#sidebar > div.links > div.link > a
Port: RISC-V div#sidebar > div.links > div.link > a
Port: s390x div#sidebar > div.links > div.link > a
SCTP div#sidebar > div.links > div.link > a
Shenandoah div#sidebar > div.links > div.link > a
Skara div#sidebar > div.links > div.link > a
Sumatra div#sidebar > div.links > div.link > a
Tsan div#sidebar > div.links > div.link > a
Valhalla div#sidebar > div.links > div.link > a
Wakefield div#sidebar > div.links > div.link > a
Zero div#sidebar > div.links > div.link > a
ZGC div#sidebar > div.links > div.link > 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 html

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-hidden="true"]` is not present on the document `<body>`
●Image elements have `[alt]` attributes
●Document has a `<title>` element
●Links are distinguishable without relying on color.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●The page contains a heading, skip link, or landmark region
●Identical links have the same purpose.
●Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
○`[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
○Deprecated ARIA roles were not used
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○Elements use only permitted ARIA attributes
○`[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
○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
○Buttons have an accessible name
○`<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
○Heading elements appear in a sequentially-descending order
○`<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 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">`
○`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
○`<object>` elements have alternate text
○Select elements have associated label elements.
○Skip links are focusable.
○No element has a `[tabindex]` value greater than 0
○`<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
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
○`<td>` elements in a large `<table>` have one or more table headers.
B
Alt Text Quality
2 of 2 images have issues
REVIEW
2 of 2 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
2 images 2 missing
IssueCount
missing2 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

C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

A+
Heading Hierarchy
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 This site can’t be reached
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Dark Mode Support
Full dark mode support
PASS
Full dark mode support
Info::
color-scheme meta tag present
The site declares support for light and dark color schemes via <meta name='color-scheme'>.
Got: light dark
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 light dark ✓Dark theme-color #fff ✓CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

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

Send Feedback