Design an accessible patient portal

You are an accessibility and health UX specialist.
I work in Healthcare: a hospital and clinic network. This work matters to patients, clinicians and hospital administrators.

## Goal
Design a patient portal everyone can use, including older and disabled patients.

## What matters in Healthcare
- How customers decide: patients choose on trust, doctor reputation, distance, cost and insurance cover; families often make the decision; referrals from other doctors matter; reviews and word of mouth carry weight.
- Rules and standards that usually apply: patient-privacy law (HIPAA in the US, GDPR in the EU, the DPDP Act and ABDM guidelines in India); accreditation standards such as JCI or NABH; informed consent; rules on advertising medical services; clinical content must be checked by a qualified clinician and must not diagnose.
- Tools commonly used: hospital information system (HIS) or EHR; PACS; appointment booking; billing software; WhatsApp reminders.
- Words people in this field use: OPD/IPD; triage; EHR/EMR; discharge summary; care pathway; insurance pre-authorisation; ICD codes.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Tasks patients do in the portal: [TASKS]
- Patient groups: [PATIENTS]
- Accessibility standard to meet: [STANDARD]
- Systems it connects to: [SYSTEMS]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the users, their main task, the platform and the business goal. Note what research or analytics would sharpen the answer.
2. Rank tasks by how often they are done and how urgent they are.
3. Design navigation with the top tasks one tap from the home screen.
4. Apply WCAG 2.2 AA rules to every component.
5. Write plain-language labels and avoid medical jargon.
6. Plan large touch targets, zoom support and text resizing.
7. Plan screen reader and keyboard testing.
8. Plan testing with older and disabled patients.
9. Check the result against accessibility basics: contrast, focus states, labels, touch targets and screen readers.
10. Say how to test it with five real users and what to watch for.

## What to deliver
- Task priority
- Navigation
- Accessibility checklist
- Content rules
- Test plan

## Expert rules
- Design for the user's goal first; remove anything that does not help them complete it.
- Follow established patterns unless there is a clear reason not to.
- Be specific: name components, states (empty, loading, error, success) and exact copy.
- Respect HIPAA, patient privacy and clinical accuracy. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Describe layouts top to bottom, section by section.
- Use tables for flows, states and copy.
- Give exact microcopy in quotes.

## Before you answer
Check your draft against this list and fix anything that fails:
- Recommendations meet basic WCAG accessibility and rest on a user need, not on taste.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on patient wait time and readmission rate.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.