Blind and Visually Impaired Community
↑
8
↓
How can I improve software user-interfaces to be more conducive to those who are visually impaired? (self.Blind)
submitted by ohx
Hi everyone. I'm a front-end engineer at a software company, and I'm working with a team of four to put together the user interface. I've been exploring ARIA and testing the web with Apple's onboard VoiceOver software.
The problem I'm running into is, I'm not exactly sure how people use VoiceOver. For example, in my first iteration of the user interface, I coded things so that when an individual pressed tab through the page, it would automatically read all content relevant to those with a screen reader.
Then I pressed control, option "A", and the screen reader began to read certain parts over twice. So basically the screen reader read everything I told it to read with ARIA, then it read everything again, this time without so it didn't have the same context.
I find that the benefit of ARIA is I can add context to a page that may not make a whole lot of sense otherwise. But what I'm concerned about is that maybe people tend to use control, option "A" over using tab, which would render my ARIA efforts useless, and the screen reader would just be redundant. That would make the overall user experience pretty bad.
What is your protocol for browsing websites? Control, option "A", or tab? Are there things you find particularly frustrating when browsing, where ARIA might just be overkill?
The problem I'm running into is, I'm not exactly sure how people use VoiceOver. For example, in my first iteration of the user interface, I coded things so that when an individual pressed tab through the page, it would automatically read all content relevant to those with a screen reader.
Then I pressed control, option "A", and the screen reader began to read certain parts over twice. So basically the screen reader read everything I told it to read with ARIA, then it read everything again, this time without so it didn't have the same context.
I find that the benefit of ARIA is I can add context to a page that may not make a whole lot of sense otherwise. But what I'm concerned about is that maybe people tend to use control, option "A" over using tab, which would render my ARIA efforts useless, and the screen reader would just be redundant. That would make the overall user experience pretty bad.
What is your protocol for browsing websites? Control, option "A", or tab? Are there things you find particularly frustrating when browsing, where ARIA might just be overkill?
Marconius 3 points 7y ago
As a voiceover user, I primarily use Safari to interact with websites on both my iPhone and my Mac. However, I don't use tab nor control+option+A to navigate a website. I will use tab to jump between text field sometimes, but most of the time I'm using the voice over rotor and quicknav with the arrow keys. The fastest way for me to jump through websites is to have the rotor set to headings and navigate down through clearly labeled headings and landmarks.
I will also use form controls if I need to interact with an array of buttons and text fields. Ultimately, let voiceover do most of the work, don't use anything with JavaScript as that seriously breaks screen readers, use plenty of alt tags especially with images if necessary, label all of your buttons and links, and constantly test with voiceover on.
Depending on where you are in the states, definitely check out a local blind resource center and there you will be able to observe how we use and interact with websites.
I will also use form controls if I need to interact with an array of buttons and text fields. Ultimately, let voiceover do most of the work, don't use anything with JavaScript as that seriously breaks screen readers, use plenty of alt tags especially with images if necessary, label all of your buttons and links, and constantly test with voiceover on.
Depending on where you are in the states, definitely check out a local blind resource center and there you will be able to observe how we use and interact with websites.
fastfinge 2 points 7y ago
It depends on the website. If it's a web app, like Gmail or facebook, I read the help pages and take my queues from whatever instructions for using the site they provide (hotkeys, etc). If it's just a page I visit once in a while, I'm not going to bother remembering any specialized instructions, and will tend to skim through the page navigating by heading. I guess the question is: are your users going to be using the site daily? If so, it's reasonable to expect them to develop new habits for using your particular site. If not, try and let Voiceover do all of the work, so that it'll work no matter how users choose to browse.
ataulm 2 points 7y ago
Depending on where you live, it'll be better contacting organisations for help with this. For example, in the UK you can get in touch with the Royal National Institute of Blindness (RNIB), the DAC (Digital Accessibility Centre) or Paciello Group for advice and consultation.
ohx [OP] 1 points 7y ago
Ah, thanks! I'll explore my options in the states to see what local organizations might be available.
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.
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.