JSJ 344: Inclusive Components with Heydon Pickering
- Charles Max Wood
- Aimee Knight
- Chris Ferdinandi
- Joe Eames
Special Guest: Heydon Pickering
In this episode, the panel talks with Heydon Pickering who is a designer and writer. The panel and the guest talk about his new book, which is centered on the topic of today’s show: inclusive components. Check out Heydon’s Twitter, Website, GitHub, and Mastodon social accounts to learn more about him. To purchase the book – go here!
0:00 – Advertisement: KENDO UI
0:38 – Chuck: Aimee, Chris, Joe, and myself – we are today’s panel. My show the DevRev is available online to check it out.
2:13 – Chuck: We are talking today about...?
2:22 – Chris: He’s talking about “inclusive components” toady!
2:41 – Guest: Traveling is very stressful and I wanted something to do on the plane. I’ve done this book, “Inclusive Design Patterns.”
If you don’t want to buy the book you can go to the blog. I have been talking with Smashing Magazine.
5:40 – Panel.
9:52 – Panel: The hard book did it get published?
10:02 – Guest: We are in the works and it’s all in the final stages right now. It has to go through a different process for the print-version.
11:54 – Panel.
11:58 – (Guest continues about the editorial process.)
12:09 – Panel: They probably switched to TFS – it’s Microsoft’s.
12:23 – Guest: There was this argument on Twitter about the different processors.
18:37 – Chris: I have some specialty friends where they tell me where I’ve screwed up my code. For example: Eric Bailey and Scott O’Hara but, of course, in very kind ways. What are some things that I can make sure that my code is going to work for many different people.
19:18 – Guest: You have accessibility and inclusive design. People think of accessibility as a check-list and that’s okay but there could be problems with this.
26:00 – Panel: That’s a great guideline.
26:05 – Chris: You talked about ARIA roles and it can be confusing. One side is: I don’t know when to use these and the other side is: I don’t now when NOT to use these so I’m going to use them for EVERYTHING! I guess both can be detrimental. What’s your advice eon this topic?
27:00 – Guest: Scott is great and I would trust him to the end of the Earth about what he says.
Guest mentions Léonie Watson and her talks about this topic.
29:26 – (Guest continues.)
29:36 – Advertisement – Sentry.io
30:31 – Chris.
30:40 – Guest: There is a lot of pressure, though, right? People wouldn’t blog about this if it wasn’t worthwhile. It doesn’t matter what the style is or what the syntax is.
The guest talks about not throwing ARIA onto everything.
36:34 – Aimee: Is this something that was mentioned in the book: people with disabilities and accessibility.
37:28 – Guest: Yes, of course. I think it’s important to making your interfaces flexible and robust to think and include people with disabilities.
39:00 – Guest mentions larger buttons.
40:52 – Panelists and Guest talk back-and-forth.
43:50 – Guest: It’s the progressive enhancement element.
44:05 – Guest: I think it’s worth noting. I think these things dovetail really nicely.
47:29 – Guest: I am the other way around – interesting.
52:50 – Chuck: Picks!
52:55 – Advertisement – Get A Coder Job!
END – Advertisement: CacheFly!
- Microsoft’s TFS
- Léonie Watson
- Heydon’s GitHub
- Heydon’s Mastodon
- Heydon’s Book
- Medium Article on Heydon
- Heydon’s Website
- Heydon’s Twitter
- Web Dev Career Guide: https://gomakethings.com/career-guide/
- Use FREECAREER at checkout to get it for free
- Neapolitan Ice Cream
- Netflix Web Performance case study
- Disney Heroes Battle Mode
- MFCEO Project Podcast
- Gary Lee Audio Experience