Consent design guideUpdated October 14, 2026

Low-literacy and accessible informed consent: a practical guide

Consent that a participant signs but did not understand is not informed. This guide covers how to write, present and check consent for people with low literacy or accessibility needs, what IRBs expect, and, plainly, which parts Capture eConsent supports and which it does not.

  • Plain-language and teach-back design
  • Honest about what eConsent does not do
  • Witness and LAR paths

Free sandbox · No credit card · 21 CFR Part 11 aligned

Accessible consent plan for an IRB submission (demo)

Study

DEMO-OBS-02

Population

Adults, mixed literacy

Signature path

On-screen + witness

  • Consent text rewritten in short sentences, key information firstReviewed by coordinator
  • Teach-back questions prepared for the visit5 questions
  • Impartial witness named for participants who cannot readSite 001
  • LAR path described for participants who lack capacityIRB wording
  • Audio or translated versionOutside Capture: arrange separately
Demo plan. Your IRB and population decide the real requirements.

What to take from this guide

  • Understanding is the test, not the signature: regulations ask that consent be in language the participant can understand. A clean signature log does not show comprehension.
  • Most of the work is in the words and the conversation: short sentences, key information first, one idea per paragraph, and a teach-back check do more than any software feature.
  • Software can help with the path, not the reading: Capture eConsent gives an on-screen signature, email OTP confirmation, optional witness co-signature, optional LAR signature and a countersigned PDF.
  • What Capture does not have: no read-aloud or audio narration, no video consent, no built-in translation and no reading-level scoring inside the consent flow. Plan those separately.
  • Your IRB decides: this is design guidance, not legal advice. Ask your IRB or ethics committee what it expects for your population.

The problem

Why consent forms fail the people they are written for

Consent documents grow because every stakeholder adds a paragraph: the sponsor adds risk language, the institution adds its template, the IRB adds a required sentence. By the time it reaches a participant it can run to many pages of dense legal text. Adults with limited reading skills, people reading in their second language, people with low vision or dyslexia, and anyone who is simply anxious in a clinic room will struggle with it. They often sign anyway, because signing is what is expected.

US and international rules on informed consent share a simple idea: the information must be given in language the participant can understand, with enough time to consider and the chance to ask questions. The revised US Common Rule also asks that consent begin with a concise summary of key information. Exact citations and local rules vary, so check with your IRB, but the direction is clear and it applies to paper and electronic consent alike.

A useful way to think about it is to separate three things: the text (what it says and how), the delivery (how the participant meets it, with whom, with what support) and the record (how agreement is captured and proven). Software mostly touches the record and part of the delivery. Most of the gain is in the text and the conversation, which is why the first sections of this guide are about writing, not tools.

The text

A plain-language rewrite checklist

Run each section of the consent through these checks before it goes to the IRB. A coordinator who has never seen the protocol is a good reviewer: if they cannot explain a paragraph back, rewrite it.

Key information first

Open with a short summary: why the study is being done, what you will be asked to do, the main risks, the main benefits, and that taking part is voluntary.

Short sentences, common words

Aim for one idea per sentence. Replace "randomized" with "chosen by chance, like flipping a coin" and "adverse event" with "a health problem".

Active voice and "you"

Write "You will visit the clinic four times" rather than "Participants will be required to attend four visits".

Define each unavoidable term once

If "placebo" or "biopsy" must appear, explain it in the same sentence and keep the term consistent afterwards.

Numbers and times in concrete terms

Say "about 45 minutes" and "one tablespoon of blood" instead of unexplained units or ranges.

Layout that is easy to scan

Descriptive headings, short paragraphs, bullet lists for steps, and generous spacing. Avoid long all-caps blocks.

Rights stated in plain terms

Say clearly that the person can say no or stop at any time and that their usual care does not change.

Test the reading level

Use the free consent readability checker to see where sentences are long. Many IRBs ask for text around the 6th to 8th grade level; check what yours expects.

The delivery

Teach-back, time and a person, not just a screen

Good consent is a conversation with a document attached. The strongest low-tech technique is teach-back: after explaining a topic, ask the participant to tell you in their own words what they will do or what the main risk is. If the answer is wrong, the explanation, not the participant, needs another try. Prepare four to six teach-back questions in advance and note in the consent record that the discussion took place.

Give people time. Offering the document ahead of the visit, with a way to ask questions before they arrive, helps participants who read slowly or want to talk it over with family. Capture's remote consent flow supports sending the consent to the participant to read on a phone or computer, but the conversation with the investigator or coordinator should still happen, in person, by phone or by video, outside Capture.

Think about the environment as well. A quiet room, a chair, large print available on request, the option of a support person, and a coordinator who is not rushing change what participants take in. For participants with vision, hearing, motor or cognitive differences, ask them what helps, and record the accommodation.

When the participant cannot read

Many regulatory frameworks allow consent for a person who cannot read through an impartial witness who attends the whole discussion, confirms that the information was accurately explained and that the participant appeared to understand, and signs the form. The exact conditions differ by region and IRB. In Capture, an optional witness co-signature is supported; see impartial witness eConsent.

When the participant lacks capacity

Where the law allows a legally authorized representative to consent on someone's behalf, the participant's own assent and dignity still matter. Capture supports an optional LAR signature; see legally authorized representative consent. Who qualifies as an LAR is set by law and your IRB, not by the software.

Be specific

What Capture eConsent supports, and what it does not

Procurement and IRB reviewers ask direct questions about accessibility. Here are direct answers, limited to what is verified.

NeedCapture eConsentHow to cover it
On-screen signatureYes: participant signs on-screen, must acknowledge the legal-binding statementUsed as is
Identity confirmationYes: mandatory email OTP confirmationParticipant needs access to email
Witness for non-readersYes: optional witness co-signatureDefine who may witness in your protocol and IRB documents
LAR consentYes: optional LAR signatureIRB-approved process for capacity and eligibility of the LAR
Staff countersignatureYes: password re-authentication and a legal meaning statement; fully executed only after countersignatureUsed as is
Proof of what was signedYes: signature hash-linked to the document content; signed PDF with timestamps and audit trailUsed as is
Read-aloud or audio narrationNot availableCoordinator reads aloud, or a separate audio file approved by the IRB
Video explanationNot availableSeparate IRB-approved video, referenced in the consent text
TranslationNot available (do not rely on it)IRB-approved translated documents handled outside Capture; confirm status with us first
Reading-level scoringNot in the consent flowUse the separate readability checker before you upload text

Screen reader and keyboard accessibility of the participant pages has not been separately certified in the materials this page relies on. If that matters for your population, test the sandbox with your own tools and ask us.

Test your consent text on a real screen

Paste your rewritten consent into a free sandbox, send it to a colleague on a phone and see how it reads. Free, every feature, no credit card.

Build a consent flow free

The record

A signature path that fits the person

Once the text and conversation are right, the record should be simple to produce and hard to dispute. Capture's eConsent keeps the sequence short and puts each step on the audit trail.

  • The participant signs on-screen after acknowledging the legal-binding statement, then confirms with an email code.
  • A witness and, where applicable, an LAR can sign in the same flow.
  • Authorized site staff countersign with password re-authentication.
  • The signed consent exports as a PDF with signature data, timestamps and the audit trail.
Capture eConsent
Electronic signature

Meaning of signature

I have reviewed this adverse event and confirm the assessment of seriousness, severity and causality.

Signer

Dr. A. Ozola, PI

Password

••••••••••

Verified on the serverAutofill blockedSingle-use token
Sign

Putting it together

A consent process for mixed-literacy populations

  1. 1

    Rewrite for plain language

    Apply the checklist above, then run the text through a readability check and a coordinator read-through.

  2. 2

    Agree accommodations with your IRB

    Describe large print, a support person, the witness process and the LAR process in the submission. Use the IRB submission checklist to make sure the pieces are there.

  3. 3

    Prepare teach-back questions

    Write four to six, and decide how the coordinator records that the discussion took place.

  4. 4

    Choose the signature path

    Standard, witnessed or LAR. Build the eConsent in the sandbox and rehearse each path. See how to write an eConsent form.

  5. 5

    Review comprehension signals

    If many participants need repeat explanations of the same section, revise that section and amend the consent through your IRB.

FAQ

Questions teams ask before they switch

Something not covered here? Ask us directly.

Does Capture eConsent have read-aloud or audio?

No. There is no audio narration or video in the consent flow. A coordinator can read the consent aloud, or you can use a separate IRB-approved audio or video file.

Can it translate the consent into another language?

No. Do not rely on built-in translation. IRB-approved translated documents have to be prepared and handled by your team; ask us about the current status of multilingual support before you plan around it.

Can a witness sign for a participant who cannot read?

Capture supports an optional witness co-signature. Whether and how a witness is acceptable is set by your regulations and IRB. See the impartial witness eConsent page.

What reading level should consent be written at?

Many IRBs ask for roughly the 6th to 8th grade level, but requirements differ. Check yours, and test the real text with the readability checker and a coordinator.

Is eConsent better or worse for low-literacy participants?

Neither by itself. Screens can add clarity if the text is plain and a person still explains it, or add friction if participants are not comfortable with devices. Offer a paper or in-person option when your population needs it.

Is this legal advice?

No. It is practical design guidance. Your IRB or ethics committee and your regulatory adviser decide what is required.

Try an accessible consent flow free

Free sandbox with every feature. No credit card, and you pay only when you go live with real participants.

Build a consent flow free