Accessibility Testing Tool list

This list is intended for Windows environment but most of these should work on Mac OSX too.

Related reading: Dynomapper’s post on 25 Awesome Accessibility Testing Tools

Global Accessibility Awareness Day (GAAD) – a recap of celebrations in India

Wow, this year’s Global Accessibility Awareness Day (GAAD) was bigger than ever before; so it is difficult for me to write full recap in one post; hence this post focuses on what has happened in India and next post will talk about events around the world.

My day started off with event at PayPal India. It’s great to have spoken at an office that I worked earlier. It’s amazing to see some of the initiatives that I have started at PayPal India like Accessibility session for new hires, Accessibility Showcase are continued. Phani, Director of Payment products welcomed the gathering; he has done a good research on accessibility for his talk. Then I spoke about Accessibility of Digital Payments. Then Nawaz Khan of PayPal spoke about JavaScript and Accessibility of other frameworks. Post that Prakash of PayPal has spoken about design for accessibility. Whole event was amazingly moderated by my good friend Shalini Subramanian of PayPal. It was great to meet a lot of old colleagues. Appreciciate PayPal for taking the momentum forward.

Then we have proceeded to NIMHANS Convention Centre to participate in Global Accessibility Awareness day hosted by Prakat Solutions, CIS and Mitra Jyothi sponsored by Informatica and a few others. Event started off with a developer workshop by Nawaz Khan of PayPal, followed by panel discussion around impact of accessible websites and apps, how organizations can play a role. Event has also seen a few cultural events, stories of people as how accessibility and technology ha played a role, event has concluded with a presentation from Sean Murphy on Accessibility at Cisco.

Other events took place in India were Aubergine Solutions Pvt Ltd of Ahmadabad has hosted a workshop on Basics of Web Accessibility. Deque India has hosted a GAAD event at Hyderabad in partnership with NASSCOM Foundation. Radio Udaan has hosted a panel discussion on accessibility that talked about not only digital things but also other areas. BarrierBreak has released a CSS Accessibility Checker.

Here is my playlist of Global Accessibility Awareness Day. If you know of any videos of GAAD, do bring it to my attention and I’ll add them to my playlist.

Accessibility of Digital Payments

This is a presentation have done on the eve of Global Accessibility Awareness Day at PayPal on 18th May 2017.

Slides

Full Text

Full text is work in progress and will be available soon. Apologies – just in midst of too many happenings, couldn’t write full text on time as I usually do.

Photos

Srinivasu speaking at PayPal about Accessibility of Digital Payments on Global Accessibility Awareness Day

Read Tweets about GAAD event at PayPal

WAI – ARIA Landmark navigation extension

Web Accessibility Initiative (WAI) of W3C, a few years ago, introduced landmark roles (also known as landmarks”) for easy navigation of web page. An introduction to ARIA landmark roles:

The purpose of this technique is to provide programmatic access to sections of a web page. Landmark roles (or “landmarks”) programmatically identify sections of a page. Landmarks help assistive technology (AT) users orient themselves to a page and help them navigate easily to various sections of a page.

They also provide an easy way for users of assistive technology to skip over blocks of content that are repeated on multiple pages and notify them of programmatic structure of a page. For instance, if there is a common navigation menu found on every page, landmark roles (or “landmarks”) can be used to skip over it and navigate from section to section. This will save assistive technology users and keyboard users the trouble and time of tabbing through a large amount of content to find what they are really after, much like a traditional “skip links” mechanism. (Refer to User Agent Notes above for specifics of AT support). A blind user who may be familiar with a news site’s menu, and is only interested in getting to the top story could easily navigate to the “main” landmark, and bypass dozens of menu links. In another circumstance, a user who is blind may want to quickly find a navigation menu, and can do so by jumping to the navigation landmark.

If you are a screen reader user, it’s rather easy to use landmarks using keyboard commands provided by screen reader. But what if you are not a screen reader user? Recent post by Matthew Atkinson of The Paciello Group titled Improving access to landmark navigation has introduced a browser extension that works greatly for non-screen reader users to benefit from landmarks on any web page and browse the page in an easy way. I have installed on Firefox and experience is pretty smooth. All user needs to do is load a web page of choice and click on Landmark navigation extension; displays list of available landmarks as shown in below image.

Screenshot of landmarks showing on ServeOM Inclusion Home page
Screenshot of ServeOM Inclusion home page showing available landmarks using Landmark Navigation extension on Firefox
.

Download and install the landmark navigation extension for Firefox, Chrome and/or Opera to tryout yourself.

Wish to know what are the ARIA landmark roles? Read Landmark roles section on WAI-ARIA spec

Tips for developers: Get your website teted for accessibility – Part 2 – Operable

This is Part 2 of 4 parts on how a developer should get their website or application tested for accessibility. Objective of this series is to provide easy method of accessibility testing to developers so that they can test as they code. This is how we would achive accessibility right at the development and design stage. These tips would not only be helpful to developers but also to interaction designers who decides interaction of elements and those who develop prototypes. This Part 2 is related to Operable section of Web Content Accessibility Guidelines 2.1.

Question: How to test for keyboard accessibility?
Answer: Load the page. Press CTRL + Home (Windows), this will take focus to the top of the page. Then use tab key to move from one element to another. Use enter or space key to activate an element. One should be able to activity every element including menus, modals, buttons etc.,

Question: When I was browsing a page with keyboard, focus does not move from an element, focus just gets stuck; is there a problem with my keyboard?
Answer: Probably not, this is called keyboard trap and needs to be avoided. When a component recieves keyboard focus, there should be mechanism to move away keyboard focus from same component.

Question: What to consider when there is a time limit for a page?
Answer: Check if there is an option to turn-off timing, adjust as per user’s requirement or extend the time limit. There could exceptions such as activity at real-time, esential time limit such as a test and time limit of 20 hours and more.

Question: What to look for elements that moves, blinks or scroll?
Answer: There should be a mechanism to pause, stop or hide. If content is being updated automatically, there should be a mechanism to pause or set how periodical that an update should happen.

Question: What is bypass blocks and how do we test?
Answer: Bypass blocks is a mechanism to enable keyboard users to skip representative set of blocks such as navigation and jump quickly to main content. This can be achieved by providing “Skip to main content” link at the top, using appropriate heading structure and/or using ARIA land marks.

Question: How to test page titles?
Answer: Look at top bar of browser window and see if page title does exist and is appropriate. For example Page title should be page name along with the company / domain name. It should not be just company name only on all the pages.

Question: What all needs to be considered as Focus order issues?
Answer: Ensure that the tab order is logical, if an element opens a modal, focus focus must be set to modal and must not move out until user closes the modal, When modal is closed, focus should be returned to the triggered element.

Question: Testing for link purpose
Answer: Ensure that all links have meaningful and spell out the context to the users. Avoid links like “Read more”, “Click here” etc., Using automated tools would be effective to test this requirement.

Question: What are the multiple ways required for a website?
Answer: A search functionality or a site map. There should be more than one way to reach a specific page on the website.

Question: How to test for focus visible?
Answer: When you tab through the page, every element should receive an indicator and you should be able to see where the keyboard focus is. It can be either custom focus indicator or browser’s default focus indicator.