Overview of the homepage (Current website)
Pain points (people with visual impairments)
Π‘all the reception
You have to wait a long time for an answer
It is not convenient to choose slots for the appointment
Daily waiting in line
Takes too much time
Colour blindness
The organizations are likely seeking ways to improve efficiency, collaboration, and decision-making within their teams.
Myopia/farsightedness
The organizations are likely seeking ways to improve efficiency, collaboration, and decision-making within their teams.
A visually impaired user
Users who frequently engage in video calls for various purposes, such as sales meetings, client interactions, project updates, and internal discussions.
Search by type is not sufficiently contrastive, especially not the default state of tabs
The text in the modal card "appointment details" is not visible enough + Icon βXβ is too small.
The text according to the colour of the button is not readable enough, it is necessary to check the size of the fonts as well.
Body temperature 38.5 (4th day in a row), runny nose, sore throat.
How to get to an appointment/online consultation with a doctor.
Find out what is the cause of the prolonged temperature, how to speed up the recovery process
Scenario (short version)
π Introductory questions
In what cases do you consult a doctor? How often does this happen?
Please tell me how exactly you make an appointment with a doctor? (type of communication) Describe your recent reception experience.
Please tell us about an negative appointment or doctor's visit.
π Script task
1. Enter the site Helsi.me in the search of your browser
2. Please find the doctor you need to make an appointment on this site
3. Please go to this doctor's page.
4. What is the address of the hospital where the doctor accepts patients?
The main measurement criteria:
User 2 -
Myopia/farsightedness
Success
User 3 -
Blind
Failed
User 1 -
Colour blindness
Success
Session table result
User 2 -
Myopia/farsightedness
Success
The task was completed, however, during the execution of the task, some users needed more time to complete intermediate tasks, since some components were not visible enough. I also noticed some changes in user behavior.
Approaching the monitor on purpose
During testing, some users unconsciously moved their heads closer to the monitor to examine the details.
Scaling web browsers more than 110%
In some cases, users resorted to zooming using the trackpad or zooming in the browser.
A blind user used readers (Voiceover reader) by switching keyboard keys. As a result of the session, the user managed to complete 70% of the tasks using the program's voiceover, but unfortunately, the last important stage was a failure.
User 3 -
Blind
Failed
After choosing the time and date of the appointment , a modal window appears for filling in personal data, unfortunately, front-end part wasn't developed right (semantic part) so the voice reader couldnβt perform its action.
User 1 -
Colour blindness
Success
There are mostly non-contrast elements, users resorted to scaling in almost all cases)
The default state of the buttons is not contrasting enough.
π The testing showed where there are gaps in the product that should be
worked on comprehensively - by the whole team, most of them can be
solved in an affordable way and in a short time. This shows that
designing and developing a sufficient level of accessibility (AA) of web pages and applications is not so massive resource-intensive.
Having collected the artifacts, I presented and sent them to the team
of developers and designers of this platform, changes were made in the
next iteration.