- Separate content from delivery. Remember Android? iOS? You’ve probably already had to repackage the site at least once to help it fit the confines of a mobile or tablet screen. Making your content available in a no-scripting situation is a whole lot easier if the important stuff is stored independently from the way that it ends up being presented.
- Semantics: use them. We would all love to commit to WCAG and WAI-ARIA wherever they apply, but time and budget constraints have a way of turning the best intentions into half-measures. At the very least, though, title your links, provide alt-text for your images, and validate your content against the HTML flavor of the week to maximize the odds that it can be interpreted intelligibly by assistive technologies.
<noscript>. When scripting just won’t work, it’s the ultimate fallback. In the best case, provide alternative content (e.g., a static, image-based map) when scripting isn’t available. At the other end of the spectrum, a quick notice will at least inform visitors of the content they’re missing. If you simply can’t render content without client-side scripting, the least you can do is admit it.
- Read up. If you have time, take a moment to familiarize yourself with the Web Accessibility Initiative’s Web Content Access Guidelines (WCAG) and Accessible Rich Internet Application (ARIA) spec. Support may vary between user agents, but a little increased awareness never hurt anyone.