Find the point of friction before changing reminders
An incomplete record does not explain why completion stopped. The link may not have arrived, the person may not recognize the sender, the form may be hard to use, the timing may be unsuitable, or the respondent may choose not to continue. Segment the path into invitation, access, start, progress, submission, and confirmation so each failure can be investigated without inferring motivation.
- Track delivery and access separately from form progress.
- Use aggregate operational data and synthetic testing, not sensitive free-text surveillance.
- Compare device, assistive-technology, language, and support routes where lawful and appropriate.
- Ask a small number of users what made the task difficult or unclear.
Make the route predictable and easy to resume
W3C cognitive accessibility guidance recommends clear content, help with mistakes, support for focus, and processes that do not rely unnecessarily on memory. Apply those principles to the surrounding workflow even when the licensed wording of an assessment itself cannot be changed. [2]
- Explain who sent the assessment, why it was requested, and what happens next.
- State expected time and any deadline before the person begins.
- Show progress without pressuring the person to answer faster.
- Preserve entered responses safely when resuming is permitted.
- Keep support and exit options visible and consistently named.
The respectful completion improvement loop
A five-step loop for reducing incomplete assessments by removing barriers while preserving informed choice.
- Locate
Identify where the path stops without assuming why.
- Listen
Gather focused feedback about access, clarity, timing, and support.
- Remove
Fix one evidenced barrier in the surrounding workflow.
- Test
Check the complete route with users and assistive technologies.
- Balance
Review completion, burden, support, accessibility, and opt-out signals.
Test the complete process for accessibility
WCAG 2.2 covers labels, instructions, error identification, status messages, focus behavior, target size, and accessible authentication. Its conformance model applies to complete processes, so test the invitation, identity or access step, form, validation, submission, and confirmation together. [1]
The W3C forms tutorial explains how labels, grouping, instructions, feedback, and accessible controls can reduce barriers for people using screen readers, speech input, or with cognitive or motor disabilities. [3]
- Complete the path with keyboard-only navigation and a screen reader.
- Zoom and reflow the interface without losing controls or context.
- Trigger each error and confirm that it is identified in text and linked to the field.
- Test session expiry, reconnection, and resume behavior.
Use reminders as navigation, not pressure
A reminder should help the recipient recognize the request, understand its status, and choose a next step. Keep cadence proportionate to the service context. Avoid artificial urgency, repeated contact after a clear opt-out, or language suggesting that a particular answer or completion is required to please the clinic.
- Name the clinic and provide a route to verify the message independently.
- Repeat the purpose, estimated time, deadline, support route, and choice to decline where applicable.
- Stop reminders when the assessment is submitted, withdrawn, replaced, or no longer needed.
- Route repeated non-completion to an accountable person rather than escalating messages indefinitely.
Measure completion and burden together
A higher completion rate can hide a worse experience if reminders increase distress, support contacts spike, or people feel unable to decline. NHS England's Accessible Information Standard requires services to identify and meet communication and information needs, which makes support-route performance part of workflow quality. [4]
- Completion and median time to completion.
- Drop-off point and successful resume rate.
- Support requests and unresolved access barriers.
- Opt-out, alternative-format, and alternative-route use.
- Accessibility defects found through testing and user feedback.
Sources and further reading
- Web Content Accessibility Guidelines (WCAG) 2.2 (opens in a new tab)World Wide Web Consortium. Published 2024-12-12. Accessed 2026-07-13. W3C Recommendation covering accessible forms, errors, authentication, focus, and complete processes.
- Making Content Usable for People with Cognitive and Learning Disabilities (opens in a new tab)World Wide Web Consortium. Published 2021-04-29. Accessed 2026-07-13. Informative design guidance for clear, usable, supportive digital content and processes.
- Forms Tutorial (opens in a new tab)World Wide Web Consortium Web Accessibility Initiative. Accessed 2026-07-13. Official practical guidance for form labels, structure, instructions, validation, and feedback.
- How to meet the Accessible Information Standard (opens in a new tab)NHS England. Accessed 2026-07-13. Official steps for identifying, recording, sharing, meeting, and reviewing communication needs.