here's my Astra contribution, Ecce Homo *from memory *

:chef_kiss:

asked Astra to paint Ecco Homo from memory:

excited about how #WebMCP can make canvas content more accessible to screen reader users. combining accessible markup with an agent makes working in a canvas better for everyone, and helps out blind users especially. youtube.com/watch?v=F-HO5xBw…

video with closed captions here! youtu.be/qIxp4q-yau0

I stood up an example of how you can pair WebMCP with an accessible canvas application to help agents and assistive tech users work together. Video shows me navigating a flow diagram in the ChatGPT browser and prompting the agent to create new keyboard accessible diagrams from text and from a screenshot.

Excited to realize that WebMCP can be used to manage focus in a web app, like a supercharged "Skip to main content" link. Here's why its interesting: This has applications for assistive technology users using agents with browsers. Instead of tabbing through the UI, move focus directly to an object. This can help screen reader users, switch users, dictation users, etc, reducing fatigue and deep linking to changes in the UI to verify the agent's work. Just add a `focus_node` tool that specifies a focusable DOM node, and the web application can simply call `.focus()`. I stumbled up this while working on the @OpenAI WebMCP hackathon, working on agent action verifiability for screen reader users: devpost.com/software/screen-…

Remembered recently this drawing I did in 2017. I wasn't thinking big enough! Titled "OH in Williamsburg in 2022"

Using Claude desktop for scheduled accessibility testing. Claude uses the AccessLint MCP to scan and run user journey against your website, and creates a report every morning with changes 😎 claude.ai/directory/accessli…

Running accessibility tests in cloud browsers, spinning up a dozen parallel tasks in Claude Code to resolve the issues, and adding scheduled monitoring with recorded user journeys in accesslint to alert on regressions. feels magical.