Mobile Accessibility Testing

This is the post excerpt.


The Smart Phone accessibility testing can be divided into two parts.

  • Unit Testing
  • Heuristic Testing

The Unit testing can be performed while developing the accessible code. there are a lot of integration test tools available on GitHub. The unit test considers easier than heuristic testing because you can look into the code and check WAI Aria roles and properties by manual and automatic testing tools. Normally, accessibility has been done after designing and coding and point out by accessibility consultant and QA testers. it is important to bring accessibility testing into a design process so tester can run continuous integration that helps the organization to reduce cost. The best practice is to run all test daily to make sure that project accessibility is not compromised.

Android Analyzer is the best example of for unit tester. The Pre built-in analyzer helps the developer and tester to test accessibility while developing the Andriod application.  This tool has built-in rules set to develop a mobile application with WCAG 2.0 standards(which is obvious, not complete accessibility solutions). but this analyzer allows testers to run in accordance with any filter being applied, such as by standard guidelines failure and warn and generate a notification for accessibility violations.

Accessibility testing or you can say, accessibility in mind while starting any project by testing by the user with disabilities is must in this Agile era. Sometimes individual components are accessible, but when they are put together into a process accessibility issues can arise.

But on the other hand, heuristic testing is difficult because it needs manual testing while testing the interface with AT(Assistive Technology) like Screen Readers, Zoom, Stylus etc.

Most of the  Heuristic testing, Depends on the personas based approach because real user testing is expensive and time-consuming. ios-accessibility-features-800x466

The Most Likely Accessibility Issues

Lately, I have been working on accessibility report on Krisrtania  University College  a small school in Norway as compare to giant schools like University of Oslo and Norwegian University of Science and Technology (NTNU).   I came across the very basic accessibility issues on their website like images with no alternative text. The Alternative consider the basic of the web page accessibility.

The institution nowadays give extra attention to the accessibility but due to lack of findings they lost a potential talent who cannot access their website due to inaccessible content. to implement 100% accessibility is hard but not impossible small initiative and responsibilities for accessible content give you a brilliant student but it depends on institution priorities, either they spend too much money on social media advert ism or   make their website accessible.

how you can ignore the user with visual disabilities. it is  testing like you are running a website without any alternative text.or leave the alternative text null which shows that image is less important or put the alternative text which has not appropriate meaning of  the picture. there is very good article about the alternative text on the images with a flow chart to which what kind of alternative text required for the images on the websites. The Most common accessibility issues faced by sight user who struggle with low vision or no vision to interact with image links. The images which direct a user to another page or content. the alternative text helps users is this information the user required on the page?

The image below shows the violation that their is no accessible code for screen reader to chat with corresponding agent to get any important information.


Why Landmarks are essential for Websites?

I’ve been working for The Web Accessibility Audit for the last six months. During this period, I came across many web pages which are designed with supposedly no accessibility in mind. I’ve used many automatic tools to analyze and examine accessibility violations. Those automatic testing tools only highlight the violations and manual checks. If the developer works on violation part then work increase for the auditor too, because either the violation goes unnoticed or drops into manual check. Lately, I audited a website on a sub-contract work for my UK based client. Below is a glimpse of the results before and after the design was made accessible. The following chart shows violation before testing:

Before Report

After I optimized the code with WCAG 2.0 SC level AA guidelines, the summary looks somewhat like this:

after report

It begs the question that how this affected the web page’s visualization? Well, presumably nothing for the normal user since they don’t know how accessibility can matter to others!page

For screen readers, this page is now a fun place where they can access each and every inch of the web page without losing information. That’s because the page is now equipped with WAI-Aria roles.

landmark1The Video demonstrate how WAI-Aria helps screen reader user to access web page easily.

Open Source Tools for A11y so far….

Automatic testing is essential to start accessibility auditing for any website. its helps to quick scan accessibility bugs in seconds from 1000 of pages website. The automatic also called high tech testing are effective and efficient which points the MC (Manual Checking)  where automatic testing fails or unreliable.

There are many automatic testing tools available on the internet, but Functional Accessibility Evaluator (FAE) 2.0 provides both website summary and page level details.


Accessibility Testing Ruter Applicaion

Ruter is very famous transport application in Oslo. Around 350,000 individuals use this services daily to find a bus, train and boat timings to reached their destinations daily.  but when its comes to Accessibility this services lacks with ISO, EU and WCAG standards. some are highlighted below.

There are many immigrants and visitors used this application with default language “English” for this app.but still some important message like delayed, suspend or construction work in progress notification shows in Norwegian which frustrates user to find accurate information about their Journey.

Language Barrier

Language barrier

like in the example above the language the bus changes its route. its create a social barrier to the end user to learn basic Norwegian to utilise this application. In some scenarios when a passenger is in hurry have no time to translate this notification with AT’s(Assistive Technology).

These Application violets too many WCAG rules like keyboard controls to colour contrast and no alternative text for ATs. we can further highlight these issue in next posts.