Improvement of accessibility (contrasting colors)

[joshuai96]

What problem are you trying to solve?

We are currently trying to improve Jitsi's accessibility after a customer had their Jitsi instance checked for conformance to the WCAG 2.

This issue is a excerpt of the test and serves as a discussion about ways to handle the following points.

For Success Criterion 1.4.3 Contrast (Minimum) there are some components which don't fulfill the required contrast of 4,5:1.

• The white text on the grey background, when you didn't give access to the microphone and camera has a contrast of 4,1:1.
  
• The red "Reject" text has a contrast of 3,5:1.
  
• Some of the user avatars (colored circle with initials) have bad contrasting colors.
• Most placeholder texts have a contrast of 2,9:1
  
  
• Background "Half blur" has a contrast of 2,5:1.
  

For Success Criterion 2.4.7 Focus Visible we already supplied two PRs, but there is still an open point:

• For the selected and unselected category the contrast is 1,4:1
  

For Success Criterion 1.4.11 Non-text Contrast there are some components which don't fulfill the required contrast of 3:1.

• The white "perfomance" icon on green background has a contrast of 2,3:1.
  

• Active and inactive toolbar buttons have a contrast of 1,7:1.
  

• All input fields (see above for chat and poll) have a contrast of 1,7:1 to the background.
  

What solution would you like to see?

I am by far no designer and I don't know if the colors used in Jitsi have some kind of corporate identity (CI) or corporate design (CD) behind them.

I would like if you could supply alternate colors that fix the contrast issues.

Is there an alternative?

If there is no CI or CD behind the used colors, we could suggest new colors that fix the aforementioned contrast issues.

[saghul]

Thanks for the report! We have work planned around WCAG compliance for Q1 2025, I'll make sure these make it to the list. Cheers!

[joshuai96]

We have some more test results regarding the WCGA, we're trying to improve. Is there any way to see or add to your list of planed changes. It might be helpful to so we may contribute as we plan to improve our test results in Q1 2025 also, so no double work on the same stuff might happen.

[saghul]

Work will start in the new year and we'll get collaborations from another internal team, so coordination is a bit weird here.

That said, since both contributions will need to be made here, to this repo, I think you can just get started with the low langing fruit, or things that don't require design decissions, and we can take it from there.