Public Health Incident App Store Listing and Accessibility Matrix
Structure localized store listing metadata and accessibility compliance for critical public health emergency apps.
Deploy this matrix prompt when launching crisis response or health awareness applications through public sector bodies. It standardizes multilingual store metadata and platform accessibility criteria.
Role: Chief Accessibility and Public Health Deployment Strategist for state and regional agencies.
Context
- Health Agency: {{agency_name}}
- Incident Context: {{health_crisis_type}}
- Alert Capabilities: {{emergency_alert_features}}
- Jurisdictional Locales: {{supported_locales}}
- Offline Capability: {{offline_functionality_level}}
- Distribution Channels: {{store_distribution_tiers}}
Task
Build a localized app storefront metadata and accessibility readiness matrix that aligns public health dissemination requirements with store listing policies, screen reader compatibility, and crisis disclosure standards.
Method
- Review {{agency_name}} credentials against platform medical disclaimer and health app verification standards.
- Map {{health_crisis_type}} communication protocols to official store search keyword rules and sensitive events guidelines.
- Evaluate {{emergency_alert_features}} for background refresh permissions, push notification critical alerts, and emergency broadcast disclosures.
- Structure localized metadata requirements across all {{supported_locales}} including title, subtitle, keywords, and accessibility descriptions.
- Audit visual assets (screenshots, preview videos) against WCAG 2.1 AA and store platform accessibility contrast standards.
- Evaluate {{offline_functionality_level}} to ensure store listing accurately discloses disconnected triage or local guidance limits.
- Map release tiers across {{store_distribution_tiers}} against store phased release and critical update channels.
- Assemble the findings into a comprehensive operational readiness matrix.
Constraints
- MUST structure the deliverable as an operational deployment matrix.
- MUST NOT generate unverified medical guidance or policy exemptions that breach platform rules.
- MUST cover both Apple App Store and Google Play listing specifications explicitly.
- Localization requirements MUST cover every locale specified in {{supported_locales}}.
Output format
- Store Deployment Overview (max 120 words)
- Storefront & Accessibility Matrix: 6-column table (Locale / Store | Metadata Field | Localized Requirement | Accessibility Standard | Platform Guideline | Validation Status)
- Critical Incident Gating Protocol (4-5 numbered verification checks prior to release)
Self-review
- Ensure all variables ({{agency_name}}, {{health_crisis_type}}, {{emergency_alert_features}}, {{supported_locales}}, {{offline_functionality_level}}, {{store_distribution_tiers}}) are addressed.
- Confirm accessibility standards align with WCAG and native platform screen reader requirements.
- Verify metadata constraints adhere strictly to character limits for both major app stores.
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.