2 out of 3 points should not be in the list at this point of time.
There is no browser around servo that is usable and they start with accessibility?
The effort should go first to have it work as an everyday browser and get as much market share as possible. Then think of accessibility and WebView Integration.
This is a unique opportunity to have a browser engine not depending on Google, Microsoft or some of AI companies wanting to get into this field. By watering it down, you will just lose the market to the ladybird which is focused.
Hard disagree.
1. Accessibility is easier to build in at the start rather than trying to tack it on at the end.
2. Building a browser around an existing webview is fairly easy compared to all the other parts that go into the finished product.
3. Making the webview integration better means more than just a single browser are using it (which would increase the user share that you deemed as important).