Skip to content
https://jcp.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
7
REVIEW
3
PASS
3
INFO
0
Checks
13
3 PASS 3 REVIEW 7 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
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::
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 56/100 — 7 failing, 9 passed
FIX
56

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
Register for Site td#leftcontent > ul#p7PMnav > div.noNav > a
JCP Terms of Use td#leftcontent > ul#p7PMnav > div.noNav > a
Oracle Privacy Policy td#leftcontent > ul#p7PMnav > div.noNav > a
Welcome to the Java Community Process! tbody > tr > td#centercontent > div.header1
register now tbody > tr > td#centercontent > a
overview page tr > td#centercontent > p > a
Annual JCP Community Party at JavaOne 2026! tbody > tr > td#centercontent > div.header1
2025 JCP Award Winners! tbody > tr > td#centercontent > div.header1
2025 JCP Award winners tbody > tr > td#centercontent > a
December 2025 Newsletter is Released! tbody > tr > td#centercontent > div.header1
December 2025 edition of the JCP Newsletter tbody > tr > td#centercontent > a
December Public EC Meeting Agenda and Recording Published tbody > tr > td#centercontent > div.header1
The agenda and recording tr > td#centercontent > p > a
2025 JCP EC Elections Results Published! tbody > tr > td#centercontent > div.header1
results of the 2025 JCP EC elections tr > td#centercontent > p > a
25 Years of the JCP Program Celebration tbody > tr > td#centercontent > div.header1
Twenty-five years of the Java Community Process tr > td#centercontent > p > a
Celebrating 25 years of the JCP with JUGs around the world tr > td#centercontent > p > a
JCP Working Groups tbody > tr > td#centercontent > div.header1
Java in Education td#centercontent > ul > li > a
message from Heather VanCura ul > li > p > a
Java Ecosystem JCP Working Group td#centercontent > ul > li > a
Java and AI Working Group td#centercontent > ul > li > a
JSR Updates tbody > tr > td#centercontent > h1
New JSRs tr > td > b > a
JSR 402 tbody > tr > td > a
Public Reviews td > p > b > a
JSR 401 tr > td > p > a
Final Releases td > p > b > a
JSR 378 tr > td > p > a
JSR 381 tr > td > p > a
JSR 393 tr > td > p > a
JSR 394 tr > td > p > a
JSR 395 tr > td > p > a
JSR 396 tr > td > p > a
JSR 397 tr > td > p > a
JSR 398 tr > td > p > a
JSR 399 tr > td > p > a
JSR 400 tr > td > p > a
JSR 401 tr > td > p > a
Maintenance Reviews tr > td > b > a
Maintenance Releases td > p > b > a
JSR 384 tr > td > p > a
JSR 385 tr > td > p > a
JSR 387 tr > td > p > a
JSR 392 tr > td > p > a
JSR 907 tr > td > p > a
JSR 199 tr > td > p > a
JSR 221 tr > td > p > a
JSR 269 tr > td > p > a
Recent News and Announcements tbody > tr > td#centercontent > div.header1
Inside the JCP Executive Committee: Purpose, Structure, and Impact td#centercontent > ul > li > a
From Hokkaido to the World: How Hiroto Yamakawa Built a Java Community that Ins… td#centercontent > ul > li > a
Java in Education at the Dominican Republic Java User Group td#centercontent > ul > li > a
JCP's 25th Anniversary - Twenty-five years of the Java Community Process td#centercontent > ul > li > a
News and Announcements from the Program Management Office (PMO) tbody > tr > td#centercontent > a
Spec Lead Guide tr > td#rightcontent > span.rightcol > a
JCP 2 tr > td#rightcontent > span.rightcol > a
EC meeting summaries tr > td#rightcontent > span.rightcol > a
Calendar tr > td#rightcontent > span.rightcol > a
Multimedia page tr > td#rightcontent > span.rightcol > a
Submit a new JSR tr > td#rightcontent > span.rightcol > a
JCP Community Github tr > td#rightcontent > span.rightcol > a
JSR 221 JDBC 4.5 Maintenance Release td#rightcontent > span.rightcol > b > a
JSR 401 Java SE 26 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 12 td#rightcontent > span.rightcol > b > a
JSR 401 Java SE 26 Public Review td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 20 td#rightcontent > span.rightcol > b > a
JSR 402 Java SE 27 iteration begins td#rightcontent > span.rightcol > b > a
JSR 221 JDBC 4 API Specification Maintenance Review 5 td#rightcontent > span.rightcol > b > a
JSR 400 Java SE 25 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 11 td#rightcontent > span.rightcol > b > a
JSR 400 Java SE 25 Public Review td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 19 td#rightcontent > span.rightcol > b > a
JSR 401 Java SE 26 iteration begins td#rightcontent > span.rightcol > b > a
JSR 399 Java SE 24 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 10 td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Release 5 td#rightcontent > span.rightcol > b > a
JSR 399 Java SE 24 Public Review td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Review 8 td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 18 td#rightcontent > span.rightcol > b > a
JSR 400 Java SE 25 iteration begins td#rightcontent > span.rightcol > b > a
JSR 398 Java SE 23 Final Release td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Release 4 td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 9 td#rightcontent > span.rightcol > b > a
JSR 398 Java SE 23 Public Review td#rightcontent > span.rightcol > b > a
JSR 199 Java Compiler API Maintenance Review 7 td#rightcontent > span.rightcol > b > a
JSR 282 Real-Time Specification for Java 2.0 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Review 17 td#rightcontent > span.rightcol > b > a
JSR 392 Java SE 17 Maintenance Release td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Release 3 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Release Contents Maintenance Release 6 td#rightcontent > span.rightcol > b > a
JSR 399 Java SE 24 iteration begins td#rightcontent > span.rightcol > b > a
JSR 392 Java SE 17 Maintenance Review td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Review 3 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Release Contents Maintenance Review 6 td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing Maintenance Release td#rightcontent > span.rightcol > b > a
JSR 397 Java SE 22 Final Release td#rightcontent > span.rightcol > b > a
JSR 385 Units of Measurement API 2 Maintenance Release 2 td#rightcontent > span.rightcol > b > a
JSR 398 Java SE 23 iteration begins td#rightcontent > span.rightcol > b > a
JSR 396 Java SE 21 Final Release td#rightcontent > span.rightcol > b > a
JSR 269 Pluggable Annotation Processing API Maintenance Release 7 td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Release 2 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Maintenance Release 5 td#rightcontent > span.rightcol > b > a
JSR 384 Java SE 11 Maintenance Review 2 td#rightcontent > span.rightcol > b > a
JSR 337 Java SE 8 Maintenance Review 5 td#rightcontent > span.rightcol > b > a
JSR 378 Portlet 3.0 Bridge for JavaServer Faces 2.2 Final Release td#rightcontent > span.rightcol > b > a
JSR 243 Java Data Objects Maintenance Release 4 td#rightcontent > span.rightcol > b > a
JSR 381 Visual Recognition Specification Final Release td#rightcontent > span.rightcol > b > a
JSR 392 Java SE 17 Final Release td#rightcontent > span.rightcol > b > a
Contact Us body > div#footer > div.footleft > a
© 2026, Oracle Corporation and/or its affiliates. Terms of Use. Privacy Policy.… body > div#footer > div.footleft2
Terms of Use body > div#footer > div.footleft2 > a
Privacy Policy body > div#footer > div.footleft2 > a
Trademarks body > div#footer > div.footleft2 > a

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
JCP Terms of Use td#leftcontent > ul#p7PMnav > div.noNav > a
Oracle Privacy Policy td#leftcontent > ul#p7PMnav > div.noNav > a
register now tbody > tr > td#centercontent > a
overview page tr > td#centercontent > p > a
2025 JCP Award winners tbody > tr > td#centercontent > a
December 2025 edition of the JCP Newsletter tbody > tr > td#centercontent > a
The agenda and recording tr > td#centercontent > p > a
Twenty-five years of the Java Community Process tr > td#centercontent > p > a
Celebrating 25 years of the JCP with JUGs around the world tr > td#centercontent > p > a
Java in Education td#centercontent > ul > li > a
message from Heather VanCura ul > li > p > a
Java Ecosystem JCP Working Group td#centercontent > ul > li > a
Java and AI Working Group td#centercontent > ul > li > a
JSR 402 tbody > tr > td > a
JSR 401 tr > td > p > a
JSR 378 tr > td > p > a
JSR 381 tr > td > p > a
JSR 393 tr > td > p > a
JSR 394 tr > td > p > a
JSR 395 tr > td > p > a
JSR 396 tr > td > p > a
JSR 397 tr > td > p > a
JSR 398 tr > td > p > a
JSR 399 tr > td > p > a
JSR 400 tr > td > p > a
JSR 401 tr > td > p > a
JSR 384 tr > td > p > a
JSR 385 tr > td > p > a
JSR 387 tr > td > p > a
JSR 392 tr > td > p > a
JSR 907 tr > td > p > a
JSR 199 tr > td > p > a
JSR 221 tr > td > p > a
JSR 269 tr > td > p > a
Terms of Use body > div#footer > div.footleft2 > a
Privacy Policy body > div#footer > div.footleft2 > a
Trademarks body > div#footer > div.footleft2 > 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

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div#tools > div.search > form#[object HTMLInputElement] > input.form div#tools > div.search > form#[object HTMLInputElement] > input.form
tr > td#leftcontent > form#[object HTMLInputElement] > input.form tr > td#leftcontent > form#[object HTMLInputElement] > input.form

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.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
JSRs by Platform JSRs by Technology JSRs by Stage JSRs by Committee List of All… tbody > tr > td#leftcontent > ul#p7PMnav

These are opportunities to improve the experience of reading tabular or list data using 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
JSRs by Platform td#leftcontent > ul#p7PMnav > li > a
JSRs by Technology td#leftcontent > ul#p7PMnav > li > a
JSRs by Stage td#leftcontent > ul#p7PMnav > li > a
JSRs by Committee td#leftcontent > ul#p7PMnav > li > a
List of All JSRs td#leftcontent > ul#p7PMnav > li > a
About JCP td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
Get Involved td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
Community Resources td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
Community News td#leftcontent > ul#p7PMnav > li > a.p7PMtrg
FAQ td#leftcontent > ul#p7PMnav > li > a
Contact Us td#leftcontent > ul#p7PMnav > li > a
New JSRs tr > td > b > a
Public Reviews td > p > b > a
Final Releases td > p > b > a
Inside the JCP Executive Committee: Purpose, Structure, and Impact td#centercontent > ul > li > a
From Hokkaido to the World: How Hiroto Yamakawa Built a Java Community that Ins… td#centercontent > ul > li > a
Java in Education at the Dominican Republic Java User Group td#centercontent > ul > li > a
JCP's 25th Anniversary - Twenty-five years of the Java Community Process td#centercontent > ul > li > a
JCP 2 tr > td#rightcontent > span.rightcol > a
Calendar tr > td#rightcontent > span.rightcol > a
Multimedia page tr > td#rightcontent > span.rightcol > a
Submit a new JSR tr > td#rightcontent > span.rightcol > a
JCP Community Github tr > td#rightcontent > span.rightcol > 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
●Input buttons have discernible text.
●Document has a `<title>` element
●Links have a discernible name
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●Heading elements appear in a sequentially-descending order
●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
○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
○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">`
○`[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.
○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.
C
Form Accessibility
Action
3 of 3 controls have issues
REVIEW
3 of 3 controls have issues
Critical::
3 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="text" name="id">; <input type="text" name="id">; <input type="submit" name="Sign-in">
3 controls
0 labeled
0 placeholder only
3 unlabeled
ControlTypeLabelMethod
idtext(none)none
idtext(none)none
Sign-insubmit(none)none

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

<input type="text" name="id">; <input type="text" name="id">; <input type="submit" name="Sign-in">

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

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
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title The Java Community Process(SM) Program - System Error ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗
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
div Use of JCP site is subject to the
4.49:1
#666666
on
#DBE5EB
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
div and the
3.21:1
#666666
on
#AFC5D3
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient

2 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 JSR Updates21.00:13.0:1
#000000
#FFFFFF
Pass
title The Java Community P…21.00:14.5:1
#000000
#FFFFFF
Pass
a Press Room21.00:14.5:1
#000000
#FFFFFF
Pass
a Get Java Here21.00:14.5:1
#000000
#FFFFFF
Pass
a JSRs by Platform21.00:14.5:1
#000000
#FFFFFF
Pass
a JSRs by Technology21.00:14.5:1
#000000
#FFFFFF
Pass
a JSRs by Stage20.61:14.5:1
#000000
#FCFDFD
Pass
a JSRs by Committee16.46:14.5:1
#000000
#DCE5EC
Pass
a List of All JSRs18.62:14.5:1
#000000
#EDF2F5
Pass
a Register for Site15.91:14.5:1
#000000
#E0E0E0
Pass
div Use of JCP site is s…4.49:14.5:1
#666666
#DBE5EB
Fail
a JCP Terms of Use21.00:14.5:1
#000000
#FFFFFF
Pass
div and the3.21:14.5:1
#666666
#AFC5D3
Fail
a Oracle Privacy Polic…21.00:14.5:1
#000000
#FFFFFF
Pass
a About JCP21.00:14.5:1
#000000
#FFFFFF
Pass
a Program Overview11.75:14.5:1
#000000
#AFC5D3
Pass
a JCP Process Document21.00:14.5:1
#000000
#FFFFFF
Pass
a Calendar19.73:14.5:1
#000000
#F6F8FA
Pass
a JCP Members13.27:14.5:1
#000000
#BFD0DC
Pass
a Executive Committee12.82:14.5:1
#000000
#BACDD9
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
1 headings
PASS
1 headings
Info::
Single H1 present
  • H1 JSR Updates
A+
Alt Text Quality
All 47 images OK
PASS
All 47 images OK
Info::
35 decorative image(s) correctly marked
Info::
12 image(s) with good alt text
47 images 12 good alt text 35 decorative
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback