For anyone following this tutorial in 2021+. The Focus Highlight addon is no longer needed (and won't work) as they added its functionality into NVDA itself. You can activate it in the settings under "Vision" -> "Enable Highlighting"
This presentation was absolutely brilliant. Thank you very much for a well made, well presented video that was had all of the essential information needed to get started with NVDA. Very much appreciated and needed.
Surely the heading fix should be to update the divs to elements so they're semantically correct? Wouldn't you want to always use standard html elements where possible before thinking about introducing aria attributes to your markup?
Completely agree...that surprised me as well. The devs need to see that the root problem is that the content isn't semantically structured. And the fix should be to add a true h2.
How do I get heading level information on its own line in the Speech View console? Currently it shows the text/heading level /any other option I have turned on, all on one line. It would also be easier to see each output in the Speech View if we can place an empty line between each output. Is it possible to set that up? Thank you for this video.
I would like to ask you if you can clarify what % of testing should be done using available tools in the market and what % should be tested manually for accessibility? I strongly believe we are not there yet where the entire testing can be relied on available tools. How these available tools and manual testing process should be combined to come up with a full proof accessible digital content? Thanks in advance.
Hello, I was wanting to know what suggested specs one should have. I have a laptop running AMD processer A10 7300. Base clock 1900 and Tops at 2.7.I have Windows 10. I also have 8 GB of ram running on SSD. Would up grading to 16 GB of ram help? I just want NVDA to be more solid on my system.
Really so helpful tutorial. thanks for tutorial. Edward Matarazzo, Have any question about dev? So, Welcome to dtaaccessibility.com/ At DTA, we provide inexpensive accessibility testing with free SEO consulting. We also do web development for small to big business with accessibility in mind. We also currently developing our own automated web accessibility testing tool. Sign up for our latest news about the testing tool as well as our services. Please Enter your details and a member of our team will be happy to walk you through our solution. FIND US : Address : 16420 Kittridge st, Van Nuys, CA, 91406 e-mail : ash_2880@yahoo.com Phone: +1 513-255-8055 Website : dtaaccessibility.com/
Yes, absolutely. Although there are reasons you might need to use ARIA attributes in a scenario like this, generally speaking it's much better to simply use semantic HTML if you can. My example was poorly chosen.
To give honest feedback, I don't think this is helpful for the visually impaired. It's great to learn about their style, but as I'm trying to help my girlfriends who is blind, these techniques are too visual. If I were to close my eyes, there would be no way of knowing where to click. We understand things in grid and visual form; they don't.
For anyone following this tutorial in 2021+.
The Focus Highlight addon is no longer needed (and won't work) as they added its functionality into NVDA itself.
You can activate it in the settings under "Vision" -> "Enable Highlighting"
Thanks!
Thanks Hendrik.
The Focus Highlight add-on still works for me in version 2021.3.5.
Thanks Bro :)
This presentation was absolutely brilliant. Thank you very much for a well made, well presented video that was had all of the essential information needed to get started with NVDA. Very much appreciated and needed.
I've been using this tool for my accessibility testing and its just what I needed! Awesome tool!!
I am a new nvda user in Taiwan, thank for sharing this useful information
Surely the heading fix should be to update the divs to elements so they're semantically correct? Wouldn't you want to always use standard html elements where possible before thinking about introducing aria attributes to your markup?
Yeah, that really surprised me to, to the extent that I wouldn't want to show this video to anyone else.....
I suppose it's possible that there's some reason that it can't be changed, but I can't think of one.
Completely agree...that surprised me as well. The devs need to see that the root problem is that the content isn't semantically structured. And the fix should be to add a true h2.
This is super helpful stuff as a Dev. Thank you!
Keep up producing useful tutorials. All the best. Great video on accessibility testing.
How do I get heading level information on its own line in the Speech View console? Currently it shows the text/heading level /any other option I have turned on, all on one line. It would also be easier to see each output in the Speech View if we can place an empty line between each output. Is it possible to set that up?
Thank you for this video.
I would like to ask you if you can clarify what % of testing should be done using available tools in the market and what % should be tested manually for accessibility? I strongly believe we are not there yet where the entire testing can be relied on available tools. How these available tools and manual testing process should be combined to come up with a full proof accessible digital content? Thanks in advance.
thank you for this! so helpful for devs!
awesome tutorial. thanks for this, it helps alot. cheers.
Hmmm speech viewer doesn't turn off the voice for me.
You can use NVDA + S to disable the voice.
for some reason, I cannot toggle between focus and browse modes. When I press insert/caps + space, it does nothing.
Thank you a very good explanation!!!
It did not auto add the add on.. it wants me to choose what to open it in.
Awesome video! Thanks!
Hello, I was wanting to know what suggested specs one should have. I have a laptop running AMD processer A10 7300. Base clock 1900 and Tops at 2.7.I have Windows 10. I also have 8 GB of ram running on SSD. Would up grading to 16 GB of ram help? I just want NVDA to be more solid on my system.
Really so helpful tutorial. thanks for tutorial.
Edward Matarazzo, Have any question about dev? So, Welcome to dtaaccessibility.com/
At DTA, we provide inexpensive accessibility testing with free SEO consulting. We also do web development for small to big business with accessibility in mind. We also currently developing our own automated web accessibility testing tool. Sign up for our latest news about the testing tool as well as our services.
Please Enter your details and a member of our team will be happy to walk you through our solution.
FIND US :
Address : 16420 Kittridge st, Van Nuys, CA, 91406
e-mail : ash_2880@yahoo.com
Phone: +1 513-255-8055
Website : dtaaccessibility.com/
@@b2btactics257 with no visual focus on TAB?
Awesome, very helpful - thanks!
Great stuff Matt, an excellent tutorial!
Thank you so much!
Wow. You have a lot of ads. Based on your actions, it looks like NVDA should save the preferred location and size of the browser window.
What option or alternative do we have for MACbook? for nvda
For Mac there is an inbuilt screen reader called VoiceOver you can learn more about it at www.applevis.com
re 17.00 Or use a heading tag?
Yes, absolutely. Although there are reasons you might need to use ARIA attributes in a scenario like this, generally speaking it's much better to simply use semantic HTML if you can. My example was poorly chosen.
Do you know of any similar downloads for Mac's
MAC has voiceover built in - click cmd+F5
To give honest feedback, I don't think this is helpful for the visually impaired. It's great to learn about their style, but as I'm trying to help my girlfriends who is blind, these techniques are too visual. If I were to close my eyes, there would be no way of knowing where to click. We understand things in grid and visual form; they don't.
Your friend would probably need to use JAWS which is all keyboard commands