How to Document Website Accessibility Barriers

If you use assistive technology and encounter barriers on a website, proper documentation is essential. Whether you're seeking accommodations, filing a complaint, or pursuing legal action, detailed records of your experience provide concrete evidence of accessibility failures. This guide walks through the documentation process step-by-step, helping you create a clear record of barriers you've encountered and how they prevented you from accessing website content or services.

Effective documentation begins with preparation. Before you attempt to use the website, have these tools ready: Create a document template with the following headers:

Begin your documentation by noting your complete technical setup. This establishes the environment in which barriers occurred. Example documentation: Date: October 25, 2025 Time: 2:15 PM EST URL: https://example-store.com/checkout Browser: Chrome 118.0.5993.89 OS: Windows 11 Pro Screen Reader: JAWS 2024 User: Screen reader user (blind) Clearly describe what you intended to do on the website. Be specific about the task or transaction you needed to complete. Examples: For each barrier you encounter, follow this documentation pattern: Example barrier documentation: Barrier 1: Unlabeled Form Field Time: 2:18 PM Screenshot: checkout-form-001.png Action Taken: I navigated to the checkout form using JAWS and Tab key. When I reached the first form field, JAWS announced "Edit, blank" with no label or description. Result: I could not determine what information the form field required. I attempted to navigate to surrounding text using arrow keys, but found no associated label. I also checked using JAWS virtual cursor mode, but no descriptive text was associated with the field. Impact: Without knowing what information to enter, I could not complete the form field or proceed with checkout. I was completely blocked from making a purchase. Document your attempts using different navigation methods available in your assistive technology. This demonstrates you made reasonable efforts to access the content. For screen reader users, try: Example multi-method documentation: Method 1 - Tab Navigation: Pressed Tab key repeatedly. Focus moved from "Shopping Cart" link directly to "Submit Order" button, skipping over all form fields. No way to access fields with Tab key. Method 2 - Forms Mode: Pressed F key to navigate to next form field. JAWS announced "No forms found" despite visible form on screen. Method 3 - Virtual Cursor: Used arrow keys to navigate through page content. Found form field text but pressing Enter did not activate or focus the field. No way to input data. Method 4 - Touch Cursor: Used JAWS touch cursor to click on form field location. Mouse click appeared to register but field did not accept focus or keyboard input. If available, try accessing the same functionality through different paths or pages. This shows whether the barrier is isolated or systematic. Document each alternative attempt with the same detail as your original attempt. After documenting each individual barrier, write a narrative summary that tells the complete story of your experience. This should read as a chronological account. Narrative template: "On [date] at [time], I visited [URL] using [browser] and [assistive technology]. As a [description of disability], I rely on [assistive technology] to access websites. My goal was to [state objective]. I first attempted to [describe action]. [Assistive technology] responded by [describe response]. This prevented me from [describe impact]. I then tried [second method]. However, [describe result and impact]. Next, I attempted [third method], but [describe result and impact]. After [number] failed attempts using multiple navigation methods, I was unable to [complete task]. This prevented me from [describe ultimate impact - purchase, access service, obtain information, etc.]. I also attempted to access the same functionality using [alternative browser/device] on [date/time], with the same results. The barriers persisted across multiple attempts and configurations."

Different types of barriers require different documentation approaches. Here are common accessibility barriers and what to record for each:

Use a consistent naming system for all screenshots and recordings: Organize your documentation in folders: Create a comprehensive document that includes:

If you contact the website owner about accessibility barriers, document all communication: If the company claims to have fixed issues, test again and document:

A crucial part of your documentation is explaining how accessibility barriers affected you personally. This goes beyond technical descriptions to describe real-world impact. Example impact statement: "As a blind screen reader user, I rely on websites to be properly coded for independence in online shopping. The unlabeled form fields on this checkout page made it impossible for me to complete my purchase independently. I spent 45 minutes attempting different methods to access the form, but ultimately had to abandon my purchase. To obtain the product, I had to call a family member and ask them to complete the purchase on my behalf, which required sharing my payment information over the phone. This experience was frustrating and degrading. A sighted user could complete this same checkout process in under two minutes. The inaccessible design prevented me from making an independent purchase and forced me to rely on assistance for a task I should be able to complete privately."

Proper documentation creates a strong foundation, but you may need additional help depending on your situation: Several organizations can provide guidance: These organizations can help you understand your rights and may offer assistance with documentation or complaints.

Proactive accessibility auditing helps you identify and fix barriers before users encounter them. Get a comprehensive WCAG assessment of your website.