I also wanted some things similar to like that (although without any site branding either). Some web pages don't work properly with CSS disabled. There is ARIA,

I also wanted some things similar to like that (although without any site branding either). Some web pages don't work properly with CSS disabled. There is ARIA, although it isn't perfect either (and as far as I could tell when I checked, formatting such as bold, fixpitch, etc doesn't seem to work properly with ARIA; this is determined by writing a short HTML file and then viewing the accessible tree (I don't know if I made any kind of mistake)). So, rather I think the way to do is to use a combination of the HTML, CSS, and ARIA to produce a kind of "augmented HTML" which can then be displayed. (If it contains only simple HTML without layout or CSS or whatever, then the same HTML could usually be used.) (ARIA can be used to e.g. find out what is a checkbox etc, so that the renderer can render that element as a checkbox and ignore any CSS and HTML and other stuff that it tries to use to make it fancy.) Supporting the Gemini protocol and text/gemini file format is also good to have, but that is separate. Stuff such as a table of contents window can also be implemented (by looking for the relevant HTML commands in the document which denote headings, sections, etc). (I think I have seen one web browser that can do such a thing for Gemini and Markdown but not HTML. However, it would be possible to do with HTML too (although a bit more complicated).) You could also add such thing as local annotations, form data save/recall, etc. (These would be controllable only by the local user. There would be no HTML or JavaScript commands for documents to control them.) I mean that, to make a better web browser: remove half of the stuff, implement the other half of the stuff differently, and then add some stuff.