A pointed reminder that if AI is trained on an inaccessible web, it will reproduce that inaccessibility at scale unless we intervene intentionally.
","content_html":"This is a pointed reminder that AI trained on an inaccessible web will reproduce that inaccessibility at scale — unless we intervene thoughtfully and intentionally.
\nThat’s the part too many people seem eager to hand-wave away. These systems are not arriving with some magically enlightened understanding of disability, inclusion, or accessible implementation. They’re being trained on the web as it is, which means they are taking all of its worst practices as truth.
\nIf we want AI-assisted coding to improve outcomes rather than exponentially accelerate harm, accessibility must be foundational.
\n","social_text":"AI is inheriting the web’s accessibility debt. If we want a different outcome, we need to change the training data, the defaults, and the incentives now.","url":"https://www.aaron-gustafson.com/notebook/links/artificial-intelligence-has-one-chance-to-get-accessibility-right/","external_url":"https://www.forbes.com/sites/keelycatwells/2026/05/03/artificial-intelligence-has-one-chance-to-get-accessibility-right/","tags":["accessibility","AI/ML","inclusive design"],"image":"https://imageio.forbes.com/specials-images/imageserve/69f5669f2264431211d8f7b1/0x0.jpg?format=jpg&height=900&width=1600&fit=bounds","date_published":"2026-05-20T21:35:36Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/building-a-general-purpose-accessibility-agent-and-what-we-learned-in-the-process/","title":"Building a general-purpose accessibility agent—and what we learned in the process","summary":"A useful look at GitHub’s accessibility agent experiment and a nice complement to my recent posts on accessibility data gaps in codegen models and optimizing codebases for AI coding agents.
","content_html":"This post is a detailed and useful look at GitHub’s accessibility agent experiment.
\nIt dovetails nicely with my post on identifying accessibility data gaps in codegen models and my follow-up on optimizing codebases for AI coding agents. The former argued that these systems are already biased toward reproducing the web’s accessibility failures; the latter argued that if we want agents to be useful, we need to give them clearer structure, better documentation, and better examples.
\nWhat I especially appreciate here is how grounded the whole effort seems to be. One takeaway is that you can’t just wave your hands and tell an LLM to “do accessibility”; you need concrete guidance, clear expectations, and solid examples. Another is that accessibility work is too contextual to treat as a simple linting problem. And, perhaps most importantly, this is a good reminder that if we want AI systems to help improve accessibility, we have to be intentional about the data, patterns, and codebases we are feeding them. Otherwise they’ll just automate the same mistakes faster.
\n","social_text":"A useful look at GitHub’s accessibility agent experiment and what it takes to make these systems genuinely helpful rather than merely busy.","url":"https://www.aaron-gustafson.com/notebook/links/building-a-general-purpose-accessibility-agent-and-what-we-learned-in-the-process/","external_url":"https://github.blog/ai-and-ml/github-copilot/building-a-general-purpose-accessibility-agent-and-what-we-learned-in-the-process/","tags":["accessibility","AI/ML","software development"],"image":"https://github.blog/wp-content/uploads/2026/01/generic-github-copilot-blocks-logo.png?fit=1920%2C1080","date_published":"2026-05-20T21:33:33Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/ai-companies-will-fail-we-can-salvage-something-from-the-wreckage/","title":"AI companies will fail. We can salvage something from the wreckage","summary":"Cory Doctorow offers a characteristically sharp critique of the AI bubble, but what I found most useful here is his framing of how these systems are actually meant to be deployed: not to empower workers, but to turn them into ‘reverse centaurs.’
","content_html":"Cory Doctorow offers a characteristically sharp critique of the AI bubble, but what I found most useful here is his framing of how these systems are actually meant to be deployed: not to empower workers, but to turn them into “reverse centaurs.”
\nThat framing cuts through a lot of the marketing nonsense. The promise is always that AI will help people do their jobs better. The deployment story, far too often, is that a human gets stuck reviewing machine output at impossible speed while absorbing the blame when things go wrong. That’s not augmentation; it’s a liability dump.
\n","social_text":"This is a sharp and useful read from Cory Doctorow, especially his framing of workers being turned into ‘reverse centaurs’ and accountability sinks.","url":"https://www.aaron-gustafson.com/notebook/links/ai-companies-will-fail-we-can-salvage-something-from-the-wreckage/","external_url":"https://www.theguardian.com/us-news/ng-interactive/2026/jan/18/tech-ai-bubble-burst-reverse-centaur","tags":["AI/ML","society","the future"],"date_published":"2026-04-29T12:40:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/accessible-faux-nested-interactive-controls/","title":"Accessible faux-nested interactive controls","summary":"Eric Bailey walks through a clever pattern for getting the feel of nested interactive controls without actually violating the platform’s semantics.
","content_html":"Eric Bailey walks through a clever pattern for getting the feel of nested interactive controls without sacrifice the platform’s semantics to get there.
\nIn this piece, Eric digs into accessible name length, accidental activation, stacking context weirdness, and progressive enhancement too. That kind of thoroughness matters because patterns like this can go sideways in a hurry when folks cargo-cult only the CSS and skip the reasoning.
\n","social_text":"This is a clever pattern from Eric Bailey: keep the larger click target, keep the secondary actions, and don’t sacrifice semantics to get there.","url":"https://www.aaron-gustafson.com/notebook/links/accessible-faux-nested-interactive-controls/","external_url":"https://piccalil.li/blog/accessible-faux-nested-interactive-controls/","tags":["accessibility","CSS","progressive enhancement"],"image":"https://piccalil.b-cdn.net/api/og-image?slug=accessible-faux-nested-interactive-controls/","date_published":"2026-04-29T12:35:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/ai-assisted-coding-transforms-pdf-to-web-app-using-nys-design-system/","title":"AI-assisted coding transforms PDF to web app using NYS Design System","summary":"This is a compelling illustration of what becomes possible when a design system is structured well enough to be usable by both people and machines.
","content_html":"This is a compelling illustration of what becomes possible when a design system is structured well enough to be usable by both people and machines.
\nWhat’s exciting to me here is not “AI turned a PDF into an app” so much as what made that possible: components, tokens, utilities, and enough design-system clarity to give the model something useful to work with. That’s a big part of the story so many people miss. If your system is inconsistent, vague, or poorly documented, AI is just going to amplify that mess.
\n","social_text":"A well-structured design system is not just a delivery mechanism for consistency; it’s also critical infrastructure for AI-assisted coding.","url":"https://www.aaron-gustafson.com/notebook/links/ai-assisted-coding-transforms-pdf-to-web-app-using-nys-design-system/","external_url":"https://www.linkedin.com/posts/plasticmind_designsystem-ai-civictech-share-7420295564430450688-0RM5/","tags":["AI/ML","pattern libraries","web development"],"image":"https://static.licdn.com/aero-v1/sc/h/c45fy346jw096z9pbphyyhdz7","date_published":"2026-04-29T12:30:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/modern-css-feature-support-for-shadow-dom/","title":"Modern CSS Feature Support For Shadow DOM","summary":"This is a tremendously useful resource for anyone working with Shadow DOM and trying to understand where modern CSS features actually stand in practice, not just in theory.
","content_html":"Adobe has produced a tremendously useful resource for anyone working with Shadow DOM and trying to understand where modern CSS features actually stand in practice, not just in theory.
\nWhat I especially like here is the framing: not simply “supported” or “unsupported,” but whether a feature is actually advisable in Shadow DOM, how it crosses boundaries, and where browsers still disagree. That’s the kind of nuance you need when you’re building real components instead of admiring specs from afar.
\n","social_text":"This is exactly the kind of resource the web platform needs more of: practical, test-backed guidance on how modern CSS features actually behave with Shadow DOM.","url":"https://www.aaron-gustafson.com/notebook/links/modern-css-feature-support-for-shadow-dom/","external_url":"https://shadow-dom-css.adobe.com/","tags":["CSS","web components","developer tools"],"date_published":"2026-04-29T12:25:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/ai-is-locking-people-out-at-scale/","title":"AI is locking people out. At Scale.","summary":"An important and sharply argued framing of AI-generated accessibility failures as a civil-rights problem, not just a quality-control issue.
","content_html":"An important and sharply argued framing of AI-generated accessibility failures as a civil-rights problem, not just a quality-control issue.
\n\n\nThis is not a minor bug trend. It is a systematic civil-rights failure that has now found its way into software as a whole, through lightning-fast adoption of AI systems that are trained on over 20 years of institutional barriers.
\n
The numbers here are bad enough on their own, but what makes this especially troubling is where these systems are being deployed: education, healthcare, finance, employment, and other places people can’t simply opt out of. That’s why I appreciate how direct this project is about accountability. If we automate interface generation without putting accessibility at the center, we’re automating exclusion.
\n","social_text":"This is the right framing: inaccessible AI-generated interfaces are not a minor bug trend; they’re a civil-rights failure at scale.","url":"https://www.aaron-gustafson.com/notebook/links/ai-is-locking-people-out-at-scale/","external_url":"https://conesible.de/wab/","tags":["accessibility","AI/ML","society"],"date_published":"2026-04-29T12:20:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/the-incredible-overcomplexity-of-the-shadcn-radio-button/","title":"The Incredible Overcomplexity of the Shadcn Radio Button","summary":"It’s just a radio button. Paul’s teardown is a good illustration of how far modern front-end practice can drift from the simple, robust platform primitives we already have.
","content_html":"It’s just a radio button.
\nPaul’s teardown is a good illustration of how far modern front-end practice can drift from the simple, robust platform primitives we already have.
\n\n\nIf you can use a native HTML element or attribute with the semantics and behavior you require already built in, instead of re-purposing an element and adding an ARIA role, state or property to make it accessible, then do so.
\n
Reading this reminded me of a pair of pieces I’ve linked to before: Making radio buttons and checkboxes easier to use and There can be only one: Options for building “choose one” fields.
\nWe have spent an astonishing amount of time and energy overcomplicating a control HTML already gives us, often in the name of developer experience or styleability. More often than not, all we’re really doing is trading resilience for ceremony.
\n","social_text":"It’s just a radio button. We really don’t need two component libraries, ARIA role remapping, and client-side JS to do what HTML already does.","url":"https://www.aaron-gustafson.com/notebook/links/the-incredible-overcomplexity-of-the-shadcn-radio-button/","external_url":"https://paulmakeswebsites.com/writing/shadcn-radio-button/","tags":["HTML","accessibility","web development"],"date_published":"2026-04-29T12:15:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/accessibility-in-the-end-of-deterministic-design-again/","title":"Accessibility in the End of Deterministic Design (Again)","summary":"Accessibility isn’t something generative interfaces will magically solve; it’s the groundwork we need in order to make those systems trustworthy at all.
","content_html":"The framing Anna Cook uses for her talk is an important one: accessibility isn’t something generative interfaces will magically solve; it’s the groundwork we need in order to make those systems trustworthy at all.
\nI also appreciate the callback in the title. We’ve been here before. The particulars may be new, but the core challenge is familiar: how do we build resilient, inclusive systems when the output is fluid, personalized, or otherwise beyond a designer’s exact control? Accessibility is not a bolt-on answer to that question; it’s where the answer has to begin.
\n","social_text":"Accessibility isn’t something generative interfaces will magically solve; it’s the groundwork we need in order to make them trustworthy at all.","url":"https://www.aaron-gustafson.com/notebook/links/accessibility-in-the-end-of-deterministic-design-again/","external_url":"https://www.deque.com/axe-con/sessions/accessibility-in-the-end-of-deterministic-design-again/","tags":["accessibility","AI/ML","inclusive design"],"date_published":"2026-04-29T12:10:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/making-keyboard-navigation-effortless/","title":"Making keyboard navigation effortless","summary":"I’m very excited by focusgroup: a declarative way to handle a bunch of keyboard-navigation patterns that currently require a lot of brittle JavaScript.
I’m very excited by focusgroup: a declarative way to handle a bunch of keyboard-navigation patterns that currently require a lot of brittle JavaScript.
This is exactly the sort of thing I want to see the platform absorb. We’ve spent years rebuilding common interaction patterns with roving tabindex, focus management, and piles of event handling code. If the browser can take more of that on, we get lighter pages, more consistent experiences, and fewer opportunities for developers to get keyboard support wrong.
The latest WebAIM Million is a sobering reminder that, at scale, the web is getting more complex faster than it is getting more accessible.
","content_html":"The latest WebAIM Million is a sobering reminder that, at scale, the web is getting more complex faster than it is getting more accessible.
\nThere are a lot of grim numbers in here, but the one that really sticks with me is how many of the same, eminently-fixable issues continue to dominate year after year. We’re still talking about contrast, missing labels, empty buttons, and missing alt text. In other words, this is not a story about edge cases. It’s a story about fundamentals.
\n","social_text":"The latest WebAIM Million is not encouraging: more complexity, more ARIA, and more detectable barriers across the top million home pages.","url":"https://www.aaron-gustafson.com/notebook/links/the-webaim-million-the-2026-report-on-the-accessibility-of-the-top-1000000-home-pages/","external_url":"https://webaim.org/projects/million/","tags":["accessibility","the web","industry"],"date_published":"2026-04-29T12:00:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/under-the-hood-of-mdns-new-frontend/","title":"Under the hood of MDN’s new frontend","summary":"This is a fascinating look at how MDN rebuilt its frontend around server-rendered HTML, web components, and a clear understanding of where interactivity actually belongs.
","content_html":"This is a fascinating look at how MDN rebuilt its frontend around server-rendered HTML, web components, and a clear understanding of where interactivity actually belongs (and how to deliver it).
\nI particularly appreciated how plainly this post describes a mismatch a lot of teams create for themselves: wrapping largely-static content in an app shell, then shipping a pile of JavaScript just to re-assert what the server already knew. MDN’s new approach feels refreshing, despite being grounded in age-old best practices: Keep the content first-class, treat interactivity as optional (and isolated), and only ship what the page actually needs.
\nThere’s a lot to like here, but more than anything I love seeing MDN embrace an architecture that’s truly aligned with the platform it documents.
\n","social_text":"This is a fascinating architecture write-up from MDN: fewer abstractions, less shipped JavaScript, and interactivity where it actually belongs.","url":"https://www.aaron-gustafson.com/notebook/links/under-the-hood-of-mdns-new-frontend/","external_url":"https://developer.mozilla.org/en-US/blog/mdn-front-end-deep-dive/","tags":["web components","web development","progressive enhancement"],"date_published":"2026-04-24T12:05:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/endgame-for-the-open-web/","title":"Endgame for the Open Web","summary":"A sobering but necessary reminder that the open web’s current crisis is not theoretical; it’s already playing out across publishing, open source, standards, and shared infrastructure.
","content_html":"This is a sobering but necessary reminder that the open web’s current crisis is not theoretical; it’s already playing out across publishing, open source, standards, and shared infrastructure.
\nI appreciate how clearly Anil connects dots that too many people are still treating as separate problems. This isn’t just about AI summaries siphoning traffic from publishers or slop code drowning maintainers or bad actors ignoring long-standing norms like robots.txt. It’s all of those things at once. The through-line is extraction: taking value from open systems without giving anything back, then undermining the very ecosystems that made that extraction possible in the first place.
\n\nThe good of the web only exists because of the openness of the web. They can’t just keep on taking and taking without expecting people to finally draw a line and saying “enough”.
\n
If you care about the web as a public good, this post is worth your time.
\n","social_text":"This is a tough read, but an important one: the attacks on the open web are not abstract anymore.","url":"https://www.aaron-gustafson.com/notebook/links/endgame-for-the-open-web/","external_url":"https://www.anildash.com/2026/03/27/endgame-open-web/","tags":["the web","AI/ML","society"],"image":"https://www.anildash.com/images/tunnel.jpg","date_published":"2026-04-24T12:00:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/slidevars/","title":"slideVars","summary":"A lovely little utility from Chris Coyier that turns CSS custom properties into a live control panel.
","content_html":"This is a lovely little utility from Chris Coyier that turns CSS custom properties into a live control panel.
\nIt’s one of those tools that immediately makes me want to crack open a demo and start playing. What’s especially nice is that it doesn’t ask you to invent some parallel configuration universe if you don’t want to; it can just inspect the variables you already have and give you a UI for experimenting with them. That makes it feel less like a framework and more like a really practical enhancement to the way many of us already work.
\n","social_text":"slideVars feels like the kind of tiny, practical tool that makes design and front-end iteration a whole lot more fun.","url":"https://www.aaron-gustafson.com/notebook/links/slidevars/","external_url":"https://codepen.github.io/slideVars/","tags":["CSS","developer tools","web development"],"date_published":"2026-04-23T12:20:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/ai-is-accidently-making-documentation-accessible/","title":"AI is accidently making documentation accessible","summary":"Documentation written for clarity is better for everyone — human or machine!
","content_html":"The real takeaway is that documentation written for clarity is better for everyone — human or machine!
\nIn other words, AI use is reinforcing what good documentation has always required: clear structure, explicit language, sensible headings, and fewer assumptions about what the reader already knows. That’s good for machines, sure, but it’s even better for people navigating with assistive tech, reading in a second language, or simply trying to get an answer quickly.
\n\n\n","social_text":"AI didn’t invent better documentation practices; it just exposed how valuable structure, clarity, and explicitness have always been.","url":"https://www.aaron-gustafson.com/notebook/links/ai-is-accidently-making-documentation-accessible/","external_url":"https://gerireid.com/blog/ai-is-accidently-making-documentation-accessible/","tags":["accessibility","AI/ML","writing"],"image":"https://gerireid.com/images/open-graph.png","date_published":"2026-04-23T12:15:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/design-systems-cant-automate-away-all-of-your-accessibility-considerations/","title":"Design systems can’t automate away all of your accessibility considerations","summary":"AI has not invented new rules for writing, it has made the cost of ignoring the old ones obvious.
\n
Eric does an excellent job outlining the kinds of accessibility issues design systems and automated tooling can reduce, but never fully eliminate.
","content_html":"Eric does an excellent job outlining the kinds of accessibility issues design systems and automated tooling can reduce, but never fully eliminate.
\nThis is the part too many teams miss: accessibility doesn’t end at the component boundary. A well-built component library can give you a stronger foundation, but it can’t guarantee the right labels, the right heading structure, the right focus management, or the right overall experience once those pieces are assembled into an interface. That work still requires judgment, care, and testing with actual people.
\n","social_text":"Passing automated checks is not the same thing as delivering an accessible experience.","url":"https://www.aaron-gustafson.com/notebook/links/design-systems-cant-automate-away-all-of-your-accessibility-considerations/","external_url":"https://zeroheight.com/blog/design-systems-cant-automate-away-all-of-your-accessibility-considerations/","tags":["accessibility","inclusive design","pattern libraries"],"image":"https://zh-marketing-wordpress-uploads.s3.amazonaws.com/wp-content/uploads/2025/11/blog-feature-computer-yellow.png","date_published":"2026-04-23T12:10:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/the-power-of-no-in-internet-standards/","title":"The Power of ‘No’ in Internet Standards","summary":"This is an important piece about where power actually lives on the web: not in the specification itself, but in whether powerful players choose to participate, implement, and ship.
","content_html":"This is an important piece about where power actually lives on the web: not in the specification itself, but in whether powerful players choose to participate, implement, and ship.
\nI also appreciate Mark’s call for more ambition here. Too often, we talk about the web as if it’s destined to be an OS for web apps rather than a public-interest platform in its own right. That’s not inevitable. But getting somewhere better requires recognizing that refusal, delay, and strategic disinterest can be every bit as consequential as formal opposition.
\n","social_text":"A useful reminder that the real power in standards work is often the power to say no.","url":"https://www.aaron-gustafson.com/notebook/links/the-power-of-no-in-internet-standards/","external_url":"https://www.mnot.net/blog/2026/02/13/no","tags":["web standards","the web","society"],"image":"https://mnot.net/blog/image/wait_here.jpeg","date_published":"2026-04-23T12:05:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/nice-select/","title":"Nice Select","summary":"This is a terrific demonstration of how far the platform has come: a richly styled select that leans on native semantics, native accessibility, and progressive enhancement instead of fighting the browser.
This is a terrific demonstration of how far the platform has come: a richly styled select that leans on native semantics, native accessibility, and progressive enhancement instead of fighting the browser.
What I especially appreciate here is the restraint. Yes, there’s some clever CSS and a little JavaScript to help with positioning, but the whole thing is built on top of the platform, not in spite of it. That’s the interesting takeaway for me: we can build interfaces that feel bespoke without throwing away the reliability and accessibility native controls already give us.
\n","social_text":"This is exactly the sort of UI work I love seeing: ambitious, polished, and still rooted in native controls and progressive enhancement.","url":"https://www.aaron-gustafson.com/notebook/links/nice-select/","external_url":"https://nerdy.dev/nice-select","tags":["CSS","HTML","progressive enhancement"],"image":"https://nerdy.dev/media/nice-selects.jpg","date_published":"2026-04-23T12:00:00Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/people-are-not-static-we-are-dynamic-in-order-to-meet-our-needs-at-any-point-in-our-lives-or-day-the-uis-we-create-must-be-able-to-adapt-to-us-not-the-other-way-around-/","title":"Different contexts, different tools, same person","summary":"People are not static, we are dynamic. In order to meet our needs at any point in our lives or day, the UIs we create must be able to adapt to us — not the other way around.
","content_html":"People are not static, we are dynamic. In order to meet our needs at any point in our lives or day, the UIs we create must be able to adapt to us — not the other way around.
\n\n\n","social_text":"People are not static, we are dynamic. In order to meet our needs at any point in our lives or day, the UIs we create must be able to adapt to us — not the other way around.","url":"https://www.aaron-gustafson.com/notebook/links/people-are-not-static-we-are-dynamic-in-order-to-meet-our-needs-at-any-point-in-our-lives-or-day-the-uis-we-create-must-be-able-to-adapt-to-us-not-the-other-way-around-/","external_url":"https://www.linkedin.com/posts/derekfeatherstone_accessibility-disability-activity-7434648295420870656-mH3o","tags":["accessibility","progressive enhancement","inclusive design"],"image":"https://static.licdn.com/aero-v1/sc/h/c45fy346jw096z9pbphyyhdz7","date_published":"2026-03-05T18:38:46Z"},{"id":"https://www.aaron-gustafson.com/notebook/links/some-blind-fans-to-experience-super-bowl-with-tactile-device-that-tracks-ball/","title":"Some blind fans to experience Super Bowl with tactile device that tracks ball","content_html":"I know someone that uses her screen reader on her mobile phone, but when she’s on her desktop computer, she uses a mangifier.
\nDifferent contexts, different tools, same person.
\nI know someone that uses voice controls on his computer. He uses direct commands like “Click Contact Us” when he’s near the start of his day, and commands like “Click link, twelve” when he’s near the end of his day with lower energy and less clear speech and a dry mouth.
\nDifferent energy/capacity, same tools, same person.
\nI know someone that uses a switch on his computer. He also uses the onscreen keyboard on his computer. The one that he chooses reflects the task he’s trying to accomplish and how he can minimize switching between the tools.
\nDifferent task, same context, same tools, same person.
\nDisability is not black and white… it’s every shade of every colour.
\n
A few years ago, a couple students at the University of Washington asked me to come to their campus for a visit. They gave me a demo of an early prototype they’d been working on — a haptic feedback device that could allow someone who is Blind or low vision to follow a game. The demo took video data from a tennis match and mapped it onto the haptic tablet. It felt like Pong, but they had a bolder vision — tackling fast-moving and complicated sports like basketball, football, American football, and hockey.
\nI immediately invited them to pitch us for the AI for Accessibility Grant Program that I ran for Microsoft. With so much focus on assistive technology to enable folks to work and accomplish common life tasks, I loved that the OneCourt team was interested in enabling people with disabilities to enjoy leisure activities like sporting events. Moreover, I saw the potential to enable Blind and low-vision parents to experience their kids’ sporting events, which could be life-changing for them.
\nNeedless to say, they wowed both me and the rest of the seleciton committee. We funded them to expand their prototypes and pursue partnerships with different professional sports leagues, teams, and venues. They were ambitious and it’s paying off.
\nFast forward a few years and they’re enabling a handful of Blind & low vision sports fans to exerience the Super Bowl in a whole new way, using their technology. It’s amazing and I could not be more proud of them.
\nCongrats y’all!
\n","social_text":"So proud of the OneCourt team for their work in bringing more leisure opportunities to the Blind & low vision community.","url":"https://www.aaron-gustafson.com/notebook/links/some-blind-fans-to-experience-super-bowl-with-tactile-device-that-tracks-ball/","external_url":"https://apnews.com/article/nfl-blind-fans-super-bowl-6daf12a08127c46c23dab6100a659681","tags":["accessibility","inclusive design","AI/ML"],"image":"https://dims.apnews.com/dims4/default/9b439cc/2147483647/strip/true/crop/5333x3554+0+1/resize/980x653!/quality/90/?url=https%3A%2F%2Fassets.apnews.com%2F1b%2Fe5%2F28e0bd88c1be654d380ee1c3b2f2%2F9a7b2e31c9464fa6a86eb6d04b0a3266","date_published":"2026-02-06T19:40:06Z"}]}