Mark replies
17th June 2002
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: Llama 3, AI for Data Journalism, llm-evals and datasette-secrets - 23rd April 2024
- Options for accessing Llama 3 from the terminal using LLM - 22nd April 2024
- AI for Data Journalism: demonstrating what we can do with this stuff right now - 17th April 2024
- Three major LLM releases in 24 hours (plus weeknotes) - 10th April 2024
- Building files-to-prompt entirely using Claude 3 Opus - 8th April 2024
- Running OCR against PDFs and images directly in your browser - 30th March 2024
- llm cmd undo last git commit - a new plugin for LLM - 26th March 2024
- Building and testing C extensions for SQLite with ChatGPT Code Interpreter - 23rd March 2024
- Claude and ChatGPT for ad-hoc sidequests - 22nd March 2024
- Weeknotes: the aftermath of NICAR - 16th March 2024