Mozilla's forced white backgrounds on support.mozilla.org and accounts.firefox.com cause physical eye pain and migraines, and you removed all user overrides
I have albinism. Pure white backgrounds are not an annoyance – they cause physical eye pain and trigger migraines. Every time I visit support.mozilla.org or accounts.firefox.com, I am forced to endure #FFFFFF with no way to change it.
To anyone about to defend Mozilla blindly: this is about accessibility and eye pain, not brand loyalty, so do not silence me.
What Mozilla has done:
- Disabled extensions (Dark Reader, Stylus, Dark Mode) from modifying these pages – they are explicitly blocked by Mozilla's own Content Security Policy.
- Removed ui.systemUsesDarkTheme and layout.css.prefers-color-scheme.content-override from having any effect on these sites – they ignore prefers-color-scheme entirely.
- Left no about:config toggle to disable the forced light theme.
The only remaining workaround is a userContent.css hack with filter: invert(1) – which requires a visually impaired user to manually edit CSS files and restart the browser. That is not accessibility – that is hostility.
Security excuse – debunked:
- "We block extensions for security" – extensions are sandboxed. Blocking them on your own support pages is a deliberate policy choice, not a technical necessity.
- "We want a consistent brand appearance" – branding does not override accessibility. Forcing #FFFFFF on users with light sensitivity is a violation of basic inclusive design.
- "We respect prefers-color-scheme" – you do not. These two domains explicitly override it.
- "Users can just use Dark Reader" – you block it.
What I demand:
Make support.mozilla.org and accounts.firefox.com respect the system prefers-color-scheme media query. If you insist on light branding, add an official dark toggle in the site header – stored in a cookie or account preference. Stop blocking extensions from applying user‑chosen themes to your own sites. That is not security; it is control. You are a non‑profit that claims to value accessibility and user control. Your actions say otherwise. Fix these two domains. No CSS hacking should be required for basic vision safety.
Toutes les réponses (11)
Hi,
The people who answer questions here, for the most part, are other users volunteering their time (like me), not Mozilla employees or developers. When a Mozilla employee jumps into a discussion, you'll see the Mozilla Staff label next to their name.
If you wish, you can leave feedback for developers on the Mozilla Connect website. Click the Firefox Menu 
button in the toolbar, click Help and select Share ideas and feedback…. Alternatively, you can use this link. Your feedback is collected by a team that reads it and gathers data on the most common issues.
You can also file a bug report or feature request. See File a bug report or feature request for Mozilla products for details.
Paul, your statement is false. NoahSUMO, a forum moderator, confirmed in this very forum that 'yes we do monitor these forums'. Mozilla staff also participate under verified labels per their Staff Participation Guidelines. So this platform is monitored by both volunteers and staff.
You are using a false claim to dismiss a legitimate disability access issue. That is not helpful, and it violates Mozilla's own moderation guidelines that require moderators to be 'an example and role model to other community'. Dismissing accessibility with misinformation is not role-model behavior.
If you cannot address the actual issue, escalate this to someone who can. I will also file a Bugzilla report and post on Mozilla Connect, as you suggested – but do not pretend this forum is invisible to Mozilla.
Its not invisible, but its main focus is support with Mozilla products. Connect is our feedback platform and the best place for this to be escalated.
Paul, if Connect is the 'best place', then you escalate it there yourself. You are a moderator. You have direct channels. I am legally blind and every redirect is additional physical strain. Do not put the burden on me to navigate yet another platform. Escalate this internally or tell me who at Mozilla is responsible for accessibility.
I will feed this back to Mozilla staff.
Thank you.
Paul, I see you helped write the article that says Mozilla employees engage on Connect. So escalate this there yourself, or I will post it and link this thread.
You are more than welcome to provide feedback about this or anything else on the Connect platform.
For anyone else reading this, instead of helping a blind user, Paul directed me to a marketing article about their "What is Mozilla Connect" and didn't link me to the actual Connect web site.
Paul said
If you wish, you can leave feedback for developers on the Mozilla Connect website.
The actual Mozilla Connect web site is https://connect.mozilla.org/
Paul could have told me that directly. But instead, he gave me a marketing article hurdle when I already have a migraine from this support site and I can't read it because it has a blaring #FFFFFF white background.
Thank you for your feedback.
I feel outraged. After finally finding a way to sign in to Mozilla Connect without a corporate SSO gateway (I finally found the Mozilla Account sign in at very bottom), I was greeted with a message:
"Take a look at what's currently trending in the community and join the fun!"
This is not fun. Migraines are not fun. Eye pain imposed by a non-profit browser organization that has complete control over my user experience on their support site when they have the resources and technical ability to fix it is not fun -- it is structural violence.
Glad that you have been able to access our feedback site. Thank you for your feedback.
Vous devez vous identifier avec votre compte pour répondre aux messages. Veuillez poser une nouvelle question, si vous n’avez pas encore de compte.