Yes. Furthermore, ensure that if JavaScript is needed or used for something, that even if the script is disabled, documentation and/or other relevant informatio

Yes. Furthermore, ensure that if JavaScript is needed or used for something, that even if the script is disabled, documentation and/or other relevant information is available (e.g. "JavaScript is needed to use IRC" isn't helpful; instead, display the host name, port number, and channel name; another example is if something uses a API, ensure its documentation is available even if scripting is disabled). Also ensure it works fine with Lynx; if it does, then it will probably work fine with others too, even if users change the settings. Specifically, it should work well without CSS. Accessibility is important too; use ARIA, and use the HTML commands (e.g. <H1>, <STRONG>, <TABLE>, etc) properly, rather than misusing them. It is also a good idea to make it fast. This is done by not including too many pictures, CSS, video, etc (you will rarely need any included in the document itself). It would be possible to do much better, but the design of HTML gets in the way.