keepcalculator

06 Numbers and Powers

Accessibility & Assistive Tech: How to Choose

Card No. 06·72246 · Updated · Standard formula, shown below

Accessibility standards and assistive technology tools work together to make digital content usable by people with disabilities, and choosing the right approach means first understanding the standards (WCAG, EN 301 549, ADA) and then matching specific tools to the user’s needs, tasks, and environment. This article explains what the standards require, how assistive tech actually works, and gives a practical framework for selecting tools—whether for yourself, a family member, or an organization.

Background: Why Standards Exist

Accessibility standards emerged from the recognition that digital barriers exclude millions of people from education, employment, and public services. The most widely referenced standard is the Web Content Accessibility Guidelines (WCAG), currently at version 2.2. WCAG is organized around four principles: content must be Perceivable, Operable, Understandable, and Robust. Each principle has testable success criteria rated at levels A (minimum), AA (the common legal target), and AAA (advanced).

Other key standards include EN 301 549 (the European standard for ICT accessibility, which references WCAG), Section 508 (US federal procurement), and the Americans with Disabilities Act (ADA) which, while not a technical standard, has been interpreted by courts to require accessible websites and apps. For non-web content like PDFs, the PDF/UA (Universal Accessibility) standard applies.

How Assistive Technology Works

Assistive technology (AT) is any tool that helps a person with a disability perform a task they could not otherwise do, or do it more easily. In the digital world, the most common categories are:

  • Screen readers (NVDA, JAWS, VoiceOver, TalkBack) convert on-screen text to speech or Braille. They rely on semantic HTML, ARIA labels, and proper heading structure.
  • Screen magnifiers (ZoomText, built-in OS magnifiers) enlarge portions of the screen, often with color contrast adjustments.
  • Speech recognition (Dragon, Windows Speech Recognition, built-in dictation) lets users control the computer and enter text with their voice.
  • Alternative input devices include switch controls, eye trackers, sip-and-puff systems, and adaptive keyboards for people with limited motor control.
  • Text-to-speech (TTS) tools read selected text aloud, useful for people with dyslexia or reading difficulties.
  • Captioning and transcription tools make audio/video content accessible to deaf or hard-of-hearing users.

These tools only work if the underlying content is built to standards. For example, a screen reader cannot interpret an image unless the developer provides alternative text (alt text). This is why standards and tools are two sides of the same coin.

How to Choose Assistive Technology

Choosing the right tool is a personal, task-driven process. There is no single “best” tool; the right one depends on the user’s specific abilities, the tasks they need to perform, and their existing devices. A structured approach:

  1. Identify the functional limitation – Is it vision, hearing, motor, cognitive, or a combination? Be specific: low vision with peripheral loss needs different tools than total blindness.
  2. List the tasks – Reading web pages? Writing documents? Navigating a phone? Using a spreadsheet? Each task may need a different tool or a combination.
  3. Inventory existing devices – Windows, macOS, iOS, Android, or Chrome OS all have built-in accessibility features that may suffice. Many users do not need third-party software.
  4. Test before buying – Use free trials, built-in tools first, and seek hands-on demonstrations from disability organizations or vendors. A tool that works in a demo may fail in real-world use.
  5. Check compatibility – Does the tool work with the specific apps and websites the user must use? For example, some screen readers work better with certain browsers.
  6. Evaluate support and training – Is there documentation, tutorials, and customer support? A powerful tool that the user cannot learn is useless.
  7. Reassess regularly – Needs change, and tools improve. An annual review is advisable.

Common Problems and Misconceptions

A frequent misconception is that accessibility is only for people with permanent disabilities. In reality, temporary (a broken arm) and situational (bright sunlight) disabilities affect everyone at some point. Another myth is that accessible design is ugly or restricts creativity—in fact, many accessibility features like good contrast and clear navigation benefit all users.

Common technical problems include:

  • Missing alt text – Decorative images should have empty alt text (alt=""), while informative images need descriptive text.
  • Poor heading structure – Screen reader users navigate by headings; skipping levels (h1 to h3) breaks that navigation.
  • Unlabeled form fields – Every input needs a visible label associated with it via the label element.
  • Color-only meaning – Using red to indicate errors without an icon or text excludes color-blind users.
  • Non-descriptive links – “Click here” tells a screen reader user nothing about the destination.

Standards vs. Tools: What to Prioritize

If you are building a website or app, standards come first. No assistive tool can fix fundamentally inaccessible content. The WCAG 2.2 AA criteria are the practical baseline. However, standards alone do not guarantee usability—automated testing tools (like axe or Lighthouse) catch maybe 30-40% of issues. Manual testing with real assistive technology is essential.

If you are an individual user, tools come first. You cannot wait for every website to become accessible; you need tools that work today. In that case, prioritize tools with strong compatibility and support, and learn their keyboard shortcuts and settings.

Costs and Free Alternatives

Assistive technology ranges from free (built-in OS features) to thousands of dollars for specialized hardware. Some notable examples:

  • Free built-in: Windows Narrator, Magnifier, Voice Access; macOS VoiceOver, Zoom; iOS VoiceOver, Switch Control; Android TalkBack, Select-to-Speak.
  • Free third-party: NVDA (screen reader), ChromeVox (Chrome extension), Balabolka (text-to-speech).
  • Commercial: JAWS (screen reader), ZoomText (magnifier), Dragon Professional (speech recognition). Many offer free trials or discounts for students.
  • Hardware: Braille displays, eye trackers, and ergonomic keyboards can cost hundreds to thousands. Funding may be available through vocational rehabilitation agencies, insurance, or nonprofit organizations.

Always start with built-in tools—they are improving rapidly and may meet most needs.

Safety and Privacy Considerations

Some assistive tools, especially cloud-based speech recognition or screen readers that send data to servers, may have privacy implications. Users handling sensitive information should check the tool’s data handling policies. Also, be cautious with free tools from unknown vendors—they may contain malware or sell data. For hardware, ensure it is comfortable and does not cause strain; ergonomic assessments can help.

Frequently Asked Questions

What is the difference between WCAG A, AA, and AAA?

WCAG levels indicate conformance. Level A is the minimum for basic accessibility, AA is the target for most laws and policies, and AAA is the highest but is not required because it can be impossible for some content (e.g., sign language for all video). For most projects, aim for AA.

Are built-in accessibility features enough?

For many users, yes. Modern operating systems include screen readers, magnifiers, dictation, and switch control that are surprisingly capable. Start with built-in tools and only purchase third-party software if you hit a specific limitation.

How do I test if a website is accessible?

Use automated tools (WAVE, axe) to catch obvious issues, then manually test with a screen reader (try NVDA on Windows or VoiceOver on Mac), keyboard-only navigation, and a magnifier. Also check contrast with a color contrast checker. No single tool covers everything.

What is ARIA and when should I use it?

ARIA (Accessible Rich Internet Applications) is a set of attributes that enhance semantics for assistive technologies. Use it to label elements, describe roles, and manage dynamic content. However, overuse or misuse of ARIA can harm accessibility—prefer native HTML elements first.

Does accessibility only matter for websites?

No. Standards apply to mobile apps, PDFs, documents, software, and even hardware. WCAG is web-focused, but EN 301 549 covers all ICT. For documents, use the accessibility checkers in Word, PowerPoint, and Acrobat.

How long does it take to make an existing site accessible?

It depends on the site’s size and current state. A small site with good structure might take a few days; a large legacy site could take months. Prioritize critical user flows (login, purchase, contact) first. An accessibility audit is the first step.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →