This website is not accessible.

ISTQB Advanced Test Manager (1)

Theory – you can scroll down if you know it 🙂

Accessibility of mobile and web applications means to enable all internet users, especially the impaired people, to feel, understand, navigate and capable the full usage of the applications. The ability of accessibility testing is extremely important for all web content creators and enables to raise the bar height and enlarge the range of users.

The impairment, so to speak, may be connected with hearing, visual, mental or physical limitations. On the other hand, being an impaired person doesn’t have to mean cyber exclusion. How the modern internet looks like depends on developers’ and testers’ willingness to deal with modern quality requirements.

It may seem that impaired people make just a tiny piece of mobile and web application users – on the contrary – stand the results of research made by Google Inc. since 2005, which prove that there are over one billion impaired users in the world, who use the applications on daily basis. The number may impress, but also shows the scale of the new market, that demands better software quality.

Developers and testers in each mobile or web project should always estimate how much and what kind of accessibility testing is required and how to measure the accessibility testing coverage. Better accessibility means a higher quality level and better user experience, which all brands would like to be associated with.

What does it mean to adopt a website’s content to meet certain needs? At first, developers should focus on good HTML code quality, compatible with helpers – devices and applications – on PCs and smartphones. For example, lack of unique ids stands for a severe bug, that might be discovered with the help of accessibility testing.

Basic principles

Here is the set of basic principles of creating applications that meet the accessibility requirements.

When creating applications that meet the unique needs of users, special attention should be paid to the implementation of user interface elements, such as:


People affected by visual impairment, that prevent the correct perception of colors, may be excluded from the audience of applications if they can not properly distinguish individual elements. This can be verified by using specific screen filters (eg from – compatible with Windows, Mac, and Linux), that mimic certain dysfunctions.

– icons

Their size and simplicity are particularly important to people with motoric impairment or with cognitive difficulties.

– the ability to change the resolution of the displayed elements

– ease of use and installation of the application

and backend elements:

– volume control

– adaptation to speech assistants, e.g. VoiceOver (iOS) or TalkBack (Android)

– appropriate structure of the application HTML code

so as to enable communication between our application and speech assistant software for the blind.

– the ability to use audio descriptions.

Practically, accessibility testing means to meet all of the above and increase the number of usability tests. However, the case is not to fulfill subjective aesthetic feelings in relation to a given application, but to conduct certain test suites, designed for particular user groups. The spectrum of the tester’s capabilities is basically unlimited – creativity is the key. It is also necessary to imagine yourself as a person with a specific need, and consequently to select a set of tests aimed at in-depth testing of a narrow area of ​​applications, e.g. selected elements of the graphical interface. It should also be noted that while in the core layer and the relevant quality requirements are simple – the code itself has to be thought out, readable and adapted to work with various types of helpers. Developing a test suite requires a lot of ingenuity and empathy from the tester.

A properly working application available for people with disabilities should always ensure:

– easy installation,

– navigating without the help of sight,

– the ability to use the application with simple gestures,

– clear feedback to the user.

Creating mobile applications and websites that will work with helpers – that support people with disabilities – is not only a correct implementation of basic functionalities but also the ability to replace or enrich specific actions in the application with others. For example – by adding vibrations each time you touch an active element, enlarge the font or highlight parts of the image for the visually impaired people. Testing of such applications should check whether:

– it is possible to navigate without using a touchscreen,

– audio description is available for every visible element,

– there are application areas devoid of audio descriptions,

– all elements to which you can click have at least 48 dp (9 mm) in length and width,

– all voice elements have an additional mechanism to support users with hearing impairments.

Both – developers of speech assistants and application developers – eventually experience the same challenge. Working on sufficient such solutions is to keep the consistency and availability of applications without losing the features of a modern product. Each new design should be supported by both parties.


You had one job.

Do you remember a friend of mine – about whom I was talking during UK Star? She cannot see. On the other hand, she would like to stay active and simply work.
She takes various jobs, when she has such opportunity and usually she actively looks for it.

Let’s focus on this particular case.

Last week this friend of mine called us saying, that she has found a new job opportunity, but the website she is supposed to enter is not fully accessible for her. She was simply asking for help. What is more, she was confused, because the job description was quite clear.

There is an application which gathers various voice recordings. The purpose of the job is supposed to be transferring those recordings into written words. Transfer them into text.
My friend uses a computer and keyboard on daily basis, so it seemed to be suitable work for her.

The problem was, that for some reason, her voice assistant (Ivona) was not able to access all website elements, so she was not able to go through the application, not mentioning to complete her job, that’s why she asked for help.

So we opened the website…

It turned out that the voice assistant has not been mistaken.


How does it work?

Assuming you have a (Polish) recording that you wish to transcript. You shall go to this website, register yourself, upload the file and the magic happens. When I write magic – I mean a person – as a friend of mine – does the transcript for you.

I shall quote my beloved developer: “This website has been implemented before the Internet era begun or by someone who has never seen the Internet before”.

The main page is even not the worst. It’s getting muuuuuuuuuuuuuuch worse when you log in. In order to perform the translation, you need to use specific keyboard shortcuts, and they are spread all over the keyboard without reasonable order. You can customise the shortcuts later, but at first, when you cannot see, you and your voice assistant have to deal with the existing ones and this task is not easy.

This website doesn’t have responsive web design.

This website doesn’t have accessible HTML code.

This website makes voice assistants completely lost.

I don’t want to say, that companies are forbidden from making ugly websites.
Do whatever you want, BUT when you employ impaired people, just try not to insult them.
Thank you.


This time I’ll leave the judgment and comments for you, guys. Just check the website by yourself if you wish.
I’m speechless.

If you have any cool job offers for people, who cannot see, I have some friends to recommend!


Make IT Accessible

BlackFriday (1)

My name is Kinga Witko and I would like to tell you about accessibility testing, how important it is and about the event that revealed some completely new layers of testing for me.

Accessibility is what we should focus on in all software application – no matter if they are web, mobile or desktop. They should be accessible for everyone, especially for people with certain mental or physical disabilities, because they are not supposed to be limited by the software.

Do you remember – there are over 1 billion people with disabilities in the world, who might be the users of your application – either web or mobile. Basically, it depends on your testing, if they would feel comfortable with these applications or not.

To make my point, I would like to tell you about an event that has really made
a difference for me.

This short story is about discovering new fields of software testing. It is also about a brave woman, who wants to use the software as any other person, but most of the time she can’t. From time to time, she feels excluded, because someone forgets about her needs during development or testing.

About a year ago, when I had a bit of experience as a software tester, especially in
a mobile testing field,  I had a chance to spend some time with a distant relative of mine – a fantastic person. She works from home, using her PC, regardless of her visual impairment, and she uses the different software at her PC with help of Ivona (text-to-speech tool). She also loves to take part in bowling tournaments and is a very active person.
What is so special about her – she also cannot see. I just never realized that she uses
a smartphone as well.
I’ve literally faced by biases.
It was such surprising for me that a person, who cannot see, uses the touchscreen device, rather than old-school Nokia, what is more – not only for talking to people but also as everyone does that. Imagine my surprise, when I saw her using buses timetable app, complaining about how horrible these apps are.

We had a quick chit chat and I said to her –  I don’t want to be rude, but how do you use
a smartphone?
She explained to me that there is an underlying helper, that you have to run on your device – it would be TalkBack on Android and VoiceOver on iOS and it would help you operate and navigate through the applications. She uses also a special application that makes her screen black all the time.

I am a tester, so I took her phone and play around for a while 😀
Believe me, it was a terrible experience. I was constantly getting lost, there were items missing in almost every application I tried. I was cheating, of course, because the screen was visible for me. I was just checking if VoiceOver is doing well or not. At the end of the day, I was disappointed and angry.

It is just not fair that we exclude other people from using the software due to their impairments. There is no label on the applications at Google Play or App Store that “this is the application for people who can see only” or “this is the application for people who don’t have hearing issues”, but in fact THERE IS. There is an invisible label which excludes quite a significant part of our society from the rage of app users.
For me – this is just not fair.

Everyone, no matter of their preferences, age or needs would like to stay social, keep up with friends, receive messages, news or post information on the internet.
Think about it 🙂

We are developers, we are testers, we are UX designers – WE CAN CHANGE IT.
What I want you to do is to go back to your project, run your application on a mobile device, run it on a PC with an assistant of your choice turned on and try to navigate.
Find out how accessible your product is.
How does it feel for the user to act with it?
Feel it.

I believe that this is our responsibility to make it work.

Let’s make it accessible for everyone.


Quick update from one of my readers – Dorota – who wrote about an incredible youtube – Molly Burke. Check Molly’s videos out and have a look at how blind people use technology