Latest / 5 Minute UX / Accessible (Morville Honeycomb): What It Is and Why It Matters
Transcript
- 0:08This lesson is Accessible (Morville Honeycomb): What It Is
- 0:11and Why It Matters. Let's get started.
- 0:19Have you ever built a product that works perfectly for
- 0:21everyone except the people who actually need it most?
- 0:24Exclusion happens when design decisions inadvertently lock out
- 0:27segments of the population. It’s not malicious; it’s just an
- 0:30oversight that treats able- bodied users in ideal conditions
- 0:32as the default. This creates a dangerous gap between functional
- 0:35for some and functional for all. The consequences are severe:
- 0:38lost market opportunities, legal risks, and ethical failures.
- 0:41You’re not just missing revenue; you’re failing to serve the
- 0:44community. Accessibility solves this by ensuring your work is
- 0:47inclusive from the start. That’s your Fix on Design
- 0:49Exclusion!
- 0:55By the end of this section, you’ll be able to define the
- 0:57‘Accessible’ facet of the UX Honeycomb and distinguish it
- 1:00from usability and compliance. Peter Morville’s UX Honeycomb
- 1:03positions accessibility as one of seven core facets, sitting
- 1:05alongside useful, findable, usable, credible, valuable, and
- 1:08desirable. This framework elevates accessibility from a
- 1:11mere technical constraint to a strategic design goal, ensuring
- 1:14it receives equal weight in your evaluations. We define
- 1:16accessible specifically as the removal of unnecessary barriers
- 1:19to access and use. It’s not just about ticking compliance boxes
- 1:22for standards like WCAG; it’s about embodying the principle
- 1:25that good design is inherently inclusive design. When you treat
- 1:28accessibility as a core heuristic, you ensure products
- 1:30work for people with diverse abilities, contexts, and
- 1:33constraints. This facet solves the critical problem of
- 1:35exclusion by preventing design decisions that inadvertently
- 1:38lock out segments of the population. It bridges the gap
- 1:40between being functional for some and being functional for
- 1:43all, creating an equitable experience that acknowledges
- 1:46varied physical and mental capabilities. Integrating this
- 1:48early during discovery phases prevents costly retrofits later,
- 1:51making it a foundational pillar rather than a final QA task.
- 1:54We’ll explore how this differs from usability in the next
- 1:57section, where we’ll separate access from ease of use.
- 2:06You’ve probably seen teams obsess over how fast a user can
- 2:08complete a task, focusing heavily on efficiency,
- 2:10learnability, and satisfaction. That is usability, and it
- 2:13matters, but it assumes the user can already access the product
- 2:16in the first place. Accessibility asks a
- 2:18fundamentally different question: can the user access
- 2:20and use the product at all, regardless of their specific
- 2:23abilities or constraints? Think back to when you tested a sleek
- 2:26interface that worked beautifully for sighted users
- 2:28but failed completely for someone relying on a screen
- 2:31reader. That product was highly usable for the able-bodied, yet
- 2:33entirely inaccessible to others, highlighting the critical
- 2:36distinction between ease of use and actual entry. Experienced
- 2:39practitioners know that removing barriers must come before
- 2:41optimizing for speed, because you cannot improve the
- 2:44experience of those who cannot enter the door. True
- 2:46accessibility goes beyond checking off WCAG standards or
- 2:49meeting ADA compliance; it is an ethos of inclusion and empathy
- 2:52that shapes the entire design. When you prioritize removing
- 2:54barriers first, you ensure the product serves everyone, not
- 2:57just the majority. That distinction between access and
- 2:59ease sets the stage for how we apply these principles in
- 3:02practice.
- 3:14In your next project, try incorporating accessibility
- 3:16checks into early design reviews instead of waiting for final QA.
- 3:19This shifts accessibility from a compliance hurdle to a shared
- 3:22responsibility that shapes the product from the start. You’ll
- 3:25want to use automated accessibility checkers to catch
- 3:27obvious issues, but you must supplement these with manual
- 3:30testing and inclusive user research. Automated tools miss
- 3:33context, so human judgment remains essential for true
- 3:35inclusivity. Train your team to think about diverse user needs
- 3:38during brainstorming sessions, ensuring that empathy drives
- 3:41every decision. When you embed accessibility into your
- 3:43workflow, you create products that are not only compliant but
- 3:46truly inclusive and user- centered. This approach prevents
- 3:49costly retrofits and fosters a more robust design that serves
- 3:52everyone. That brings the lesson full circle, back to the moment
- 3:55you’ll first put these principles into practice.
- 4:00Welcome to The Take. I'm joined by a fellow practitioner and
- 4:03together we're going to dig into Accessible (Morville Honeycomb):
- 4:06What It Is and Why It Matters — what it means in practice and
- 4:09what's worth remembering.
- 4:11[HOST] We touched on how accessibility is often treated
- 4:14as a final QA task rather than a core heuristic. [LEARNER] That
- 4:18hits a nerve because I still see teams treating it like a
- 4:21compliance checkbox at the end. [HOST] It’s dangerous because
- 4:24fixing semantic HTML after visual design is locked is
- 4:27incredibly expensive. [LEARNER] True, but the real friction is
- 4:30convincing stakeholders that early integration isn’t just
- 4:33nice to have. [LEARNER] They want speed, and accessibility
- 4:36feels like a drag on the timeline to them. [HOST] That’s
- 4:39where the distinction between access and ease of use becomes
- 4:43your strongest argument. [HOST] You can’t optimize for
- 4:46efficiency if the user can’t even enter the door in the first
- 4:49place. [LEARNER] I love that framing, but it’s hard to
- 4:52measure "entry" compared to task completion rates. [HOST]
- 4:55Exactly, which is why we need to stop relying solely on automated
- 4:58tools for validation. [LEARNER] Those tools miss the context, so
- 5:02we’re still left with manual testing gaps. [HOST] This is
- 5:05where AI is starting to shift the needle for us in a practical
- 5:08way. [LEARNER] You mean using AI to simulate diverse user
- 5:11interactions during the early design phase? [HOST] Yes,
- 5:14generating alt text or checking contrast ratios in real time
- 5:17keeps the barrier removal proactive. [LEARNER] That could
- 5:20actually help us catch issues before they become technical
- 5:23debt in development. [HOST] It moves accessibility from a
- 5:27reactive audit to a continuous design constraint.