5min read

Short Guide to Quick Accessibility User Testing. Part 2

In the last two posts of the series we have discussed the importance of user testing and the arguments in favor that you can use while advocating for the study. You can read more about it in the introductory article. Part 1 of user testing guide shed some light on organizing user testing session based on Polidea’s project with Papereed. Our aim was to create an accessible iOS app and test it with users suffering from vision impairment. Part 2 offers examples of questions, hints and observations that you may find useful in your work.

Follow the structure of an interview

Be ready to prepare the detailed plan of your interview and conduct it step-by-step later on. The following example may be of some inspiration:

Introduce yourself and discuss the logistics, answering the basic questions such as:

  • Who are we?
  • Why are we here and what is the goal of today’s meeting?
  • Where are we?
  • Who is involved?
  • What will be our roles?

Tip: It is important to highlight the main idea of user testing, meaning: gathering feedback. There are no bad answers!

Introduce the setting and people involved

It may sound like this:

“There are 3 of us here in the observation room. While we will be talking, Agnieszka will take notes and observe your performance. There is a one-way mirror in the room. At its other side sits Przemek who is ready to help us with tech issues in case somethings goes wrong.”

Tip: Show that you’re in the same team with participants and not the the designs you’re testing

It is definitely more challenging to form a rapport with visually impaired or blind users during such testing session. They should be informed as far as the number of people in the room is concerned. Imagine that you are their eyes now—you are responsible for providing them with all the information they need. Also, remember not to involve too many people—it is always more comfortable in a smaller group.

Then come the following questions:

  • What will you be asked to do for us?
  • How long will the testing session take?
  • Are we going to record it? Do we plan to share the material in the future?

While providing the answers try to be as precise and clear as possible. Creating an atmosphere of comfort and mutual understanding is crucial.

Present the product

Be prepared to provide users with a quick intro about the main concept, clarifying the general idea of the product.

Present participants

Prepare the list of some basic questions concerning: occupation, technology literacy, applications used, the type of phone, the period of using iPhone, certain features you want to focus on (in our case, we wanted to explore accessibility features) and apps the users find useful on a daily basis.

Follow the scenarios

Start by asking participants to perform concrete actions. Try not to refer to them as “tasks” on purpose as they are not something you can success or fail in. Scenarios should have clear focus points: things you are interested in and elements that you feel can be challenging for the users.

While observing test users’ performance, remind them to think aloud. Take notes if the key tasks were completed or turned out challenging. Analyze what could be the reason behind: maybe you should have provided them with a hint? Encourage them to share their ideas that could improve the overall experience. Ask the follow-up questions to investigate the problematic areas. They may be inspired by the following list:

  • Who told you about this?
  • What made you click that?
  • Why did you decide to go to the next screen?
  • Where did you hear that?
  • How would you change the app’s options?

Find some time for extra questions

If there’s some time left, take this opportunity to ask some extra questions about app usage.

Example: Did you enjoy using the application? Is it similar to the type of apps you use on a daily basis? What is the first thing that comes to your mind after using it?

Prepare short summary

Remember to thank all the participants for their time and help. Specify the follow-up procedures (for e.g with payment). Ask if they have any questions.


See how to engage users
with flawless UX/UI in our free
product design guide!

During the interview—10 things to remember

  • Ask open and follow-up questions (5W1H: Who, What, Where, When, Why, How), answer questions with questions: “What does this button do? What do you think it does?”
  • Ask test participants to continuously think out loud and comment as they move through the interface. They should share everything with you: their doubts, the way they come to the right solution, their impressions and feelings and the things they don’t understand.
  • Watch the body language, facial expression and tone of voice (yours and theirs).
  • Don’t be afraid of silence and pauses (people need some time to think)
  • Always pretend that you don’t know the correct answer: get the test users to educate you even if you already know something
  • Be careful not to influence answers with your opinion or personal experience!
  • Write down quotes whenever possible
  • Gather answers to all the focus points while taking notes (you should have them properly defined before)
  • Do your best to make the participants feel comfortable. Respect their private space, avoid intense eye contact and “expert” attitude.
  • Show that you’re on the same team with participants and not the the designs you’re testing

After the interview—synthesize and share

Keep the momentum going and write concise report or prepare visual presentation with the recommended solutions straight after the testing—with fresh memory and energy to share all the insights.

The report structure should be simple. Just tell (write down):

  • What you did
  • What you heard
  • What are the design recommendations
  • What you suggest to do next

It is not about writing an extensive material. Summarize the most important insights you discovered and prepare short, but strong argumentation based of what users did and said. Such material works best in improving the product.

Give recommendations!

Think about the things that can be implemented straight away to improve the product. Share all the insights from the study with team members and make them feel close to the participants. Explain clearly why it is important to make some changes and start from easy, but effective tasks. Quick and visible effects that really improve the usability of the app will encourage everyone to continue.

Good luck!


MagdaUI Designer


Sign in and expect sharp insights, recommendations, ebooks and fascinating project stories delivered to your inbox

The controller of the personal data that you are about to provide in the above form will be Polidea sp. z o.o. with its registered office in Warsaw at ul. Przeskok 2, 00-032 Warsaw, KRS number: 0000330954, tel.: 0048 795 536 436, email: (“Polidea”). We will process your personal data based on our legitimate interest and/or your consent. Providing your personal data is not obligatory, but necessary for Polidea to respond to you in relation to your question and/or request. If you gave us consent to call you on the telephone, you may revoke the consent at any time by contacting Polidea via telephone or email. You can find detailed information about the processing of your personal data in relation to the above contact form, including your rights relating to the processing, HERE.

Data controller:

The controller of your personal data is Polidea sp. z o.o. with its registered office in Warsaw at ul. Przeskok 2, 00-032 Warsaw, KRS number: 0000330954, tel.: [0048795536436], email: [] (“Polidea”)

Purpose and legal bases for processing:


Used abbreviations:

GDPR – Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016
on the protection of natural persons with regard to the processing of personal data and on the free movement
of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)

ARES – Polish Act on Rendering Electronic Services dated 18 July 2002

TL – Polish Telecommunications Law dated 16 July 2004

1)        sending to the given email address a newsletter including information on Polidea’s new projects, products, services, organised events and/or general insights from the mobile app business world |art. 6.1 a) GDPR, art. 10.2 ARES and art. 172.1 TL (upon your consent)

Personal data:name, email address

2)       statistical, analytical and reporting purposes |art. 6. 1 f) GDPR (based on legitimate interests pursued by Polidea, consisting in analysing the way our services are used and adjusting them to our clients’ needs, as well as developing new services)

Personal data:name, email address

Withdrawal of consent:

You may withdraw your consent to process your personal data at any time.

Withdrawal of the consent is possible solely in the scope of processing performed based on the consent. Polidea is authorised to process your personal data after you withdraw your consent if it has another legal basis for the processing, for the purposes covered by that legal basis.

Categories of recipients:

Your personal data may be shared with:

1)       authorised employees and/or contractors of Polidea

2)       persons or entities providing particular services to Polidea (accounting, legal, IT, marketing and advertising services) – in the scope required for those persons or entities to provide those services to Polidea


Retention period:

1)       For the purpose of sending newsletter to the given email address – for as long as the relevant consent is not withdrawn

2)       For statistical, analytical and reporting purposes – for as long as the relevant consent is not withdrawn

Your rights:


Used abbreviation:

GDPR – Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016
on the protection of natural persons with regard to the processing of personal data and on the free movement
of such data, and repealing Directive 95/46/EC (General Data Protection Regulation)

According to GDPR, you have the following rights relating to the processing of your personal data, exercised by contacting Polidea via [e-mail, phone].

1)       to access to your personal data (art. 15 GDPR) by requesting sharing and/or sending a copy of all your personal data processed by Polidea

2)       to request rectification of inaccurate personal data
(art. 16 GDPR) by indicating the data requiring rectification

3)       to request erasure of your persona data (art. 17 GDPR); Polidea has the rights to refuse erasing the personal data in specific circumstances provided by law

4)       to request restriction of processing of your personal data (art. 18 GDPR) by indicating the data which should be restricted

5)       to move your personal data (art. 20 GDPR) by requesting preparation and transfer by Polidea of the personal data that you provided to Polidea to you or another controller in a structured, commonly used machine-readable format

6)       to object to processing your personal data conducted based on art. 6.1 e) or f) GDPR, on grounds relating to your particular situation (art. 21 GDPR)

7)       to lodge a complaint with a supervisory authority,
in particular in the EU member state of your habitual residence, place of work or place of the alleged infringement if you consider that the processing
of personal data relating to you infringes the GDPR
(art. 77.1 GDPR)

No obligation to provide data:

Providing your personal data is not obligatory, but necessary for Polidea to provide you the newsletter service

Refusal to provide the above data will result in inability to receive the newsletter service.


In the process of providing the newsletter service, we make decisions in an automated way, including profiling, based on the data you provide.


“Profiling” means automated processing of personal data consisting of the use of your personal data to evaluate certain personal aspects relating to you, in particular to analyze or predict aspects concerning your personal preferences and interests.


The automated decisions are taken based on the analysis of clicked and viewed content. They affect the targeting of specific newsletter content to selected users registered to receive the newsletter service, based on the anticipated interests of the recipient.