Open Bug 1982698 Opened 2 months ago Updated 1 month ago

github.com - bad Contrast Control results with GitHub's colorblind theme

Categories

(Firefox :: Disability Access, enhancement)

Firefox 141
enhancement

Tracking

()

UNCONFIRMED

People

(Reporter: ihor, Unassigned, NeedInfo)

References

()

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:141.0) Gecko/20100101 Firefox/141.0

Steps to reproduce:

Enabled high contrast option

Actual results:

Github already has a high contrast theme (can be enabled here https://github.com/settings/appearance), but enabling the high contrast option in Firefox breaks the website.

Expected results:

Deny/allow list for website URLs where I want to have high contrast colors

Summary: Disable high contrast for websites that already have a high contrast theme/breaks website → Disable high contrast for websites that already have a high contrast theme/it breaks website

There's already a request for adding a Contrast Control exceptions list: Bug 1971045.

I'm renaming this issue for someone to look into what's wrong with GitHub specifically.

Component: Untriaged → Disability Access
See Also: → 1971045
Summary: Disable high contrast for websites that already have a high contrast theme/it breaks website → github.com - bad Contrast Control results with GitHub's colorblind theme

I can't seem to be able to reproduce the issue. Can you please provide more aditional informatin.

  • Are you using macOS or another OS?
  • Are you using white or dark theme for contrast?
  • Do you have any other settings in the system?

Mostly to me if you use white theme on macOS, the whole system becomes broken. I could barely find the slide to put it back to normal.

Flags: needinfo?(ihor)
See Also: → 1984664

Redirect a needinfo that is pending on an inactive user to the triage owner.
:ayeddi, since the bug has recent activity, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(ihor) → needinfo?(ayeddi)
You need to log in before you can comment on or make changes to this bug.