handcoding + nvda   72

Managing Protected Applications | Webroot
This page goes over how you can set Webroot so that certain applications have full system access, such as NVDA.
webroot  nvda  windows  windows10  accessibility  a11y  2019 
january 2019 by handcoding
Shut up JAWS | TPG – Digital Accessibility Solutions
“One of the tasks I perform regularly is to test web content using screen readers. It can be somewhat annoying to be capturing data in a desktop application while testing in a browser, as the screen reader is chattering away on every application, while I am only interested in how it works with web content in the browser.”
jaws  nvda  screenreaders  accessibility  a11y 
september 2018 by handcoding
SwitchingFromJawsToNVDA · nvaccess/nvda-community Wiki
(Perhaps one might also be able to use this to go in the opposite direction?)
“The purpose of this guide is to assist users of JAWS (Job Access With Speech), a commercial screen reader by Freedom Scientific to switch to the open source screen reader NVDA (NonVisual Desktop Access) with ease. It assumes prior knowledge of JAWS and that you are proficient in its use.”
jaws  nvda  2018  screenreaders  accessibility  a11y 
september 2018 by handcoding
Time to revisit accesskey? – Tink
“Interaction with the virtual buffer works like this: the screen reader listens for keyboard events. When it detects a key press that corresponds to a screen reader command, that action is executed in the virtual buffer. For example, if the h key is pressed when a Windows screen reader is running, focus will move to the next heading (h1 – h6) in the virtual buffer. Otherwise the key is passed back through to the browser, where it will be caught by the JavaScript that handles the shortcuts provided by the website.

“The trouble is that Windows screen readers utilise almost every available key for screen reader specific commands. This means that few keys make it past the screen reader to the browser, and consequently the JavaScript shortcuts are never triggered.”


“It is possible to tell both NVDA and Jaws to pass the next key through to the browser. In NVDA you press the NVDA modifier (insert) f2, followed by the key you want to pass through. In Jaws it’s the Jaws modifier (insert) 3, followed by the key to pass back to the browser. This is not a user-friendly way to interact with a website though, even assuming you know it’s possible in the first place.”


“An April 2015 update to Jaws 16 introduced a feature that attempts to solve the problem. The “Web application reserved keystrokes” setting tells Jaws to stop intercepting keys that have been reserved by the website. In the case of Facebook, Jaws would ignore the p as a command to move to the next paragraph, and send the key through to the browser where it would trigger the JavaScript shortcut for posting a status update.

“This feature does solve the problem (for Jaws users at least), but it’s something of a dirty hack. In order for Jaws to know which keys have been reserved by the website, it’s necessary to reference the shortcuts in the HTML. For example:

<div data-at-shortcutkeys={‘j’: ‘Key to navigate to next post’, ‘q’: ‘Key to place focus in chat’}></div>

“Jaws then has to scrape the DOM to get at that information. It’s a method that’s prone to error, and scraping the DOM is always much less efficient than querying the accessibility API.”
tink  screenreaders  jaws  nvda  2018  keyboard  shortcuts 
august 2018 by handcoding
Understanding screen reader interaction modes – Tink
“By creating a virtual copy of the document, screen readers make it possible for blind people to interact with content in ways that would otherwise be impossible on the Windows platform. This happens because the screen reader intercepts most keypresses before they reach the browser, triggering an interaction with the virtual document instead.”


“Not all keypresses are captured by the screen reader however. When the tab key is pressed, it is automatically passed through to the browser where it causes keyboard focus to move to the next piece of interactive content, exactly as though the screen reader weren’t running. The same thing happens in other circumstances too, when the enter key is used to activate a link or the space key to select a checkbox for example.”


“There are subtleties to this mode of interaction, though. For example, NVDA will automatically enter/exit focus mode when the tab key is used to move focus on/off the form field, but not if the cursor keys are used. JAWS will automatically enter/exit forms mode whichever method is used to move focus to the field, although as of JAWS16 it’s possible to configure JAWS to ignore forms mode when navigating through content using the cursor keys. Both screen readers can also be forced to switch modes manually, and both indicate the switch in mode with an audible ‘click’.

“There is one anomaly amongst form fields when it comes to forms/focus mode. Although it’s possible to select a radio button without switching modes, it is necessary to be in forms/focus mode in order to use the cursor keys to cycle through the radio buttons in a group. Being unaware of this can sometimes lead to the mistaken belief that a radio group is somehow flawed.”


“To all intents and purposes, applications mode is the same as forms/focus mode – it causes the screen reader to pass keystrokes back through to the browser so they can fulfil their original purpose. For example, when the tablist and tab roles are used as part of the tab widget design pattern, using the tab key to move focus onto the first tab in the set causes a Windows screen reader to automatically switch into applications mode. From that point all the keyboard interaction is handled by the script.”
nvda  jaws  formsmode  focusmode  2014  browsemode  forms  focus  screenreaders  canonical 
august 2018 by handcoding
Sounds frustrating! There’s an audio problem affecting users of any screen reader on some Windows computers, and it needs to be fixed – Mosen Consulting
“It’s not surprising that as screen reader users, most of us are not happy to take the productivity hit that comes from waiting for our audio to respond to a command. So what can you do if you have one of these affected devices? Here are a few options in order of complexity.”
audio  screenreaders  windows  jaws  nvda  2018 
august 2018 by handcoding
Screen Reader Keyboard Shortcuts
This looks to be a pretty decent collection of keyboard shortcuts for NVDA, JAWS, VoiceOver, and TalkBack.
keyboard  shortcuts  2017  jaws  nvda  accessibility  a11y 
november 2017 by handcoding
Firefox 57 from an NVDA user's perspective - Marco's Accessibility Blog
"Firefox 57, also known as Firefox Quantum, will be released on November 14. It will bring some significant changes to the Firefox rendering engine to improve performance and open the door for more new features in the future. Here is what you need to know if you are a user of the NVDA screen reader."
firefox  firefox57  nvda  accessibility  a11y  macrozehe  2017 
november 2017 by handcoding
NV Access | In-Process Halloween 2017: Firefox 57, Windows Fall Creaters Update, Australian NDIS and more
"There has been a lot of talk in the community lately about Mozilla’s soon to be released update to the popular Firefox web browser. The changes in Firefox 57, known as Firefox Quantum are designed to improve the speed and security of the browser. This, unfortunately, also impacts on the user experience for screen reader users. At this stage, NV Access is recommending that users switch to using Firefox’s Extended Support Release (ESR) version, and avoiding 57 until it is suitable for use with NVDA."
firefox  firefox57  nvda  2017  accessibility  a11y 
october 2017 by handcoding
Dialogs in web pages in Firefox and Chrome now get browseMode if the parent document also has browseMode by michaelDCurran · Pull Request #7433 · nvaccess/nvda
(This change been committed for NVDA 2017.4:)
"The web accessibility community has requested that dialogs be navigable the same way any normal web document is (I.e. has NVDA browseMode by default), unless they are embedded in an application. Currently NVDA treats dialogs similar to applications in that browseMode is not available by default.”

(This is also why you no longer need to have role="document" within dialogs—since that was to work around an issue that is fixed by this.)
nvda  nvda2017  accessibility  a11y  dialog  2017  document 
august 2017 by handcoding
SVG | Accessible Examples | test page
via @AmeliasBrain: "Useful reference of SVG markup for adding alternative text, and which ones actually work in common browser/screen-reader combos."
(via https://twitter.com/AmeliasBrain/status/881294288767729665)
via:AmeliasBrain  svg  canonical  alttext  jaws  nvda  2017 
july 2017 by handcoding
Test table without headers and ids
"Headers are a pain for developers, prone to error, and hard to test."
headers  tables  accessibility  a11y  id  nvda  jaws 
june 2017 by handcoding
aria-current design patterns
This page summarizes the current level of support for aria-current as of May 2017:

In short:
- JAWS 18: Universally supports all values
- NVDA 2017: Supports none of the values
- TalkBack: Supports none of the values
- VoiceOver: Universally supports all values

It looks like aria-current will be added in NVDA 2017.2, though:
jaws  nvda  aria-current  2017  navigator  talkback  voiceover 
may 2017 by handcoding
Text links: aria-label and title
As of NVDA 2014, it looks like it ignores the title attribute on a link if it matches. (As does JAWS.)
nvda  title  links  accessibility  2013  a11y 
march 2017 by handcoding
"This add-on excludes beeps in the speech mode when pressing NVDA+s. You can only toggle between off or talk."
nvda  add-ons  speech  2017 
february 2017 by handcoding
Accessibility Testing with the NVDA Screenreader
"This is the first post in a two-part series on Accessibility Testing for Developers by Matt Isner, a developer here at Deque Systems. For today’s post, Matt has created a video demonstration for sighted developers on how to install and configure the NVDA screen reader for accessibility testing. (Please note: NVDA is for Windows only.)"
nvda  video  beginners  2016  tutorials  accessibility  a11y  deque 
october 2016 by handcoding
Event Handlers and Screen Readers | Unobfuscated: May 21, 2013
"Here is a table outlining the events delivered when you press the "ENTER" key on an anchor tag with various different roles applied to it (also shows the ctrl-option-SPACE events for VoiceOver as this is commonly used instead of the ENTER key by users)."
accessibility  keydown  keyup  a11y  nvda  jaws  voiceover  2013  keypress 
september 2016 by handcoding
Getting Started with NVDA - The A11Y Project
"If you’re used to using VoiceOver and miss the on-screen text description output, NVDA also has this available as a feature. To enable descriptive text output, check the Tools > Speech viewer checkbox. This will open a new, always-on-top, window with a continuous log of text that is being described by NVDA."
nvda  transcript  output  settings  text  accessibility  a11y  2015 
september 2016 by handcoding
NVDA – Voice options – CNIB - YouTube
This video offers a decent demo of NVDA’s default voice, eSpeak, against Microsoft’s SAPI voice, Anna.
voices  nvda  accessibility  a11y  2015  comparison  anna 
june 2016 by handcoding
NV Access | High-Quality Voices Available for NVDA
"NV Access is very happy to announce the availability of the Nuance Vocalizer range of voices for NVDA. These voices, which have proven to be popular on iPhones and the Mac, can now all be purchased for one affordable price for use with NVDA. Whether you use NVDA installed on one computer, or carry it around with you for access at anytime on a USB flash drive, these performant and high-quality voices will be there when you need them.

"Purchasing Vocalizer today for 75 EUR gives you access to over 50 different voices covering more than 30 major languages."
nvda  accessibility  voices  a11y  2012 
june 2016 by handcoding
Alternative voices for NVDA! | Pam Griffith
"Starting with NVDA version 2011.3, the Microsoft Speech Platform is now supported by NVDA. You will first need to install the Speech Platform Runtime. Then you may browse the redistributable language packs for the specific voices for the languages you prefer. Some voices are low quality, so you may have to hunt around for the good ones.

"I like the "ZiraPro" U.S. English voice, and the British one seems nice too.”

(You can hear demos of the voices here: https://cloud.voiceelements.com/tts)
nvda  accessibility  voices  2012  a11y 
june 2016 by handcoding
Vocalizer Demo
The Vocalizer text-to-speech engine seems pretty decent, actually.

(“Evelyn" is pretty nice. And “Ava” isn’t bad either.) ("Samantha” also seems similar-ish to “Kate” that you have.) You can get all these—well, not Evelyn for some reason—from here: https://vocalizer-nvda.com/downloads

(Also, pretty sure that “Tom” is the “Tom” that you have.)

And you can buy Vocalizer from here: http://www.atguys.com/store/index.php?main_page=advanced_search_result&search_in_description=1&keyword=vocalizer&x=0&y=0
texttospeech  nvda  2016  voices  accessibility  a11y 
june 2016 by handcoding
How and Where To Report Accessibility Bugs | CSUN 2016 | Whose Line Is It Anyway?
"How and Where To Report Accessibility Bugs—Current List of Bug Tracker Systems"
a11y  bugs  apple  firefox  nvda  jaws  safari  2016  accessibility 
june 2016 by handcoding
Dialog focus setting research
"Where should focus move when you open a dialog? Let's experiment."
2016  accessibility  a11y  nvda  jaws  voiceover  dialog  aria  focus 
june 2016 by handcoding
Welcome to the NVDA Community Add-ons website
"NVDA is a very flexible and extensible screen reader. NVDA add-ons are additional packages that can be downloaded and installed into your copy of NVDA to enhance existing functionality or add additional features.”

Some of the ones that may be worth a look include:
* Focus Highlight
* And maaaybe NoBeepsSpeechMode?
nvda  addons  2016  accessibility  a11y 
may 2016 by handcoding
Accessibility Testing with the NVDA Screenreader - YouTube
"This is a guide for developers on how to install and configure the NVDA screen reader for Windows for accessibility testing.”
(via: https://twitter.com/aardrian/status/734453313694015489)
nvda  tutorials  video  youtube  deque  2016  via:aardrian  beginners  screenreaders  accessibility  a11y 
may 2016 by handcoding
NVDA doesn't know a difference between Links and Same Page Links · Issue #141 · nvaccess/nvda
It looks like this is the NVDA feature request to have it announce in-page links.
nvda  accessibility  a11y  2014  links 
march 2016 by handcoding
Testing output for different combinations of alt and title on img
(From February 2016:)
"This page serves to test different variants of using alt and title and report on the output of a number of screen readers."
jaws  nvda  title  alt  images  img  accessibility  a11y  testing  2016 
february 2016 by handcoding
BUTTON with TITLE containing IMG with null ALT - Screen reader compatibility
It seems that code such as this (with a button) works in all screen readers:
<button title='This is button title'><img src='1234.png' alt=''></button>
screenreaders  jaws  nvda  2016  accessibility  a11y  title  button  images 
january 2016 by handcoding
A element containing IMG with TITLE - Screen reader compatibility
It looks like code such as this works in all screen readers:
<a href='4567.html'><img src='1234.png' title='this is an image title'></a>
jaws  nvda  accessibility  a11y  title  images  links  2015 
january 2016 by handcoding
Loopback review: An easy way to route your Mac’s audio to your software and devices | Macworld
"The only drawback of Loopback is its price: At $99 regularly ($75 in an introductory sale), it’s not a casual purchase for most people. Audio professionals and those who regularly record podcasts will find the price perfectly fine, and the demand for such a specialized offering may be so low that Rogue Amoeba needs to price it high to make it viable to continue to develop. Loopback fits the bill nicely as an elegant way to better control audio routing." (Perhaps this might come in handy for capturing JAWS's audio output or the like?)
audio  mac  osx  software  reviews  jaws  nvda  2016 
january 2016 by handcoding
Jantrid: Woe-ARIA: The Surprisingly but Ridiculously Complicated World of aria-label/ledby
"There are certain elements such as links, buttons, graphics, headings, tabs and menu items where the content is always what makes sense as the label. While it isn’t clear that it can be used for this determination, the ARIA spec includes a characteristic of “Name From: contents” which neatly categorises these controls.

"Thus, we reach our first solid rule: if the ARIA characteristic “Name From: contents” applies, aria-label/ledby should completely override the content."
"The solution I eventually implemented in NVDA is that for check boxes and radio buttons, if the label is invisible, we do render the name as the content for the check box. Finally, another solid rule."
aria  aria-label  aria-labelledby  accessibility  a11y  2015  nvda 
december 2015 by handcoding
Firefox and IE (but not Chrome) "remember" last tab order even after hard refresh, but only with NVDA running. · Issue #4386 · nvaccess/nvda
It looks like NVDA "helpfully" remembers your last focus position within a given page?

"Yes, NVDA remembers the user's last position on the page. We do this so that going back or forward will position the user where they were previously, just as this would occur visually. Unfortunately, browsers don't/can't tell us where they scrolled to in this case, so we have to mimic this behaviour."
nvda  focus  accessibility  2014  a11y  focusmanagement 
december 2015 by handcoding
#3321 (Fieldsets that contain a checkbox grouping does not read the legend at times) – NVDA Trac
Here’s that NVDA bug about how it doesn’t handle <legend>s properly if there’s an <a> in the <legend>.
nvda  legend  anchor  accessibility  a11y  bugs  2015  fieldset 
december 2015 by handcoding
How to map your Mac’s CapsLock key to a NVDA or JAWS key in a Windows virtual machine | Marco's Accessibility Blog
"OK folks, this is hopefully it, the ultimate way to map the CapsLock key of your MacBook to be used as a NVDA or JAWS modifier key in a virtual machine running Windows."
keyboard  remapping  capslock  2015  nvda  accessibility  a11y 
december 2015 by handcoding
FIELDSET containing links - Screen reader compatibility
As of December 2015, it looks like NVDA has issues with <fieldset> elements if its <legend> contains a link.
nvda  2015  jaws  fieldset  legend  comparison  canonical  links  accessibility  a11y 
december 2015 by handcoding
Yes/No radio buttons inside FIELDSET - Screen reader compatibility
This page goes over screen-reader support for basic fieldset/legend use. (Looks like that use case is pretty widely supported.)
fieldset  legend  nvda  jaws  canonical  forms  2015  accessibility  a11y 
december 2015 by handcoding
Text links: aria-label and title
This page tests whether screen readers read title attributes on links. In short: JAWS and NVDA do most of the time (unless the title attribute is identical to the link text).

But you may as well ignore this page because this other page is waaaay more comprehensive:
nvda  jaws  2014  accessibility  a11y  title  links 
november 2015 by handcoding
Upper Case Character Test
"This is a test to determine how screen readers handle words or phrases in all upper case.“ (It would seem that words of 5 or more letters are often read as regular words.)
screenreaders  accessibility  a11y  nvda  jaws  2011 
november 2015 by handcoding
WebAIM: The Resurgence of ZoomText and Window-Eyes
"We often consider VoiceOver with Safari as a testing platform and not Window-Eyes or ZoomText when in fact Window-Eyes with IE, ZoomText with IE, and ZoomText with Firefox are all more common combinations than VoiceOver with Safari."
screenreaders  accessibility  a11y  2015  jaws  nvda  windoweyes  zoomtext 
august 2015 by handcoding
Screen Reader Settings: NVDA - wiki.gpii
"The NVDA settings are stored in a plain text file. On Windows, this file is located in a page like: /Users/kasper/AppData/Roaming/nvda/nvda.ini."
nvda  migration  settings  screenreaders  2015 
august 2015 by handcoding
Injecting content into the page
This page goes over a bunch of tests combinations for aria-live properties (including tests with JAWS and NVDA).
nvda  jaws  aria  aria-live  accessibility  a11y  2015 
july 2015 by handcoding
WebAIM: E-mail List Archives
"There are courses on using screen readers for web developers and QA professionals. We have one at Deque called "Testing with Screen Readers. It covers JAWS, NVDA, and VoiceOver in some detail, on both a conceptual and technical level."
screenreaders  tutorials  jaws  nvda  2015 
july 2015 by handcoding
IVONA Text-to-Speech
"Neospeech doesn't sell their voices to private customers anymore. Only to other companies. While neospeech was once the leader in voice synthesis competitors have finally catched up. Ivona is a good example of this. Their English voices, especially the British ones, are excellent. I love their Brian voice. The AT&T voices have been around for years but are still a good alternative as well." (via: http://forum.audiogames.net/viewtopic.php?id=8356)
nvda  voices  2015  accessibility  windows  a11y 
july 2015 by handcoding
Alternatives to the fieldset element
This page offers some pretty comprehensive testing of various fieldset alternatives for radio buttons, including: fieldsets themselves, aria-describedby, and role="radiogroup". (The tests cover NVDA 2014.2, JAWS 16, and VoiceOver on OS X Mavericks.)
aria  accessibility  a11y  radiogroup  fieldset  forms  2014  jaws  nvda  canonical  radio 
july 2015 by handcoding
A "click here" link with TITLE attribute - Screen Reader Compatibility
This page tests whether screen readers will announce a superfluous title attribute on a link.
a11y  accessibility  screenreaders  2014  jaws  nvda  links  title 
june 2015 by handcoding
The Incredible Accessible Modal Window, Version 3
This page might just offer the canonical set of code for modal dialogs / overlays / lightboxes. And it looks to be up to date as of 2014.
2014  nvda  accessibility  a11y  overlays  lightboxes  canonical  role  dialog  alertdialog 
june 2015 by handcoding
ARIA Live Region Test
"In order to get the updated [content] to be read properly by VoiceOver in Mac OS X, NVDA in IE, and Window-Eyes in Firefox, the method used in Game 3 is necessary -- [place] all updated content in one container, not in separate containers within a live region parent."
aria  wai-aria  accessibility  a11y  aria-live  2015  jaws  nvda  testing  scores  canonical 
may 2015 by handcoding
Using display:table has semantic effects in some screen readers | 456 Berea Street
"When testing the technique I describe in Flexible height vertical centering with CSS, beyond IE7, I noticed that, in some cases, some screen readers will treat “tables” created with CSS as if they were real HTML tables. I did not expect that."
jaws  nvda  2011  tables  displaytable  accessibility  a11y  2015 
may 2015 by handcoding
Accessibility support for CSS generated content – Tink
via @rogerjohansson: "'generated content is […] recognised by screen readers.' IOW don't use CSS content for things you don't want spoken."
css  generated  accessibility  a11y  2015  nvda  jaws  generatedcontent 
march 2015 by handcoding
Aural UI of HTML elements
This post goes over how screen readers announce various HTML elements and other semantic bits.
markup  accessibility  a11y  jaws  nvda  canonical  screenreaders  2015  semantics  audio  announcements 
march 2015 by handcoding
Unify – Unicode support on browsers and devices
This page summarizes how screen readers pronounce various high-Unicode characters.
screenreaders  nvda  jaws  unicode  characters  2015 
february 2015 by handcoding
Screen reader: Acapela Group gives further support to NV Access with Acapela TTS voices for NVDA.
"The Acapela TTS voices for NVDA product already supports several languages: English (US), English (UK), English (Australia), English (India), Spanish (Spain), Spanish (US), Portuguese (Portugal), Portuguese (Brazil), Russian, Italian and Greek.

Voices are available in two versions, a Basic license (59 Euros) or a Premium license (99 euros), both are multilingual and allow up to 3 installations."
acapela  nvda  accessibility  a11y  2015  voice 
february 2015 by handcoding
Marco Zehe on Twitter: "@theunfocused You can press ctrl to stop speech, or the *right* shift key to pause and resume speech. Or do you mean mute the synth?"
via @MarcoInEnglish: "You can press ctrl to stop speech, or the *right* shift key to pause and resume speech."

He then added, "NVDA-key+S toggles between speech, beeps, and off. NVDA is normally either Insert key."

And: "But right-clicking NVDA symbol, Settings, Keyboard, you can enable the CAPSLOCK key to be the NVDA key, too."
nvda  accessibility  a11y  2015  screenreaders  via:MarcoInEnglish 
january 2015 by handcoding
Basic screen reader commands for accessibility testing
via @paciellogroup: "New! Basic screen reader commands for accessibility testing, by @LeonieWatson"
jaws  nvda  screenreaders  accessibility  a11y  2015  quickreference  via:paciellogroup  keyboard  shortcuts 
january 2015 by handcoding
Accessibility tests
Via @stevefaulkner: "Ever wondered what pages sound like in JAWS and NVDA? Here are a wide range of simple tests: http://bit.ly/1xbd0lj by @russmaxdesign"
accessibility  a11y  jaws  nvda  comparison  2014 
november 2014 by handcoding
SwitchingFromJawsToNVDA – NVDA Community
"The purpose of this guide is to assist users of Freedom Scientific's JAWS For Windows in switching to NVDA. It assumes prior knowledge of JAWS and that you are proficient in it's use. It is not intended to be a replacement of the included user guide, rather as a means to make NVDA seem less daunting."
jaws  nvda  a11y  accessibility  2014  comparison 
february 2014 by handcoding
WebAIM: Using NVDA to Evaluate Web Accessibility
"This article is designed to help users who are new to NonVisual Desktop Access (NVDA) - external link learn the basic controls for testing web content, and to serve as a reference for the occasional NVDA user. NonVisual Desktop Access (NVDA) is a free and open source screen reader for the Microsoft Windows operating system."
nvda  tutorials  beginners  webmaim  accessibility  a11y  2013 
march 2013 by handcoding
Form control labeling tests
This page is about "Testing form control labelling support in popular browsers and screen readers" (and it appears to be continuously updated, too.)
forms  labels  canonical  jaws  nvda  screenreaders  accessibility  a11y  2012  comparison 
october 2012 by handcoding
WAI ARIA Landmark Role Tests
This page goes over how various screen readers handle ARIA landmark roles (as of November 2011). Most newer screen readers seem to be handling them well... except for Window Eyes, which kinda tanks.
screenreaders  aria  2011  jaws  windoweyes  wai-wria  nvda  landmarkroles  comparison  canonical  a11y  accessibility 
august 2012 by handcoding
Learning How to Test with Screen Readers | Web Axe - Practical Web Design Accessibility Tips - Podcast and Blog
"Here are some good articles to help learn how to use a screen reader to test for web accessibility." (This post includes links relating to NVDA and JAWS.)
jaws  nvda  accessibility  testing  screenreaders  2011 
april 2011 by handcoding
HTML5, ARIA Roles, and Screen Readers in March 2011 | Research | Accessible Culture
"Last year, in HTML5, ARIA Roles, and Screen Readers in March 2010, I took a look at how then current screen readers behaved with some of the HTML5 section elements and related WAI-ARIA document and landmark roles. Now that the major screen readers have all seen some significant updates, and both Firefox 4 and Internet Explorer 9 have officially been released, I figure it's time to perform the review again and see what, if anything, has changed."
accessibility  jaws  nvda  canonical  aria  wai-aria  roles  windoweyes  comparison  2011 
april 2011 by handcoding
HTML5, ARIA Roles, and Screen Readers in May 2010 | Research | Accessible Culture
"[...] I wanted to play around a bit and confirm for myself how some of the leading screen readers for Windows, namely JAWS 11, Window-Eyes 7.11, NVDA 2010.1, and SAToGo 3.0.202, currently handle basic HTML5 sectioning elements as well as ARIA landmark and other roles."
accessibility  aria  wai-aria  html5  comparison  2010  jaws  nvda  windoweyes  satogo  software 
august 2010 by handcoding
HTML5, ARIA Roles, and Screen Readers in May 2010 — Research — Accessible Culture
"[...] I wanted to play around a bit and confirm for myself how some of the leading screen readers for Windows, namely JAWS 11, Window-Eyes 7.11, NVDA 2010.1, and SAToGo 3.0.202, currently handle basic HTML5 sectioning elements as well as ARIA landmark and other roles." (Summary: NVDA wins.)
aria  wai-aria  jaws  nvda  2010  comparison  accessibility  windoweyes  satogo  landmarkroles  html5 
may 2010 by handcoding
Configuring Your Machine For Testing With A Screen Reader » Yahoo! User Interface Blog (YUIBlog)
"When developing using the WAI-ARIA Roles and States, you need to test your code in a screen reader to ensure everything is working as you expect. As a follow up to my presentation on Developing Accessible Widgets with ARIA and in the interest of helping other developers test their code, I thought I would provide some tips on how to configure your development environment for screen reader testing."
aria  wai-aria  2008  nvda  jaws  accessibility  screenreaders  windoweyes  software  canonical 
april 2010 by handcoding
Screen Readers And WAI-ARIA Landmark Roles – Humanising Technology
"Like lists and other page elements, document landmark roles have their own quick nav keys. In NVDA it’s the d key and in Jaws it’s the semi colon. [...] Using a landmark quick nav key to move through the page, a screen reader will tell you what kind of landmark you’ve arrived at. For example, Jaws will report 'Search landmark' or 'Navigation landmark'."
accessibility  bestpractices  2010  wai-aria  aria  landmarkroles  jaws  nvda 
march 2010 by handcoding
NVDA command key quick reference
"This document is based on the command key quick reference file installed with version .6 of NVDA a free open source screen reader for Windows." (via: https://twitter.com/stevefaulkner/statuses/4627292023)
nvda  quicksilver  2009  keyboard  shortcuts  hotkeys  via:stevefaulkner 
october 2009 by handcoding
The WAI-ARIA Windows screen reader shootout « Marco’s accessibility blog
"I’ve taken each one of the following screen readers running on the Windows platform on a tour through some WAI-ARIA implementations that are out there for everyone to use." (via: https://twitter.com/stevefaulkner/statuses/2420355607)
nvda  jaws  reviews  comparison  screenreaders  software  windows  windoweyes  supernova  2009  accessibility 
july 2009 by handcoding
Low-Cost Screen Readers
"In the following article the International Braille and Technology Center Access Technology Team reviews four free or low-cost screen readers: Thunder, NVDA, System Access, and WebAnywhere." (via https://twitter.com/stevefaulkner/statuses/1746359715)
2009  reviews  comparison  screenreaders  nvda  thunder  systemaccess  webanywhere  nfb 
may 2009 by handcoding
How to use NVDA and Firefox to test your web pages for accessibility « Marco’s accessibility blog
"This article aims to provide a guide to testing your web sites or web applications using both NVDA and Firefox. [...] NVDA (Non-visual Desktop Access) is a free and open-source screen reader for the Microsoft Windows operating system."
2009  firefox  accessibility  wai-aria  testing  screenreaders  nvda 
april 2009 by handcoding

related tags

a11y  acapela  accessibility  add-ons  addons  alertdialog  alt  alttext  anchor  anna  announcements  apple  aria  aria-current  aria-label  aria-labelledby  aria-live  audio  beginners  bestpractices  browsemode  bugs  button  canonical  capslock  characters  comparison  css  deque  dialog  displaytable  document  fieldset  firefox  firefox57  focus  focusmanagement  focusmode  forms  formsmode  generated  generatedcontent  headers  hotkeys  html5  id  images  img  jaws  keyboard  keydown  keypress  keyup  labels  landmarkroles  legend  lightboxes  links  mac  macrozehe  marcysutton  markup  migration  navigator  nfb  nvda  nvda2017  osx  output  overlays  quickreference  quicksilver  radio  radiogroup  remapping  reviews  role  roles  safari  satogo  scores  screencasts  screenreaders  semantics  settings  shortcuts  software  speech  supernova  svg  systemaccess  tables  talkback  testing  text  texttospeech  thunder  tink  title  transcript  tutorials  unicode  via:aardrian  via:AmeliasBrain  via:MarcoInEnglish  via:paciellogroup  via:stevefaulkner  video  voice  voiceover  voices  wai-aria  wai-wria  webanywhere  webmaim  webroot  windoweyes  windows  windows10  youtube  zoomtext 

Copy this bookmark: