Skip to content
https://java.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
404 Error Page
Action
HTTP 429, bare page
FIX
HTTP 429, bare page
Warning::
Unexpected status code: HTTP 429
Expected HTTP 404 but received 429. This may confuse search engine crawlers.
Got: HTTP 429
Warning::
Bare server default 404 page
The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.
404 Page Quality Default 404 Page
Status Code HTTP 429 ✗Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗
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.

F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
1 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 1 <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
6 landmarks
REVIEW
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) 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.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer

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

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
h1 Java
2.15:1
#000000
on
#224669
needs 3.0:1 (large text)
32px · above the fold
h3 Java to run desktop applications
1.52:1
#000000
on
#023142
needs 3.0:1 (large text)
19px · above the fold
h3 Developers and Enterprise Administrators
1.52:1
#000000
on
#023142
needs 3.0:1 (large text)
19px · above the fold
title Java | Oracle
2.15:1
#000000
on
#224669
needs 4.5:1 (normal text)
16px · top of page (header area)
a Developer Resources
2.15:1
#000000
on
#224669
needs 4.5:1 (normal text)
16px · top of page (header area)
a Enterprise Resources
2.15:1
#000000
on
#224669
needs 4.5:1 (normal text)
16px · top of page (header area)
a Java for Desktop Apps
2.15:1
#000000
on
#224669
needs 4.5:1 (normal text)
16px · top of page (header area)
p Oracle Java is the #1 programming langua…
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · above the fold
p For End Users on a Desktop or Laptop com…
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · above the fold
a Download Java for Desktops
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · above the fold
a What is Java
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · above the fold
a Help for end users
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · above the fold
p Free Java Development Kit (JDK) download…
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · mid-page
a Developer Downloads
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · mid-page
a Developer Resources
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · mid-page
a Enterprise Resources
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · mid-page
a OpenJDK Early Access
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · mid-page
a © 2025 Oracle
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · mid-page
a Select Language
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · mid-page
a Support
1.52:1
#000000
on
#023142
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Java2.15:13.0:1
#000000
#224669
Fail
h3 Java to run desktop …1.52:13.0:1
#000000
#023142
Fail
h3 Developers and Enter…1.52:13.0:1
#000000
#023142
Fail
title Java | Oracle2.15:14.5:1
#000000
#224669
Fail
a Developer Resources2.15:14.5:1
#000000
#224669
Fail
a Enterprise Resources2.15:14.5:1
#000000
#224669
Fail
a Java for Desktop App…2.15:14.5:1
#000000
#224669
Fail
p Oracle Java is the #…1.52:14.5:1
#000000
#023142
Fail
p For End Users on a D…1.52:14.5:1
#000000
#023142
Fail
a Download Java for De…1.52:14.5:1
#000000
#023142
Fail
a What is Java1.52:14.5:1
#000000
#023142
Fail
a Help for end users1.52:14.5:1
#000000
#023142
Fail
p Free Java Developmen…1.52:14.5:1
#000000
#023142
Fail
a Developer Downloads1.52:14.5:1
#000000
#023142
Fail
a Developer Resources1.52:14.5:1
#000000
#023142
Fail
a Enterprise Resources1.52:14.5:1
#000000
#023142
Fail
a OpenJDK Early Access1.52:14.5:1
#000000
#023142
Fail
a © 2025 Oracle1.52:14.5:1
#000000
#023142
Fail
a Select Language1.52:14.5:1
#000000
#023142
Fail
a Support1.52:14.5:1
#000000
#023142
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.

B
Lighthouse Accessibility Audits
Score 84/100 — 5 failing, 23 passed
REVIEW
84

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 all div.mainContent > div > div.pdynamicbutton > a.call
Decline all div.mainContent > div > div.pdynamicbutton > a.required
Powered by div > div.footer > div.left > label

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
privacy policy div.mainContent > div > div#cookieConsentDescription > a

These are opportunities to improve the legibility of your content.

Navigation

A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.f20 > div#pop-div205502739110645569 > div#pop-div306560129672858978 > div#pop-frame016586970698812853 body.f20 > div#pop-div205502739110645569 > div#pop-div306560129672858978 > div#pop-frame016586970698812853

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
Java to run desktop applications div.sc04w1 > ul.sc04cards > li.sc04card > h3.hdg-xsm

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
Support div.u10w5 > div.u10-links > p > a
Privacy div.u10w5 > div.u10-links > p > a
Terms of Use div.u10w5 > div.u10-links > p > a
Trademarks div.u10w5 > div.u10-links > p > a

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
●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.
●`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 have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○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
○Buttons have an accessible name
○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
○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.
○Identical links have the same purpose.
○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
Heading Hierarchy
3 headings, 1 skip(s)
PASS
3 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H3 (missing H2)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Java
  • H3 Java to run desktop applications skipped
  • H3 Developers and Enterprise Administrators

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
All 1 images OK
PASS
All 1 images OK
Info::
1 image(s) with good alt text
1 images 1 good alt text
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="menu">
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#menucheckbox(none)none

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

<input type="checkbox" id="menu">

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

A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: /jcom/assets/jcom_print.css
Print Stylesheet ✓ Print Optimized
Print stylesheet /jcom/assets/jcom_print.css ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback