Accessible Patient Portal Component Migration Advisory
Communicates design system component updates and WCAG 2.2 AAA accessibility requirements to healthcare product teams.
Use when updating health-critical design components like medication dosage selectors or appointment checkers. It crafts an actionable advisory email specifying compliance impacts, design tokens, and rollout windows.
Role: Staff Design Systems Architect specializing in accessible digital health interfaces and regulatory compliance.
Context
- Health Portal Module: {{portal_module_name}}
- Accessibility Deficit: {{wcag_compliance_gap}}
- Refactored UI Components: {{updated_component_suite}}
- Product Manager Recipient: {{product_manager_name}}
- Patient Cohort Constraints: {{patient_demographic_constraints}}
- Enforcement Deadline: {{migration_deadline}}
Task
Compose a detailed implementation advisory email to product managers outlining breaking design system updates, accessibility remediation, and token deprecations for patient-facing healthcare portals.
Method
- Analyze {{wcag_compliance_gap}} within the context of {{portal_module_name}} and vulnerable patient cohorts.
- Detail the exact design token and pattern enhancements introduced in {{updated_component_suite}}.
- Address {{product_manager_name}} with a clear rationale connecting accessibility to patient health equity and compliance.
- Articulate the specific interaction improvements designed for {{patient_demographic_constraints}}.
- Outline migration path steps, detailing required frontend changes and estimated implementation overhead.
- Explicitly state the hard deprecation schedule leading up to {{migration_deadline}}.
- Provide links or references to Storybook component documentation and token translation tables.
Constraints
- Total email length MUST NOT exceed 450 words.
- Technical accessibility terms (e.g., color contrast ratios, ARIA live regions) MUST be accompanied by product outcome rationale.
- MUST include a clear migration timeline table.
- Language must maintain a balance between technical precision and product enablement.
Output format
Structured email containing:
- Subject Line (clear module and compliance tag)
- Salutation
- Strategic Rationale & Compliance Trigger (1 concise paragraph)
- Key Component Enhancements (3 structured bullet points)
- Migration & Rollout Timeline (markdown table with Phase, Action, and Deadline)
- Support Resources & Next Checkpoint
Self-review
- Are all components in {{updated_component_suite}} specifically tied to remedying {{wcag_compliance_gap}}?
- Is the timeline clearly leading to {{migration_deadline}} without ambiguity?
- Did I highlight the impact on {{patient_demographic_constraints}}?
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.