---
name: accessible-technology-guide
description: "A practical checklist for making a website, app or tool accessible, covering assistive technology support, key features, standards and how to test. Use when a team building web, mobile or desktop software needs a practical accessibility checklist with features, standards and testing. Do not use for a full accessibility consulting plan for buildings or services. Related topics: accessibility, technology, accessible."
---

# Accessible Technology Guide

A practical checklist for making a website, app or tool accessible, covering assistive technology support, key features, standards and how to test.

## When to use

Use this skill when a team building web, mobile or desktop software needs a practical accessibility checklist with features, standards and testing. Do not use it for a full accessibility consulting plan for buildings or services.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Tie each accessibility feature to the target audience and the technology type.
3. Add one concrete check for each selected compatibility item.
4. Name the standard to follow and what it requires at the level the team needs.
5. Describe testing with the chosen tools and with real users.
6. Set a review rhythm across the months given and list a few reliable resources.

## Inputs

- **Target audience** (free text, e.g. "people with low vision or older adults")
- **Technology type** (choose one: Web, Mobile, Desktop, Other)
- **Compatibility to support** (choose any: Screen Readers, Keyboard Navigation, High Contrast Mode)
- **Color scheme** (choose one: High Contrast, Normal)
- **Base font size in points** (number from 12 to 24)
- **Audio descriptions needed** (choose one: Yes, No)
- **Standard to follow** (choose one: WCAG 2.1, Section 508, Other)
- **Testing tools** (choose any: Screen Readers, Keyboard Navigation, Switch Access)
- **Months of ongoing improvement** (number from 1 to 12)
- **Learning resources already used** (longer free text)

## Output

A guide with headed sections: Features, Standard, Testing, Ongoing Improvement and Resources, with one concrete check per compatibility item.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Accessible Technology Checklist

Write a practical guide for a team making a piece of technology more accessible. Cover what to build, which standard to follow and how to test it.

- Target audience: {{Target audience}}
- Technology type: {{Technology type}}
- Compatibility to support: {{Compatibility to support}}
- Color scheme: {{Color scheme}}
- Base font size in points: {{Base font size in points}}
- Audio descriptions needed: {{Audio descriptions needed}}
- Standard to follow: {{Standard to follow}}
- Testing tools: {{Testing tools}}
- Months of ongoing improvement: {{Months of ongoing improvement}}
- Learning resources already used: {{Learning resources already used}}

Organize the guide by the work, not by theory: features to build, then the standard, then testing. Tie each feature to the audience, such as contrast and text size for low vision. Cover each compatibility item chosen with one concrete check, such as every control reachable by Tab. Say how to test with the listed tools and with real users, and set a review rhythm over the months given. Recommend a few well-known resources without inventing titles.

Return headed sections: Features, Standard, Testing, Ongoing Improvement, Resources.

## Pitfalls

- Treating a screen reader pass as full coverage, leaving keyboard and switch users out.
- Choosing high contrast only, without checking contrast ratios in the normal theme.
- Inventing resource titles or links that do not exist.
