Path: Home · Guides · Plain language requirements in the BC public sector

Plain language requirements in the BC public sector

Bottom line: British Columbia’s plain-language rules are more specific than most writers realize and less enforceable than most managers assume. The province publishes a numeric reading-level target, a sentence-length limit, and a 17-item checklist — all binding on government web content through the Core Policy and Procedures Manual. The accessibility legislation, by contrast, requires organizations to build a committee and publish a plan, but has not yet produced an in-force standard governing what a document must look like. Writers are caught between a specific rule that covers a narrow surface and a broad rule that specifies nothing.

This brief separates the two, translates WCAG into document-level practice, and ends with a checklist that can be run against a real file.

It describes practice, not law. It is not legal advice, and organizations subject to enforcement should confirm their obligations against the primary sources cited throughout.

1. What the province requires

The authority runs through the Core Policy and Procedures Manual, Chapter 22, which assigns responsibility for web content standards. Government Digital Experience sets and maintains those standards. Two requirements sit at the top:

  1. All B.C. government web content follows the Web Style Guide.
  2. Content is written in plain language and aims for a Grade 8 reading level or lower.

The province’s plain language checklist turns that into 17 steps. The measurable ones:

RuleThreshold
Sentence lengthIdeally no more than 15 to 20 words
Paragraph lengthOne topic, no more than 5 sentences
Reading levelGrade 8 or lower
Voice and tenseActive voice, present tense
PersonFirst and second person; conversational tone
AcronymsDefined on first use
ReviewSomeone other than the writer reads it

The remaining items are structural:

  • a descriptive page title
  • the main point first
  • scannable headings, and one clear purpose per section
  • lists in place of long sentences
  • no non-essential words
  • common words, with complex terms defined
  • inclusive language
  • no ministry or program names unless required
  • only critical information included

The content style guide adds conventions that catch writers coming from other jurisdictions:

  • Sentence case for headings, titles, buttons, and calls to action
  • Numerals for 2 and above; spell out zero and one; never open a sentence with a numeral
  • Terminology substitutions: “public service employee” rather than “public servant”; “reader” or “person” rather than “user”; “people who live in B.C.” rather than “British Columbians” or “citizens”
  • Link text that stands alone, read out of context
  • Headings that front-load the important words and avoid the question format

What this actually binds

These rules govern B.C. government web content. They do not, by their own terms, govern a Word document circulated internally, a PDF posted to a board portal, or a municipality’s committee report. In practice they are the closest thing the province has to a general house standard, and most public sector organizations that adopt anything adopt this. The distinction matters when a client asks whether something is required or recommended: for gov.bc.ca web content, required; elsewhere, the strongest available convention.

2. The accessibility layer

The Accessible British Columbia Act (SBC 2021, c 19) came into force in June 2021 and applies to public sector organizations across the province — ministries, health authorities, post-secondary institutions, school districts, municipalities, and Crown corporations.

What it requires of an organization:

ObligationDetail
Accessibility committeeAt least half the members must be people with disabilities or people who support them; at least one Indigenous member
Accessibility planIdentifies and removes barriers, developed in consultation with the committee
Feedback mechanismA way for the public and staff to report accessibility barriers

Deadlines: roughly 750 organizations in the first phase had until 1 September 2023. A second group of about 33 had until 1 September 2024. Both dates have passed; the obligations are ongoing, not one-time.

What it does not yet require. The Act names information and communications as one of the areas in which accessibility standards may be made, alongside employment, service delivery, built environment, transportation, health, education, and procurement. It is enabling legislation: the standards are made by regulation, and the information-and-communications standard is not in force. Enforcement provisions — inspection and monetary penalties — are likewise not yet active.

The practical consequence. An organization can be fully compliant with the Accessible BC Act today while publishing documents that a screen reader cannot navigate, because the Act currently obliges it to have a committee, a plan, and a feedback channel, not to meet a document standard. Anyone citing the Act as the reason a PDF must be tagged is citing the wrong instrument. The right one is below.

3. What WCAG 2.2 AA asks of documents

The B.C. government has committed to WCAG Level AA for its websites and applications — a commitment in place since 2014 and restated in the AccessibleBC Plan (2022–2025), Priority 2. The current version is WCAG 2.2, published October 2023; conforming to a newer version satisfies the earlier ones.

WCAG is written for web pages. Most public sector output is Word and PDF. The translation:

Document practiceUnderlying requirementFailure mode
Apply real heading styles, descending without skipping levelsInfo and Relationships (1.3.1); Headings and Labels (2.4.6)Bold large text is invisible to assistive technology; the document has no navigable structure
Mark table header rows; avoid merged cells and blank spacing rowsInfo and Relationships (1.3.1)Cell values lose their column and row meaning when read aloud
Write alt text that carries the informationNon-text Content (1.1.1)“Chart” as alt text discards the content; if alt text cannot be written, the information belongs in the body
Never use colour as the sole cueUse of Color (1.4.1)A red row meaning “stop” means nothing without a word
Meet contrast ratios: 4.5:1 body text, 3:1 large text and UI componentsContrast Minimum (1.4.3); Non-text Contrast (1.4.11)Light grey on white is the most common failure in designed public sector PDFs
Write link text that stands aloneLink Purpose in Context (2.4.4)“Click here” repeated eleven times, listed out of context by a screen reader
Set document language and export tagged PDFs with checked reading orderLanguage of Page (3.1.1); Info and Relationships (1.3.1)A perfectly structured Word file loses all structure at export
Give forms real labels and a logical tab orderLabels or Instructions (3.3.2); Focus Order (2.4.3)A fillable PDF whose fields announce as “edit box, edit box, edit box”

None of this changes what a document says. All of it changes who can use it.

4. Where federal and municipal expectations differ

Federal. The Canada.ca content style guide sets its own plain-language rules and applies to federal web content, not provincial. Writers moving between the two should expect divergence on terminology and capitalization rather than on principle — both target a comparable reading level and both prefer active voice and second person. The federal accessibility regime runs through the Accessible Canada Act and its regulations, which have progressed further toward enforceable standards than the provincial equivalent.

International. ISO 24495-1:2023 defines plain language through four governing principles: readers can find what they need, understand what they find, use that information, and the content is relevant to them. Its contribution is the reframing — plain language as a measured user outcome rather than a property of the text. Useful when a client wants a defensible external reference that is not tied to one jurisdiction.

Municipal. Practice varies widely and is generally set by policy rather than standard. The City of Vancouver’s language access policy (ADMIN-073, 2023) and its accessibility strategy are representative: they commit the organization to accessible and translated communication without prescribing sentence length or reading level. A writer working municipally should expect to supply the specifics themselves, usually by importing the provincial checklist.

5. Compliance checklist

Twenty items. Run against a finished document, not a draft.

Language

  • ☐ The main point appears in the first paragraph
  • ☐ Sentences average 15 to 20 words; outliers are deliberate
  • ☐ Paragraphs cover one topic and run no more than 5 sentences
  • ☐ Active voice and present tense throughout
  • ☐ The reader is addressed as “you”
  • ☐ Acronyms are defined on first use and used consistently afterwards
  • ☐ Terms a first-time reader will not know are defined
  • ☐ Reading level is Grade 8 or lower, or the exception is documented

Structure

  • ☐ The title is descriptive and works out of context
  • ☐ Headings are sentence case, front-loaded, and not questions
  • ☐ Heading levels descend in order with no skipped levels
  • ☐ Each section has one identifiable purpose
  • ☐ Lists replace sentences carrying more than three parallel items
  • ☐ Numbers follow the convention: numerals for 2 and above, zero and one spelled out
  • ☐ Nothing non-essential survived the final cut

Accessibility

  • ☐ Headings use real styles, not visual formatting
  • ☐ Tables have marked header rows, no merged cells, no blank spacing rows
  • ☐ Every image has informative alt text, and no information is conveyed by colour alone
  • ☐ Contrast meets 4.5:1 for body text and 3:1 for large text and interface components
  • ☐ Link text stands alone, and PDF exports are tagged with document language set and reading order checked

6. What the rules do not cover

Three gaps worth stating plainly, because the checklist above can be passed by a document that fails its readers.

Reading-level scores measure the wrong thing. Flesch-Kincaid and its relatives count syllables per word and words per sentence. They cannot detect a missing premise, an undefined obligation, a contradiction between paragraphs 3 and 11, or a procedure whose steps are in the wrong order. A document can be rewritten to Grade 6 and remain unusable, and the rewrite that achieved the score may have removed the qualifier that made the rule correct. The score is a smoke detector, not an inspection.

The standards say nothing about whether the document should exist. The most effective plain-language intervention on a 40-page policy is often to determine that staff need a two-page procedure and a decision table, and that the 40 pages are a reference document nobody was ever going to read start to finish. No checklist asks that question.

Compliance is not comprehension. ISO 24495-1 is right that plain language is a user outcome, and the only method that measures the outcome is watching someone use the document. Five observed readers will find defects that no automated check and no review committee will surface — and the signal is hesitation, not failure. Organizations that test their documents find this out. Organizations that audit their documents do not.

The rules are a floor. Treat them as one.

Further reading

Primary sources

Applied


Compiled September 2026 by Adam Teeling, a technical writer in Vancouver, BC. The status of standards under the Accessible British Columbia Act changes by regulation; verify section 2 against the primary sources before relying on it.