So You Want to Build a Browser Engine

Re:So You Want to Build a Browser Engine by eropple on Monday June 10, 2024 @11:08AM (#40634458)

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.

[ Parent | on HN ]

Re:So You Want to Build a Browser Engine by bdahz on Monday June 10, 2024 @11:29AM (#40634626)

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?

[ Parent | on HN ]

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?

[ Parent | on HN ]

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?

[ Parent | on HN ]

Re:So You Want to Build a Browser Engine by bdahz on Monday June 10, 2024 @01:48PM (#40636108)

Sorry, I was just raising my question. Because in my country most app maker does not care about accessibility. Now I know.

[ Parent | on HN ]