Power users love to bash accessibility features like this. Its a classic case of "I don't need a wheelchair ramp so i dont know why the library added one!"
Accessibility is way more than screen readers. It's more than specific disability-minded modes. The web needs to be friendly to everyone, including people who may not know they could benefit from accessibility features. Everyone benefits from this type of work.
There are definitely some legit feature concerns and priorities being called out here. Mozilla has left a lot to be desired of late on that front. But a power user is more than capable of jumping into settings or about:config to turn things like this off, or finding an extension to get by for now.
Also the firefox dev team isn't tiny. This isn't blocking other work or anything in a substantial way, it's a fairly isolated piece of UI, and there's no guarantee that skipping this would change the timeline on anything else.
I tried to use Copilot but it just kept getting in the way. The advanced autofill was nice sometimes, but its not like i'm making a list of countries or some mock data that often...
As far as generated code... especially with html/css/js frontend code it consistently output extremely inaccessible code. Which is baffling considering how straightforward the MDN, web.dev, and WCAG docs are. (Then again, LLMs cant really understand when an inaccessable pattern is used to demonstrate an
onclick
instead of a semantica
or to explain aria-* attributes...)It was so bad so often that I dont use it much for languages I'm unfamiliar with either. If it puts out garbage where i'm an expert, i dont want to be responsible for it when I have no knowledge.
I might consider trying a LLM thats much more tuned to a single languge or purpose. I don't really see these generalized ones being popular long run, especially once the rose-tinted glasses come off.