Mark mailed me in response to my query about limiting his accessibility series to weblogs rather than expanding it to cover general sites:
Because every project needs to start and end somewhere. There are disabilities I’m not covering at all. There are certainly more than 25 things that *every* site should implement. And so forth. Focusing on weblogs lets me delve deeper into specifics about implementation. This is already apparent in day 6 -- talking about the specific templates in each weblogging system that you need to check -- and it will become even more important later on. Many of the standard arguments against accessibility (my client doesn’t want it, it’s too expensive, the site needs to look exactly like the brochure) don’t apply to weblogs, so I will use that to my advantage.
Concentrating on implementation sounds like a great idea—there are several accessibility resources explaining concepts but I haven’t seen any that explain how accessibility can be achieved, especially by web content creators who are not HTML experts.
More recent articles
- Weeknotes: Parquet in Datasette Lite, various talks, more LLM hacking - 4th June 2023
- It's infuriatingly hard to understand how closed models train on their input - 4th June 2023
- ChatGPT should include inline tips - 30th May 2023
- Lawyer cites fake cases invented by ChatGPT, judge is not amused - 27th May 2023
- llm, ttok and strip-tags - CLI tools for working with ChatGPT and other LLMs - 18th May 2023
- Delimiters won't save you from prompt injection - 11th May 2023
- Weeknotes: sqlite-utils 3.31, download-esm, Python in a sandbox - 10th May 2023
- Leaked Google document: "We Have No Moat, And Neither Does OpenAI" - 4th May 2023
- Midjourney 5.1 - 4th May 2023
- Prompt injection explained, with video, slides, and a transcript - 2nd May 2023