Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Not very well.

I'm one of those web developers who still uses Firefox as my daily driver which means the products I work on work on Firefox. Maybe twice a year a tester uses Chrome and turns up something that's not quite right.

Developers like me are a major reason why Firefox is still a viable web browser and there is someone like me in most organizations. If it wasn't for people like us more and more web pages would work in Chrome only and you just couldn't do things with Firefox. Collectively we probably contribute as much to the success of Firefox than all the people who actually check in changes to the source code but we are not treated accordingly. If they piss all of us off Firefox will become a non-viable web browser.

So far as accessibility I am doing a round of accessibility on my site and found things have gotten way worse for multiple reasons. I used to use NVDA + Firefox but since upgrading to Win 11 NVDA is completely broken for me and I have to pull the power plug on my computer to shut down NVDA.

Narrator + Edge basically works, but Narrator + Firefox is completely spastic. I might have a navigation bar with elements like

-- Choice 1

-- Choice 2

-- Choice 3

in a <nav> and it might read something like "Choice Landmark 1 Navigation Navigation Landmark Choice 2 Landmark Choice Navigation 3 Landmark" where using any ARIA role comes across as website vandalism because it makes Narrator + Firefox blurt out "Landmark" and "Group" and similar words randomly when it is reading stuff.

When something is that broken it doesn't seem worth even putting a ticket it for it.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: