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
- ChatGPT Containers can now run bash, pip/npm install packages, and download files - 26th January 2026
- Wilson Lin on FastRender: a browser built by thousands of parallel agents - 23rd January 2026
- First impressions of Claude Cowork, Anthropic's general agent - 12th January 2026