Guide
Ask for a site people can actually use
Accessibility is a set of requirements, not a style. Ask for it plainly.
Difficulty: intermediate
1. Ask for it as a requirement, not a preference
Vague requests get vague results. Name the standard, because it is a real thing agents recognise.
This must meet WCAG 2.2 AA. Treat that as a requirement, not a nice to have.
2. Ask for keyboard use to work
Anyone should be able to use the whole site without a mouse, and you can check it yourself in a minute.
Everything must work with the Tab key alone, and whatever is focused must be clearly visible.
3. Say that colour cannot be the only signal
This is the most commonly missed one, and it affects a lot of people.
Never use colour alone to show an error or a success. Pair it with an icon and words.
4. Ask for real text alternatives
Empty or lazy alt text is worse than none, and it is the default output when nobody asks.
Every image needs alt text that describes what it shows. Decorative images should be marked so screen readers skip them.
5. Ask for motion to be optional
Animation can make some people physically unwell. The fix is one setting the browser already provides.
Respect the reduced motion setting. If it is on, turn every animation off rather than making it smaller.
Accessibility is not a visual style and it is not a plugin you add at the end. It is a handful of requirements that are cheap when asked for at the start and expensive to retrofit.
Two of these you can check yourself in under a minute: press Tab through the whole page, and see whether you can tell what is focused.