Seven books for treating accessibility as a design decision rather than a late audit.
Most teams meet accessibility as a checklist arriving near the end of a project, which is the most expensive moment to meet it. These books move the work earlier, starting with what a team can do this quarter and going on to the argument you will need internally, the design decisions themselves, and the words on screen that a screen reader reads aloud. The order assumes you are starting from close to nothing.
Kalbag covers the whole picture quickly, from assistive technologies and legal context through to colour, typography and the markup a screen reader depends on. The chapter on testing is honest about what an automated checker can and cannot find.
Holmes reframes disability as a mismatch between a person and their environment rather than a fixed personal attribute, and that reframe is what changes how a team decides things. Read it when you need to win the case internally before any technical guidance is much use.
Horton and Quesenbery organise the material around design decisions, turning principles into guidance on layout, navigation, forms, media and error handling. Each principle chapter closes with questions to ask during a design review, so it folds into a process you already run.
Metts and Welfle cover how text behaves with a screen reader and how a product delivers bad news, which are the two moments where careless words do the most harm. Written for anyone who ends up writing the interface.
Plain English and readability are accessibility work, and this is the clearest method for both. Winters starts from a user need and from evidence about what people search for, then answers it in whatever format actually fits.
Inaccessible services usually fail before the interface, in names, decisions and the organisation behind the screen. Downe's principles cover being easy to find, setting expectations about what happens next, and behaving consistently whichever channel someone uses.
Norman's case that most so called user error is design error is the foundation the inclusive design argument rests on. Worth rereading with accessibility in mind, because the gulfs of execution and evaluation are wider for some people than for others.