← Back to context

Comment by robocat

1 day ago

Pick a subset aimed directly at accessibility.

The least-needed features are often accessibility nightmares (e.g. animation - although usually not semantic).

The accessible subset could then be government standardized and used as a legal hammer against over-complex HTML sites.

For a while search engines helped because they encouraged sites to focus on being more informative (html DOCUMENTS).

I think web applications are a huge improvement over Windows applications, however dynamic HTML is a nightmare. Old school forms were usable.

(edited to improve) Disclosure: wrote a js framework and SPA mid 00's (so I've been more on the problem side than the solution side).

Styles can be provided as client-side dependencies instead of free form CSS:

   <meta name="dependencies" content="mathjax/1.1 highlightjs/2.0 navbar/5.1"/>

then browser decides how to resolve them.