One of the core ideas behind the flavor of inclusive design I present is inclusivity by default. Compatibility with so many niches sounds far more daunting than it really is: if you only selectively override browser defaults and use plain-old, semantic HTML ( POSH), you’ve done half of the work already. 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, to name a few. Not all users load a page in a common web-browser and navigate effortlessly with their eyes and hands. Specifically, I focus on supporting underrepresented ways to read a page. I don’t expect anybody to fully agree with the list nonetheless, the article should have at least some useful information for any web content author or front-end web developer. Until that happens, here’s a non-exhaustive, highly-opinionated list of best practices for websites that focus primarily on text. I realize not everybody’s going to ditch the Web and switch to Gemini or Gopher today ( that’ll take, like, at least a month /s). Split elements and possessive hyperlinks.But most users don’t change their fonts….Can’t users on poor connections disable images?.Scripts and the Content Security Policy.Toggle table of contents Table of Contents The table of contents should help you skim. If you find the article too long, just read the introduction and conclusion. See the updated date and changelog after the post title. This is a “living document” that I add to as I receive feedback. It also does not apply to websites that focus more on generating revenue or pleasing investors than being inclusive.
It does not apply to websites that have a lot of non-textual content. The following applies to minimal websites that focus primarily on text.
0 kommentar(er)
