iOS Updating Content

This post was co-authored by Chris McMeeking and Jennifer Dailey. Updating Content consists of elements that constantly change, such as clocks and scrolling advertisements. Unlike dynamic elements that only change through user action, items that constantly change should not have every update recognized by VoiceOver. Implementing updating content in this way will make the app more difficult to navigate and use for VoiceOver users. However,… Continue Reading iOS Updating Content

Accessible Tabbed Navigation in Android

This post was co-authored by Chris McMeeking and Melinda Kothbauer. TabWidgets are a tool that can add great functionality to your mobile Android apps; however, they are inaccessible by default. WCAG 4.1.2 describes the need for all user interface components to have a name, role, and value to ensure that assistive technology users have the necessary information to navigate screens effectively. This is especially true… Continue Reading Accessible Tabbed Navigation in Android

What iOS Traits Actually Do

This post was co-authored by Chris McMeeking and Alistair Barrell. Accessibility Traits Accessibility Traits are yet another useful and important feature in the realm of iOS Accessibility. An Accessibility Trait allows you to choose the best description for what an element in your application does.  It is important to set up these traits properly so that a user does not get confused when clicking on… Continue Reading What iOS Traits Actually Do

Accessible Text Input in Android

This post was co-authored by Chris McMeeking and Melinda Kothbauer. The default text entry field in Android is the EditText object. EditText objects are difficult because the common practices for making Android UI elements accessible (content descriptions), do not work. Android provides the framework to make EditText objects accessible, but it is important to know what, when, and how to use the built-in tools. In… Continue Reading Accessible Text Input in Android