Goal
The path to "Webアクセシビリティの教科書"
Here is the reading path leading up to this book, derived from its dependencies and ordered from the fundamentals.
The path so far (3 books)
Why read this first: Once type design is a weapon you can wield, you advance to component-oriented UI development—the proving ground where those types shine most. Learning React gives you the experience of building UI declaratively while guarding props and state with types, letting you feel the benefit of types in making screens.
Why read this first: Once you can build UI with React, you extend your responsibility to the quality of whether that UI is 'usable by everyone.' This web accessibility book systematizes WAI-ARIA, keyboard operation, and screen-reader support, elevating UI you can build into UI everyone can use.
Sources
Why read this first: Once you've learned the implementation principles of WAI-ARIA and semantic HTML, you move on to concrete examples of how they fail and improve in practice. The Web Accessibility Textbook contrasts failure and success examples across requirements definition, navigation design, forms, and content, grounding implementation principles in real projects.
Sources