[zersiax]

Here's a question, will accessibility be considered? I fully realize my HN contributions are a bit of a broken record but also, if I don't bring this up, it appears nobody does so here we are.

Is this going to work with screen readers, magnification, speech recognition etc? I guess a more abstract version of that question is: Does Ladybird intend to offer some kind of feature parity with existing solutions where integration with OS-specific accessibility architectures (UIA, AT-SPI2, etc.) are concerned? If not, it's a non-starter for quite a few people, and I'd rather know so I know to even keep up with this project or add it to the "user first but oh not actually all users first" pile :)

[ibejoeb]

This is worthy goal, but it's approaching "perfect is the enemy of good" territory. By the numbers, in order to get broad adoption and power in the market, they should not focused on being the accessible browser. They need to nail making it a viable option for the greatest number of people at the lowest cost (which, at this point, is measured in time.) It needs to work as well as Chrome at operating web tech.

[for_i_in_range]

How about you help build that if you want that?

[ergocoder]

Whatever the non-profit tries to spin it, the reality is probably a no.

"User first" definitely doesn't mean targeting all 8 billions people on the planet.