zlacker

[parent] [thread] 6 comments
1. rapnie+(OP)[view] [source] 2022-06-22 10:18:54
Still, I do a lot of browsing the web and did not encounter broken pages on Firefox, luckily.
replies(1): >>ecmasc+m
2. ecmasc+m[view] [source] 2022-06-22 10:21:28
>>rapnie+(OP)
On the websites I work on I have stopped testing on Firefox for the most part. I do testing once in a while, but I'd rather spend the time to make the site more accessible since it's a larger group than Firefox users.
replies(3): >>gostsa+i2 >>harry8+L2 >>postal+pe
◧◩
3. gostsa+i2[view] [source] [discussion] 2022-06-22 10:34:56
>>ecmasc+m
So, how should I feel as a blind user who uses Firefox? :)
replies(1): >>ecmasc+V2
◧◩
4. harry8+L2[view] [source] [discussion] 2022-06-22 10:39:22
>>ecmasc+m
If you abandon stanards which requires testing with different implementations you absolutely abandon acessibility for vastly more people in the future, imho.
◧◩◪
5. ecmasc+V2[view] [source] [discussion] 2022-06-22 10:40:22
>>gostsa+i2
Happy that I use my time to try to help your disability and make your life easier rather than make sure that a web browser that hardly anyone uses work 100% correctly.

Surely, most of the time Firefox will work just fine or at least good enough and by that standard I am sure that a site that has put some focus for it being easier to read with a screen reader is more important?

replies(1): >>gostsa+Dl
◧◩
6. postal+pe[view] [source] [discussion] 2022-06-22 12:02:21
>>ecmasc+m
You want accessibility but don't want to test for it.
◧◩◪◨
7. gostsa+Dl[view] [source] [discussion] 2022-06-22 12:48:25
>>ecmasc+V2
Maybe so, but another option is that the main functionality of the website tells me to use Chrome in a vary accessible way. :)

Don't take it like I'm trying to be snarky, it was just funny to be in two minorities with contradicting significance for the developer.

[go to top]