Denis Skripnik (Blind Dev) pfp

Denis Skripnik (Blind Dev)

@blind-dev

12 Following
11 Followers
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
Sometimes it feels like program code behaves like a living being that’s just messing with you… Have you ever experienced this? You see an error but can’t figure out the cause. And then you spend 2-3 days debugging before finding the solution. I’ve been there. And the funny thing is that it could turn out to be a stupid bug, like having part of a variable in a different case than when you call it. The thing is, I’m visually impaired and use a screen reader. And it doesn’t announce the case, so sometimes you forget which version you used. Plus, the editor didn’t always show errors for some reason… Maybe I don’t remember all the details – it happened a year ago. But reading the post about deploying to production before the weekend reminded me of this story. And of course, I wish all of you that the programs would fix all the bugs and improve functionality on weekends (while you’re resting) – just kidding! 😄
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
1 reply
1 recast
1 reaction
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
2 reactions
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
3 reactions
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
1 reaction
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
Don’t rely solely on icons in your interfaces! I’m blind from birth and use the NVDA screen reader. This program reads aloud all my actions, system events, and text content. The crucial point is that it only reads text – buttons and elements with icons alone are not announced. Take the button under posts in Farcaster web (formerly warpcast), for example. It opens a menu with “Recast” and “Quote” options. For me, it’s announced as “Submenu button”. This forces me to either guess by clicking (which can be risky) or do nothing at all. Accidental clicks can lead to unintended actions like complainting a post or disliking it. That’s why it’s great when developers add proper labels to buttons – either in the value attribute or using aria-label=“name”. This HTML attribute enhances accessibility without cluttering the interface visually, making it understandable for blind users. Thank you for your attention! Please share this post – it’s an important message for developers.
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
0 reply
0 recast
0 reaction
Denis Skripnik (Blind Dev) pfp
Hello! I am a blind Farcaster user and I use the NVDA screen reader. I'm excited to join this awesome social network! Interface suggestions for Farcaster web: 1. The buttons on posts are not labeled properly. For example, I see the number “1” next to a post. When I click on it, a list with “Recast” and “Quote” options appears. It would be helpful to label this button as “Share 1”. 2. There is an action menu button above the post, which includes options from copying a link to blocking a user. It would be great if it could be labeled as “Actions”. 3. There are additional post actions below the “Share” button. I’ve been hesitant to click on them because they are also not labeled. Discovering their functions through trial and error is not very effective… Use aria-labels=“element name” for accessible interface. Many interfaces add icons but overlook accessibility. Looking forward to improvements! Open to questions & testing. Thanks for attention! Please share & comment.
5 replies
2 recasts
14 reactions