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 (4 books)
Why read this first: Once you understand the basics of TypeScript's type system, you systematically learn the knack of using it 'effectively.' Effective TypeScript provides judgment criteria—eighty-three concrete items on leveraging type inference and taming any—for making types a weapon in practice.
Why read this first: Once the practical primer has made you comfortable developing with types, you move on to more refined type-design best practices. Effective TypeScript shows, item by item, 'why you should write it this way,' elevating your design from types that merely work to types that help readers and your future self.
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