Eric Bailey shares his thoughts, which can be summed up as follows:
- People who create inaccessible code, but do not realize they are doing so.
- People who create inaccessible code and realize they are doing so, but do not know how to fix it.
- People who create inaccessible code, and do not care about fixing it.
- People who create inaccessible code that they think is accessible.
- People who create inaccessible code that our industry thinks is accessible, but experientially is not.
Eric says that he has been type number five more than he cares to admit.
The blog post doesn’t go into more detail, but I think it’s interesting to categorise the different reasons behind why someone may have built something inaccessible. Someone should take this idea and present a corresponding “cure” for each symptom!
Prefer longer newsletters? You can subscribe to week11y, fortnight11y or even month11y updates! Every newsletter gets the same content; it is your choice to have short, regular emails or longer, less frequent ones. Curated with ♥ by developer @ChrisBAshton.