<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Usability on Lanie: Faith, Tech, and Advocacy</title>
    <link>https://lanie.work/tags/usability/</link>
    <description>Recent content in Usability on Lanie: Faith, Tech, and Advocacy</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 19 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://lanie.work/tags/usability/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Using Steam with NVDA: What Works, What Doesn&#39;t, and What Valve Should Fix</title>
      <link>https://lanie.work/gaming/steam-nvda-usability/</link>
      <pubDate>Sun, 19 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://lanie.work/gaming/steam-nvda-usability/</guid>
      <description>&lt;p&gt;I use Steam with NVDA every day. It works, mostly. But &amp;ldquo;mostly&amp;rdquo; is doing a&#xA;lot of heavy lifting in that sentence.&lt;/p&gt;&#xA;&lt;p&gt;In 2025, Valve added accessibility settings to the Steam desktop client and&#xA;introduced a built-in screen reader for SteamOS and Big Picture Mode. That&amp;rsquo;s&#xA;real progress, and I want to acknowledge it. But the desktop experience that&#xA;most Windows users rely on still has significant barriers for screen reader&#xA;users. This post is not a WCAG audit. It&amp;rsquo;s a report from daily use.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
