Make digital services clearer for people in Ontario
When people interact with government and public-facing digital services they expect to complete tasks quickly and confidently. Complex language, inconsistent terminology, and hidden assumptions cost time, increase support calls, and block people from getting the benefits and services they need. Plain-language content is not just a writing preference — it’s a design decision that directly affects usability, accessibility, and compliance for Ontario digital services.
Core plain-language principles for Ontario services
Plain-language content helps users do what they came to do: find the right information, complete a form, or understand a decision. For teams building digital services in Ontario and across Canada, plain language should follow practical, measurable principles that align with accessibility and privacy expectations.
Key principles to apply:
- Put the user’s task first: Open pages and labels with the action the user needs to take, not the internal process name.
- Use short sentences and plain vocabulary: Prefer everyday words, break long sentences, and keep paragraphs focused on one idea.
- Be explicit about next steps: Tell users what will happen when they click a button, submit a form, or wait for a decision.
- Keep terminology consistent: Standardize labels, error messages, and field names across services so users don’t have to relearn terms.
Design patterns and content components that work
Plain language becomes effective when paired with strong content design patterns. These patterns help teams across Ontario replicate good writing at scale and meet expectations such as accessibility under the Accessibility for Ontarians with Disabilities Act (AODA) and privacy transparency under PHIPA and PIPEDA where applicable.
Use these content components as building blocks:
- Task-based headings: Start with what the user will accomplish, e.g., “Apply for a rebate” rather than “Rebate Application”.
- Summary bullets: Place a short summary at the top of pages that answers: who this is for, what it does, and how long it takes.
- Progressive disclosure: Show only the essential information first and provide “Learn more” sections for details, legal text, or exceptions.
- Clear error messages: Describe the problem, the cause (if known), and the exact next step the user can take to fix it.
Process: how to design, write, and maintain plain-language content
Delivering plain-language content reliably requires a repeatable process that starts with research and ends with governance. Teams in Ontario — including municipal, provincial, and non-profit providers — should build workflows that bake content quality into each stage of delivery.
Follow a practical content workflow with measurable checkpoints:
- Content research and discovery: Interview real users, review support logs, and map common tasks. Identify legal or privacy constraints early (for example, when PHIPA or PIPEDA considerations affect wording on health or personal data pages).
- Content modelling and IA: Define content types, field labels, and relationships so templates enforce plain-language patterns across pages and services.
- Write and edit in plain language: Draft content using short sentences, clear verbs, and active structures. Use readability tools to check sentence length and grade level, but prioritise clarity for the target audience over a specific score.
- Usability testing and accessibility checks: Test with representative Ontario users, including people with disabilities. Combine task-based testing with technical AODA checks.
- Analytics and continuous improvement: Monitor task completion, support contacts, and search queries to find unclear content and iterate quickly.
Writing guidelines and practical tips for content creators
Concrete rules help writers produce consistent plain-language content every time. Below are specific guidelines you can adopt immediately when creating or reviewing content for Ontario digital services.
- Prefer verbs that describe user actions: Use “renew your licence” instead of “licence renewal” where context allows.
- Avoid acronyms and jargon: Spell out terms on first use and provide short explanations for necessary technical terms.
- Use examples and numbers: Replace vague statements with examples and concrete numbers, e.g., “Allow 10 business days” rather than “Allow some time”.
- Design accessible content: Use headings for structure, meaningful link text, and descriptive alt text. Keep forms simple and label fields clearly for screen reader users.
Legal, privacy, and accessibility checkpoints for Ontario teams
Plain-language writing in Ontario digital services often intersects with legal and privacy requirements. Content teams should coordinate closely with legal and privacy leads to ensure clarity doesn’t compromise required disclosure or compliance language.
Relevant checkpoints to include in your workflow:
- AODA alignment: Ensure content structure, headings, and navigation meet accessibility requirements for people with disabilities in Ontario.
- Privacy transparency: When collecting personal data, clearly explain why the data is needed, how it will be used, and how long it will be retained. Where PHIPA or PIPEDA applies, provide plain-language summaries of rights and contacts for questions.
- Required legal notices: Convert dense legal text into short summaries and offer the full legal wording as an expandable section labelled “Full legal text” for those who need it.
- Recordkeeping: Maintain version history for public-facing content so you can show when changes were made and why — useful for audits and transparency obligations.
Testing and measuring the impact of plain-language changes
Quantifying the value of plain-language content helps secure investment and build organisational momentum. Ontario teams should use a mix of qualitative and quantitative measures to track improvements.
Useful metrics and methods:
- Task completion rates: Measure whether users can finish key tasks without contacting support.
- Time on task and abandonment rates: Shorter times and lower abandonment usually indicate clearer content and flows.
- Support contact volume: Track calls, emails, and chat messages tied to confusing pages; a drop after content updates demonstrates impact.
- User feedback and moderated testing: Run short interviews or usability sessions with diverse Ontario participants to uncover misunderstandings that analytics miss.
Scaling plain-language content across agencies and projects
Maintaining plain-language standards across multiple teams and services requires governance: style guides, content templates, shared components, and training. Consistency reduces cognitive load for users who move between services, and it makes maintenance faster for content teams.
Actions to scale effectively:
- Create a plain-language style guide: Include rules for headings, tone, terminology, and how to present legal and privacy information.
- Build content templates: Use CMS templates that enforce summaries, task headings, and FAQ structures to reduce writer variability.
- Provide training: Offer short, practical workshops for writers, designers, and developers on writing for tasks, using templates, and running quick usability checks.
- Governance and review: Establish an editorial review process that includes a plain-language check before publishing.
Plain-language content reduces friction and improves access for people across Ontario
Clear content leads to faster transactions, fewer support requests, and better outcomes for residents. By treating plain language as part of service design — and by building repeatable processes, templates, and tests — Ontario teams can deliver services that are fairer and easier to use. The technical and legal context in Canada and Ontario makes plain-language work both a usability win and a compliance necessity.
—
Work with the Association of Registered Web Developers to deliver plain-language services
The Association of Registered Web Developers produces professional technology articles and practical guidance for teams working in Ontario and across Canada. We provide resources on web development, SEO, accessibility, privacy-aware content, and more — and we offer R.W.D. certification opportunities so writers and developers can get recognised for practical skills. Visit arwd.ca to learn about certification, content guidance, and training that helps teams create plain-language digital services that meet Ontario expectations and serve residents reliably.









