Accessible Aadhaar

Prioritizing accessibility in Aadhaar's book appointment flow
Duration
2 weeks
Role
Discovery and Research
Design

Team of 3 other designers
Tools
Figma

Project Overview

The Aadhaar card is a national identity card for all residents of India regardless of age and gender. With an Aadhar card, an individual can avail banking, mobile and other government and non-government services.

Problem Statement
Despite its importance and wide usage by over 1,25,00,00,000 people, a vast number of people complain about usability issues and inaccessibility of both the online portal and mobile app. Although the Aadhaar website claims to follow the World Wide Web Consortium (W3C) and Web Content Accessibility Guidelines (WCAG) 2.0 level AA, our team found it violated basic accessibility standards. We came up with a list of robust recommendations in our redesign of the book appointment flow, a key pain point, keeping usability and accessibility at the forefront.
Background
Purpose of the Aadhar Card
Existing Problems

Aadhaar is a universally acceptable government-issued card. Owning an Aadhaar card has as an all - purpose advantage.It can be used for a number of purposes, from opening a bank account to acting as a proof of identity. Aadhaar is used by everyone who wants to apply for government related service and programs - there is no need to apply for a separate card for each of these services.

The Aadhaar website is notoriously known to be extremely difficult to navigate, despite being essential to use.

We decided to focus on the book appointment flow as it is the most common flow users have to interact with. In order to get a new Aadhaar (1), they need to book an appointment and in order to update their Aadhaar (2), they have to book an appointment.

I based our user personas on secondary data made available by the company that currently designed the Aadhaar website as well as going through a11y and Rosenfield Media's persona resources.

1. Around 33% of the people who have tried to update details related to their Aadhaar identity also said the process was difficult, according to the State of Aadhaar 2019 report.

2. Aadhaar's newer digital features have also yet to be embraced, claimed the report, with nearly 77% of holders not using features such as mAadhaar app, QR code, or virtual Aadhaar.

3. Gaurav Gupta, Partner and Asia Regional Director of Dalberg said, "One big lesson for policy makers from this report is that 95% of people who do not have Aadhaar want one, but do not know how to get it."

Intent - Why accessibility?

1. Most countries have accessibility laws that websites are mandated to follow. The Aadhaar website, a government website, is not on the list of compliant websites as of March 2021 per the Guidelines for Indian Government Websites.

2. The Aadhaar website is more than a product - it's a utility. People only use the website to solve a query or accomplish a task. So, each user must be treated as a first time user and each use case as a first use case.

3. Filling out forms can be tedious. The user has to take ensure that all the details are correct and that the process is followed to avoid identification issues and long queues at the Aadhaar center.

4. Illiteracy is a big issue in rural India. The website must be understandable and usable for all.

Understand
What is accessibility?
Why is it important?

Although the web removes some barriers - such as communication and interaction barriers - it can be a place of exclusion if not designed to be accessed by all. As Tim Berners-Lee said

"The power of the web is in its universality. Access by everyone, regardless of disability, is an essential aspect."

About 15% of the worlds population has some form of disability. The rates of disability are rising as the population is ageing and chronic health conditions are increasing. Furthermore, people with disabilities have less access to health care services and experience unmet health care needs.

Although the web removes some barriers - such as communication and interaction barriers - it can be a place of exclusion if not designed to be accessed by all. As Tim Berners-Lee said

"The power of the web is in its universality. Access by everyone, regardless of disability, is an essential aspect."

About 15% of the worlds population has some form of disability. The rates of disability are rising as the population is ageing and chronic health conditions are increasing. Furthermore, people with disabilities have less access to health care services and experience unmet health care needs.

WCAG

The Web Content Accessibility Guidelines (WCAG) are a set of guidelines, composed and reviewed by a global community of digital experts, that make digital content accessible for users with disabilities.

There are 4 main principles of WCAG-

1. Perceivable - Users must be able to perceive the information being presented. The information cannot be invisible to all of a user’s senses. For example: text alternatives for non-text content; captions and other alternatives for multimedia.

2. Operable - Users must be able to operate the interface. The interface cannot require
interaction that a user cannot perform. For example: users should have enough time to read and use the content which does not cause seizures and physical reactions; Users can use different input modalities beyond
keyboard.

3. Understandable - Users must be able to understand the information and the operation
of the user interface. The content or operation cannot be beyond the user’s understanding. For example: The text should be readable and understandable; the content appears and operates in predictable ways

4. Robust - Users must be able to access the content using a wide variety of user agents, including assistive technologies. For example: the content should be compatible with current and future user tools.

User flow
I based our user personas on secondary data made available by the company that currently designed the Aadhaar website as well as going through a11y and Rosenfield Media's persona resources.

I scoured the playstore reviews and government grievance portals to identify pain points.
personasreviewspain pointsuser flowuser flows
Redesigned User flow
Based on the user pain points, our team re-designed the user flow for book appointments. We found that Update Aadhaar (1), New Aadhaar (2) and Manage Appointments (3) were the 3 key actions relevant to the book appointment flow that users took.

In the existing flow users had to -
1. Select center
2. Select purpose
3. Enter details
4. Book/confirm their appointment

But what if all centers do not support both getting a new Aadhaar and updating the existing Aadhaar? Some centers only did updation work.

Proposed Flow 2:
1. Select purpose
2.Select center
3. Enter details
4.Book/confirm

But what if the center does not have a desirable slot for the user? The user wouldn't be able to enter their details then for future appointments.

Final Flow:
1. Select purpose
2. Enter details
3.Select center
4.Book/confirm

This way, the website can save details to the account and the user can login later to select a slot at their convenience
flowchart
Heuristic Analysis
Although we kept NNG's 10 heuristics in mind, we focused on how we could implement accessibility in the writing as well as design of the book appointment flow.
mockup
Design
Wireframing
Instead of focusing on the visual design and high fidelity mockups, we wanted the focus to be on the task flow and the layout, keeping accessibility and usability at the forefront.


We created wireframes for all 3 flows manage appointment, book appointment (update) and book appointment (new Aadhaar).
Conclusion
Reflections
Learning about accessibility and implementing it while designing are two different things. After a couple of mentorship sessions with people in the accessibility space, I realized how inaccessible the web can be. Designing for accessibility requires attention to detail and a whole lot of empathy. I was constantly thinking about people with low vision or motor disabilities - how would they approach filling in a form? How long should the One Time Password be valid for? Where should I place this button so that the screen reader will logically navigate to it? After studying the principles of accessibility in detail, I can't unsee the inaccessible features in a digital product. This project confirmed my commitment and motivation to keep accessibility at the forefront of my work and delve deeper into the space.