Bluesky is “screen reader accessible” the way a staircase with curb cuts on each step is a “wheelchair ramp.” No keyboard nav. No useful landmarks. No focus memory. I lose my place every time I interact with a post. Compliance ≠ usability. Day 5 asking @support.bsky.team to fix this #A11yFail- Yes, Bluesky has alt text. But alt text isn’t the full picture (pun intended). It’s meaningless if I can’t even reach the post. Adding alt text to an inaccessible site is like advertising hearing aids on the radio — you’re leaving out a majority of the people who need it the most. #Accessibility
- What would help? – Keyboard shortcuts (j/k) to jump between posts – Landmarks or headings for screen reader nav – Restore focus or scroll position after interaction Reddit had it. Twitter *STILL* has it. This is basic UX for screen reader users. Let’s make Bluesky usable, not just compliant. #A11yMay 13, 2025 04:59
- Further reading: W3C: Developing a Keyboard Interface WebAIM: Keyboard Accessibility MDN: ARIA Landmarks These aren't "nice-to-haves" — they're the missing pieces.