7299: Accessibility Issue - Too low contrast on rule result values

[Suchitainf]

This PR addresses an accessibility issue where the contrast of the rules score on Automated Analysis screen is too low.

Please review the change and let me know if any changes are required.

The UI looks like this now:

---

Progress

• Commit message must refer to an issue
• Change must be properly reviewed

Issue

• JMC-7299: Accessibility Issue - Too low contrast on rule result values

Reviewers

• Marcus Hirt (@thegreystone - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jmc pull/268/head:pull/268
$ git checkout pull/268

Update a local copy of the PR:
$ git checkout pull/268
$ git pull https://git.openjdk.java.net/jmc pull/268/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 268

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jmc/pull/268.diff

[bridgekeeper]

👋 Welcome back schaturvedi! 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.

[mlbridge]

Webrevs

• 00: Full (ce5aa115)

[openjdk]

@Suchitainf 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:

7299: Accessibility Issue - Too low contrast on rule result values

Reviewed-by: hirt

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 2 new commits pushed to the master branch:

• 8bc1247: 7272: Method profiling page should show the frame type
• a2995a1: 7264: Improve the performance of the JFR parser

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
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.

[Suchitainf]

/integrate

[openjdk]

Going to push as commit 6723a70.
Since your change was applied there have been 2 commits pushed to the master branch:

• 8bc1247: 7272: Method profiling page should show the frame type
• a2995a1: 7264: Improve the performance of the JFR parser

Your commit was automatically rebased without conflicts.

[openjdk]

@Suchitainf Pushed as commit 6723a70.

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