{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreidxicxcb6rvmnx5tgcznsf6bar755shu6iy6nwnxsb6urdfileuqe",
    "uri": "at://did:plc:mz7h4r2iyp2egghuqaolnsev/app.bsky.feed.post/3mp6edjwbojf2"
  },
  "path": "/forum/accessibility-advocacy/born-accessible-or-just-same-old-savior-complex",
  "publishedAt": "2026-06-26T05:39:26.000Z",
  "site": "https://applevis.com",
  "textContent": "The article: Native Speakers: Why AI's Most Powerful Users Are Blind (Linux Foundation, 22 June 2026)\nThe authors: Phillip Lamb (CEO, Live Oak Digital) and Liad Yosef (co-creator of MCP Apps).\nThe argument: It's an excellent one. LLMs are fundamentally language-native, so building agent-ready software through MCP and WebMCP is, in large part, the same engineering problem as building accessible software. Accessibility isn't a bolt-on; it's becoming part of the architecture.\n\nThen comes the anecdote.\nTo illustrate AI's \"omissions\", the authors describe a blind developer who built an accessibility tool entirely through AI-assisted coding. During a demo, a sighted colleague points out that the bottom half of the letters are cut off on the screen. The AI never mentioned it.\nThat's a perfectly valid example of an AI omission.\nBut notice how the story is framed.\nThe achievement isn't that a blind engineer independently built software using an agentic workflow. That's merely the setup.\nThe memorable moment is that a sighted colleague spotted the visual bug.\nEvery developer ships bugs. Every developer benefits from testing by people with different perspectives. If a sighted developer misses keyboard accessibility, we don't tell the story as \"a blind colleague rescued them from reality.\"\nThe bug wasn't the story.\nThe blind engineer building the software was.",
  "title": "Born Accessible\" or Just the Same Old Savior Complex?"
}