Skip to main content

Accessible Prescriptions: Large Print and Clear Medicine Instructions

An accessible prescription keeps each medicine’s identity, amount, unit, route, timing and review instructions together in a format the patient can use. Offer readable text, sufficient contrast and a clear reading order, then test the actual print or digital copy with the patient. Enlarging a crowded table or shrinking everything onto one page does not establish accessibility.

By Bractis · Updated · 16 min read

Indian clinics producing prescriptions for people with low vision, older adults and anyone who needs larger text, clearer language or assistance reading medicine instructions.

Ask what the patient can use before choosing the format

Age alone does not tell the clinic whether a person can read a prescription. Ask about preferred text size, contrast, language and whether paper, a phone or another format is most useful. Record the preference with the patient’s agreement so that the next visit does not restart the same conversation.

Someone may read a large printed sheet comfortably but struggle with a compressed image sent to a phone. Another person may prefer selectable text that can be enlarged or read aloud. A relative who helps with medicines may be useful, but their availability should not be assumed, and help reading a prescription does not automatically authorise access to unrelated records.

Test the chosen format using the actual instruction task: can the patient find one medicine, identify the relevant amount and explain when it is intended to be used? This is a usability check for that person and copy. It does not certify every prescription or establish that the medicine plan itself is clinically appropriate.

Keep the meaning together when the page becomes larger

Each medicine needs a clear visual group. Keep the medicine identity and strength near its amount, unit, route and timing; place duration or review information where its relationship is unambiguous. Large text is less helpful if the amount wraps to a different line and looks as though it belongs to the next medicine.

A wide medicine table may work on paper but require sideways navigation on a phone. Consider a well-structured medicine block for narrow digital reading, provided the underlying clinical content remains identical. If a table is used, retain meaningful headers and avoid relying on column position alone to communicate what a bare number means.

When a prescription spans pages, repeat the appropriate patient/document identification and page numbering without unnecessarily exposing extra personal details. Keep a medicine’s instruction together where feasible; if it must continue, clearly label the continuation. Do not cut off a qualifier merely to maintain a preferred page count.

Use digital criteria accurately and test paper separately

WCAG 2.2’s contrast criterion uses at least 4.5:1 for ordinary text and 3:1 for qualifying large text. Its resize-text criterion addresses enlargement to 200% without loss of content or functionality, subject to its exceptions. These are digital accessibility criteria; they are not a universal prescription font-size rule or a guarantee that a particular patient can read a page.

W3C’s reflow guidance addresses reading at narrow widths, while recognising content such as data tables that may require two-dimensional layout. An exception for a table does not justify clipped cells or inaccessible content. Preserve readable text and provide a usable way to reach information that extends beyond the viewport.

For paper, inspect a real printout under ordinary reading conditions. Low toner, thin letterforms, a faint watermark or a photocopy can reduce usability even when the original screen looked clear. Use the patient’s feedback to adjust the format; a successful web contrast calculation does not measure the print in their hand.

Source: W3C: Understanding WCAG 2.2—Contrast (Minimum)

Source: W3C: Understanding WCAG 2.2—Resize Text

Source: W3C: Understanding WCAG 2.2—Reflow

Review the output by task, not by appearance alone

The following original review matrix can be used by reception, the prescribing clinician and the person preparing documents. Use fictional prescriptions for routine template testing. Patient feedback can then identify individual needs without exposing real prescriptions in public design reviews.

On a narrow screen, scroll the table horizontally to read all columns.

Accessibility checks for medicine instructions in print and on a phone
Patient taskCheck on the actual outputCommon misleading shortcut
Find the intended medicineIdentity, strength and status are distinct and readableRelying only on colour or the position of a row
Understand the amountNumber, unit and medicine remain visibly connectedEnlarging the number while the unit wraps elsewhere
Find timing and durationLabels and qualifiers remain next to the applicable instructionA separate footer whose scope is unclear
Read a second pageContinuation, document version and page order are evidentShrinking the whole document to avoid another page
Enlarge on a phoneText remains available without clipping or lost instructionsSending only a low-resolution screenshot
Use reading assistanceText order and labels make sense when read sequentiallyAssuming visual columns guarantee a useful reading order
Identify the current copyRevision and superseded status are understandableTwo differently formatted copies with conflicting instructions

Use labels and language without adding a guessing task

Plain-language directions should preserve the clinician’s intended timing and conditions. Symbols, meal pictures or morning/evening icons can supplement text, but they should not be the only way to express an instruction. Different routines, literacy and cultural interpretations can change what a symbol means to a reader.

For bilingual output, compare the complete instruction in both languages. A Hindi heading beside an English abbreviation is not automatically a Hindi instruction. Check the rendering of Devanagari or other scripts on the final PDF and printer; missing glyphs, broken character joins or tiny fallback fonts may not appear in the editor.

Keep abbreviations out of patient-facing directions when they depend on professional interpretation. Do not replace them with a translation that changes a prescribed interval into an assumed meal schedule. Where explanation requires clinical judgment, the clinician should review the wording rather than leaving reception to improvise.

Generate accessible copies from the same approved plan

A separately typed large-print handout can drift from the signed prescription. Prefer an accessible presentation of the same approved clinical version. If the clinic must prepare an additional copy manually, establish a comparison and sign-off step, label its relationship to the prescription and repeat that process after changes.

A format preference should not change medicine selection or erase a warning. When a clinician revises the plan, check the ordinary PDF, large-print copy, portal view and any translated copy that remains available. Identify which older versions are historical and communicate the replacement to the patient through the agreed route.

Do not assume a PDF is accessible because its text can be selected. Reading order, document structure and practical use with assistive technology require separate checks. Likewise, a browser page passing a reflow check does not prove that a downloaded prescription or phone messaging preview behaves the same way.

Worked case A-88: compare the meaning in every candidate copy

A-88 is a separate fictional editing exercise with six medicine entries, M1 to M6. These are labels, not real medicines or instructions. At 09:15 on 28 October 2026, the clinician authorises source prescription P2, changing a qualifier Q that applies only to M4. P1 is superseded. No medicine, amount or clinical qualifier is supplied by this example; it tests whether different presentations preserve the actual approved plan.

At 09:30, the clinic prepares a two-page larger-print copy L2, a PDF F2 for phone viewing and a structured text view T2. All are intended to represent P2. The patient prefers spoken Hindi, larger Devanagari text and a paper copy for use when the daughter’s shared phone is elsewhere. The exercise assumes the underlying Hindi explanation has been checked against the clinical source. That fictional check is not validation of any translated wording in this article.

The staff comparison at 09:45 finds an error in T2: Q appears beneath M5 rather than within M4’s block. Every word is present, but the relationship is wrong. T2 is held and never delivered. Corrected text view T3 is compared with P2 at 10:15, with Q restored to M4. This creates a new presentation version, not a new clinical prescription P3. A layout repair cannot quietly revise the prescriber’s qualification.

There are four P2 output records across three formats: L2, F2, T2 and T3, with T2 and T3 belonging to the text-view format. An older screenshot S1 still represents P1. Thus the five listed output records do not mean five clinical plans. At 10:30, only L2 and T3 are supplied as the current copies. F2 remains an evaluated candidate, and T2 remains the unissued draft that explains the correction.

On a narrow screen, scroll the table horizontally to read all columns.

Fictional A-88 copy comparison: source version, complete meaning and delivery
Output recordSource and content checkUse or disposition in this example
L2: larger-print paper, two pagesP2; M1 to M3 on page one and M4 to M6 on page two; amounts, units and Q stay with their medicineSupplied at 10:30 after checking the actual print; two pages form one copy
F2: phone PDF candidateP2; content comparison finds the six entries and Q intactPatient loses the row while panning in the clinic preview; not selected as the supplied phone copy
T2: first structured text viewIntended P2 content, but Q is placed under M5 instead of M4Held at 09:45; never delivered, despite containing all the words
T3: corrected structured text viewP2; Q restored to M4 and comparison completed at 10:15Supplied at 10:30 alongside L2; assistive-technology behaviour is not yet tested
S1: older screenshot in the family conversationP1; does not contain the current P2 qualificationIdentified as superseded; no claim that all saved or forwarded copies have been removed

Separate content accuracy, a usable reading task and a WCAG result

At 10:35 in fictional A-88, the patient finds M3 on L2 and keeps its amount and unit together while reading. With T3 already open, the patient also explains that Q belongs to M4. These are two useful observations about two particular copies. They do not show that the patient can independently open the phone link, navigate every entry or use the same layout under different lighting. Keep the help given during a task in the record.

Version recognition reveals another problem. At 10:40, the patient points to the older S1 screenshot as the copy to follow because it is easier to find in the family conversation. Staff explain the P2 replacement and show how L2 and T3 identify that source. At the 10:45 cutoff, a repeat check of which copy is current has not occurred. The record therefore has two selected reading tasks demonstrated and one version-identification question still open. The daughter’s correct answer cannot complete that patient check.

The phone PDF’s awkward panning is useful usability evidence, but this encounter did not perform a WCAG evaluation. For vertically scrolling web content, SC 1.4.10 addresses reflow at a width equivalent to 320 CSS pixels, with its two-dimensional-layout exception. SC 1.4.4 separately addresses text enlargement up to 200%, with exceptions for captions and images of text. Pinching one PDF on a phone, measuring the physical screen or doubling a paper font does not establish either result.

Reading order needs its own inspection. WCAG’s Meaningful Sequence criterion requires a correct sequence to be programmatically determinable when order affects meaning. W3C technique PDF3 describes reading and tab order in tagged PDFs and ways to inspect them. A staff member reading the visual page aloud does not test the order delivered to a screen reader. T3’s accurate text comparison is useful, but cannot stand in for checking its structure and the relevant assistive-technology workflow.

On a narrow screen, scroll the table horizontally to read all columns.

Fictional A-88 observations: what was demonstrated and what remains unknown
QuestionEvidence at the 10:45 cutoffLimit or next action
Can the patient read the amount with its unit?On the actual L2 print, the patient finds M3 and reads the linked fields at 10:35One selected medicine on this print; no universal font-size recommendation follows
Does the qualifier stay with the right medicine?Patient explains Q’s M4 scope with T3 already open; content comparison also matches P2Opening and independent navigation were not assessed in that task
Which copy will the patient follow?Patient initially selects old S1; replacement explained at 10:40Repeat patient check is pending; do not record the version question as resolved
Will assistive technology receive a useful order?No screen-reader or accessibility-API check performed for these copiesAssign technical checking separately; neither selectable text nor patient feedback is a WCAG pass

Source: W3C: Understanding WCAG 2.2—Resize Text

Source: W3C: Understanding WCAG 2.2—Reflow

Source: W3C: Understanding WCAG 2.2—Meaningful Sequence

Source: W3C technique PDF3: Correct tab and reading order in PDF documents

Keep a short record of the requested format and checks

Record needs respectfully and in terms of the task. “Requests larger print and reads Hindi instructions” is more useful than a broad label about ability. The following outline documents what the clinic actually supplied and checked; leave untested assistive-technology behaviour marked as untested.

Hand over the usable copies and the unresolved reading question

The patient’s paper preference matters because the phone is shared and the daughter is not always present. Supply and review the paper route on its own merits; access to a family smartphone does not establish access whenever instructions are needed. With the patient’s agreement, the daughter can help locate the current digital copy without becoming the sole person who can identify the plan.

At 10:45, the nurse accepts another patient check of the current version, while the clinician retains any question about clinical meaning or necessary care. Technical staff accept checking the digital reading order; completion is not claimed. Do not leave a patient dependent on an unverified future software repair. The clinic should agree a usable communication arrangement and record what was actually supplied and explained, with unresolved points clearly owned.

This record is an original fictional example, not an accessibility certificate or proof of Bractis output support. Its practical value is that the next person can distinguish a complete copy from a readable task and a still-unchecked technical behaviour. If the clinician later changes P2, both supplied formats need comparison again; a working layout does not make its contents permanently current.

Pilot the longest ordinary prescription, not an empty template

Choose a fictional case with six medicine entries, one long name, a multi-line qualifier and a review note. Produce the ordinary and larger-print formats. Inspect whether the last medicine, continuation heading and contact information remain complete. A one-row example rarely exposes the page-break problems that matter during daily use.

Compare a desktop view, a narrow phone view and the physical print. Include a patient or staff volunteer who can assess the relevant reading task, while keeping the case fictional. Record the observed limitation precisely: “unit separated from amount on page two” leads to a fix; “looks accessible” does not.

Use these cases when evaluating Bractis prescription outputs. Ask to see the actual supported formats and any assistive-technology checks already performed. This guide does not claim that a particular output is certified, clinically validated or suitable for every person with low vision.

Fictional example: six medicine entries should not be forced onto one page

A clinic enlarges a six-entry prescription for a patient who requests larger print. The second page begins halfway through an instruction, separating its unit from the medicine. The team changes the grouping and adds clear continuation identification, then checks the final print with the patient’s reading task. The two-page copy contains the same approved plan as the ordinary version; no direction is shortened or omitted merely to fit the layout.

Accessible Prescription Output Review

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Preferred medium
Which format and language can the patient use, and how is that preference retained?
Semantic grouping
Can the amount, unit, timing and qualifier be traced to the correct medicine after wrapping or page breaks?
Actual-output check
What happens on the clinic printer and the patient’s likely phone format?
Version consistency
How do ordinary, accessible and translated copies stay aligned after a clinical change?

Questions doctors ask

Is there one prescription font size that works for every older patient?

No single size establishes usability for everyone. Ask about the patient’s needs and test the actual reading task. Digital accessibility thresholds and large-text definitions are not a universal prescription print-size rule.

What text contrast should a digital prescription interface meet?

WCAG 2.2 specifies at least 4.5:1 for ordinary text and 3:1 for qualifying large text under its contrast criterion. Apply the criterion accurately and assess other accessibility needs; the ratio alone is not a complete accessibility check.

Should the clinic shrink text to keep a prescription on one page?

Page count should not override readability or completeness. Use clear medicine grouping and continuation information when additional pages are needed, preserving every approved instruction.

Is a screenshot of a prescription an accessible digital copy?

It may be difficult to enlarge or read with assistive technology and can lose detail through compression. Assess a usable text-based format and the actual patient workflow instead of assuming an image is sufficient.

Can a large-print handout be typed separately from the prescription?

That creates a risk of inconsistent versions. Prefer the same approved clinical content in another presentation; if a separate copy is necessary, compare it, identify its version and repeat the check whenever the plan changes.

Is an accessible copy correct if it contains every word from the prescription?

The relationships must also remain correct. An amount needs its unit and medicine, and a qualifier must stay with the intended instruction. In fictional A-88, T2 contains the words but places Q under the wrong medicine. It is held until that meaning is corrected and compared with the approved source.

Does one patient reading the larger-print copy prove WCAG compliance?

No. It provides evidence about that person’s reading task on that copy. WCAG evaluates digital accessibility through applicable criteria and conformance requirements; a paper reading task is not that evaluation. Record both useful patient feedback and technical checks separately, leaving untested behaviour explicit.

Sources and scope

Updated on . This article combines the cited references with Bractis’s original workflow analysis and illustrative examples. Product capabilities depend on the configured scope. No independent clinical or legal review is claimed.

  • W3C: Understanding WCAG 2.2—Contrast (Minimum)

    Official page directly read 28 October 2026. Informative explanation of SC 1.4.3, including digital text thresholds, large-scale text and exceptions. It is not a paper-prescription standard or universal print-size rule.

  • W3C: Understanding WCAG 2.2—Resize Text

    Official page directly read 28 October 2026. Informative explanation of SC 1.4.4: enlargement up to 200% without losing content or functionality, except captions and images of text. It does not establish print usability or conformance of any example output.

  • W3C: Understanding WCAG 2.2—Reflow

    Official page directly read 28 October 2026. Informative explanation of SC 1.4.10, including 320 CSS-pixel width for vertically scrolling content and the limited two-dimensional-layout exception. These are digital evaluation conditions, not physical phone measurements or paper-format requirements.

  • W3C: Understanding WCAG 2.2—Meaningful Sequence

    Official page directly read 28 October 2026. Explains SC 1.3.2 where content order affects meaning. The A-88 examples are original fictional analysis, not a W3C-validated prescription design or a completed accessibility assessment.

  • W3C technique PDF3: Correct tab and reading order in PDF documents

    Official technique directly read 28 October 2026. Applies to tagged PDF documents and describes reading-order inspection using assistive technology or accessibility APIs, with tab-order checks for focusable content. Techniques are informative examples, not mandatory implementations or certification of a PDF.

Try the workflow
with Bractis.

Use a fictional six-medicine plan to compare ordinary, larger-print and narrow-screen copies, including a page break and a subsequent prescription revision.

Request a clinic demo