Inclusive Components — Accessible web interfaces, piece by piece

by Heydon Pickering

Inclusive Components examines common web UI patterns through the lens of inclusion. The aim is to find more accessible and robust solutions for the patterns we author, plug in, and use every day.
Each chapter tackles a single component, addressing how different and vulnerable people might read and interact with it, and how they can be better accommodated. The in-depth explorations are meticulously illustrated and code examples culminate as working demos.
Inclusive design is not about wrong and right, but bad to better. You'll learn plenty of tips from Inclusive Components, but you'll also adopt the mindset to go on and make even better components.

Genres: Design, Technology, Programming, Website Design, Software, Nonfiction

278 pages, Kindle Edition

Published September 1, 2018

Reviews

[Michele Dellaquila · Rating 3 out of 5]

P.S. I don’t read all pages, but I arrived halfway (read 181 pages)

## Introduction
Inclusive Components is a book written by Heydon Pickering that aims to be
practical manual for creating complete accessibility interfaces.

In my opinion, it’s more theory than practice. It’s a good book that will help you learn the 'components pattern' that you find on the W3C website, for this reason, I think that it doesn’t deserve more than 3 stars.

## Why didn't like it?
The thing added is the experience of the author that tells you:
this works is for this reason, that’s bad for this reason.

Obviously, I simplify the things, but it isn’t no more to pick the component pattern contains on W3C and describe it with more details, focusing on his experience to tell you what the wrong methods are and the correct ones to implement them.

In my opinion, as a simple web dev that wants to enter into the accessibility world,
I believe 'components pattern' that you find on W3C website tells you everything about
how to make a component accessible.

Also, it’s more theory than practice, as I said at the start,
there are few practical examples; it’s more discursive.

## Why I appreciated it
It’s a good book, it’s not hard understand because the author makes things clear.

—————————————————————————————————————————

I hope this opinion can help you to decide if to invest your time in this book or not. Please share your opinion in the comments; maybe I don't understand the core value of the book.

[Jan]

I'm not used to thinking this way about frontend components, about how accessible it is.
This should be something all devs at least know something about (as I can assure you: this is hardly the case).
It does complicate things that I used to consider easy, though.
That's why I appreciate the examples that show how things can be done, explaining why in the process.
There's also this smashed.by website that contains the whole example.

Could use some editing as sometimes things are referenced as if they are printed, but they are not in the book.

[Sarah]

I refuse to rate this book. This is the case, like the book, **** the author. I used to look up to the author until he went completely bananas and now I'm on the way out of web industry, so I'll probably donate this book.

[Ana Rafaela · Rating 5 out of 5]

Incredibly light reading considering how much quality content it contains.

[César · Rating 3 out of 5]

Fue una buena lectura. Necesario conocer un poco más de la parte técnica para sentirse atrapado pero estuvo bien.