Re:So You Want to Build a Browser Engine
by robin_reala on Monday June 10, 2024 @11:02AM
(#40634377)
VeryGoodGraphics has no accessibility tree and no results when searching the documentation for “accessibility”, which makes it broadly immoral (or if you want to disagree with that, at least illegal to use it to build production systems in many locations). If you can’t get that right from the start, or even have plans for it, then you’re obsolete.
[ Parent
| on HN ]
If there is a VGG-native browser then accessibility is not so hard to implement. The awkward problem is that current VeryGoodGraphics is just a canvas node in HTML (using WebAssembly + WebGL). So adding accessibility support will be a nightmare technically.
Even if you don't care about that (and you should!), "you can't highlight text [without doing additional work that nobody will do because it wasn't an explicit KPI for them]" is itself really disappointing and bad.
We escaped Flash. We shouldn't clamor to go back.
The reasons to escape Flash are the performance and power-consumption issues, rather than accessibility.
If you take browser as a document viewer then accessibility is critical. However if you take browser as a universal application platform, then accessibility is not necessary, right?
Re:So You Want to Build a Browser Engine
by robin_reala on Monday June 10, 2024 @11:40AM
(#40634747)
No? Why shouldn’t apps be accessible?
Re:So You Want to Build a Browser Engine
by RussianCow on Monday June 10, 2024 @12:49PM
(#40635482)
> However if you take browser as a universal application platform, then accessibility is not necessary, right?
Are you really suggesting that people with disabilities shouldn't be able to use web apps?