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 1 asking @support.bsky.team to fix this #A11yFail
No keyboard nav. No useful landmarks. No focus memory. I lose my place every time I interact with a post.
Compliance ≠ usability.
Day 1 asking @support.bsky.team to fix this #A11yFail
Comments
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
– 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. #A11y
W3C: Developing a Keyboard Interface https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/
WebAIM: Keyboard Accessibility https://webaim.org/techniques/keyboard/
MDN: ARIA Landmarks https://developer.mozilla.org/en-US/ docs/Web/Accessibility/ARIA/Reference/Roles/navigation_role