Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI could look better in High Contrast Mode #5218

Open
6 of 43 tasks
nchevobbe opened this issue Nov 20, 2024 · 4 comments
Open
6 of 43 tasks

UI could look better in High Contrast Mode #5218

nchevobbe opened this issue Nov 20, 2024 · 4 comments
Labels
accessibility Related to making the profiler UI accessible

Comments

@nchevobbe
Copy link
Member

nchevobbe commented Nov 20, 2024

When enabling a High Contrast Theme on Windows and setting forced colors in Firefox, the profiler looks a bit odd:

image

┆Issue is synchronized with this Jira Task


  • Focus indicators aren't visible
  • Edit Profile name button color should probably be ButtonText
  • Edit Profile name button hover color should be SelectedItemText image
  • Top right corner buttons should have a ButtonText color (and borders probably) image
  • Top right corner buttons should have a SelectedItemText color on hover image
  • Profile info Delete and Re-sybolicate buttons should have borders image
  • Top right corner buttons icons aren't visible
  • Documentation button should look like a link
  • (Re)upload data checkboxes don't look like checkboxes image
  • Upload button icon should be ButtonText, and the button should have a border
  • Profile information Uploaded icon (the cloud one), is barely visible image
  • Selected track doesn't look selected image Here Parent Process is selected. Hover style should be handled
  • Tracks context menu arrow button looks like a rectangle image . It should also have a ButtonText color
  • Track timespan should have a ButtonText color image
  • Track "active" timespan should get a SelectedItem background image
  • Track "preview timespan" shouldn't have a lowered opacity (set on .filterNavigatorBarUncommittedItem)
  • Track "zoom" icon isn't visible image
  • Track "zoom handles" should have a ButtonText border or background image
  • Track "zoom timespan" should have borders image
  • Timeline time tooltip should have a border or a CanvasText background with a Canvas text image
  • (checked) radio input don't look like radio
    image
  • "Invert call stack" checkbox doesn't look like a checkbox input when checked
    image
  • Filter stacks input clear button should have a ButtonText color image
  • "Breadcrumb" separator icons are rendered as a rectangle
    image
  • Call tree selected item doesn't get a background when tree isn't focused
  • Call Tree sidebar toggle button (.sidebar-open-close-button) isn't visible
  • sidebar-histogram-bar-color are not visible (maybe those should be <meter> too ? )
  • Call Tree sidebar Categories headers don't have enough contrast on hover image
  • Call Tree sidebar Categories headers could have a border
  • Call Tree search matching texts are not visible. They should have a Mark background and MarkText color
  • Flame Graph/Stack Chart/Marker Chart keep a light background in dark mode, but this one might be more related to dark mode support than an issue with High Contrast Mode
  • Flame graph tooltip "histograms" are not visible (might be fixed at the same time as we handle them in the Call Tree ?)
  • Flame Graph/Stack Chart tooltip category colors are not visible (same, might be fixed as the same time as we handle them in the Call Tree)
  • Flame graph item colors could have higher contrast. The accessibility team created a High Contrast palette that we could pick color from (https://www.figma.com/design/VHRA9hZ54oJqKKJwPd6FWa/High-Contrast-Mode?node-id=1870-2617&node-type=canvas&t=cESK0Mn8tfktc9Ow-0)
  • Marker Chart/ Marker Table filter icon isn't visible image
  • bottom right corner Legal/Privacy/Cookies close button doesn't have enough contrast on hover image
  • keyboard shortcut panel doesn't have border and the <kbd> items don't get a distinct style
    image

@julienw
Copy link
Contributor

julienw commented Nov 29, 2024

Hey Nicolas, what more would you think is needed after your patch #5220 ?

@nchevobbe
Copy link
Member Author

Hey Nicolas, what more would you think is needed after your patch #5220 ?

Quite a lot eh. I wanted to list the different issues here so we can have tasks that people could work on. I'll try to do it in the beginning of next week

@nchevobbe
Copy link
Member Author

Hey Nicolas, what more would you think is needed after your patch #5220 ?

Quite a lot eh. I wanted to list the different issues here so we can have tasks that people could work on. I'll try to do it in the beginning of next week

@julienw I went through the UI and added tasks in the first comment of this issue. I may have missed some, but fixing those would already improved things a lot. Then I guess we should have the accessibility team have a look at this to confirm I'm not saying non-sense

@julienw julienw added the accessibility Related to making the profiler UI accessible label Dec 2, 2024
@nmlapre
Copy link

nmlapre commented Dec 2, 2024

Great list, thanks for the investigation Nicolas. Not much more to add from the accessibility side of things.

As a general note when starting any work of this kind: anywhere we have ButtonText we should pair it with ButtonFace, and anywhere we use SelectedItemText we should pair it with SelectedItem. We'd also prefer GrayText (for disabled controls) paired with ButtonFace. I note this because sometimes, depending on your settings, you might think they're equivalent since they may appear quite similar. For example, ButtonFace can look very similar to the Background color if not configured. It's important to get the pairings right so that people who want to configure one of the colors have a consistent experience and can easily visually distinguish controls.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility Related to making the profiler UI accessible
Projects
None yet
Development

No branches or pull requests

3 participants