Does anyone know if #LibreWolf or any other privacy focused #firefox forks keep #screenreader and other #accessibility features? Sadly, most of these projects seem to consider accessibility an unneeded feature that ads bloat and security issues and just strip it out completely, so I don't have high hopes. This just seems to be the latest one getting popular after the recent #firefox issues. #a11y
@fastfinge They might keep them. But I doubt that a random fork of Firefox can afford to invest money in being intentional about that, or employing accessibility expertise with the same calibre as the big players.
What happens when that ARIA attribute isn't supported yet, or there's a bug in complex recursive accessibility trees, or there's a new HTML element? Waiting months or years for the fork to catch up (if it ever does at all) doesn't sound appealing.
In short, I think browser accessibility goes way beyond whether the buttons in the bookmarks manager have labels, or if there's an increasingly stale accessibility engine available.
@jscholes LibreWolf updates the fork within a week of a new firefox release. The main difference is removal of advertising features and better defaults. So I'm not too worried about bugfixes. I'm more worried about what they are and aren't removing.
