If you make many web pages that do not require JavaScript, CSS, and many images or videos, then that also improves the speed, and is better for accessibility.

If you make many web pages that do not require JavaScript, CSS, and many images or videos, then that also improves the speed, and is better for accessibility. For other cases you do need some scripts and stuff, I have suggested a "widget" attribute nd <widget> element. Both <script> and <widget> elements support the widget attribute. If recognized by the browser and enabled by the user, then the element and its contents are replaced by something implementation-dependent (and not necessarily representable in normal HTML). Otherwise, a <widget> element acts like <span>. This also improves speed, as it can skip loading a script if it has its own version, and possibly also use a native code version specific to the browser or an extension. It also allows better user customization, for example if a special text editing widget is used on the web page (rather than a normal <textbox>), then it can be replaced with one that has vi or emacs key bindings, or to implement it without animations if the user wants to implement that script without animations. The other alternative, for stuff that doesn't need HTML and HTTP, is to use Gopher. Then, no need to consider what kind of user interface is used and any other kind of accessibility; it already is!