Blog

Archive for the "ARIA" Topic

ARIA Widget Checklist: For Screen Reader Testing

Posted on:

Introduction One of the most significant challenges with ARIA support is determining support level differences between assistive technology and browser combinations, and doing so in a structured manner so that bugs can be accurately and reliably submitted to AT venders so that these support levels can steadily increase equally. However there are still significant discrepancies between valid ARIA usage and what is supported between specific screen readers and browser combinations, so there is immense benefit for such screen reader venders to get on the same page and test these assistive technologies more thoroughly and to also involve the public for… Read More

Differences between ARIA 1.0 and 1.1: Changes to role=”combobox”

Posted on:

Welcome to the fourth and final installment of SSB’s review of the differences between ARIA 1.0 and 1.1. In our last post –Differences between ARIA 1.0 and 1.1: Changes – we reviewed changes to existing attributes such as aria-haspopup, aria-activedescendant, role=”form”, amongst others. Today, we explore the changes to role=”combobox”. The most recent Candidate Recommendation of the Accessible Rich Internet Applications (WAI-ARIA) specification was published on October 27, 2016. You can view the full document on the W3 website. It’s important to note that this document is still subject to change with future publications, and that these observations are meant to provide… Read More

Differences between ARIA 1.0 and 1.1: Changes

Posted on:

Welcome to the third installment of SSB’s four-part review of the differences between ARIA 1.0 and 1.1. In the last post – Differences between ARIA 1.0 and 1.1: Additions to “role” – we explored the additions to “role”.  Today, we review the changes that were made to various attributes. The most recent version of the Accessible Rich Internet Applications (WAI-ARIA) guidelines was published on October 27, 2016. You can view the full document on the W3 website. Changes aria-owns The aria-owns attribute can be used to change the order of the accessibility tree, which is important when the DOM element structure… Read More

Differences between ARIA 1.0 and 1.1: Additions to “role”

Posted on:

Welcome to the second installment of SSB’s four-part review of the differences between ARIA 1.0 and 1.1. In the last post – Differences between ARIA 1.0 and 1.1: Deprecations & Additions – we reviewed deprecations and additions like aria-keyshortcuts, aria-roledescription, and aria-current. Today, we explore the additions to “role”. The most recent Candidate Recommendation of the Accessible Rich Internet Applications (WAI-ARIA) specification was published on October 27, 2016. You can view the full document on the W3 website. It’s important to note that this document is still subject to change with future publications, and that these observations are meant to provide a… Read More

Differences between ARIA 1.0 and 1.1: Deprecations & Additions

Posted on:

The most recent version of the Accessible Rich Internet Applications (WAI-ARIA) guidelines was published on October 27, 2016. You can view the full document on the W3 website. It’s important to note that this document is still subject to change with future publications, and that these observations are meant to provide a high-level overview of broad-level changes that will be important to be aware of going forward. As such, these details are likely to remain valid regardless. Also, many of these additions are minimally supported or not supported at all by browsers and assistive technologies as yet. I’ll be posting… Read More

Accessibility Considerations for Localization

Posted on:

Localization is the process of translating a product into different languages or adapting a product for a specific country or region.   When localization is performed on web content, information such as alternatives used by people with disabilities may inadvertently be overlooked.  When pages are localized, language teams often update strings of content and view the visual changes on the web page.  Some accessibility information is not visible on a web page but still must be localized, e.g. alternative text for images and text positioned off-screen for screen readers. Localization teams need procedures and tools to help them find this accessibility… 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

Mobile Browser Support for ARIA Roles, States, and Properties

Posted on:

Last month I had the pleasure of attending and speaking at the 1st Annual IAAP Access 2015 Conference, including a session I presented on the current state of mobile browser support for ARIA.  After the session a number of people asked me to share the test results and related content which I am outlining in this post. What Was Tested? Thirty different ARIA roles (landmarks and widgets) with key aria properties (e.g. aria-expanded, aria-checked, etc.) were tested with: VoiceOver on iOS 9.1, 8.4.1, and 8.1.3 Talkback 3.6.03/4.31 on Android 5.0.2/6.0 Firefox 36.0/41.0.2 Chrome 40.0.22/46.0.24… Windows Phone 8.1 IE browser (WP8.1) /Windows 10… Read More

Creating an Accessible ARIA Tree Control

Posted on:

Overview A few weeks back I set myself the goal of digging back into the current ARIA implementations and specifications to keep some of my coding and development skills sharp.  My general approach to such things is to setup little programming exercises for myself that I then have to complete.  Classically this is like “make a TODO list.”  In this case I went for:  “build out an HTML element tree that has some reasonable semblance of native operating system tree functionality.”   Thus started the journey to building out a well-structured, decomped, ARIA enabled HTML tree. Before I go any further,… Read More

Release of the Windows 10 Edge Browser – What it Means for Accessibility and ARIA Support in IE

Posted on:

As the launch date for Windows 10 comes closer, so does the release of a new web browser. Previously code named Spartan, this new browser has officially been branded by Microsoft as Edge. Part of what this entails is the deprecation of Internet Explorer. As a bit of history, Internet Explorer (IE) was developed and first released in the mi 90’s, approximately twenty years ago. This was at the same time when Accessibility APIs were in development, and still had a long way to go before reaching what we know and use today. Also, this was before ARIA was officially… 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 info@ssbbartgroup.com or call (800) 889-9659. We look forward to helping you!