Software

Designing Tech Products for Inclusive Digital Access

A researcher reviewing a visualisation
AI-generated illustration.
Inside this article
  1. Make digital access a product requirement
  2. Build accessibility into the interface
  3. Test real tasks with users
  4. Design for limited budgets
  5. Make privacy choices understandable
  6. Keep alternatives and measure task completion

Technology companies support inclusive digital access when people with different abilities, budgets, devices, skills, languages, and internet connections can use their products confidently and make their own choices. This includes signing up, paying, and getting help when something goes wrong.

Accessible controls, low data costs, clear privacy choices, and workable alternatives help people use a service. Without them, some people are left out.

Make digital access a product requirement

More people can use a product when its main tasks work in different situations. Someone might use a screen reader, share a phone, have limited data, rely on an older device, or need help with an unfamiliar process. If a product is designed only for newer phones, fast connections, and confident readers, people who do not have those things face barriers.

Disability belongs at the center of this work. The World Health Organization estimates that 1.3 billion people, or 16% of the global population, have a significant disability. Barriers in a product can prevent people from communicating, learning, working, or using services, even when they have the skills and interest to do so.

Before development begins, find assumptions that could block people from using the product. Ask what someone needs to finish the main task, what could get in the way, and whether they have another way to proceed if they lack the expected device, connection, or ability. Ask these questions about account setup, identity checks, payments, search, and account recovery, as well as the home screen.

Build accessibility into the interface

For websites and web services, WCAG 2.2 is the current version of the Web Content Accessibility Guidelines recommended by the W3C. Published as a W3C Recommendation on December 12, 2024, it sets criteria that can be tested for needs related to vision, hearing, movement, speech, photosensitivity, and some cognitive and learning disabilities. The criteria include text alternatives for images, captions for media, keyboard operation, and clear indicators of which item has keyboard focus.

A company can use WCAG 2.2 as a starting point for design and testing. A form should mark required fields with text, show keyboard users where they are on the page, and explain errors so assistive technology can read them aloud or display them. Captions give people access to spoken information in a video and help anyone who cannot play audio at that moment.

Meeting WCAG does not guarantee that every person can use a product. The W3C notes that WCAG does not cover every user need, so companies also need to test with disabled people and assistive technologies. The United Nations Convention on the Rights of Persons with Disabilities treats access to information and communications technology as part of taking part in society. The Convention addresses states, so it gives broader context about rights rather than setting legal duties for a particular company.

A developer working at a computer
AI-generated illustration.

Test real tasks with users

Accessibility and usability overlap. A product can pass checks on individual parts of its interface and still make a real task hard to finish. For example, a screen reader might announce every button correctly, but account recovery could still be confusing or require the user to read a visual code.

Include people with different access needs in research while there is still time to change the design. Test realistic tasks in prototypes and finished products using different browsers and assistive tools, such as screen readers, magnifiers, high-contrast modes, and speech recognition. Automated checks find some defects, but they cannot show whether a person understands an instruction or can recover from an error.

Test whether someone can create an account, verify their identity, correct a payment mistake, and regain access after losing a device. Note where people pause, get stuck, or seek help. Fix the causes, then test the task again with people who use different access methods. This can reveal barriers across the whole journey, not just on individual screens.

Design for limited budgets

A free sign-up does not make a digital service affordable. People also pay for devices, repairs, data, assistive technology, subscriptions, and add-ons. Requiring a recent phone, large downloads, or a constant high-speed connection adds to the cost of using the service.

International Telecommunication Union data for 2024, published in May 2025, put the median cost of a data-only mobile broadband basket at 1.1% of gross national income per capita globally. The fixed-broadband basket was 2.5%. The burden varied sharply with income: subscribers in lower-middle-income economies paid around six times as much of their income for the mobile basket as those in high-income economies, and subscribers in low-income economies paid around 19 times as much. In low-income economies, fixed broadband, where available, cost nearly a third of average income. These figures describe connectivity baskets, not the full cost of using a particular product.

Product choices can lower some of these costs. Make essential tasks work on older devices, limit unnecessary downloads, turn off autoplay that uses data, and let users save their progress if the connection drops. Explain subscription terms and paid features before users spend time or share sensitive information. These steps do not remove broader affordability barriers, but they keep the product from adding more.

Internet access also varies by location and income. The ITU estimated that 76% of the world’s population was online in 2026, leaving 2 billion people offline. Its 2025 Global Connectivity Report found that 85% of urban residents used the internet, compared with 58% of rural residents. Those population estimates do not explain why each person is offline, but they show why a product should not assume constant connectivity.

Make privacy choices understandable

People need to know what information a service collects, why it collects it, and what choices they have. Dense legal text and hidden settings make it hard for users to control their privacy. Collect only information needed for the product’s stated purpose, explain important choices in plain language, and make privacy controls work with assistive technology.

The U.S. National Institute of Standards and Technology’s Privacy Framework says organizations should assess privacy risks throughout the life of data, from collection to storage, sharing, and use, and address them with product and operational safeguards. The framework is voluntary, not a legal rule. In practice, this means considering what could happen to a person at each stage, rather than treating privacy as a notice shown at signup.

People also need help when something goes wrong. Provide another way to recover an account when automated verification fails, and let users contact support without going through the same inaccessible steps. A UK government report on digital inclusion among disabled adults found that, even among people who went online as much as they wanted, 53% worried about privacy and security, while 48% worried about scams or harmful content. These findings describe the people in the report, and show why both usability and safety matter for participation.

Privacy and security overlap, yet they answer different questions: security helps prevent unauthorized access, while privacy concerns how information is collected and used. The distinction is useful when choosing safeguards; see the difference between encryption and access control.

Engineers reviewing a monitoring display
AI-generated illustration.

Keep alternatives and measure task completion

Moving a service online helps some people, but it excludes others if the online route becomes the only practical option. For important tasks, consider what support or offline option remains for people who cannot or choose not to use the online service. The right alternative depends on the service. It could be phone support, in-person help, or a supported way for someone else to act on the user’s behalf.

Digital access can support social connection, but it does not replace every form of contact. In the UK report on disabled adults, 63% said being online made them feel more connected to other people, while 76% said it did not replace face-to-face interaction. The findings show perceived benefits alongside limits; they do not establish that product design alone causes connection or loneliness.

Track whether people finish important tasks, where they make errors, how often they leave partway through, and when they need help. Compare results across relevant user groups when it is lawful and appropriate to collect and analyze that information. One overall completion rate can hide a serious barrier affecting some people. Do not collect sensitive information just to create demographic breakdowns unless there is a clear purpose and safeguards.

There is no established business return that applies to every investment in accessibility or inclusion. Product owners should judge changes by what people can access and complete, as well as by operational and commercial results. They should not claim that one feature benefits every group equally. Global data are also incomplete: the figures here do not give a current, complete picture of connectivity and product use by disability type and other overlapping factors.

About this article

Created with AI assistance using published sources. Illustrations are AI-generated. Redbag does not claim hands-on testing or exclusive reporting. Check the linked sources for changing product details.

Our approach ↗

Keep connecting the dots.