Jens Oliver Meiert

Thoughts on an Accessibility “Get Well” Plan

Post from June 29, 2022 (↻ November 23, 2022), filed under (feed).

Have you wondered how to anchor accessibility in an engineering team, one that isn’t yet producing accessible sites or apps?

The other week, I met with another LivePerson engineering lead on these questions, and later sat down to document options to start with. Here they are, for further refinement and discussion.

Hiring and Staffing


Short-term (goal: increase exposure to accessibility topics, plant concepts):






Processes and Communication

❧ What would you add? Share your accessibility “get well” plans!

Toot or tweet about this?

About Me

Jens Oliver Meiert, on September 30, 2021.

I’m Jens, and I’m an engineering lead—currently manager for Developer Experience at LivePerson—and author. I’ve worked as a technical lead for Google, I’m close to W3C and WHATWG, and I write and review books for O’Reilly. I love trying things, sometimes including philosophy, art, and adventure. Here on I share some of my views and experiences.

If you have a question or suggestion about what I write, please leave a comment (if available) or a message. Thank you!

Read More

Maybe this is interesting to you, too:

Looking for a way to comment? Comments have been disabled, unfortunately.

Cover: The Web Development Glossary.

Get a good look at web development? Try The Web Development Glossary (2020). With explanations and definitions for literally thousands of terms from Web Development and related fields, building on Wikipedia as well as the MDN Web Docs. Available at Apple Books, Kobo, Google Play Books, and Leanpub.

Learn about new posts by feed, on Mastodon, or on Twitter.

Found a mistake? Email me,

You are here: Home → Archive → 2022 → Thoughts on an Accessibility “Get Well” Plan

Last update: November 23, 2022

Professional frontend developers produce valid HTML and CSS.