Boagworld: UX, Design Leadership, Marketing & Conversion Optimization · Paul Boag, Marcus Lillington

Champions of Accessibility and User Centric Development

·56 min·5 clips

Natalie explains why frustrated users sue over accessibility after being ignored for years.

Paul opens loosely. The virtual meetup gives the episode its scruffy warmth, with people drifting through chat while Paul and Marcus prod each other into gear. The scarf gets attention. Paul puts it down to a sore throat and jokes about isolation, while Marcus notes that staying home is not exactly new territory for him. Then Donald pulls the conversation into focus. He talks through the title he has more or less given himself: user experience developer. It fits because his work is not only about making things function. The thing has to feel right in use. His job sits between visual design and back-end engineering, taking attractive interface ideas and making them behave properly for real users. Paul is clearly into this. He pushes the point that developers shape user experience more than many teams admit, especially when a static comp turns into a live site. Wireframes leave blanks. They do not cover every error message, layout break, edge case, or bit of scale that shows up during implementation. That is where the developer starts making design decisions, whether anyone names them that way or not. Performance belongs in the same conversation. Paul treats speed as part of user experience, not a separate technical chore. Accessibility widens the frame. The cold open points to the long fight for an accessible web, and Donald's role shows why that cannot sit only with designers. The room stays casual to the end, circling back to chat-room teasing, Slack-channel abuse, and Paul admitting he has no idea what comes next week. Still, the idea lands: user-centered development is where good intentions either survive contact with the real interface or fall apart.

As heard by us

A grounded case for treating developers as central to UX and accessibility.

The episode makes a solid case for the user experience developer role as the point where code and usability meet. The guest treats the job as more than getting features to ship: it is about making them work well, keeping the user in view, and balancing the strengths of designers…

Read the full review in PlayNext →

Why you'd press play

If you build sites, this is the argument for caring about what happens after the mockup.

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from Boagworld: UX, Design Leadership, Marketing & Conversion Optimization