Mozilla needs to bring in the Bobs from Office Space: "What is it you say you do here?"
Mozilla needs to bring in the Bobs from Office Space: "What is it you say you do here?"
Just because a modal window exists doesn't mean it's bad for accessibility.
Unless it's a real emergency or the contents don't make sense until you do something, every modal window is an accessibility problem.
It doesn't sound like that's PaulHoule's motivation anyway — he knows that these tickets are not going to be fixed, just closed — the point is to "pour just a little bit of sand in the gears".
I generally approve of subversive actions which are naturally damaging if and exactly if the accusation they are based on is true.
That is, the logic is something like "well, either it gets fixed, in which case it's a victory for good, or they're hypocrites who don't really care, in which case 1. it wastes their time and 2. they deserve to have their time wasted."
Is the point to target Mozilla, or to actually make a difference in accessibility?
And my whole point is that a strategy can have multiple effects. As I understand it:
- Firefox care about usability => the issues get fixed or at least considered.
- Firefox don't care about usability => sand in the gears.
So it's a hybrid strategy whose purpose depends on the situation.
But reporting real problems because you are annoyed that problems keep appearing and don't get fixed doesn't look like a societal hurting behavior to me. It does look like personally hurting, but antagonizing the author because of this is a real societal hurting behavior.
On the opposite side, I'm also unreasonable frustrated when those modals appear and I cannot close it by clicking outside of it.
End results? Modals are horrible in most situations, especially when you want people to actually ingest some information.
Toasts in Windows are a good example -- often I am trying to use the tray but a toast pops up and I have to wait for the toast to clear or a toast pops up that makes me use the tray icons that it covers up if I want to deal with the situation. Of course on Windows there is the problem that clicking on a toast doesn't seem to ever do anything (like take you to the app that made the toast) and there is not a good mechanism to see the toast once it's past, etc.
In the case of Firefox I was particularly annoyed by little panels that floated above bookmark items on the chrome at the top of the page because, I dunno, there is something new I can do with my bookmarks, I guess. What I do know is that I wanted to click on something that was at the top of the web page and that stupid panel was in the way -- it wouldn't have stopped me from clicking on something else, but it's predictable that you're going to load a web page and frequently click on a link on a navbar at the very top.
A human being with some empathy might realize that you're initially in a state where you're not receptive to a message and later realize you are.
If I got a popup advertising a new feature after I completed a task I'd be a lot more receptive to it, particularly in that I'd be feeling the glow of having completed a task, being satisfied with the product, and not feeling so pressured, having some headspace to learn about a new feature.
As it stands, without any example, I for one have no idea what is being talked about, where these popups in FF are, how they affect accessibility.
Do I dislike modals that cover the entire window, yes, absolutely, but I have never encountered such in FF as a browser.
CTA to translate between languages which the translation models don't support "yet". It's disrupting for absolutely no reason.