Research question and scope
Published September 4, 2026.
This study asks whether customers requesting an alternative format receive a usable item within the promised time. The design focuses on process improvement within a named operation. It does not estimate disability prevalence or compare individual employees.
Define the journey from request through delivery and confirmation of usability. Capture the requested format, source asset, channel, remediation owner, promised checkpoint, delivery event, customer confirmation, repeat contact, and unresolved barrier. Avoid collecting diagnosis data when it is not required for fulfillment.
Outcome definitions
Distinguish requested, accepted, produced, delivered, and confirmed usable. Primary measures can include confirmed usable fulfillment and time to that state. Secondary measures include transfers, missed checkpoints, repeat requests, and abandonment. Report counts, open cases, and missing confirmation.
The W3C Web Content Accessibility Guidelines provide technical guidance for web content. The U.S. Department of Justice accessibility guidance provides legal context. Neither substitutes for a review of the specific service and applicable obligations.
Analysis and limitations
Show a flow by format and source asset. Review a sample with an accessibility testing rubric and more than one method where practical. Record whether failures arose in intake, remediation, secure delivery, or the source content.
Customers who confirm usability may differ from nonresponders. Some customers will solve the problem without telling support, while others may abandon before a case is created. Small format-specific samples create wide uncertainty. Results are local and observational.
Use findings to repair one high-volume source asset or handoff. Monitor usability, turnaround, privacy incidents, repeat contacts, and whether the alternative introduces a new barrier.