Archive for the "Assistive Technology" Topic

ZIP, Z I P, or Z.I.P.? Forcing Correct Pronunciation in Screen Readers

Posted on:

If you’ve ever used a GPS navigation system or app while on a road trip, you know that sometimes the software can’t parse an abbreviation or pronunciation that we take for granted. For example, St. Dunston Lane gets read as “Street Dunston Lane” or McLean is read as “McLEEN” instead of “McLANE.” These are not life or death issues in terms of vehicle navigation or accessibility, but they can be annoying. What do you do when a screen reader is mispronouncing a word that you consider important to your organization’s message?  In general, we do not recommend screen reader specific… Read More

How the W3C Text Alternative Computation Works

Posted on:

The Text Alternative Computation Over the years, there has been a lot of confusion about the W3C Text Alternative Computation and how this works, especially when influenced by the addition of CSS and ARIA attributes. As a bit of forewarning, this article is not primarily meant for general web developers, though having an understanding of these concepts will aid their efforts in building accessible software. Instead, this article is meant to aid browser and assistive technology vendors, as well as those who test and evaluate web technologies for accessibility, in order to identify where the breakdown is between the W3C… Read More

The Latest Innovations in Inclusive Technologies

Posted on:

I had the pleasure of attending my first M-Enabling Summit in Washington, DC earlier this week. The Summit aims to set a unique stage for identifying emerging opportunities, technological developments, and future innovations for accessible and assistive mobile applications and services. The Opening Session and Keynote at this year’s M-Enabling Summit focused on many fascinating technologies and new developing ways to interact with customers and product users. Technologies such as 3D printers, cloud-powered devices, driverless cars and facial, gesture and speech recognition offer new features, capabilities, one-off customizations and interactions that can assist user’s with disabilities. Peter Korn, Accessibility Architect with Amazon Lab126,… Read More

Infinite Scrolling – Impact on Accessibility Series: #1 Common Issues

Posted on:

This blog is the first of three in the “Infinite Scrolling- Impact on Accessibility” series.   Before examining the common issues, it is important to know the definition of infinite scrolling and the Section 508 and WCAG 2.0 standards that may impact users. Definition and Standards Infinite scrolling is a design practice in which content on the page continually load as a user navigates down the page or screen- eradicating the need for pagination.  Authors must take the following Section 508 and WCAG 2.0 standards in consideration when applying such technique into their application. Section 508 1194.22(l)“When pages utilize scripting languages… Read More

Indicating Link Purpose with ARIA

Posted on:

An Analysis on Different Screen Reader Behaviors Authors must avoid using the same text for links that retrieve different resources. Users without disabilities may be able to identify the links differently based on other page content; however, users with cognitive disabilities and users who are blind or visually impaired may have difficulty making the distinction when link text does not adequately describe each link’s purpose. For example, across a site, you have several links that direct users to view more information on a particular section, such as Read Review for a particular project. When there are multiple links of the same text,… Read More

Android 5 Lollipop – Switch Access has Arrived on Android!

Posted on:

There are several accessibility features added with Lollipop – version 5 of the Android platform that is now available on many Android models including the Nexus 5. The new accessibility features include a high contrast option that improves contrast of text, a color inversion view, options for color correction to assist people who are color blind, and switch access.  The addition of switch access builds on the keyboard support provided with Android and is a big step forward. Historically Apple’s iOS had more accessibility features such as Assistive Touch and switch access (iOS 7+) — new additions with Android are… Read More

Considerations for Testing with Speech Recognition Software such as Dragon Naturally Speaking

Posted on:

SSB recommends testing with multiple types of assistive technology (AT) whenever possible. The focus of AT testing is not to verify technical compliance but to understand whether the implementation is accessibility supported and whether the content is functional for people with disabilities. This functional testing optimally includes speech recognition, screen readers, screen magnification, and other accessibility features used by people with disabilities such as color and contrast software, switch control, and devices used by people who are deaf or hard of hearing etc.. Historically some people have focused testing efforts with screen readers only this does not accurately reflect the… Read More

Dragon 13 ARIA Support is Here!

Posted on:

Dragon Naturally Speaking 13 (both premium and professional versions) was release recently and adds support for the Accessible Rich Internet Application (ARIA) specification. Dragon is speech recognition software that allows a user to dictate text as well as control their computer through spoken commands. Dragon 13 tests for this post were performed using Internet Explorer 11 and Firefox 31 (with the Firefox Dragon extension) that is installed when Dragon 13 is run the first time with Firefox. aria-labelledby The aria-labelledby property allows authors to reference page content such as text as the accessible name for a control such as an… Read More

Web Accessibility 101 Video Series: Screen Magnification Challenges – Forms

Posted on:

In this week’s featured video in our Web Accessibility 101 Series, Client Services Director Mike Schutte demonstrates potential challenges for users of screen magnification software when attempting to complete form fields, and offers ideas for developers to improve form accessibility. Be sure to check out SSB’s YouTube Channel for more videos in this series!

Expanding the Use of the aria-haspopup Property

Posted on:

The WAI-ARIA 1.0 Specification adopted by the W3C currently limits use of the aria-haspopup attribute to context menus and sub-level menus. It also states that “a popup is generally presented visually as a group of items that appear to be on top of the main page content”. Elements can trigger other types of pop-ups, including dialogs, windows and tooltips. Arriving at an implementable cross-platform solution can be difficult. This is due, in part, to the different ways in which screen readers announce aria-haspopup=true. This differs by screen reader and by element. For example: On a link or a radio button… Read More

Put yourself on the path to complete accessibility!

Just fill out the form below and we’ll contact you to set up your free consultation with an expert specializing in your industry.

If you need more immediate assistance, please send an email to or call (800) 889-9659. We look forward to helping you!