Chapter 12: Identifying Input Purpose

While filling the form elements on mobile screens labels and instructions help the users identify the purpose of the form. On a mobile it is not sufficient. If the user need to type in an address field, the content required to be typed in with address line 1, address line 2, selecting state or country […]

Chapter 13: Touch Target

Touch target is the area in which the user can effectively tap to invoke an action. If the size of the touch target is not sufficient different user groups may find it difficult to tap on a specific element of the screen. A low vision user may not be able to point their finger on […]

Chapter 14: Text Resize

Users may want to increase the font size on the app screens for better readability. Except for the captions and text on images, users should be able to resize the text up to 200% without loss of content or functionality and without the use of assistive technologies. Both Android and IOS provides means for the […]

Chapter 15: Orientation

The content displayed on the screen should be confined to a specific orientation of the screen. Users may want to restrict the orientation of their device either to portrait or landscape due to various reasons. If the user decides to restrict the orientation of their device say to portrait, the content that is displayed only […]

Chapter 16: Screen Language

Every app need a default language. Due to the effect of localization, we may not expect that every app developed will be in English. For the user agents and assistive technologies to render the right content, ensure that the language is set for the project. Sometimes the default will be set and the developers have […]

Chapter17 : Screen Titles

The title of the screen speaks what activity or the content it contains. Providing a title with the content that describes the content or activity it holds improves the accessibility of the app. How to provide a title ..IOS The title on the IOS screen can be provided with the UI navigationbar object. Typically the […]

Chapter 18: Notification & Status Messages

When notifications or status messages are part of your app, first check for the following. Does these messages auto disappear? Can the accessibility service able to identify and announce the message when it is displayed? Are these notifications or messages consistently displayed in the same location on the screen each time they are displayed? Depending […]

Chapter 19: Web View

So far we are talking about the native apps. A part from native, mobile apps may be web or hybrid. In many cases inside a native screen a web page has to be loaded. More like code once and use multiple times. Common web pages such as privacy policy, terms and conditions are loaded on […]

Chapter 20: Miscellaneous

Magic tap Gesture (IOS) Magic Tap is two finger double tap. This is used to perform most common actions on the app. For example, Answer or hang up on phone app, play or pause in music app etc. Use the accessibilityPerformMagicTap method to handle the Magic Tap gesture. You might use this gesture to trigger […]

Chapter 21 : Unit Testing

Before the code is shared with the QA team for accessibility audit, developers can have a quick look for any potential accessibility bugs. Let us now see how can the app developers do an unit test before the handover. IOS It is always good to test the app with the built in accessibility features such […]

Contact Us

Maxability Pvt Ltd Flat 360,
Block D2 SLS Signature Appartments,
Kaverappa Layout, Kadubeesanahalli,
Bangalore - 560103.

914 823 3361