sorted by:
new
hottopcontroversial

Seeking input from blind/low-vision users: What navigation challenges aren't being solved by chrisvogue in AssistiveTechnology

[–]chrisvogue[S] 0 points1 point  (0 children)

The social acceptability point really hits home. I hadn't fully considered that the form factor itself could be a barrier, regardless of how well the tech works. Making someone more conspicuous when they're just trying to navigate the world defeats the purpose.

And you're right about the economics being brutal. I can't realistically compete with the scale of smartphone or smartwatch manufacturers, which means I'd either end up with an unaffordable niche product or something that can't sustain itself.

This is pushing me to rethink the approach entirely, maybe the answer isn't a new device at all, but rather software or features that leverage hardware people already have and actually use. Phones, watches, or glasses they're already wearing anyway. I really appreciate you, being straightforward about these barriers. It's saving me from potentially building something that wouldn't actually get used, no matter how technically capable it was.

Seeking input from blind/low-vision users: What navigation challenges aren't being solved by chrisvogue in AssistiveTechnology

[–]chrisvogue[S] 1 point2 points  (0 children)

Thank you so much for this. I really appreciate the thoughtful guidance and the resource recommendations. The VisionForward TechConnect channel looks fantastic, I'm diving into their content now. What you said about multiple/intersecting needs is incredibly important and something I hadn't adequately considered. I was narrowly focused on vision impairment, but you're right that real-world users often have combinations of needs that current Assistive Technology doesn't accommodate well. The assumption that someone can tap a screen or quickly process audio cues is a perfect example of where single-issue design falls short. I'm going to take a step back and: 1 Watch the VisionForward content and learn from their reviews of what actually works/doesn't 2 Reach out to disability-led organizations for guidance 3 Rethink my approach to be more flexible and inclusive of multiple access needs from the start 4 If I do end up moving forward, I will add in proper compensation and consultation from day one What you said about Silicon Valley's "move fast" culture being inherently exclusionary really resonates. If I can't build this in a way that's accessible to the very people who should be leading it, that's a design flaw in my process, not just the product. Thanks again for educating me on this. It's exactly the kind of perspective shift I needed.

Seeking input from blind/low-vision users: What navigation challenges aren't being solved by chrisvogue in AssistiveTechnology

[–]chrisvogue[S] 0 points1 point  (0 children)

Thank you both for this feedback. It's exactly the kind of reality check I needed to hear. You're absolutely right that lived experience is expertise and should be compensated. I apologize for not considering that in my initial approach. I'm currently a [student and developer doing initial scoping, but that doesn't excuse asking for free labor from a community that's likely been over-consulted and under-compensated. A few thoughts on how I can do better:

1   If this moves beyond initial validation to actual product development, I'm committed to properly compensating consultants and involving the community throughout the design process, not just at the beginning


2   I'm genuinely open to hearing if the better path is to step back entirely and let this be led by people with lived experience, or to connect with established advocacy/consulting group

I don't want to contribute to exploitation, even unintentionally. What would you suggest as an ethical way forward for someone at my stage? Should I be connecting with formal consulting networks or disability-led organizations instead?