<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alicia Jarvis, CPACC, CSM on Medium]]></title>
        <description><![CDATA[Stories by Alicia Jarvis, CPACC, CSM on Medium]]></description>
        <link>https://medium.com/@a11yalicia?source=rss-af8687857e13------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VDCE0g3gSh3pOfCSwqgwpw.jpeg</url>
            <title>Stories by Alicia Jarvis, CPACC, CSM on Medium</title>
            <link>https://medium.com/@a11yalicia?source=rss-af8687857e13------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 03:44:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@a11yalicia/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Couch Test: Rethinking Streaming Accessibility Through the Customer Journey]]></title>
            <link>https://medium.com/design-bootcamp/the-couch-test-rethinking-streaming-accessibility-through-the-customer-journey-bd08cf71df39?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd08cf71df39</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[tv-accessibility]]></category>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Sat, 26 Sep 2026 11:06:15 GMT</pubDate>
            <atom:updated>2026-09-26T17:40:17.896Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Woman on couch uses remote while TV shows The Wild Path accessibility menu; cozy living room with dog nearby." src="https://cdn-images-1.medium.com/max/1024/1*lHcATWlqfhhGlENSpbFaPA.png" /><figcaption>Couch Test</figcaption></figure><p>Recently, I attended the Toronto International Film Festival. This year it definitely felt different and the feeling didn’t just come from the inaugural Disability Creatives Reception or the nine disability-centered films that were featured. Access was embeded in the entire customer experience from physically accessible venues, companion and accessible seating, open captions and described video across dozens of films and a fully accessible red carpet. I spend a lot of my day-to-day thinking about accessibility and customer experiences and this one really felt delibrate and well thought-out.</p><p>Since so much of my work is related to TV and streaming, I left the festival with one very important question: What happens when the glitz and glamour are over and someone with a disability sits down on the couch to watch one of these fantastic films?</p><p>Disability inclusion in the screen industry may start with what happens on the big screen or even behind the scenes.<a href="http://screen.it/"> </a>However, the inclusive experience continues on to what happens when someone makes the choice to actually watch a film or tv series in the comfort of their own home. They sit down, pick up the remote, open the app, look for something to watch, and then they press play. Can they do all of that independently?</p><p>That’s what I call the Couch Test.</p><p>Accessibility isn’t just a feature</p><p>When we talk about streaming accessibility, the conversation can quickly become a checklist of features.</p><ul><li>Captions.</li><li>Described video.</li><li>Screen reader support.</li><li>Text size.</li><li>Contrast.</li></ul><p>All of these things matter, but that’s not how customers experience a streaming service. They experience a journey that might look something like:</p><p>Discover → Sign up → Sign in → Browse → Search → Choose → Watch → Customize → Get help</p><p>Accessibility can show up, or break down, at every one of those steps and that’s why I’ve started thinking about TV accessibility through the lens of customer journey mapping.</p><p>Start by mapping the journey</p><p>One of the things I like about journey mapping is that it makes you stop thinking about individual screens and start thinking about the whole experience.</p><p>Instead of asking:</p><p>“Do we have captions?”</p><p>I want to ask:</p><p>“Can someone easily find and turn on captions when they need them?”</p><p>Instead of:</p><p>“Is described video available?”</p><p>Ask:</p><p>“Can someone tell which content has described video and easily turn it on?”</p><p>And instead of:</p><p>“Is our login accessible?”</p><p>Ask:</p><p>“Can someone actually get into the service independently?”</p><p>That little shift in perspective can change the entire conversation.</p><p>I like to think about myself as the person on the couch, sitting several feet away, and holding a remote. I am navigating with directional buttons and I’m looking at an interface from across the room. By putting the customer experience first, it shifts my thinking. Suddenly, focus becomes crucial, and I’m finding myself asking questions like, where does the remote guide me next? Can I identify what’s selected? Can I return to the previous point? Is the text legible from the couch? Does the experience function with the assistive technology someone may use? These details might seem minor when viewing a screen during a product review, but they’re not so minor when you’re the one trying to watch a show.</p><p>The emotional side matters too. This is one of the things I find interesting about journey mapping. It isn’t just about what someone does; it’s also about how the experience makes them feel. Imagine finally finding something you want to watch, you’re ready to relax, you know the content has described video, but you can’t figure out where to turn it on. You find the setting, but it’s buried three menus deep. Or you turn it on and suddenly can’t figure out how to get back to the show. The feature technically works, but the experience doesn’t feel accessible. It feels frustrating, and that’s an important distinction. Good design should reduce friction by not creating another thing for the customer to figure out.</p><p>The journey doesn’t stop at Play</p><p>I think we sometimes treat the Play button as the finish line, but it’s not. We should be asking ourselves questions like:</p><ul><li>What happens when someone wants to change the caption size?</li><li>Turn described video off?</li><li>Rewind?</li><li>Find another episode?</li><li>Change audio settings?</li><li>Fix a problem?</li><li>Contact customer support?</li></ul><p>The journey keeps going and that’s why I think about streaming accessibility as three connected pieces:</p><ol><li>The content needs to be accessible.</li><li>The product needs to be accessible.</li><li>The service around it needs to be accessible too.</li></ol><p><strong>Include accessibility into the journey map</strong></p><p>The good news is that product teams don’t necessarily need to create a whole new process. Take the customer journey map you already have and apply an accessibility lens.</p><p>At each stage, ask:</p><p>Who could experience a barrier here?</p><p>What accessibility needs might they have?</p><p>What could get in their way?</p><p>Have we tested this with people with disabilities?</p><p>How will we know if we’ve actually improved the experience?</p><p>That last question is really important because accessibility shouldn’t disappear after launch. We can look at things like accessibility feature adoption, journey completion, customer feedback and accessibility-related support contacts to understand where people are still experiencing friction.</p><p>So… does your streaming service pass the Couch Test?</p><p>For me, it comes down to a pretty simple test.</p><p>Imagine someone sitting on their couch, and ask yourself, Can they:</p><p>Find it?</p><p>Navigate it?</p><p>Read it?</p><p>Hear it?</p><p>Control it?</p><p>Customize it?</p><p>Understand it?</p><p>Get help when something goes wrong?</p><p>And most importantly, can they just sit back and enjoy the show? That’s the goal because product management isn’t really about adding a collection of features to a streaming service.<a href="http://service.it/"> It</a>’s about making the whole customer journey work for more people. That’s the shift I want to see more of in TV and streaming:</p><p>From features to journeys.</p><p>From compliance to experience.</p><p>From testing the product to understanding the customer.</p><p>And from asking:</p><p>“Is this accessible?”</p><p>to asking:</p><p>“What does this experience actually feel like from the couch?”</p><p>Next time you are watching tv, ask yourself: Does my favourite tv or streaming service pass the Couch Test? Our work isn’t complete until it does all the time, and everytime.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd08cf71df39" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-couch-test-rethinking-streaming-accessibility-through-the-customer-journey-bd08cf71df39">The Couch Test: Rethinking Streaming Accessibility Through the Customer Journey</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[15 Years of GAAD: built by community, driven by inclusion]]></title>
            <link>https://medium.com/design-bootcamp/15-years-of-gaad-built-by-community-driven-by-inclusion-7a5ebbb0d998?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a5ebbb0d998</guid>
            <category><![CDATA[gaad]]></category>
            <category><![CDATA[digital-accessibility]]></category>
            <category><![CDATA[accessibility]]></category>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Fri, 22 May 2026 02:44:29 GMT</pubDate>
            <atom:updated>2026-05-22T21:05:25.658Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="White “GAAD” text in a circle on a textured black background. A keyboard icon is in the corner, suggesting a tech theme." src="https://cdn-images-1.medium.com/max/1024/1*zWOsLtUDTW_N_S_T43cEXQ.jpeg" /></figure><p>This year marks the 15th anniversary of Global Accessibility Awareness Day (GAAD), and it has given me an opportunity to reflect not only on my career in accessibility, but also on my own lived experience as someone who is limb different.</p><p>Accessibility has never been just part of my job. It has always been personal.</p><p>Growing up limb different shaped the way I experienced the world long before I ever worked in technology. It taught me early on that environments, products, and systems are often designed around assumptions of what people “should” be able to do. Sometimes those barriers were physical. Sometimes they were digital. Often, they were invisible to everyone except the people experiencing them.</p><p>In 2011, when my contract ended at Bell Canada, I found myself at a turning point professionally and personally. What I remember most from that time is not uncertainty, but community. It was the accessibility community in Toronto that showed up for me in ways I will never forget. Attending accessibility meetups gave me a sense of belonging, offering support, encouragement, opportunities to learn, and space to grow. That experience shaped the trajectory of my career and deepened my commitment to accessibility work in a way that still grounds me today.</p><p>This year’s GAAD theme, “Design. Develop. Deliver.” resonates deeply because accessibility cannot exist as a single checkpoint or conversation. It must be woven into every stage of creating experiences that people rely on every day.</p><h3>Design: inclusion starts with intention</h3><p>As someone who has navigated a world not always designed with disability in mind, I know how meaningful it feels when inclusion is considered from the start. Accessible design is about more than meeting standards or passing audits. It is about intentionally creating experiences where people feel included, respected, and independent.</p><p>Some of the best accessibility work I’ve seen happens when teams move beyond designing for compliance and start designing for people. That shift changes conversations, builds empathy, and challenges assumptions. When accessibility is prioritized early in design, everyone benefits.</p><h3>Develop: accessibility is built through collaboration</h3><p>Over the years, I’ve had the opportunity to work alongside incredibly passionate product managers, designers, developers, testers, researchers, and advocates who genuinely want to make technology better.</p><p>Accessibility work can sometimes feel overwhelming because there will always be more to improve. What continues to inspire me is seeing how much progress happens when people come together with curiosity, humility, and a willingness to learn.</p><p>I’ve watched accessibility evolve from being treated as an afterthought to becoming part of larger product and business conversations. Teams today are asking better questions, involving disabled voices earlier, and recognizing that accessibility improves experiences for everyone. That progress may be more difficult to quantify, but its qualitative impact is significant.</p><h3>Deliver: accessibility must work in real life</h3><p>For disabled people, accessibility is never theoretical, which is why delivery matters so much. It impacts whether we can independently complete tasks, participate in conversations, access information, or feel included in experiences others may take for granted.</p><p>Accessible experiences cannot stop at good intentions, roadmap discussions, or polished demos. They have to work consistently in the real world for real people using different devices, assistive technologies, and ways of interacting.</p><p>As someone with lived experience, I know how impactful it is when accessibility is done well and how exhausting it can be when it is overlooked.</p><h3>Looking ahead…</h3><p>One of the things I appreciate most about GAAD is the sense of community it represents. Over the years, I’ve met many people across the accessibility space, including advocates, professionals, allies, and people with disabilities who continue pushing this work forward every day. Those connections have shaped not only my career, but also how I think about leadership, inclusion, and what it means to build meaningful products.</p><p>Fifteen years later, accessibility conversations are happening earlier and more often than they once did. There is still a long way to go, but there is also real momentum.</p><p>As we mark this milestone anniversary, human-centered inclusive design reminds us that accessibility is not just about technology or compliance. It’s about people feeling seen, included, and able to fully participate, and that is work worth continuing to design, develop, and deliver together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a5ebbb0d998" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/15-years-of-gaad-built-by-community-driven-by-inclusion-7a5ebbb0d998">15 Years of GAAD: built by community, driven by inclusion</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The power of peer support during Limb Loss and Limb Difference Awareness Month]]></title>
            <link>https://a11yalicia.medium.com/the-power-of-peer-support-during-limb-loss-and-limb-difference-awareness-month-fc687d0244be?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc687d0244be</guid>
            <category><![CDATA[amputee]]></category>
            <category><![CDATA[limb-loss]]></category>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[limb-differences]]></category>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Fri, 01 May 2026 03:13:24 GMT</pubDate>
            <atom:updated>2026-05-02T01:09:05.047Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Man in a wheelchair with a prosthetic leg faces an “Out of Order” elevator. Wall reads “Amputees Helping Amputees.” Indoor setting." src="https://cdn-images-1.medium.com/max/1024/1*oA9LIlTulKiRA4crdqtIHg.png" /><figcaption>Amputees helping amputees</figcaption></figure><p>As Limb Loss and Limb Difference Awareness Month comes to a close, I find myself reflecting on the power of community and peer support. Attending the Celebration of Amputees event hosted by Limb Loss Connection was a powerful reminder of what connection can do. In a room filled with shared experiences, encouragement, and understanding, the value of peer support was impossible to miss. I even left with some awesome swag from Ottobock. It was a small but very meaningful reminder of the support and innovation surrounding the limb loss and limb difference community.</p><p>That feeling brought me back to fond memories of my childhood attending Child Amputee Seminars with The War Amps. Those gatherings were the first places where I experienced what it meant to be surrounded by people who truly understood my life experience. The veterans and organizers created space for learning, connection, and confidence. They showed me early on that community and story-telling could shape how a person saw themselves and their future.</p><p>Throughout April, Limb Loss and Limb Difference Awareness Month serves as more than just a campaign for awareness. It is a reminder of the importance of human connection, belonging, and ensuring that no one has to face limb loss or limb difference alone.</p><p>Peer support has been proven to be life-changing because it meets people where they are. When someone connects with another person who truly understands their experience, it helps ease isolation and replaces fear with hope. That sense of being understood is not just comforting, it is deeply important for mental health and well-being.</p><p>As someone who has had a lifetime of experience living with limb difference, I know firsthand how powerful connection can be. Being part of the limb loss and limb difference community has taught me that support does not always need to come from a professional setting to be meaningful. Sometimes the most healing moments come from someone pulling up a chair, introducing themselves by their first name only and sharing a compelling story of lived experience or a moment of laughter that only comes from a mutual understanding.</p><p>That lesson continues to shape my work as the founding chair of a disability-focused employee resource group at Bell. In that role, I continue to see how much people benefit from spaces where lived experience is welcomed, respected, and shared. Whether in a workplace or in the broader community, belonging makes a real difference in how people feel, cope, and thrive.</p><p>That kind of connection also has a powerful impact on mental health. It doesn’t matter if someone is born with a limb difference or missing limb, amputation of any kind at any stage of life often brings grief, uncertainty, frustration, and changes in identity. Peer support helps lighten that burden by creating space for honesty, encouragement, and shared strength. It reminds people that they are not alone in what they are feeling.</p><p>Mental health remains an important part of the journey to acceptance, even when it is not always visible. Feeling connected to others reduces loneliness, builds confidence, and makes life feel more manageable. It also reminds people that healing is not only physical, it is emotional, social, and deeply personal.</p><p>Looking back, my experiences with The War Amps, the Child Amputee Seminars, the recent Celebration of Amputees event, the awesome Ottobock swag in my bag, and my work leading a disability-focused employee resource group at Bell all reinforce how much people need community to thrive. When we create spaces where people feel seen, valued, and supported, we make room for resilience and hope. That kind of connection becomes a powerful protective factor for mental health and a source of strength during change and uncertainty.</p><p>As this awareness month ends, I want to thank some really amazing friends that reached out and reminded me that peer support is far more than encouragement. It is and always has been a form of care. Connection helps people heal, build resilience, and reminds every person with limb loss or limb difference that they matter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc687d0244be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What building safer conversational AI for youth mental health taught me]]></title>
            <link>https://medium.com/design-bootcamp/what-building-safer-conversational-ai-for-youth-mental-health-taught-me-e20a81033c92?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/e20a81033c92</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[mental-health]]></category>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Tue, 24 Mar 2026 11:25:06 GMT</pubDate>
            <atom:updated>2026-03-24T11:25:06.467Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Laptop displays “Building Safer AI for Youth Mental Health Hackathon,” notebook reads “How do we make this safer for struggling youth?”" src="https://cdn-images-1.medium.com/max/1024/1*1bU7rm_mw2dZDNcldF9jSA.png" /><figcaption>Safe development of conversational AI systems in youth mental health contexts</figcaption></figure><p>This past week, I was very humbled to participate in a groundbreaking national hackathon focused on building safer AI for youth mental health. It was a very insightful experience that required some really deep thinking and long sleepless nights.</p><p>As an accessibility professional, I’ve dealt with a lot of problem solving, team building, product inclusion and accessibility challenges over the years, but this particular challenge felt different right from the start. Mental health, diversity, equity and inclusion were core to the challenge. We were tasked with this very important problem:</p><p><strong>How might we make an AI agent genuinely safe for a young person who might already be having a really hard time?</strong></p><h3>The people behind the “users”</h3><p>As we stress tested the mock virtual assistant, I kept envisioning real moments while we worked. Teamwork was vital as we were all dealing with the pressure of tight time-constraints while maintaining our own mental well-being in this context and throughout this process. My team quickly figured out that I’m naturally a bit of a nighthawk. Often late at night as I was working through this challenge, there were moments that brought me back to a younger version of myself. I pictured a teen lying awake at night, not sure who to talk to, or someone staring at their phone, typing and deleting the same message over and over. It brought me back to being that young person trying to make sense of something really heavy, without knowing how to put it into words.</p><p>It made everything feel more real, and more human. I quickly understood just how important quality was in this challenge.</p><p>Conversational AI, in this space, doesn’t feel like a feature. It feels like a presence. Like something that’s stepping into a moment which already matters a lot, and that feeling has stayed with me throughout this challenge and I’m sure it will stay with me beyond.</p><h3>Rethinking what “safe” actually means</h3><p>By creating scenarios to stress test a mock VA, we realized pretty quickly that the usual ways of thinking about safety and quality isn’t enough.</p><p>It’s easy to test the happy paths of simple, straight-forward, and carefully crafted “standard” conversations, document system failures and then create default “safe” responses. But what happens when we apply messy, multi-turn, multi-lingual conversations that are nuanced, vague and full of spelling mistakes, slang and cultural references? And then, what if we applied real harm reduction methodology to ask harder, messier questions like:</p><ul><li>Would this actually make someone feel understood?</li><li>Could this response accidentally shut someone down?</li><li>Are we creating space for someone to open up — or quietly pushing them away?</li></ul><p>There were moments where I caught myself thinking, this sounds fine … but how would it land for a young girl who was born with short arms, lives in a small town, struggles with body image, is feeling alone and is looking for help?<em> </em>That shift, from checking boxes to really thinking about impact was extremely uncomfortable at times, but deeply important.</p><h3>The part I kept coming back to…</h3><p>Accessibility was always in the back of my mind, because this challenge had a deeper, more meaningful impact. If any young person can’t understand what’s being said, or if the experience feels confusing or overwhelming, none of it works.</p><p>Safety in this context isn’t just about creating simple and straight-forward guardrails, it’s about keeping language simple, making things easier to follow when someone’s already stressed, and supporting different ways people communicate. Typical self-expression doesn’t exist in this context and the system would need to be able to navigate through the messiness of human behaviour in someone’s most vulnerable moments.</p><p>For me, it reinforced something I already believe deeply: <strong>if it’s not accessible, it’s not safe.</strong></p><h3>Sitting with the tension</h3><p>One of the hardest parts of the whole experience was sitting with this question:</p><p><strong>When is AI helping — and when is it causing harm?</strong></p><p>There’s a real risk in trying to make AI feel too capable in moments that actually need human intervention. Assessing whether something is being helpful or harmful means making sure it’s not only easy to reach a real person when it matters most, but it also means assessing the level of guidance and intervention that is required for a particular situation or circumstance. There isn’t a perfect answer here, but ignoring the question isn’t an option.</p><h3>What I’m taking with me</h3><p>I left the hackathon feeling a bit different about my work. I’m much more aware of the level of responsibility that comes with building in this space. More thoughtful about the small details that can change how something feels for someone on the other side.</p><p>A few things I know I’ll carry forward:</p><ul><li>Think about people in their hardest moments, not just their easiest ones</li><li>Care about how something feels, not just how it performs</li><li>Make space for youth voices — they understand this better than anyone</li><li>Keep accessibility front and center, always</li></ul><h3>Final thought</h3><p>What stuck with me most is this, when a young person reaches out for help, even in a small way, it’s not casual. It takes courage.</p><p>Whatever or whomever meets them in that moment, whether it’s a person or a piece of technology, becomes part of that experience. Being part of this hackathon reminded me that this isn’t just about building smarter systems. It’s about showing up, in the right way, when it really matters.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e20a81033c92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/what-building-safer-conversational-ai-for-youth-mental-health-taught-me-e20a81033c92">What building safer conversational AI for youth mental health taught me</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When inclusion ships: A product launch with purpose]]></title>
            <link>https://medium.com/design-bootcamp/when-inclusion-ships-a-product-launch-with-purpose-083bdf008f07?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/083bdf008f07</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Thu, 05 Mar 2026 08:04:00 GMT</pubDate>
            <atom:updated>2026-03-05T08:04:00.396Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Video call on a laptop screen with a woman in a brown shirt using sign language. Books and plants in the background. Hands typing." src="https://cdn-images-1.medium.com/max/740/0*PJWKjeAJa6drYFsr.jpg" /></figure><p>As product leaders, we talk a lot about inclusion. But every so often, we get to ship it.</p><p>Launching a virtual sign language interpretation (VSLI) service is one of those moments where product, purpose, and people genuinely come together. For me, this launch carries a deeper meaning — not just as a senior technical product manager focused on accessibility, but as a woman with a disability.</p><p>Accessibility work is often described as “the right thing to do.” And it is. But when you’ve personally navigated systems that weren’t designed with you in mind, it becomes more than principle. It becomes personal.</p><p>For Deaf and hard of hearing individuals, communication barriers can quietly shape every interaction — from accessing services to participating in meetings to consuming media. When those barriers intersect with gender inequities, the impact compounds. A virtual sign language interpretation service helps remove one of the most fundamental obstacles: the ability to communicate in real time, on equal footing.</p><p>Accessibility isn’t a feature. It’s infrastructure.</p><p>From a product perspective, launching a Virtual Sign Language Interpretation Service for a retail environment isn’t about adding a button to a screen. It touches device selection and procurement, authentication flows, real-time video performance, privacy safeguards, compliance requirements, and overall user experience for both the customer and the customer service representative. It requires thoughtful decisions about the customer experience including retail store location, design, setup and hardware, latency, interpreter availability, secure session handling, and what happens when connectivity fluctuates. It means ensuring the whole experience works seamlessly for the customer from the time they walk in the door to the time they leave the store.</p><p>It also means doing the work early. Engaging Deaf users in discovery. and writing accessibility acceptance criteria into product requirements from day one. Testing with real users, not just internal QA scripts. Establishing clear ownership so accessibility isn’t treated as an afterthought.</p><p>Partnership matters deeply in this work. Organizations like Canadian Hearing Services bring lived expertise that product teams simply cannot replicate on their own. Building responsibly means listening, iterating, and remaining accountable long after launch day.</p><p>As a woman with a disability working in product leadership, this launch feels like representation in action. Too often, accessibility is championed quietly — advocated for in roadmap debates, defended in budget discussions, negotiated in scope trade-offs. Being able to stand behind a service that tangibly removes barriers is a reminder that lived experience is not a limitation in product leadership. It is an advantage.</p><p>There is significant operational rigor behind a launch like this. Retail, legal, regulatory, technology and product alignment. Vendor contracts and SLAs. Security reviews. Customer care training. Accessible marketing and communications. Executive sponsorship. None of it is accidental. Inclusion at scale requires structure.</p><p>We can measure usage, uptime, connection speed, interpreter response times, and satisfaction scores. Those metrics matter. But the deeper impact is harder to quantify. It’s in the moment when someone can access a service independently. When participation doesn’t require workaround or accommodation requests. When access is built in.</p><p>For me, this product launch represents more than a milestone. It represents progress — not just in product maturity, but in who gets to shape the systems we build.</p><p>Accessibility is often described as a journey. That’s true. But moments like this are reminders that the journey moves forward because people insist it does.</p><p>And sometimes, we get to ship something that makes the path a little more accessible for everyone.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=083bdf008f07" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/when-inclusion-ships-a-product-launch-with-purpose-083bdf008f07">When inclusion ships: A product launch with purpose</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Start the new year by running your sprint reviews with zoom and text scaling turned on]]></title>
            <link>https://medium.com/design-bootcamp/start-the-new-year-by-running-your-sprint-reviews-with-zoom-and-text-scaling-turned-on-997b40d3b9b2?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/997b40d3b9b2</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Mon, 12 Jan 2026 12:10:08 GMT</pubDate>
            <atom:updated>2026-01-12T12:10:08.194Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="TV screen shows “Masterchef Canada” episode with two chefs, kitchen background. Menu below includes options like “Top Critic.” Room has plants." src="https://cdn-images-1.medium.com/max/1024/1*cSfdGcQ9epkf_UeP3chqnw.png" /></figure><p>Sprint reviews are all about one thing: figuring out whether what we built actually works for real people.</p><p>As we kick off the new year, it’s a good time to pause and ask an honest question: are we really seeing our product the way people use it? When we review a TV experience at the default size, we’re usually seeing it under ideal conditions. Everything fits. Nothing is stressed. It’s the most forgiving version of the product, and it’s rarely the one people experience at home.</p><p>There’s a small but powerful shift you can make this year: run your sprint reviews with zoom magnification and text scaling enabled, and leave them on.</p><p>This isn’t about running a one-off accessibility exercise. Just bump the zoom to 2X or 4X, set the text to large, and review the product like that.</p><p>What tends to happen is the room quiets down, attention sharpens, and details that might’ve been brushed off before start to stand out. It’s a simple way to kick off the year with a clearer view of what you’re shipping.</p><h3>Why zoom and text scaling matter on TV</h3><p>Zoom magnification and text scaling aren’t edge cases. A lot of people rely on them — people with low vision, older viewers, and anyone sitting farther from the screen than we usually design for.</p><p>TV already introduces challenges:</p><ul><li>You’re several feet away from the screen</li><li>Interfaces are dense and visually busy</li><li>Focus, layout, and text all need to hold up as things get bigger</li></ul><p>Zoom shows you how the layout behaves under pressure.</p><p>Text scaling shows you whether your content still makes sense when words take up more space.</p><p>If either of those settings breaks the experience, that’s not user error. It’s feedback from the product.</p><p>Sprint review is the right place to see this feedback, because you’re looking at real screens, real flows, and real constraints — not idealized mocks.</p><h3>What you’ll notice almost immediately</h3><p>Once zoom or text scaling are on, issues surface fast.</p><p>Text that seemed readable suddenly feels crowded. Headings overwhelm the screen. Labels wrap in odd places or push other content out of view. Important information gets cut off, while secondary details quietly disappear.</p><p>Layouts that once felt solid start to feel fragile. The user interface doesn’t adapt and horizontal scrolling suddenly appears. Pop-ups overflow and primary actions drift off-screen with no obvious way back.</p><p>Focus is often where things really unravel. It becomes harder to track where you are. Focus indicators get clipped or lost, and navigation starts to feel more tiring than intuitive.</p><p>These aren’t rare edge cases. They’re everyday usability problems — and you don’t have to hunt for them.</p><h3>How to do this without making it awkward</h3><p>You don’t need a new process or a big announcement.</p><p>Turn on zoom and/or increase text size before the demo starts. Don’t frame it as a test. Treat it like a perfectly normal way someone might be using your product.</p><p>Walk through real tasks: search, sign-in, settings, playback, error states. Zoom and text scaling are especially good at exposing complexity, so resist the urge to stick to only the happiest paths.</p><p>As you go, talk about what you’re noticing. If something feels harder to read or navigate, say it out loud. Let the team experience it together, in real time.</p><p>When issues come up, capture them like any other product work, because that’s exactly what they are.</p><h3>The shift this creates</h3><p>What I love about this practice is how quickly it changes how teams think.</p><ul><li>Designers start considering scale and text size earlier.</li><li>Engineers build layouts that adapt more gracefully.</li><li>Product managers catch problems before users ever do.</li></ul><p>Accessibility stops feeling abstract, and no-one has to imagine what a low-vision user *might* experience — it’s right there on the screen, shared by everyone in the room. Starting the year this way sets the tone for smarter, more inclusive decisions in every sprint.</p><h3>One step to take this year</h3><p>As you start the new year, try this: run your sprint review with zoom and/or text scaling turned on. Leave them on. Pay attention to what breaks or what suddenly feels harder than it should.</p><p>If your product only works when text is small and everything is perfectly sized, it doesn’t really work.</p><p>Sprint review is the safest, smartest place to discover that, and the best place to start fresh this year.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=997b40d3b9b2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/start-the-new-year-by-running-your-sprint-reviews-with-zoom-and-text-scaling-turned-on-997b40d3b9b2">Start the new year by running your sprint reviews with zoom and text scaling turned on</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The anatomy of an accessible video player (on TV)]]></title>
            <link>https://medium.com/design-bootcamp/the-anatomy-of-an-accessible-video-player-on-tv-54998fbbe240?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/54998fbbe240</guid>
            <category><![CDATA[video-player]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[connected-tv]]></category>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Wed, 17 Dec 2025 12:13:25 GMT</pubDate>
            <atom:updated>2025-12-17T12:13:25.165Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Video player interface with labeled controls: play, captions, settings, and described video. Progress bar shows 5:20/20:00. Caption text displayed." src="https://cdn-images-1.medium.com/max/1024/1*vai1n_miOE9imtbSPy4oxw.png" /></figure><p>A video player is the heart of any TV experience. It’s where content, business goals, and human needs collide — and where accessibility failures are most visible.</p><p>Unlike mobile or web, TV video players must work across remotes, ten-foot viewing distances, assistive technologies, and wildly different hardware capabilities. When a video player isn’t accessible on TV, users don’t just have a “slightly worse” experience — they often can’t watch at all.</p><p>An accessible TV video player isn’t one feature. It’s a system. Let’s break down its anatomy.</p><h3>Clear, predictable focus management</h3><p>If focus is broken, nothing else matters.</p><p>On TV, the remote is the primary input. Every control in the video player must be reachable, visible, and logically ordered using directional navigation.</p><p><strong>What accessible focus looks like:</strong></p><ul><li>Visible focus indicators with sufficient contrast</li><li>Logical left/right/up/down navigation between controls</li><li>No focus traps (users can always exit overlays and menus)</li><li>Focus returns to a predictable location after closing menus</li></ul><p><strong>Common failure modes:</strong></p><ul><li>Focus disappearing when controls auto-hide</li><li>Focus jumping unexpectedly when captions or settings open</li><li>Inability to reach controls like “More options” or “Audio tracks”</li></ul><p>For keyboard-only users, switch users, and screen reader users, <strong>focus <em>is</em> the interface.</strong></p><h3>Large, legible controls for the 10-foot experience</h3><p>TV is not a phone across the room — it’s a different context entirely.</p><p>Video player controls must be readable, distinguishable, and usable from a distance, across screen sizes and resolutions.</p><p><strong>Accessibility requirements:</strong></p><ul><li>Text that remains legible at typical viewing distances</li><li>Icons paired with text labels where possible</li><li>Adequate spacing between controls to prevent mis-navigation</li><li>High contrast between controls and video content</li></ul><p><strong>Watch out for:</strong></p><ul><li>Tiny progress bars that are impossible to scrub precisely</li><li>Low-contrast icons over bright or complex video scenes</li><li>Controls that rely on color alone to convey state (e.g., play vs pause)</li></ul><h3>Captions that are actually usable (and customizable)</h3><p>Captions are not an optional enhancement — they’re core functionality. But <em>having</em> captions is only half the story. An accessible TV video player gives users control over how captions appear so they can read them comfortably in their own environment.</p><p>Living rooms vary. Vision varies. Lighting varies. Caption customization is how you meet users where they are.</p><h3>Essential caption customization options</h3><p>An accessible TV video player should allow users to adjust:</p><ul><li><strong>Text size </strong>So captions remain readable at different viewing distances.</li><li><strong>Font style </strong>Including a clear, sans-serif option optimized for TV readability.</li><li><strong>Text colour </strong>Supporting high-contrast combinations beyond white-on-black.</li><li><strong>Background colour and opacity </strong>Allowing users to reduce visual noise from busy video content.</li><li><strong>Edge styles or text outlines </strong>Especially important for users with low vision.</li><li><strong>Window position (when supported) </strong>So captions don’t cover critical on-screen information.</li></ul><h3>Respect system-level accessibility settings</h3><p>On TV platforms that provide system caption preferences (such as Android TV and tvOS), the video player should:</p><ul><li>Honour system caption styles by default</li><li>Avoid overriding user-defined preferences</li><li>Clearly indicate when player-level settings differ from system settings</li></ul><p>Ignoring system caption settings forces users to reconfigure accessibility options they’ve already set — often repeatedly, across apps.</p><h3>Discoverability matters</h3><p>Caption controls and customization must be:</p><ul><li>Easy to find from the player UI</li><li>Reachable using only a remote</li><li>Labeled clearly for screen readers</li></ul><p>Burying caption settings behind ambiguous icons or deep menus turns a required accessibility feature into a scavenger hunt.</p><h3>Common failure modes</h3><ul><li>Captions shrink or disappear when controls appear</li><li>Caption styles reset between episodes</li><li>Custom styles work for VOD but not live content or ads</li><li>The player ignores system caption settings entirely</li></ul><p>For many users — especially those who are Deaf, hard of hearing, neurodivergent, or watching in noisy environments — caption customization is the difference between usable and unusable content.</p><h3>Screen reader and voice support</h3><p>Yes — people use screen readers on TV.</p><p>Your video player must expose meaningful labels, roles, and states to assistive technologies like TalkBack and Voice Assistant.</p><p><strong>Accessible player elements should:</strong></p><ul><li>Announce control names (“Play,” “Pause,” “Skip forward 10 seconds”)</li><li>Communicate state changes (“Paused,” “Captions on”)</li><li>Avoid redundant or verbose announcements during playback</li></ul><p><strong>Be especially careful with:</strong></p><ul><li>Progress bars and time indicators</li><li>Dynamic controls that appear or disappear</li><li>Auto-updating content that steals focus</li></ul><p><strong>Pro tip: </strong>Test with real screen reader users. Emulators won’t reveal timing and verbosity issues.</p><h3>Audio and subtitle track selection</h3><p>Accessible players don’t assume a single audio experience.</p><p>Users must be able to:</p><ul><li>Select described video tracks</li><li>Switch between spoken languages</li><li>Understand which track is currently active</li></ul><p><strong>Key requirements:</strong></p><ul><li>Clear labeling (e.g., “English — Described Video”)</li><li>Consistent navigation within track selection menus</li><li>Persistence of user preferences across sessions when possible</li></ul><p><strong>Failure example: </strong>Described Video exists but is buried three layers deep in an unlabeled menu.</p><h3>Playback controls that respect user control</h3><p>Auto-play, auto-advance, and hidden controls can quickly become accessibility barriers.</p><p><strong>Accessible behavior includes:</strong></p><ul><li>Enough time to read and interact with controls</li><li>The ability to pause, stop, and resume playback reliably</li><li>No unexpected playback changes triggered by focus movement</li></ul><p>This is especially important for:</p><ul><li>Users with motor impairments</li><li>Users with cognitive or attention-related disabilities</li><li>Screen reader users navigating sequentially</li></ul><h3>Error states and loading feedback</h3><p>Accessibility doesn’t end when playback fails.</p><p>Your player should clearly communicate:</p><ul><li>Buffering and loading states</li><li>Playback errors and recovery options</li><li>Network or entitlement issues</li></ul><p><strong>Accessible feedback means:</strong></p><ul><li>Visible, readable messages on screen</li><li>Screen reader announcements for status changes</li><li>Clear next steps (Retry, Go back, Learn more)</li></ul><p>Silence or spinning indicators alone are not accessible.</p><h3>Consistency across content types</h3><p>An accessible player behaves the same way everywhere.</p><p>Users shouldn’t have to relearn controls for:</p><ul><li>Ads vs main content</li><li>Live vs on-demand</li><li>Trailers vs full episodes</li></ul><p>Inconsistent player behavior is a cognitive accessibility issue — and a trust issue.</p><h3>Accessibility is the player</h3><p>On TV, accessibility is not a layer you add to a video player. <strong>The video player <em>is</em> the accessible experience.</strong></p><p>When it’s done right:</p><ul><li>Users stay longer</li><li>Content reaches more people</li><li>Support tickets go down</li><li>Accessibility debt stops compounding</li></ul><p>If you’re building or auditing a TV video player, start here. Break it down. Test it with real users. <strong>Please remember</strong>: if someone can’t control playback independently, the content might as well not exist.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=54998fbbe240" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-anatomy-of-an-accessible-video-player-on-tv-54998fbbe240">The anatomy of an accessible video player (on TV)</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Solving small text and contrast issues for large-screen readability]]></title>
            <link>https://medium.com/design-bootcamp/solving-small-text-and-contrast-issues-for-large-screen-readability-7847a96e7d2c?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/7847a96e7d2c</guid>
            <category><![CDATA[visual-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[tv-ux]]></category>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Thu, 04 Dec 2025 08:30:10 GMT</pubDate>
            <atom:updated>2025-12-04T08:30:10.506Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Why your beautiful UI becomes unreadable the moment it hits a TV screen — and how to fix it.</em></p><figure><img alt="Hand holds a remote, searching for “series” on a TV screen. Letters and numbers appear above a row of show thumbnails." src="https://cdn-images-1.medium.com/max/1024/1*4M7VXmtIwGcerZzrWRgUBQ.jpeg" /></figure><p>The user experience for TV aligns more with billboard design than with app design, and cannot be treated as a simple enlargement of mobile interfaces. The challenges of viewing distance, screen variability, lighting conditions, and non-touch interaction all collide — and small typography and low contrast are usually the first things to break. It’s a reminder — especially on the International Day of Persons with Disabilities — that accessibility isn’t a side note, but central to resilient design.</p><p>Here’s how to fix them before your users struggle, squint, or churn.</p><h3>Why TV text fails: the 10-foot problem</h3><p>Smartphone users typically hold their devices 10 to 14 inches from their face for optimal viewing, while TV viewers sit 8 to 12 feet away, affecting perceived content size and clarity. A font size comfortable on a phone may seem tiny on a TV, posing a challenge for user interface design across devices. Environmental factors worsen readability on TVs:</p><ul><li><strong>Bright Room Lighting:</strong> Overhead lights or sunlight can cause glare, reducing text and image visibility.</li><li><strong>Reflections:</strong> Reflections from surroundings can obscure content and distract viewers.</li><li><strong>Low-Quality or Older TVs:</strong> Older or lower-resolution TVs may display pixelated and blurry images.</li><li><strong>Compressed Streamed UI Layers:</strong> Compression during streaming can degrade UI quality, causing blurriness.</li></ul><p>These factors can make a clear mobile interface appear blurry or illegible on a TV. Designers must consider viewing distance, screen size, resolution, and conditions to ensure effective user interaction across platforms.</p><h3>Size text for actual viewing distance</h3><p>TV text needs to be larger than you think, especially for labels, menus, and metadata. Amazon TV have 10-foot-UI guidelines that include text size recommendations, of 28px minimum when viewed on a 1080p screen; however, it does not take any degree of vision loss into account, use 28px as a minimum rather than a target, aim to exceed it wherever possible.</p><h3>General safe ranges:</h3><ul><li><strong>Body text:</strong> 28–36 px</li><li><strong>Menu items:</strong> 32–44 px</li><li><strong>Titles:</strong> 48–80 px</li><li><strong>Subtitles &amp; captions:</strong> 55–75 px (varies by OS, often user-controlled)</li></ul><p>And remember: different TV OSes handle scaling differently. Roku, for example, renders text differently than Apple TV or Tizen.</p><p><strong>Best practice: </strong>Design and prototype with a <strong>10-foot preview</strong> — whether that’s a real TV, simulated view in Figma, or a remote-device preview.</p><h3>Increase contrast — far beyond WCAG minimums</h3><p>On TV, just hitting a WCAG 4.5:1 contrast ratio often isn’t enough to make sure content is easy to see and read. This is especially true in places where the viewing conditions change a lot, and where the display tech quality really affects the user experience.</p><p>Why is this happening?</p><ul><li>Many new TVs have strong image processing features that aim to make pictures look more vibrant and dynamic. But sometimes, this means losing details in darker parts of the picture, which can mess with how well you can see text and other key elements.</li><li>Dynamic backlighting systems try to boost contrast by changing brightness based on what’s on the screen. However, they can sometimes squash midtones, making it tough to tell different shades apart, especially in text or graphics that need those midtones to be clear.</li><li>Motion smoothing features, meant to cut down on motion blur in fast scenes, can accidentally make static images or text look less sharp. This can make things look soft or blurry, hurting the readability of on-screen content.</li><li>When UI elements get compressed, they can lose their sharp edges, making it tough to focus on them. This is a big issue for smaller text or icons, which might blend into busy backgrounds.</li><li>Plus, the glow from the room can really lower the perceived contrast on the screen. Ambient lighting can wash out colors and lessen the impact of contrast ratios, so it’s important to think about lighting when checking visibility.</li></ul><p>Given these issues, it’s smart to aim for:</p><ul><li><strong>7:1 or higher</strong> contrast ratio for text. This higher ratio helps text stay readable against different backgrounds, even in not-so-great viewing conditions.</li><li><strong>10:1 or higher</strong> for small UI elements. Small text and icons need even more contrast to be easily seen and used, especially for people with visual impairments.</li><li>Avoid using thin, lightweight fonts on bright or complex backgrounds, as this can make visibility worse. Choosing bolder fonts can improve readability and make sure text pops out.</li></ul><p>If your design needs background images, here are some ways to keep things visible:</p><ul><li>Use darkening overlays to lower the brightness of the background image, helping text stand out better. This keeps the text readable without losing the image’s visual appeal.</li><li>Scrims, or semi-transparent layers over the background, can help mute distracting elements and boost text visibility. This is handy for busy or colorful images.</li><li>Blur layers can also help by softening the background image, reducing visual noise and letting the text take center stage. This creates a more focused and readable interface.</li><li>Adding solid-color plates behind text can create a clear contrast that improves readability, no matter how complex the background is. This is great for making sure important info is easy for everyone to access.</li></ul><p>Ultimately, your users shouldn’t have to guess where to look or struggle to read what’s on the screen. By focusing on contrast ratios and using smart design strategies, you can create a more inclusive and user-friendly experience for a wide range of visual abilities and viewing conditions.</p><h3>Avoid low-resolution text rendering</h3><p>Some platforms — especially legacy or budget TVs — render text using older GPU pipelines. This means:</p><ul><li>anti-aliasing is inconsistent</li><li>thin strokes disappear</li><li>semi-transparent edges look fuzzy</li><li>white text blooms on bright panels</li></ul><h3>Solutions:</h3><ul><li>Use <strong>medium to bold weights</strong></li><li>Avoid ultra-thin fonts and light weights</li><li>Test on the lowest-quality device you support — not just your 4K OLED demo unit</li><li>Use vector or system text where possible (images with text often degrade)</li></ul><h3>Give text space to breathe</h3><p>Dense layouts might look clean on desktop, but on TV they quickly turn into visual noise.</p><p>Improve readability by:</p><ul><li>Increasing <strong>line height</strong> (150–170%)</li><li>Adding <strong>letter spacing</strong> to uppercase labels</li><li>Using <strong>high-contrast focus states</strong> with clear outlines</li><li>Avoiding long paragraphs — break text into scannable chunks</li></ul><p>Your UI should look legible from across the room, not just from your desk.</p><h3>Test in real living-room conditions</h3><p>Nothing replaces real-world testing.</p><h3>Simulate:</h3><ul><li>A bright sunlit room</li><li>A dim home-theatre environment</li><li>A budget 1080p TV in “Vivid” mode</li><li>Older devices with lower GPU rendering quality</li></ul><h3>Ask users:</h3><ul><li>“Can you read this title from where you’d normally sit?”</li><li>“Which items feel too small or too light?”</li><li>“Where did your eyes go first?”</li></ul><p>Even better: Use remote testing tools to observe how the UI performs over real streaming networks — the compression alone may change your design decisions.</p><h3>Design for reality, not for your monitor</h3><p>When designers see their UI on a real TV for the first time, one phrase usually comes out: <strong>“Oh wow… everything looks smaller than I expected.” </strong>That’s normal. The fix is straightforward: <strong>bigger text, higher contrast, better spacing, and real-world testing.</strong></p><p>Build these into your design and QA cycles and you’ll reduce support tickets, improve accessibility, and create an experience that feels “effortless” for users — no squinting required.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7847a96e7d2c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/solving-small-text-and-contrast-issues-for-large-screen-readability-7847a96e7d2c">Solving small text and contrast issues for large-screen readability</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why accessibility on TV is fundamentally different from mobile]]></title>
            <link>https://medium.com/design-bootcamp/why-accessibility-on-tv-is-fundamentally-different-from-mobile-2a252508d31e?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/2a252508d31e</guid>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 20:49:15 GMT</pubDate>
            <atom:updated>2025-11-11T20:49:15.886Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Hands interacting with smartphone on left, TV and remote on right. Blue interface, simple layout. Concept of mobile vs TV control." src="https://cdn-images-1.medium.com/max/1024/1*kdxUoJprYXEWwvYjx47BIw.jpeg" /></figure><p>We often borrow mental models from mobile when designing for TV because people’s behavior and expectations are becoming similar across devices. However, this can be problematic. Touch interactions, like tapping, are intuitive on mobile but not suitable for TV, where users typically rely on remote controls or voice commands. Similarly, simply adding labels and roles for accessibility, as done on mobile, may not enhance the TV viewing experience, which is more passive.</p><p>While mobile design ideas can be useful, TV requires its own unique design approach due to its distinct input, viewing, distance, and cognitive environments. Therefore, TV accessibility needs a specialized practice, not just an adaptation of mobile guidelines.</p><h3>Understanding the difference in user Interactions</h3><p>Mobile users interact directly with content by touching the screen, while TV users rely on a remote to move a highlight around. This key difference shapes the user experience, making mobile interactions feel more hands-on and intuitive, unlike the more detached feel of using a TV. How you select things really affects how easy and enjoyable it is to use the interface and engage with content. For a good experience, navigating should be easy. TV interfaces need to have a clear and logical order for moving around, so users don’t get lost. If the focus jumps around unpredictably, it can confuse users and hurt the overall experience. Focus jumps happen when the highlight moves unexpectedly, and traps occur when users can’t move through the options. Both of these can be really frustrating and make people lose interest.</p><p>Accessibility here isn’t just digital. It’s physical ergonomics, distance, posture, and environment. TV lives in the room, not just in the hand. Good navigation builds user confidence, and accessibility isn’t just about what you see and hear; it’s about designing in a way that makes navigation clear and consistent for everyone.</p><h3>Respecting personal preferences and social experience</h3><p>Mobile devices are typically used by individuals with unique personal preferences, such as color schemes, font sizes, and layout configurations. These preferences also include accessibility features like screen readers, voice commands, and text size adjustments to cater to diverse needs, enhancing user experience and satisfaction. Whereas, television viewing usually involves groups of 2 to 6 people with varying sensory and cognitive abilities. Differences in hearing, vision, and comprehension among viewers necessitate inclusive design to accommodate diverse capabilities, ensuring all can engage with the content effectively.</p><p>Design must address multiple needs for both mobile and television platforms, creating flexible solutions for varied user interactions. For instance, in a family watching a movie, the interface should consider different engagement levels.</p><p>Caption size exemplifies this challenge, as what works for one viewer may not suit another based on their distance from the TV. Flexible design, such as adjustable caption sizes, is crucial to meet the needs of all viewers and enhance the viewing experience.</p><h3>Designing for the 10 foot experience</h3><p>This fundamentally changes visual accessibility:</p><ul><li>hit areas are not finger-sized — they’re <em>focus-sized</em></li><li>information density must be lower</li><li>fonts must be larger</li><li>color contrast needs to be stronger</li></ul><p>A beautiful mobile UI can become illegible on TV because of distance. If glare is bad on mobile, users will tilt the phone; however, if glare is bad on TV, users need to change the entire lighting setup.</p><h3>Disparity Between Mobile and TV Accessibility Standards</h3><p>Mobile accessibility is well-developed and standardized, showcasing a significant evolution in how applications and websites cater to users with disabilities. This development stems from a concerted effort by various stakeholders, including developers, designers, and advocacy groups, to create inclusive digital experiences. In contrast, TV accessibility remains fragmented, presenting numerous challenges for users who rely on assistive technologies to navigate and enjoy content on their televisions.</p><p>Every TV platform:</p><ul><li><strong>Roku</strong>: Roku has made strides in accessibility, offering features such as voice control and screen reader functionality. However, the implementation can vary significantly between different Roku devices and channels, leading to an inconsistent user experience.</li><li><strong>Apple TV</strong>: Apple TV is known for its robust accessibility features, including VoiceOver, which provides spoken descriptions of on-screen elements. Apple’s commitment to accessibility is evident, yet the complexity of its interface can still pose challenges for some users.</li><li><strong>Fire TV</strong>: Amazon’s Fire TV includes accessibility options like VoiceView, but similar to other platforms, the effectiveness of these features can differ based on the apps being used. This inconsistency can frustrate users who expect a seamless experience across all content.</li><li><strong>Android TV / Google TV</strong>: Android TV and Google TV offer a variety of accessibility tools, including TalkBack. Nonetheless, the diversity of manufacturers and customizations can lead to a fragmented experience, complicating the navigation for users with disabilities.</li><li><strong>Samsung Tizen</strong>: Samsung’s Tizen platform provides accessibility features, including voice guides, but the implementation can vary between models and software versions, which may hinder usability for some users.</li><li><strong>LG webOS</strong>: LG’s webOS includes accessibility settings, but like other platforms, the effectiveness and availability of these features can differ, leading to a lack of uniformity that can be detrimental to user experience.</li></ul><p>Each of these platforms implements screen readers differently, which can lead to confusion and frustration for users who switch between devices. The variations in roles, focus events, spatial navigation, and component trees mean that there is no standard approach to accessibility across these platforms. This lack of uniformity results in a fragmented landscape where users may find themselves struggling to access content that should, in theory, be readily available to them.</p><p>Web and mobile accessibility patterns and guidelines are <em>mature, while</em> TV accessibility is still very <em>messy.</em> The disparity in development between mobile and TV platforms highlights the urgent need for a more cohesive approach to accessibility in the television space. As more consumers turn to smart TVs as their primary source of entertainment, ensuring that these platforms are accessible to all users, regardless of their abilities, is crucial for inclusivity and equal access to media. The evolution of TV accessibility must prioritize user experience, standardization, and the incorporation of best practices from the ICT accessibility standard to create a more equitable viewing environment for everyone.</p><h3>The takeaway</h3><p>When TV product managers claim “if it works on mobile, it will work on TV,” they are applying assumptions that don’t fit.</p><p>Accessibility on TV is not merely an enlarged version of mobile accessibility.</p><p>Accessibility on TV is <strong>spatial</strong> accessibility.</p><p>The medium is characterized by physical space, social context, and interaction based on focus — requiring different skills, patterns, and testing methods.</p><p>To achieve accessible TV, we must stop “porting” mobile patterns and begin designing for the true nature of TV:</p><p><strong>an experience crafted for distance, shared context, and users who cannot directly touch the interface they are interacting with.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2a252508d31e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/why-accessibility-on-tv-is-fundamentally-different-from-mobile-2a252508d31e">Why accessibility on TV is fundamentally different from mobile</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Testing with TV Watchers Can Teach You About ‘Keyboard-Only’ Design]]></title>
            <link>https://medium.com/design-bootcamp/what-testing-with-tv-watchers-can-teach-you-about-keyboard-only-design-3842f4fb3c36?source=rss-af8687857e13------2</link>
            <guid isPermaLink="false">https://medium.com/p/3842f4fb3c36</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[interaction-design]]></category>
            <dc:creator><![CDATA[Alicia Jarvis, CPACC, CSM]]></dc:creator>
            <pubDate>Mon, 03 Nov 2025 17:46:49 GMT</pubDate>
            <atom:updated>2025-11-03T17:46:49.233Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="TV displaying flowchart with yellow arrows and a play icon, beside a remote control. Blue background, clean design." src="https://cdn-images-1.medium.com/max/1024/1*UykeIjBDGHzi1Ch12j9b5w.png" /><figcaption>Logical focus order is a contract, not a philosophy</figcaption></figure><p>Most TV app teams think they’ve solved navigation once they support ↑ ↓ ← → + OK. When you build for connected TVs, “keyboard-only” isn’t just an accessibility edge case — it’s the default interaction model. Howver, it’s not until you run some tests with real users — especially those with dexterity and fine motor control challenges — that you realize how much friction hides in those few buttons. It quickly becomes obvious that “keyboard-only” is not only about inputs — it’s about <strong>predictability</strong>.</p><h3>The myth of “it works with the remote”</h3><p>Many teams test navigation with developers or QA staff who already know how the interface is <em>supposed</em> to work. They can zip through menus using muscle memory and visual cues. When you test with real users — especially those who depend on predictable focus order and voice feedback — you see how quickly a design breaks down.</p><ul><li>Focus gets trapped inside carousels.</li><li>Hidden elements steal focus.</li><li>On-screen keyboards hijack navigation paths.</li><li>Remote “Back” doesn’t always behave as expected.</li></ul><p>These may seem like minor annoyances in development, but for users, they’re roadblocks. Users don’t memorize your UI, they memorize rules. When “down” moves down — except in that one weird component — that inconsistency destroys trust instantly. The mental labour then becomes, “remember where the trap doors are”, and that then creates frustration and rage. Users don’t rage because something takes 8 keystrokes. They get frustrated and rage because they feel trapped, and the feeling of being “stuck” matters much more than the feeling of being “too slow”.</p><h3>What real user testing reveals</h3><ol><li><strong>Predictability builds confidence: </strong>Watching a user navigate your app without visual guidance shows how critical predictable focus order is. Each press should move the focus logically — top to bottom, left to right, or following the layout’s hierarchy. If users can anticipate where focus will go next, they relax into the experience.</li><li><strong>Labels and context matter: </strong>When testers rely on screen readers like TalkBack (Android TV) or VoiceView (Fire TV), generic button labels like “Select” or “More” turn into noise. Real users quickly point out where your labeling breaks down: when “More” leads to <em>what</em>, exactly? Testing makes abstract accessibility principles suddenly tangible.</li><li><strong>Time delays equal frustration: </strong>Keyboard-only navigation often exposes timing issues — focus that jumps too slowly, or hover effects that require extra taps. Watching users wrestle with lag is an instant reminder that accessibility isn’t just about compliance — it’s about <em>performance</em>.</li><li><strong>Discoverability is design: </strong>Many remote users can’t “hover” or “scroll” the way touchscreen users can. Real testing reveals which features are invisible without pointer input. Can users reach settings, search, or captions with directional keys alone? If not, they don’t exist for keyboard users.</li></ol><h3>Turning insights into action</h3><ul><li><strong>Map your focus order early.</strong> Treat it as part of the design system, not a QA afterthought.</li><li><strong>Use nextFocusUp, nextFocusDown, nextFocusLeft, and nextFocusRight</strong> to define navigation logic explicitly.</li><li><strong>Label everything.</strong> Test your content with screen readers in Explore-by-Touch mode.</li><li><strong>Include real remote users in your test pool.</strong> You’ll catch issues your team no longer notices.</li></ul><h3>The bigger picture</h3><p>Designing for “keyboard-only” isn’t about checking an accessibility compliance box. It’s about designing for how people <em>actually</em> use TV apps — with remotes, limited input, and varied abilities.</p><p>Keyboard-only design succeeds when <strong>focus</strong> behaves like the user <em>expects</em>, not like the platform API <em>allows</em>. Testing with real users doesn’t just uncover bugs; it sharpens your empathy and strengthens your product’s usability for everyone. If your usability tests uncover frustration, that is not an edge case, it’s a message. It means your app’s mental model is expensive, and that you should start building toward predictability, not novelty.</p><p>That’s the standard keyboard-only users live on — and when you meet it well? It also produces TV experiences that <em>everyone</em> describes as “smooth”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3842f4fb3c36" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/what-testing-with-tv-watchers-can-teach-you-about-keyboard-only-design-3842f4fb3c36">What Testing with TV Watchers Can Teach You About ‘Keyboard-Only’ Design</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>