Knowledge base
AuraScore 81/100

Plain Language and Accessibility Audit for Public Knowledge Bases

Audit civic knowledge base articles to ensure plain language compliance, accessibility standards, and statutory accuracy for citizens.

Use this template when preparing citizen-facing knowledge bases for accessibility compliance audits or public service portal migrations. It helps knowledge managers identify jargon, readability blockers, and structural navigation gaps across community-facing articles.

Template

Role: Senior Public Sector Knowledge Architect with deep expertise in civic communications and WCAG digital accessibility standards.

Context

  • Public Agency: {{agency_name}}
  • Primary Citizen Demographics: {{target_constituency}}
  • Reviewed Content Sample: {{sample_article_batch}}
  • Regulatory & Statutory Mandates: {{statutory_framework}}
  • Required Target Reading Level: {{target_reading_level}}
  • High-Volume Public Inquiries: {{top_citizen_queries}}

Task

Produce a comprehensive Plain Language and Accessibility Audit Report evaluating the provided citizen knowledge base articles, identifying clarity barriers, statutory misalignment, and structural readability gaps, while providing actionable remediation blueprints.

Method

  1. Analyze {{sample_article_batch}} against the target grade level defined in {{target_reading_level}} using recognized readability indices.
  2. Cross-reference article terminology against {{statutory_framework}} to detect obsolete legal references or misstated compliance rights.
  3. Evaluate the content structure for accessibility barriers, such as missing hierarchical headings, non-descriptive hyperlink text, and complex tabular data.
  4. Map article content against {{top_citizen_queries}} to determine if answers resolve citizen intent within the first two paragraphs.
  5. Identify agency jargon, administrative acronyms, and passive phrasing that impair comprehension for {{target_constituency}}.
  6. Formulate plain-language rewrite examples for the three most problematic article excerpts.
  7. Prioritize remedial action items by combining citizen impact severity and statutory compliance risk.

Constraints

  • MUST adhere strictly to the plain-language threshold specified in {{target_reading_level}}.
  • MUST NOT recommend omitting legally required procedural disclaimers under {{statutory_framework}}.
  • Technical accessibility recommendations MUST align with WCAG 2.1 Level AA criteria.
  • Avoid speculative assumptions regarding undocumented public agency policies.

Output format

Deliver an evaluation report structured as follows:

  1. Executive Summary (under 200 words)
  2. Readability & Linguistic Barrier Matrix (table: Article Title, Current Grade Level, Jargon Identified, Citizen Risk)
  3. Statutory & Structural Compliance Gaps (bulleted by mandate)
  4. Remediation Demonstrations (3 side-by-side 'Original vs. Plain-Language' rewrites)
  5. Prioritized Action Plan (categorized into Immediate, 30-Day, and 60-Day milestones)

Self-review

  • Confirm every variable in {{sample_article_batch}} and {{statutory_framework}} is evaluated.
  • Ensure all rewrite demonstrations explicitly demonstrate plain-language principles without losing legal meaning.
  • Verify that the report adheres strictly to the prescribed section ordering and length limits.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

support-success
support-knowledge-base
public-sector-nonprofit
knowledge-base
plain-language
accessibility