What is the accessibility barrier report form template?
Many accessibility problems only come to light when someone runs into them: a button a screen reader can't announce, a form that times out, a heavy door, a lift that's out of service. A dedicated reporting form, linked from your accessibility statement, website footer or reception desk, makes it easy for people to tell you.
This template asks where the barrier was and then asks for the detail that place needs: the page URL for a website, the platform and screen for an app, the building and area for premises, or the document name. It then asks what kind of barrier it was from a list covering digital and physical barriers, what the person was trying to do, what happened, whether they could finish, and lets them attach screenshots or photos.
An optional page records any assistive technology, such as a screen reader, magnifier or voice control, with product and version, so your team can reproduce the problem. People choose whether they want a reply and in what format. Each report is saved as a PDF in your FileIt vault. The form helps you hear about barriers; it doesn't on its own make anything accessible or compliant.
- Best for
- Organisations with websites, apps, documents or premises used by the public
- Filled in by
- Visitors, customers, users or staff who meet a barrier
- Time to complete
- About 4 minutes
- Includes
- Location-specific follow-ups, 18 barrier types plus other, outcome, file upload, assistive technology details, reply method and accessible reply formats
Who uses a accessibility barrier report form?
- A 'Report an accessibility problem' link in a website footer or accessibility statement
- A QR code at reception for physical access issues
- Feedback on a newly launched app or website
- Collecting reports about inaccessible PDFs and forms
- Accessibility feedback after an event
- Building a log of barriers to prioritise fixes
Questions on this accessibility barrier report form
27 questions over 4 pages · includes file upload, conditional questions, multiple pages.
1 Where it happened
- Where did you meet the barrier?* Website · Mobile app · Building or premises · Document, PDF or form · Event · Phone or customer service · Video or audio content
- Web address (URL) of the page* asked only when it applies
- Which platform?* asked only when it applies iPhone or iPad · Android · Other
- Which screen or feature? asked only when it applies
- Which building, and which part of it?* asked only when it applies
- Name or link of the document* asked only when it applies
- Where exactly? asked only when it applies
- Which service, phone line or office? asked only when it applies
- Title or link of the video or audio asked only when it applies
- When did it happen?
- About what time?
2 What happened
- What kind of barrier was it?* Doesn't work with my screen reader · Can't reach or use something with a keyboard · Low contrast or text too small · Content breaks when zoomed or enlarged · Images or icons have no description · No captions, transcript or sign language · Time limit too short · Form hard to fill in or errors unclear · CAPTCHA or puzzle I couldn't complete · Language hard to understand · Steps, no ramp or no level access · Heavy, narrow or hard-to-open door
- What were you trying to do?*
- Describe what happened*
- Were you able to finish what you were doing?* No, I couldn't · Yes, but only with help from someone · Yes, but with difficulty · Yes, by using another route or channel
- Screenshots, photos or recordings
3 Assistive technology
- Were you using any assistive technology or aids?* Yes · No · Prefer not to say
- Which ones?* asked only when it applies Screen reader · Screen magnifier or zoom · Voice control or dictation · Switch access · Alternative keyboard or mouse · High-contrast or custom colours · Captions · Hearing aid or hearing loop · Wheelchair or mobility aid · Guide dog or cane
- Product names and versions, if you know them asked only when it applies
- Device and browser asked only when it applies
4 Contact
- Would you like us to contact you about this?* Yes, please contact me · No, I'm just letting you know
- Your name* asked only when it applies
- How should we reply?* asked only when it applies Email · Phone call · Text message · Letter by post
- Email* asked only when it applies
- Phone number* asked only when it applies
- Postal address* asked only when it applies
- Do you need our reply in an accessible format? asked only when it applies Large print · Easy read · Braille · Audio recording · Sign language video
The accessibility barrier report form, page by page
1 Where it happened
People choose where they met the barrier: a website, mobile app, building or premises, document or form, event, phone or customer service, video or audio, or somewhere else. A website asks for the page URL; an app asks for the platform and screen; premises ask for the building and part of it, such as the main entrance; a document asks for its name or link; an event asks where exactly; phone or customer service asks which service or office; video or audio asks for its title or link. Date and time are optional.
2 What happened
A required checklist covers common barriers: problems with screen readers or keyboards, low contrast, content breaking when zoomed, missing image descriptions or captions, short time limits, hard forms, CAPTCHAs and difficult language, as well as steps, heavy doors, lifts, toilets, parking, signage, noise or lighting, and staff who couldn't help.
People describe what they were trying to do and what happened, and say whether they could finish, needed help, managed with difficulty or used another route. Screenshots, photos or short recordings can be attached.
3 Assistive technology
This page explains that it helps reproduce the problem and that people should share only what they're comfortable with. They say whether they were using assistive technology or aids, with 'prefer not to say' available. A yes reveals a checklist (screen reader, magnifier, voice control, switch access, alternative keyboard, high contrast, captions, hearing aid or loop, wheelchair, guide dog or cane) and a box for product names and versions. Website reports also ask for device and browser.
4 Contact
People choose whether they'd like a reply. If they do, they give their name and choose how you should reply: email, phone call, text message or a letter by post. The form then asks only for what that method needs: an email address, a phone number or a postal address. They can also ask for the reply in an accessible format, such as large print, easy read, braille, audio or a sign language video. A note explains that details are used only to respond and that they don't need to share any medical condition.
Make the template yours
- Remove locations that don't apply, such as premises for an online-only service
- Add a dropdown of your buildings or sites
- Add your target response time to the confirmation message, if you commit to one
- Route reports to the team that owns the website, app or building
- Add an alternative contact method, such as a phone number, in the cover text
- Link the form from your accessibility statement and help pages
Tips for a better accessibility barrier report form
- Make sure the reporting route itself is accessible — test the published form with a keyboard and a screen reader
- Always offer another way to report, such as phone or email, for people who can't use an online form
- Reply in the format the person asked for
- Thank people for reports even when a fix will take time, and tell them what you plan to do
- Look for patterns across reports to prioritise the fixes that help most people
- Get advice on your legal obligations from a qualified adviser; this form doesn't cover them
Every response becomes a PDF in your vault
Each report is saved as a PDF in your FileIt vault, with any screenshots or photos attached. With owner notifications on, your team is emailed straight away, so people who asked for a reply aren't left waiting.
The Responses table lets you filter reports by location or barrier type, and export them all to a CSV to track recurring problems and plan fixes.
- Start from this template. It opens in the FileIt Forms designer — change any question, add pages, set the rules for when questions appear.
- Share it. Turn on a public link, or send it to people by email, each with their own link. They don’t need a FileIt account.
- Get the answers as PDFs. Each response is saved as a PDF in the vault folder you choose, with uploaded files attached — and listed in a Responses table you can export to CSV.
Accessibility barrier report form: frequently asked questions
Is this template free?
Yes. It's included in the FileIt Forms app on every account, including the free plan, and you can edit, add or remove any question.
Do respondents need a FileIt account?
No. Anyone with the form's link can respond without signing up or signing in.
Is the form itself accessible?
Test your published form with a keyboard and the assistive technology your users rely on before you launch it, and always offer another way to report, such as phone or email.
Can people report anonymously?
Yes. Name and contact details are only asked for when someone wants a reply.
Does using this form make us compliant with accessibility law?
No. It's a way to hear about barriers. Meeting accessibility standards or legal duties depends on how you design and fix your services; take advice from a qualified adviser.
Do people have to tell us about their disability?
No. The assistive technology questions include 'Prefer not to say', and the form states that no medical information is needed.
Can people attach screenshots or photos?
Yes. Up to five images, PDFs or short videos can be attached.
Can reports go to different teams?
Make a copy of the form for each team, for example digital and facilities, each saving to its own folder with its own notifications.