I made my web best practices article about twice as big as before:
https://seirdy.one/2020/11/23/website-best-practices.htmlExcerpt:
> My primary focus is supporting *underrepresented ways to read a page*. Not all users load a page in a common web-browser and navigate effortlessly with their eyes and hands. Authors often neglect people who read through accessibility tools, tiny viewports, machine translators, “reading mode” implementations, the Tor network, printouts, hostile networks, and uncommon browsers.
Cross-browser compatibility is easy. Supporting these niches while sticking to open standards is as hard as you can make it. WCAG compliance is necessary but insufficient.
Feedback welcome, especially from anyone with an accessibility background or with special needs! I hope to expand the article with technical approaches to accommodating neuro-atypical people soon, including recent WCAG discussions on clarifying sarcasm, idioms, and jokes.
I'd also like to hear about other underrepresented ways to read, or if anything I wrote impacted how you design pages.
I'd recommend against over-using the "_blank" target, though. It might make sense when a page contains unsaved changes or playing media, but it's otherwise unnecessary. Users who want to open a link in a new tab will do so on their own.