8359024: Accessibility bugs in API documentation

[hns]

Please review a change to fix a couple of accessibility errors in JDK API documentation as detected by our accessibility testing.

• Contrast between link and normal text colors was below 3 and therefore would have required other styling (such as underlining). This is fixed by slightly darkening text color (our text color isn't black but dark-gray).
  Old colors: https://webaim.org/resources/linkcontrastchecker/?fcolor=282828&bcolor=FFFFFF&lcolor=437291
  New colors: https://webaim.org/resources/linkcontrastchecker/?fcolor=181818&bcolor=FFFFFF&lcolor=437291

• Links in the headings of inherited member summaries used the wrong color and contrast to background color was below 4.5. This is fixed by removing a bogus .expanded selector that shouldn't have been there in the first place.
  Old colors: https://webaim.org/resources/linkcontrastchecker/?fcolor=181818&bcolor=DEE3E9&lcolor=437291
  New colors: https://webaim.org/resources/linkcontrastchecker/?fcolor=181818&bcolor=DEE3E9&lcolor=47688A

• Remove the role="tablist" and aria-orientation="horizontal" attributes from table captions if they do not contain tabs. This is the only code change, and the only change that comes with a test change (I guess the CSS changes are noreg-hard as we don't have a way to do automatic accessibility testing).

All changes are invisible or so subtle that they are practically impossible to spot in normal browsing, so I spare myself the task of uploading demo docs.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8359024: Accessibility bugs in API documentation (Bug - P3)

Reviewers

• Volkan Yazici (@vy - Committer)
• Chen Liang (@liach - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25716/head:pull/25716
$ git checkout pull/25716

Update a local copy of the PR:
$ git checkout pull/25716
$ git pull https://git.openjdk.org/jdk.git pull/25716/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25716

View PR using the GUI difftool:
$ git pr show -t 25716

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25716.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back hannesw! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@hns This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8359024: Accessibility bugs in API documentation

Reviewed-by: vyazici, liach

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 244 new commits pushed to the master branch:

• 2af869b: 8156715: TrustStoreManager does not buffer keystore input stream
• 5c1f77f: 8360201: JFR: Initialize JfrThreadLocal::_sampling_critical_section
• 54acadb: 8294226: Document missing UnsupportedTemporalTypeException
• ... and 241 more: https://git.openjdk.org/jdk/compare/7838321b74276e45b92c54904ea31ef70ed9e33f...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@hns The following label will be automatically applied to this pull request:

• javadoc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (0fec8083)

[hns]

/integrate

[openjdk]

Going to push as commit 9a726df.
Since your change was applied there have been 244 commits pushed to the master branch:

• 2af869b: 8156715: TrustStoreManager does not buffer keystore input stream
• 5c1f77f: 8360201: JFR: Initialize JfrThreadLocal::_sampling_critical_section
• 54acadb: 8294226: Document missing UnsupportedTemporalTypeException
• ... and 241 more: https://git.openjdk.org/jdk/compare/7838321b74276e45b92c54904ea31ef70ed9e33f...master

Your commit was automatically rebased without conflicts.

[openjdk]

@hns Pushed as commit 9a726df.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

[hns]

/backport :jdk25

[openjdk]

@hns the backport was successfully created on the branch backport-hns-9a726df3-jdk25 in my personal fork of openjdk/jdk. To create a pull request with this backport targeting openjdk/jdk:jdk25, just click the following link:

➡️ Create pull request

The title of the pull request is automatically filled in correctly and below you find a suggestion for the pull request body:

Hi all,

This pull request contains a backport of commit 9a726df3 from the openjdk/jdk repository.

The commit being backported was authored by Hannes Wallnöfer on 24 Jun 2025 and was reviewed by Volkan Yazici and Chen Liang.

Thanks!

If you need to update the source branch of the pull then run the following commands in a local clone of your personal fork of openjdk/jdk:

$ git fetch https://github.com/openjdk-bots/jdk.git backport-hns-9a726df3-jdk25:backport-hns-9a726df3-jdk25
$ git checkout backport-hns-9a726df3-jdk25
# make changes
$ git add paths/to/changed/files
$ git commit --message 'Describe additional changes made'
$ git push https://github.com/openjdk-bots/jdk.git backport-hns-9a726df3-jdk25

⚠️ @hns You are not yet a collaborator in my fork openjdk-bots/jdk. An invite will be sent out and you need to accept it before you can proceed.