A quick accessibility review: Swiggy iOS App

Swiggy is an online portal using which one can order food from restaurants around and food will be delivered through their executive. When Madhu Singhal, Founder of Mitra Jyothi told me that she needs to use Swiggy but its app on iOS is not accessible using VoiceOver that prompted me do a quick accessibility review of Swiggy. Some of the observations are:

  • Bottom navigation tabs have no problem. works well with VoiceOver
  • Home button (at the top), area selector widget, favorites button do not have an accessible name
  • When swiping using gestures, offers widget is not accessible
  • Able to Select and open a restaurant
  • Able to read through the menu options
  • Buttons provided to add / remove an item from the menu list does not have label
  • Cart is completely inaccessible
  • Call button does not have accessible name

Though user is able to make a choice of options in mind, it just stops there and noway they can proceed with adding them to card and place an order.

Do refer to Mobile Accessibility Practices page to learn about building accessible mobile applications.

Schedule a call to get started with Digital Accessibility

Now-a-days, there is a positive momentum about accessibility and businesses would want to make their products accessible. But challenge for many is that they do not know where to start and how to go about.

To mark 6th edition of Global Accessibility Awareness Day, I have decided to spend sometime with people who would like to know about accessibility and start their journey into building accessible products. Through this month, one can schedule a call with me for 30 minutes to discuss brief about accessibility and how they can get started.

Once call is scheduled all you need to do is call on the provided number at the time that you have opted. In case I could not answer your call, I apologize in advance and I shall call you back at the earliest possible.

Should you have problem in scheduling, do Send me an email

Link again: Schedule a call

Global Accessibility Awareness Day 2017 – Let’s raise awareness about accessibility

6th edition of Global Accessibility Awareness Day will be observed on 18th May, 2017. As always, this is one such event that success of the event does not get measured by it’s size or format but by impact that event could create. Thanks to Prakat Solutions Inc.,, here is a quick video of my opening remarks about Global Accessibility Awareness Day that I spoke last year.

Some of the topics that could touch upon to raise awareness about are:

There are several events being planned. If you are hosting an event, do comment here with link to your event page.

Good luck,

Tip for Developers: Get your website tested for accessibility -Part 1 Perceivable

Quite often, I receive emails from non-profit organizations asking if I can help them with accessibility testing for their newly built website. I also see most of them do not get built accessibility in mind though many of them are for organizations who offer services to people with disabilities. This post illustrate a few tips that developers can use while building a website. While we intend to see many developers have knowledge on accessibility, it’s absolutely fine to start with a willingness to build an accessible product. This post illustrates advice in the form of question and answer in reference to Web Content Accessibility Guidelines (WCAG) 2.1. This will be series of four articles to cover Perceivable, Operable, Understandable and Robust.

Question: Do you have images or any other non-text content?
Answer: When you have images, identify if they are informative images decorative images. If informative images, provide an alternate text. For decorative images, provide empty alt text i.e. alt=””; alt attribute must be present in any form of image; if not provided, path of the image gets exposed to assistive technologies such as screen reader, shown on text only browsers (or when images are turned off in the browser), shown to search engines.

Question: Do you have audio-only conent on the website?
Answer: Provide synchronized captions or text transcript

Do you have video only content?
Answer: Provide audio-description

Do you have a live audio / video event happening?
Answer: Ensure there is voice over when only visual actions are happening and captions are provided for audio. This will aid visually impaired users to know what’s visual actions are happening and hearing impaired users to know what the conversation is happening. If there is only music being played, show captions as “Music being played” and if possible what instrument is being played and some illustration.

Question: How my content should be structured and organized?
Answer: Ensure content is structured in a logical order, Headings are marked up appropriately using Hx values e.g. h1, h2 etc., Do not just decorate content as a heading, mark-up list items as ordered or unordered list, ensure all form fields do have associated labels using “for” and “id” attributes, radio buttons and check boxes have associated with their group label.

Question: My user tells me that my content is not read in right sequence, what could be wrong?
Answer: When content is presented in a sequence that is different than usual, it’s essential to ensure sequence of content is meaningful programmatically.

Question: Can I color code the information?
Answer: Yes, color can be used to convey information but color must not be the only form of presenting information. Example, accept is marked as “green” button and decline is marked as “red button”, same labels i.e. accept / decline must be provided as a text in addition to color code.

Question: Can I play audio or music automatically on my web page?
Answer: It’s a not a good practice to play audio automatically on a web page; reason being it would disrupt users with screen readers and people who do not expect an audio on loading of a web page. However, if audio has to played automatically and length is more than 3 seconds, controls must be provided to pause or stop the audio.

Question: How can I check for contrast of colors?
Answer: Simple way is to use Color Contrast Analyzer tools. See the list on Accessibility Testing tools section of Our Resources page

Question: How to meet resize text requirement?
Answer: User browser’s default zoom option (mostly CTRL and +) and zoom up to 200%

Question: Can I use images of text?
Answer: Where possible, it’s advisable to use text to convey the information rather than embedding onto an image.

Question: What’s graphics contrast?
Answer: It’s a new Success Criterion – 1.4.12 Graphics Contrast of WCAG 2.1. If information is conveyed only in the form of graphic e.g. charts etc., it must have minimum contrast ratio of 4.5:1.

Accessibility Conformance Testing (ACT) Rules Format 1.0 First Public Working Draft is now available

Accessibility Testing is critical for ensuring accessibility of any product. Similar to any other testing e.g. performance, functional etc., quality is an essential component for accessibility testing too!

Accessibility Guidelines Working Group has published First Public Working Draft of Accessibility Conformance Testing (ACT) Rules Format 1.0 and accepting comments and feedback by 5th May, 2017.

As the size and complexity of web development is growing, it’s essential to have adequate tools to automate accessibility testing. To make rules universal, there needs a standard specification. That is what ACT Rules format aims to address.

About the ACT framework

There are currently many products available which aid their users in testing web content for conformance to accessibility standards such as WCAG 2.0. As the web develops and grows in both size and complexity, these tools are essential for managing the accessibility of resources available on the web.

This format is intended to provide a consistent interpretation of how to test for accessibility requirements so as to avoid conflicting results of accessibility tests. It is intended for both manual accessibility tests as well as for automated testing done through accessibility test tools (ATTs).

Describing how to test certain accessibility requirements will result in accessibility tests that are transparent with test results that are reproducible. The Accessibility Conformance Testing Rules Format (ACT Rules Format) defines the requirements of these test descriptions, known as Accessibility Conformance Testing Rules (ACT Rules).

The spec consist of Scope of the specification, ACT rule structure that talks about rule outline, rule description, accessibility requirements, Limitations, assumptions and exceptions, accessibility support; Test subject types, ACT test procedures, ACT data format and Rule Quality Assurance.

Do read through ACT rule format draft and File a issue on github if you have some feedback. Comments that the working group is looking for is about:

  • Does the ACT Rules Format address all the topics that are critical to rule design?
  • Does the section on accessibility support adequately address the topic?
  • Does the section on Accuracy Benchmarking adequately address the topic?
  • Are there improvements to better support developers of test rules to transpose their rules and adopt this format?

As a reminder, last date to submit the feedback is 5th May, 2017.