Bring your karma
Join the waitlist today
HUMBLECAT.ORG

Blind and Visually Impaired Community

Full History - 2018 - 05 - 30 - ID#8nbl0l
5
Do you have any thoughts on computer interfaces for the blind? What would make them more usable? (self.Blind)
submitted 5.1921549639917695y ago by VerbosePineMarten
I've spent a couple of years working on novel UI designs as a hobby, especially with wearable and accessible computing. I got to thinking about interfaces tailored specifically to blind users, and I really wanted to hear your guy's end of things. I've used screenreaders before to see what it's like, and the problem is that they're inherently low\-bandwidth interfaces \(i.e. not much info per unit\-rate of interaction\). It also doesn't help that they're abstracting an inherently visual interface, which adds more overhead.

My current designs are based on stereo soundscapes that abstract the computer/program state directly, with spoken word used mostly for things that are already inherently textual \(error messages, webpage content, text editing, etc.\), with lots of haptic feedback. I'm used to a command\-line interface myself, so I've been looking at ways to "annotate" text outputs with other sounds to increase the information density rate.

A lot of the stuff I've tried is based purely on sound, or cheap haptic feedback devices, to minimize the need for specialized equipment.

I guess what it really boils down to is this: we have the "desktop metaphor" for abstracting files/navigation on computers. We also have the WIMP \(windows, icons, menus, pointer\) metaphor, and more recently the "everything is a tile" paradigm on mobile devices. What metaphor would work best for the blind, especially in terms of audio\-only interfaces? Are there any interface elements that work well for you on screen readers? What about the ones that don't? Are there any things you can think of that would make computers faster and easier to use for you, especially if we're talking a ground\-up design instead of mapping over an existing interface?
bradley22 1 points 5y ago
I'm used to the way things are and don't think they need to change. We can change a screen reader or people can make another one like NVDA but at the end of the day it's the developers who need to change their sites and the programmers who need to make their programs more accessible. If we made everything usable with this super new tech or screen reader, it would be great for us but it would allow the web developers/programmers to slack off more than they usually do.
VerbosePineMarten [OP] 1 points 5y ago
> it would be great for us but it would allow the web developers/programmers to slack off more than they usually do.

As a programmer, I agree. It's kind of nuts to me that they *don't* strive to make things as accessible as possible. In my experience, making things accessible tends to make the program more usable for everyone, not just those who need the accessibility features.

I've been considering writing a series of parsers to turn websites into well-formatted, clean unicode text so that they can be fed into screen readers (and for various other projects I've been working on), but it's an absurdly complex undertaking. I wish web design was standardized >.<
bradley22 1 points 5y ago
I'd not recommend doing that. Websites are okay as they are now it's just some sites could be better. Honestly? Changing the way things work to force people to use your program to read sites would not be a good idea. I don't think these kind of hold your hand tools that are meant to help the blind/elderly are good. What happens if the site changes? The person who created the tool gets into an accident? Or anything like that? I think it's better that people learn how to use the internet as it is now than be shown a more accessible program that lays everything out neatly.
VerbosePineMarten [OP] 1 points 5y ago
Or force the devs to talk to a UI designer before they intentionally malformat their websites. But I take your point.


Parsers came up mostly because I'm one of those cranks who wishes everything was neat, easy-to-navigate (visually, for me) HTML.
bradley22 1 points 5y ago
Ah, okay.
genericblindman 1 points 5y ago
I'd say the "everything's a beep" model would work well. There's a huge amount of information that can be sent using a series of standardized beeps and similar tones. With pitch and tone changes to underlying beep formats to denote difference within a category. Literally you could have a folder beep and then change the beep depending on what you're doing with teh folder or what type of folder it is. Likewise you could have a file beep, maybe the folder beep is a different version of the file beep with the same changes applied to it. Or it could be 2 really fast beeps to denote the folder/file relationship. This mimics the same way you can have different types of icons for different types of folders and files but they all mostly look the same at their base. Likewise for operations, you don't need to speak out every little operation, beeps and other types of sounds can give all the information needed. Words should only be used when words already exist and are mutable, like filenames. But operations that involve words like, new folder, don't need to be spoken. It's always going to be called "new folder", the words are thus immutable, so you can replace it with a sound. Likewise with certain folder names for showing full paths. System or root folders will likely never change their name, so can be denoted with a beep. You could potentially represent certain full paths many folders deep with just a single beep with tone and pitch transformations. Obviously there should be an option to speak it out anyways for beginners or people who've never used that thing before. The speak out function should be a single or at most double hotkey on the keyboard so it's always easy to access at a moments notice. Literally like every time you press Alt it should speak out whatever thing you're currently on or doing. Then when you know the sound you can use just the tone. Also the ability to assign your own custom quick tones for things you do often even if the text is mutable. You can cram in a wide variety of beeps and swishes and whatnot all with their own tone and pitch transformations into a tiny amount of time and convey ridiculously huge amounts of information since each beep could itself be symbolic for some complex multilayered piece of data. It does become like another language but for a lot of people navigating and using a computer is already like that.
VerbosePineMarten [OP] 1 points 5y ago
This is basically assigning lietmotifs or "audio icons" to each object within the system. Kinda like how each pokemon has their own unique roar when you encounter one in battle :D

I've thought of doing something similar, but adding spatial movement of the sound source to convey more information. Also, there are certain universals we can use -- harsh tones = bad, etc. This would be a good way to make it a bit more intuitive.
This nonprofit website is run by volunteers.
Please contribute if you can. Thank you!
Our mission is to provide everyone with access to large-
scale community websites for the good of humanity.
Without ads, without tracking, without greed.
©2023 HumbleCat Inc   •   HumbleCat is a 501(c)3 nonprofit based in Michigan, USA.