Structural Design

Accessibility

A digital-service quality practice for making products, content, and interactions usable by people with diverse abilities and assistive needs.

Concept facts

Accessibility is the practice of making digital products, content, and services usable by people with diverse abilities and assistive needs.

Also known as
A11y, accessible design, digital accessibility.
Used in
Product design, content, front-end implementation, procurement, QA, service delivery, and usability evaluation.
Interpret with
WCAG, assistive technology, inclusive design, usability, error prevention, cognitive load, and real user context.

Plain-language explanation

Accessibility means people can perceive, operate, understand, and use digital services across different abilities, technologies, and contexts. It includes but is not limited to standards compliance.

Accessibility should be considered throughout design, content, development, testing, and maintenance.

Why it matters

In public-service and development-sector contexts, inaccessible digital services can prevent people from applying, paying, learning, receiving support, or completing required actions.

Use contexts

  • Web and mobile product design.
  • Forms and transactional flows.
  • Content and document publishing.
  • Procurement and quality review.
  • Usability testing with accessibility considerations.

Application guidance

Use WCAG-aware review, accessible content practices, keyboard and screen-reader checks where appropriate, inclusive research, and usability evidence. Do not rely only on automated checks.

Practical example

An education platform publishes course registration, payment, and class information online. The pages are visually readable, but keyboard users cannot reach some controls, headings are not structured properly, and important fee information appears only inside images.

Accessibility review shows that the issue is not decorative compliance. The barriers can prevent learners with disabilities, low vision, or assistive-technology reliance from understanding and completing enrollment.

Interpretive boundaries

  • Accessibility is not only a checklist.
  • Automated checks cannot confirm every user need.
  • Accessibility and usability overlap but are not identical.
  • WCAG conformance does not guarantee full accessibility in real-world use contexts.
  • Standards-sensitive claims require source and subject review.

Applied at Userhub

Accessibility is relevant when Userhub evaluates whether digital services are usable across varied abilities, contexts, devices, languages, and assistive needs.

See Userhub UX Lab for applied UX research and evaluation context.

Sources and references

  • W3C. (2023). Web Content Accessibility Guidelines (WCAG) 2.2. W3C Recommendation. https://www.w3.org/TR/WCAG22/
  • ISO/IEC. (2012). Information technology – W3C Web Content Accessibility Guidelines (WCAG) 2.0 (ISO/IEC Standard No. 40500:2012). International Organization for Standardization.
  • ISO. (2018). Ergonomics of human-system interaction – Part 11: Usability: Definitions and concepts (ISO Standard No. 9241-11:2018). International Organization for Standardization.

Cite this entry

APA

Userhub. (2026). Accessibility. UX Reference. https://userhub.com.bd/reference/accessibility/