I enjoy tackling my own browser engines (in Haskell) for atypical form factors! I'm currently wrapping up "Rhapsode" targetting voice I/O, building upon eSpeak NG, Voice2JSON, & my own CSS styling engine. Just need to implement forms & there won't be much more I can add to it within that form factor!
I've started a webpage debugger "Amphiarao" which is a locally-run webservice which allows you to test how your pages behave in Rhapsode. You can interact with Amphiarao using Selenium or (in an interface resembling WebInspector or elementary OS) any web browser capable of handling webforms. Did put some special effort in to making sure it'll sound great once that includes Rhapsode!
https://rhapsode.adrian.geek.nz/amphiarao (need to improve that page...)
And soon (with help from Amphiarao) I'm going to start tackling a visual browser engine designed for TVs & eReaders "Haphaestus"! This'll treat paginated webpages like a DVD menu of links, with the ability to play the auditory rendering from Rhapsode via the VCR buttons. With a mode for traversing browser history as a branching tree.
I will be building upon the same URL dispatcher & CSS styling engine I've already implemented for Rhapsode.
I have tentative plans for following up with a desktop/laptop browser with builtin WYSIWYG (separate ones for HTML vs CSS) if I can get help with getting inline layout & text selection. I want to make sure that I'm not sacrificing internationalization in the name of "simplicity"! Could also help take advantage of how easy Haskell makes multithreading... Anyone interested?
In all cases I am not telling webdevs they can't style their webpages for Rhapsode or Haphaestus, but I am telling them they don't need to for their pages to look (or sound) decent. Whilst making it easy for readers to switch away from poor webdesign choices (interestingly the CSS spec had a concept of "alternate styles' since the beginning)!
I handle webforms by extracting them into their own webpages to be rendered via special codepaths (standard accessibility advice applies) appropriate for the device and/or OS I'm targetting. I support webfeeds, even if I lean on other projects to manage subscriptions. And I integrate with the FreeDesktop.Org specs enough that I advertise other projects from your OS's package repositories you can install to open as-yet unsupported links, because unlike Chrome or Firefox I don't want to be responsible for mediating everything you might want to do online!
> Reply with your small web projects?
> My latest is a Gemini-first wiki, with a web extension.
> The software is called Phoebe.
> One of the sites using it The Transjovian Council.
> I have been working on a different web-first wiki engine for a long time. It is called Oddmuse.
> One of the sites using is Campaign Wiki, where tabletop role-playing groups can create wikis for their campaigns.
> Here are a bunch of other wikis I also run, using Oddmuse.