handcoding + jaws   106

Jaws does not enter application mode when focus is moved inside a container with role="application" · Issue #93 · FreedomScientific/VFO-standards-support
“When focus is programmatically moved to an element inside a container with role=‘application’, JAWS does not enter application mode. Tabbing to the next element inside the container will then enter application mode.”

And then there was this reply from Léonie:
“I think this is expected behaviour. When focus is moved using JS, Jaws will be in Virtual Cursor mode. Triggering applications mode from within virtual mode would be quite problematic in other circumstances.”
jaws  accessibility  applicationmode  application  modes  screenreaders  github  2018 
february 2019 by handcoding
Shortish note on JAWS support for regions | TPG – Digital Accessibility Solutions
(It looks like JAWS no longer announces all landmark regions by default:)

“JAWS has a ‘Web Verbosity Level: Low/Medium/High’ You can view/set this by opening the Settings Center and expanding the ‘Web/HTML/PDF’ tree item and selecting the ‘Reading’ item. The default verbosity level is ‘Medium’ If you press the ‘Medium…’ button the configuration dialog will be displayed.

“What you will note is that at the default ‘medium’ verbosity, only a subset of the landmark regions are checked, thus only these regions will be announced. Note this does not mean that the user cannot navigate to the unchecked regions using the region navigation keys: R/Shift+R; it means that when navigated to the content of the region will be announced without denoting the regions start and end.”
jaws  2018  tpg  landmarks  aria  accessibility  a11y 
february 2019 by handcoding
Unexpected keyboard focus of inactive tab in a tablist · Issue #132 · FreedomScientific/VFO-standards-support
“When interacting with an ARIA Tab widget, it’s common to set the currently active tab to have a tabindex=0 and to set the inactive tabs to have a tabindex=-1. When testing various different implementations of Tab widgets, it was noticed that if navigating by the virtual cursor, and then hitting the Tab key, keyboard focus would be set to the first tab in the tablist, regardless of whether or not it was the currently active tab / the tab with the tabindex=0.

“Removing the possibility that incorrect JavaScript/focus management could be to blame, a reduced test case continues to display this behavior across browsers.”
jaws  bugs  tabs  tablists  aria  accessibility  a11j  2019  github 
january 2019 by handcoding
JAWS 18.0.2945 Latest Update Plus What's New
(On JAWS’s new focus-hightlight jobbie:)
“The following is a list of improvements made between the JAWS 18 April 2017 release and the May 2017 update.

“Beginning with this update, JAWS now visually highlights text in Windows 10 and Windows 8.1 as you navigate using the Virtual Cursor. As JAWS reads, the current text being read is highlighted so a sighted user such as a parent, teacher, developer, or tester can easily follow the text visually. JAWS visual tracking is available in Internet Explorer, Chrome, Firefox, PDF documents opened in Adobe Reader, and Microsoft Mail. It is enabled by default in these specific applications.

“Note that when navigating by line on pages in the web browser, JAWS highlights the virtual line and not the actual line as it appears on the web page.

“While the default settings for the highlight should work well for many users, you can also customize the appearance of the visual highlight including the color, style, transparency, thickness, and spacing. For example, the default color is Lime Green while the default style is Block, which places a solid rectangle around the highlighted text.

“However, you may prefer a different color, style, and more transparency for the highlight. To change these Settings, open Settings Center while focused in one of the supported applications, expand the new Visual Settings group, select Highlight Virtual PC Cursor, and then press F6 to move to the pane where you can configure visual tracking settings.”
jaws  jaws18  2017  accessibility  focus  a11y 
january 2019 by handcoding
Selecting Text, Cut, Copy, and Paste from the Keyboard
This post goes over how to select, copy, and paste text using JAWS (including within web browsers).
jaws  screenreaders  accessibility  keyboard  2019  tutorials  copy  paste  select 
january 2019 by handcoding
WebAIM: JAWS ate my tables
(This post talks about some of the heuristics that JAWS uses to gauge whether a table is a data table or a layout table. *Just as a heads-up—this post is also from 2009.*)

“JAWS Behavior

“UPDATE: In response to the details provided here, Freedom Scientific reports that JAWS 11.0.756 released Dec. 17, 2009 resolves many of these issues and now accounts for the presence of table headers in it’s consideration of table type.

“Data tables should typically be assigned table headers (the
element) for all header cells. The presence of a
element in a table should be a dead giveaway that a table is intended for data. I’ve seen very few instances of the
element inappropriately used in layout tables. However, JAWS does not consider table headers or any other markup commonly used in data tables to determine the table type.

“Instead, JAWS assumes the presence of a data table if it has at least 2 rows and 2 columns AND at least 4 cells in the table are between 200 and 16000 square pixels in size. 16000 square pixels is not much – a long sentence of default text or a small 200X80 pixel image.”
jaws  tables  heuristics  datatables  layouttables  2009 
september 2018 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
Major New Features in JAWS Inspect | TPG – Digital Accessibility Solutions
“For those familiar with the Say All feature in JAWS, this new report essentially runs the Say All command on a web page and gives you back an easy-to-use, linear text version of the JAWS speech.”
jaws  jawsinspect  2018  tpg  work  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
Fieldset, Label, and Legend Elements - Level Access Web Labs
“JAWS 18+ only announces fieldset label when entering in Firefox and Chrome but in IE still announces for each tab stop in the fieldset. Doesn’t seem to announce fieldset for Edge.”
accessibility  a11y  jaws  fieldset  2018 
may 2018 by handcoding
Steve Faulkner on Twitter: "Tried JAWS 2018 latest with @Firefox 60.0b11 (64-bit) version and it is now usable, from a sighted users perspective at least 👏🏽… https://t.co/kzo54sqraE"
(As of April 2018:)
“Tried JAWS 2018 latest with @Firefox 60.0b11 (64-bit) version and it is now usable, from a sighted users perspective at least”
firefox  jaws  2018  twitter  stevefaulkner 
april 2018 by handcoding
How to Bypass Navigation Quick Keys
"In order for JAWS to know what keys are being used by the web site, web page authors must include a line containing the key assignments as part of an HTML element where the keystrokes are intended to work. For instance, if you use a <div> tag to hold the main content of the page and the keystrokes are meant to work anywhere on the page, you would do something like the following:

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

"No matter where JAWS is focused on the page, the web site keys will work since they are attached to the main <div> tag.

"Alternatively, if you had a section of the page reserved for sending and receiving chat messages, you might have certain keystrokes that only work in the chat area. In this case, you would attach the "data-at-shortcut keys" attribute and associated keystrokes to the <div> tag used to designate the chat section. These keys will now only work when JAWS focus is in the chat area.

"In JAWS 16.0.2136 and later, there is now a setting called "Allow Web Application Reserved Keystrokes" that you can configure through Settings Center or Quick Settings. When enabled, pressing any key that is both a JAWS command and defined by the web site as a keystroke, will perform the web site specific function instead of the JAWS command. If this option is off, all JAWS keystrokes are processed normally unless INSERT+F3 is pressed first to pass a keystroke through to the application."
jaws  keyboard  shortcuts  accessibility  a11y  2018 
january 2018 by handcoding
This page goes over the JAWS keyboard shortcuts for navigating between various element types (such as links, lists, description lists, blockquotes, buttons, and others).

The page that Steve mentions in this thread also goes over the expected announcement from JAWS when navigating to various element types
jaws  accessibility  a11y  canonical  keyboard  shortcuts  announcement  aural  2018 
january 2018 by handcoding
What's New in JAWS 2018 Screen Reading Software
"For JAWS users who rely heavily on Braille or for users of Fusion that can see well enough to use the screen for tracking focus, too much speech can be overwhelming while navigating using the keyboard and mouse. However, users still want to be able to use speech to read once they have moved to a location on the screen, or just checking a Window Title, column heading in a table or spread sheet, or even reading the time from the System tray. In both these situations, Speech On Demand can be very helpful. You will find that switching applications with ALT+TAB or using ARROW keys to move through a document are silenced. Speech is only triggered when using a limited set of reading commands such as speaking the current character, word, line, paragraph, or doing a Say All."
jaws  speechoncommand  jaws18  accessibility  a11y  2017  shortcuts  keyboard 
december 2017 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
JAWS Keyboard Shortcuts | Screen Reader Keyboard Shortcuts
This page offers a quick reference for JAWS' keyboard shortcuts. (There’s also a PDF version, which is linked from this page.)
jaws  quickreference  accessibility  a11y  2017  deque  pdf  keyboard  shortcuts  canonical 
july 2017 by handcoding
aria-expanded test
This is your CodePen that you used to uncover the bug in JAWS 18 in which it doesn’t recognize when the currently focused <button>’s aria-expanded state has changed if the expanded content is above the <button>.
jaws  jaws18  bugs  accessibility  a11y  aria-expanded  aria  2017 
july 2017 by handcoding
Shut up JAWS | The Paciello Group – Your Accessibility Partner (WCAG 2.0/508 audits, VPAT, usability and accessible user experience)
"That’s it, you are done. Now JAWS will be silent unless you have one of the applications you have enabled, open."
jaws  stevefaulkner  tpg  accessibility  prefs  a11y 
july 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
What's New in JAWS 18 Screen Reading Software
via @JohnKMcNabb: "JAWS follows VoiceOver and adds visual tracking, a feature to visually highlight text as it reads"
jaws  screenreaders  accessibility  a11y  2017 
june 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
Speech History Mode
via @pauljadam: "Speech History Mode
JAWS retains list of last 50 announcements spoken by speech synth. INSERT+SPACE, then H"
jaws  speech  history  2017 
may 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
What's New in JAWS 18 Screen Reading Software
"The new Vocalizer Expressive 2.2 voices are only available for JAWS 18 and later. If you previously installed Vocalizer Expressive Voices that were used with JAWS versions prior to JAWS 18, those voices will continue to work with earlier versions but will no longer be seen by JAWS 18 once you have installed your first Vocalizer Expressive 2.2 voice.”

"JAWS 18 offers significant improvements when working in Google Docs.”

And it looks like JAWS 18 adds some ARIA 1.1 bits too:
"JAWS 18 ads support for several ARIA 1.1 features that are being used on certain web pages. These include the aria-modal, aria-current, and aria-placeholder attributes, as well as support for partially visible tables."
jaws  voices  audio  2016  jaws18 
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
MouseOver Re: new member - jfw - FreeLists
This page goes over how you can disable JAWS’s jibba jabba onmouseover
onmouseover  jaws  accessibility  a11y  2016 
august 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
JAWS and MAGic Reading Commands and Cursors Used by JAWS
Among other JAWS shortcut keys:

// “browse” mode
laptop users: CAPS LOCK+SEMICOLON -- Virtual cursor

// “focus” / “forms” mode
laptop users: CAPS LOCK+P — JAWS cursor
jaws  keyboard  shortcuts  virtualcursor  browsemode  focusmode  accessibility  a11y  2016 
may 2016 by handcoding
Surf's Up! Surfing the Internet with JAWS and MAGic
On configuring the JAWS key to Insert (or Scroll Lock):
"The JAWS key can be changed from the INSERT key to the CAPS LOCK or SCROLL LOCK key. This can be done by opening the list of JAWS managers (INSERT+F2) and choosing Settings Center. JAWS Key for either desktop or laptop layout is found in the Keyboard branch of the tree view. This must be changed in the default settings."
jaws  jawskey  keyboard  shortcuts  accessibility  setup  a11y  2016 
april 2016 by handcoding
Technical Support: What can I do if JAWS Convenient OCR isn't giving clear recognition results or runs text together?
"The Convenient OCR takes the physical image on the screen at that moment, and is dependent on many factors for accuracy. The feature responds most favorably when it is getting a quality image and working with about 300 dpi. The clearer and larger the image, the better the Convenient OCR results will be. It is not going to be perfect, but it is intended to give a fighting chance where there is no other option. A few tips you can employ to try to get the best image quality from which to start include […]"
jaws  ocr  screenreaders  2016 
march 2016 by handcoding
Comparison of Browsers on HTML5 Video Accessibility: 2015 Update | Terrill Thompson
"This is an update to my earlier Comparison of Browsers on HTML5 Video Accessibility, published two years ago.”

(This test covers IE 11, Firefox 37, Chrome 41, and others. Alongside JAWS 16 and VoiceOver.)
html5  video  2015  accessibility  comparison  jaws  firefox  ie  chrome 
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
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
Short note on Jaws keyboard layouts | The Paciello Group – Your Accessibility Partner (WCAG 2.0/508 audits, VPAT, usability and accessible user experience)
"Jaws has different keyboard layouts because on desktops it makes heavy use of the numpad, whereas the numpad is typically not available on laptops. When you install Jaws the desktop keyboard layout is the default. You can change to the laptop keyboard layout in the startup wizard (Jaws > Help > Startup wizard), or by going to Jaws > Options > Basics > Keyboard layout.

"Web navigation remains unchanged with either keyboard layout, but basic text navigation changes, as does the key that acts as the Jaws modifier key. In desktop layout the modifier key is either insert or numpad 0. In laptop layout it is the capslock key. You hold it to use it as the Jaws modifier, and double tap it to toggle caps on/off."
jaws  accessibility  a11y  keyboard  laptop  shortcuts  2015 
november 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
Seeing Different: JAWS V15 - Speech History
"Since JAWS V15, you can now use a function to navigate through a history of the speech output that JAWS has spoken in the current session."

(The short version: hit Insert+Space, then H.)
jaws  speech  history  accessibility  a11y  2015  keyboard  shortcuts 
september 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
JAWS Keystrokes
via @stevefaulkner: "JAWS Keystrokes - all 400+ of them"
jaws  quickreference  keyboard  shortcuts  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
How To Use 32 Bit SAPI Voices In A 64 Bit System
Well, this seems like a pretty good reason not to use 64-bit Windows: "If you are running a 64 bit operating system such as Windows 7 or Vista 64 bit you may have noticed that many of the text to speech voices out there are 32 bit. What that means is that if you look in your 64 bit Text to Speech control panel none of the 32 bit voices can be selected as a default voice."
windows  vm  vmware  jaws  accessibility  a11y  voices  2015  32bit  64bit 
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
IFRAME with no alt content and no title - Screen Reader Compatibility
* When an iframe is missing a title attribute:
- JAWS 14 will attempt to announce the iframe’s filename
- But JAWS 13 and JAWS 15 are OK.

See also this page for how screen readers react when an iframe is given a title attribute:
jaws  iframe  screenreaders  jaws13  jaws14  jaws15  2014  title  accessibility  a11y  canonical 
june 2015 by handcoding
IFRAME with title - Screen Reader Compatibility
When an iframe is given a title attribute:
- JAWS 13 happens to read the title twice
- But all other screen readers are OK.

See also this page for how screen readers react when an iframe's title attribute is omitted:
jaws  iframe  screenreaders  jaws13  jaws14  jaws15  2014  title  accessibility  a11y  canonical 
june 2015 by handcoding
Important update for IE with future considerations for Assistive Technologies and integrated Accessibility API support in Windows 10 with Edge. | LinkedIn
"This includes all versions of IE, 9 through 11 on all supported OS versions from Vista to Windows 8.x and above.

This means that IE 11 (the last to ever be released), mostly supports ARIA 1.0 as it currently stands, but will fall farther and farther behind as 1.1 is developed and as 2.0 comes over the horizon.

As a result, new Accessibility Tree features and bug fixes that are adopted and incorporated within new browser releases will not be reflected in IE at all, and must instead rely upon Assistive Technology vendors to either choose to make up these gaps on their own using the DOM, or ignore them in favor of standards compliant browsers for better and more responsive accessibility. "
ie  accessibility  a11y  jaws  via:stevefaulkner  2015 
may 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
Screen Reader Testing
"More and more we are seeing font icons on the web. This is a test to see if these can be used in a manner which still supports screen readers."
iconfonts  icons  fonts  accessibility  a11y  2015  jaws  voiceover 
april 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
JAWS HTML Commands | AccessAbility
"Below are several lists of useful keyboard commands for JAWS, current since Version 14."
jaws  shortcuts  keyboard  hotkeys  2015  accessibility  a11y 
february 2015 by handcoding
Is Accessibility a Supply or Demand Issue? | The Paciello Group – Your Accessibility Partner (WCAG 2.0/508 audits, VPAT, usability and accessible user experience)
Via a comment from Patrick Pauke: "The required attribute and aria-required are not completely equivalent. The former also triggers automatic validation and built-in form submission error messages in browsers – which are currently not 100% accessible – while the latter only signals that a form field is required to assistive technologies (without any further validation/error bubbles being triggered in browsers)."

(So that is, if you use the "required" attribute, and if you have a field that you haven’t had a chance to enter text in yet, JAWS will report the field as "required, invalid." But that doesn’t happen if you were to use aria-required="true".)
aria  wai-aria  aria-required  required  forms  paciellogroup  accessibility  a11y  2015  html5  jaws 
february 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
Juicy Studio: Handling erratic behaviour with AT
"The following is the standard approach to dealing with JAWS Quirks [...]"
accessibility  a11y  quirks  JAWS  2013  canonical  virtualcursor  virtualbuffer 
june 2014 by handcoding
WebAIM: Keyboard Shortcuts for JAWS
This post goes over the main keyboard shortcuts for JAWS.
accessibility  jaws  shortcuts  keyboard  2014 
may 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
Juicy Studio: The HTML5 outline algorithm and JAWS
"[...] Fortunately, the problem with JAWS can be solved using WAI-ARIA by applying the heading role and aria-level attribute on the heading elements that are reported incorrectly."
html5  markup  aria  headings  a11y  accessibility  2013  jaws 
may 2013 by handcoding
Alex's blog: Firefox preferences for screen readers
Via @surkovalexander: "#Firefox user preferences for #a11y screen readers"
firefox  a11y  accessibility  screenreaders  jaws  plugins  2013 
april 2013 by handcoding
I thought title text improved accessibility. I was wrong. | Silktide blog
"One of the main things I noticed is that the title attribute isn’t read aloud, AT ALL. There’s an option in JAWS that allows you to read title text instead of the normal anchor text, but it’s not enabled by default."
jaws  a11y  accessibility  2013  titleattribute  title 
january 2013 by handcoding
Abbr and Acronym Test
"JAWS 12 supports abbr and acronym, but it's off by default. If turned on, it reads the value of the title attribute rather than the visible text."
jaws  acronym  abbr  accessibility  a11y  2012 
october 2012 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
All Character References as Read by JAWS and Window-Eyes — JAWS, Window-Eyes and Character References — Accessible Culture
This post goes over how many common Unicode characters are read (or not read) by various screen readers. (And the data is still accurate for JAWS 13 as of Sept. 2012: http://webaim.org/discussion/mail_thread?thread=5501#post1)
unicode  characters  jaws  windoweyes  2012  screenreaders  canonical  accessibility  a11y 
september 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
WebAIM: Designing for Screen Reader Compatibility
"Two of the most common screen readers are JAWS, by Freedom Scientific, and Window Eyes, by GW Micro." This also has the cuseful section on "How Screen Readers Read Content". (The only downside here is that I couldn't find a date of when this was published, so it's hard to know how current this is.)
screenreaders  jaws  windoweyes  2012  canonical  webaim 
august 2012 by handcoding
JAWS, IE and Headings in HTML5 | Articles | Accessible Culture
"You'll have to make up your own mind on how you deal with this issue. For me, until there's broad support for the h1-only approach across most screen readers and browsers in use, I'll take the more backwards-compatible route and use appropriately ranked h1 to h6 elements in my HTML5 pages."
a11y  accessibility  headings  h1  screenreaders  jaws  html5  bugs 
october 2011 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
« earlier      
per page:    204080120160

related tags

32bit  64bit  a11j  a11y  abbr  accessibility  acronym  ajax  alt  alttext  announcement  announcements  apple  application  applicationmode  aria  aria-current  aria-expanded  aria-live  aria-required  audio  aural  backbutton  bestpractices  browsemode  bugs  button  canonical  caption  characters  chrome  click  comparison  copy  css  datatables  dblclick  deque  dialog  displaytable  domscripting  eventhandlers  feather  fieldset  firefox  focus  focusmode  fonts  forms  formsmode  generated  generatedcontent  github  glyphs  h1  hal  hash  hcard  headers  headings  heuristics  history  homepagereader  hotkeys  html5  i18n  iconfonts  icons  id  ie  ie6  iframe  images  img  javascript  jaws  jaws10  jaws13  jaws14  jaws15  jaws18  jawsinspect  jawskey  jquery  keyboard  keydown  keypress  keyup  labels  landmarkroles  landmarks  language  laptop  layouttables  legend  links  mac  markup  microformats  modes  mousedown  mouseup  navigator  nesting  newwindows  number  numbers  nvda  ocr  octothorpe  onmouseover  osx  outlook  paciellogroup  parallels  paste  pdf  phonenumbers  plugins  pound  poundsign  prefs  presentations  pricing  quickreference  quirks  radio  radiogroup  required  reset  reviews  roles  safari  satogo  scores  screenreaders  select  semantics  setup  shortcuts  software  speech  speechoncommand  stevefaulkner  summary  supernova  svg  tables  tablists  tabs  talkback  target  telephones  testing  tink  title  titleattribute  titletag  tpg  tutorials  twitter  unicode  via:AmeliasBrain  via:cgriego  via:paciellogroup  via:stevefaulkner  via:tinyfly  video  virtualbuffer  virtualcursor  vm  vmware  voiceover  voices  wai-aria  wai-wria  webaim  windoweyes  windows  word  work  xhtml  zoomtext 

Copy this bookmark: