Last month, we kicked off an initiative around accessibility. We made the announcement on MSO because originally we had intended for the rollouts to only happen on SO and on the Teams product. Once the work on this began, we realized it made sense for some changes to be deployed network-wide. We were able to be a little more ambitious than we had planned and decided to take advantage of that, since the changes that we could make network-wide will benefit more people.
We started rolling out some color contrast changes. The community noticed some of these changes last week, particularly around accepted answers. We’re sorry that we didn’t announce those pushes would be network-wide prior to them going out. That was an oversight, and we’re trying to get better at making sure we can give you a heads up on changes.
As the team has been working on this project, we’ve run into some issues around color hacks, legacy code, etc. We have decided to put a pause on this initiative and future updates so that we can sort that out.
Some of the color contrast changes that have been deployed network-wide, or will be deployed soon, are:
The answer count was updated to a darker green
Ignored: the opacity was removed, the text was lightened, and the answer count was updated
Deleted: the opacity was removed and the background and text were lightened
Watched: the text and title were darkened
View counts: three classes were updated: “warm” (orange to yellow), “hot” (medium to dark orange), and “supernova” (orange to red)
The accepted answers checkmark was updated to a darker green:
Comments: The number of votes was updated to a darker grey, and the text was darkened on the character limit counter:
Our "cool" class needed increased contrast, so the color was darkened:
Mod flag: The background color was darkened:
Right sidebar: Increased text contrast in the top yellow module and the watched tags module:
Thank you for reporting concerns about deployments and reporting bugs that you’ve spotted. The team is reviewing that feedback. We’re actively thinking about accessibility and how to resume this work in the near future. Taking this pause will allow us to fine-tune the approach to these important changes based on what we’ve learned so far.
As Rosie mentioned in the original MSO post, a core part of our mission is that our products and tools empower people to find what they need to develop technology. We want the platform to be a space where everyone can easily access the information they are seeking. We will come back to Meta in the near future with the new plan and timeline once it’s been solidified. We’re looking forward to working on these improvements with you.