Share
Explore

icon picker
Accessibility Passport

for digital tools, services, and content

Project by

✅ 1. Can people use it without needing to see it?

🦯 "Is it usable with screen readers, audio, or without looking?"

Why this matters
Not everyone sees—or sees in the same way. Some people are blind, have low vision, or use the web hands-free.

Examples
Add alt text for all images, including diagrams, charts, and GIFs.
Use resources like to find out how write image descriptions that are informative, descriptive and concise.
Use AI responsibly (with informed consent) to produce Alt Text for images. 👉
Make sure buttons, menus, and links can be reached by keyboard or screen reader.
Use WAVE or a11y project tools to test your site or app.

✅ 2. Can people understand it without hearing it?

🧏 "Does the core info come through without audio?"

Why this matters
Some people are Deaf or hard of hearing. Others are in loud or quiet places.

Examples
Provide captions for all videos.
Add full transcripts for podcasts, audio guides, and voiceovers.
Avoid using sound alone to indicate an action (e.g. a ding with no visual alert).

✅ 3. Is it okay to take your time?

🐢 "Can people read, watch, or respond at their own pace?"

Why this matters
People process at different speeds. Rushing can make a tool unusable.

Examples
Avoid auto-advancing slides or videos without a pause/play option.
Don’t cut people off with timeouts—offer “Extend Time” buttons.
Let animations be paused or turned off.

✅ 4. Does it work with different bodies and tools?

👐 "Can people use it with assistive tech or alternative inputs?"

Why this matters
Not everyone uses a mouse, or even hands.

Examples
Make sure your app works with voice control, eye tracking, head pointers, switches, and keyboard navigation.
Test your site without a mouse. Can you still use it?
Use semantic HTML and ARIA labels so assistive tools can interpret your layout.

✅ 5. Is everything readable and clear?

🔍 "Are fonts, colours, and layouts comfortable and legible?"

Why this matters
Low vision, dyslexia, and fatigue affect how people read. Busy pages or weak contrast strain eyes.

“Fatigue is the early sign of a failing system.” — Not a flaw in the user, but a flaw in the design.

Examples
Use high contrast between text and background (check with WebAIM Contrast Checker).
Avoid tiny fonts or low-contrast greys.
Don’t rely only on colour to convey meaning (e.g. “green = success” needs a label too).

✅ 6. Are there multiple ways to understand the same thing?

🔁 "Can people learn or act through more than one sensory channel?"

Why this matters
Everyone processes differently. Some people learn best through visuals. Others need words or movement.

Examples
Don’t just show text—also use images, step-by-step GIFs, or voiceover guides.
For how-to guides, offer both a written walkthrough and a visual/video version.
Let users choose text-to-speech (TTS) or watch a captioned video instead of reading.

✅ 7. Is the language friendly and plain?

📖 "Can someone understand this without specialist knowledge?"

Why this matters
Many users aren’t fluent in English, or don’t have a technical background.

Examples
Use plain language wherever possible.
Avoid unexplained jargon or abbreviations.
Offer translations when you can—or use symbols and icons to support meaning.

✅ 8. Is it okay to make mistakes?

🩹 "Can people recover easily if they click the wrong thing or miss a step?"

Why this matters
Accidents happen. Good design catches you when you fall.

Examples
Have clear “undo”, “cancel”, or “go back” buttons.
Don’t punish errors—guide users gently to fix them.
Give feedback on what went wrong and how to fix it.

✅ 9. Is it stable, consistent, and forgiving?

🧱 "Does the layout stay put? Are patterns predictable?"

Why this matters
Unexpected layout changes disorient people using screen readers or custom settings.

Examples
Keep buttons, menus, and navigation in consistent places.
Avoid sudden pop-ups or layout shifts.
Let people preview their input before submitting.

✅ 10. Have you tested it with real users—especially those with access needs?

🧑‍🤝‍🧑 "Have people who rely on access features tried it?"

Why this matters
You can’t catch everything alone. Accessibility is lived, not theorised.

Examples
Invite feedback from disabled users, testers, or advocates.
Use real-world accessibility tools like NVDA, VoiceOver, or JAWS to test.
Listen when people say “this doesn’t work for me”—and change it.


🔧 Helpful Tools and Resources


🔗 Links

— test for accessibility issues on websites
— community-driven accessibility resources and checklists
— creative and thoughtful approaches to writing descriptions

📑 Standards & Regulations

— W3C Accessibility Standards Overview
EN 301 549 EU Web accessibility standards - latest changes:
Accessibility requirements for ICT products and services: EN 301 549 V3.2.1
Accessibility requirements for ICT products and services: EN 301 549 V4.1.1
— the EAA effective as of June 2025
— more links to EU information on the EU Accessibility Act

🤖 Using AI to generate alt text

Tools like or image captioning models can help generate alt text descriptions, especially for diagrams, screenshots, and instructional images. But uploading images to an AI tool is not always neutral or harmless.
Before using an AI tool:
✅ Make sure you have the right to use and upload the image ✅ Avoid uploading people’s likenesses or artworks without informed consent ✅ Be mindful that uploaded images may be used in future training data, even if this is not immediately visible to the user ✅ Consider editing AI-generated alt text for clarity, tone, and context — automation is a starting point, not a finished product



⌨️ Keyboard Accessibility

Use Your Site Without a Mouse

Action
Windows/Linux
Mac
Move between focusable items
Tab
Tab
Move backwards
Shift + Tab
Shift + Tab
Activate link/button
Enter or Space
Return or Space
Scroll down
Arrow keys or Page Down
Arrow keys or Fn + ↓
Focus address bar
Ctrl + L or Alt + D
Command + L
Cycle through browser tabs
Ctrl + Tab / Ctrl + Shift + Tab
Control + Tab / Control + Shift + Tab
There are no rows in this table
🧩 Extra Tips & Links
If nothing seems to get focus: try pressing Tab first, then look for a visible focus outline.
If there's no outline, try opening browser settings and enabling keyboard navigation or focus highlighting.



Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.