pull down to refresh

Hello, I am seeking data on issues users with disabilities may have found in various bitcoin wallets. I have already done a bit of research but am looking for any recent issues, blog posts, surveys, etc. that might have been asked here or elsewhere since ~2020.
There have been a few Bitcoin accessibility initiatives in this space over the years, but I’m not convinced it’s improved much since the first screen-reader challenges were raised around 2014 (in MultiBit, Bitcoin-Qt, Armory, Electrum and the now-defunct IcyWallet project). I am also aware of the work the Bitcoin Design Community has been doing and the issues listed in the Accessibility fix hit list from just a few years ago.
In my testing so far in 2025 I have found major blockers in just about every bitcoin wallet I have used. I am thinking we may still be leaving out a significant minority of the population who could benefit from FOSS freedom tech like bitcoin and NOSTR, but am looking for evidence that supports or refutes this.
I’m looking for:
  • Recent reports, blog posts or surveys on issues like screen reader support, keyboard navigation, contrast, navigation, etc.
  • GitHub issues or docs that log accessibility gaps or fixes since 2020
  • First-hand experiences: what challenges did you or someone you know face, and any workarounds
Questions
  • What blockers remain in 2025 (e.g. unreadable QR codes, missing ARIA labels, lack of keyboard-only navigation)?
  • Have any wallet teams published accessibility roadmaps or fixes?
  • Are there recent user tests, surveys or community threads (StackExchange, Reddit, GitHub) on this topic?
Would you or someone you know be willing to share your experience to inform this study?
Any pointers to articles, threads, audits or anecdotes are greatly appreciated.
7 sats \ 3 replies \ @OT 30 Jun
One of the musicians I used to play with was blind. I was looking to see if anyone had done something to make Bitcoin accessible. I don't remember finding anything at the time.
reply
Unfortunately, it seems to still be the case, but have seen some interest and beginning progress in this area. Most designers and devs really want to do the right thing, but just need to be guided on what works best for all users.
reply
7 sats \ 1 reply \ @OT 30 Jun
She used to communicate digitally through some kind of electronic voice reader. I bet since the explosion in AI this would be a lot better now.
reply
It was probably a screen reader like TalkBack on Android or VoiceOver on iOS.
There are some built-in AI tools that can help with accessibility (can do OCR and guess at unlabelled buttons, images, and content) but at the cost of privacy and reliability.
Ideally, the meaningful text content should be exposed to respective accessibility APIs in a manner that is understandable by the user. This simply means following some guidelines by the W3C to ensure that content is always exposed properly and in the correct reading order.
reply
Pinned it into ~Design to increase visibility. For how long the survey will stay online?
reply
Thanks! I will probably keep it up for at least a month. It can sometimes be hard to get data on users that may have been left behind.
reply
You could also try these other dedicated places to promote the survey:
reply