How do I recognise accessibility work respectfully?

Name the useful change and its observed result. You can thank captions, keyboard support or accessible documents without identifying who needed them or turning someone’s access needs into a public story.

Can I say the change helps everyone?

Use a narrower claim you can support. For example, captions provide a text version of spoken content. You do not need to claim that every person benefits in the same way.

Should I thank someone for pointing out a barrier?

Yes, when they are comfortable with the recognition. Thank the report or the test privately if public attention would reveal personal information. Fixing the barrier remains the organisation’s responsibility.

Recognition messages

Recognising Accessibility Work: 10 Thank-You Messages

Recognise the change that made participation possible, and avoid speaking for people whose experience you have not checked.

Be precise about what improved

“Thank you for adding labels to the chart. I can follow the comparison without distinguishing the colours.” That speaks from an actual experience and names the change. The fictional examples below cover products, documents and workplace participation.

An accessibility improvement deserves the same practical credit as any other useful work. It does not need a sentimental story about the people who benefit. Recognise the planning, testing and maintenance that made the improvement possible.

Keep personal information with the person

Someone may have reported a barrier through a private accommodation request. A public thank-you should not reveal that request or imply consent to discuss it. Ask before identifying the person; often you can thank the work without naming the original report.

The inclusion guide covers the broader workplace value. These messages focus on a specific access improvement and avoid claiming that one change establishes legal compliance or resolves every barrier.

10 messages you can send

Thank you for fixing the keyboard focus in the form. I can now reach the error message and return to the field without using a mouse.
After testing a product change
Describes the verified behaviour rather than claiming universal accessibility.
You added captions and checked the names the automatic transcript missed. Thanks for making the recording easier to use accurately.
On a meeting recording
Recognises the review after automation.
I appreciated you sending the agenda and documents before the call. I could read them at my own pace and join the discussion prepared.
On meeting preparation
Names a useful practice without requiring disclosure.
Thanks for checking the new venue’s access information before confirming it. We had time to make a different choice.
On event planning
Credits checking before a decision became difficult to change.
The chart now labels the series directly. Thank you for making the comparison readable without relying on colour alone.
On a data presentation
Names an observable improvement.
You brought the inaccessible step into the planning discussion before the release scope closed. Thanks for giving the team time to address it.
On early reporting
Recognises timing and ownership.
Thank you for replacing the scanned instructions with selectable text. Search and text tools can now work with the document.
On document access
Explains what the change enabled.
Your check of the screen-reader labels found the duplicate button names. Thanks for testing the actual flow instead of only the appearance.
On functional verification
Credits the relevant test.
I appreciated the option to contribute in writing after the workshop. It gave me a way to finish the thought I couldn’t get into the live discussion.
On flexible participation
Speaks from the sender’s own experience.
Thanks for documenting the remaining access issues alongside the fixes. We know what improved and what still needs work.
On honest follow-up
Avoids treating one improvement as completion of the whole task.

What makes one land

Describe the barrier and the verified change, without announcing anyone’s disability.
Avoid calling a whole product accessible on the basis of one fix.
Thank people for planning and testing access, not only responding to complaints.
Keep individual accommodation requests private unless the person explicitly wants them shared.

Questions people ask

How do I recognise accessibility work respectfully?: Name the useful change and its observed result. You can thank captions, keyboard support or accessible documents without identifying who needed them or turning someone’s access needs into a public story.
Can I say the change helps everyone?: Use a narrower claim you can support. For example, captions provide a text version of spoken content. You do not need to claim that every person benefits in the same way.
Should I thank someone for pointing out a barrier?: Yes, when they are comfortable with the recognition. Thank the report or the test privately if public attention would reveal personal information. Fixing the barrier remains the organisation’s responsibility.