Web Style Guide change log

January

Updated guidance

• Added guidance for Using maps in web content
• Added guidance for Using graphics and alt text: Visual Data 

September

New content

• Added a new section for brand names and how to display them online.
• New content and contact information for Corporate branding online.

January

Updated guidance

• Added guidance on formatting 'On this page' compared to formatting lists.

May

Updated guidance

• Added guidance and examples for when and how to use an external link.
• Revised guidance on opening links in new tabs and when to open documents or files in a new tab.

March

New content

• Use camel case in email addresses that contain more than one word. Without camel case screen readers will try to read out the name of the email address as one word. They're also more difficult for sighted users to read, especially for those with learning disabilities

July

Updated guidance

• Added guidance and examples to Unique page titles. Page titles should be kept to under 70 characters. After 60 to 70 characters page titles are cut off in search engine results (depending on screen size). Page titles should be clear while using as few words as possible

New content

• Guidance on using 'Last reviewed' and 'Last updated' dates was added to Formatting web content

   

December

New content

• When and how to link to news releases
• Capitalizing documents and files
• Linking to documents and files

October

New content

Launched the Writing Guide for Indigenous Content. This guide is to help writers create content that respects the cultural integrity of Indigenous Peoples. This includes:

• How to create content for or about Indigenous Peoples
• Using Indigenous names and spellings for Indigenous people
• Choosing terminology that respects the cultural integrity of Indigenous Peoples
• Using active language and avoiding possessive terms and other harmful framing
• When and how to use proper capitalization and formatting of Indigenous terms
• How to write collaboratively and use IGBA+ to inform your content

September

New content

• How to write policy content for the web

July

Updated guidance

• How to use ministry, organization or program names
• Added examples of proper nouns for organizations and programs

New content 

• When and how to use alerts

February

The former Writing for the Web Guides were published as the Web Style Guide. The following is a log of what changes to expect in the revised guide.

Updated guidance

• For ease and consistency across the site use colons to introduce all lists
• When to use numerals versus words to make content easier to scan
• Capitalize both superior and lower courts for consistency with Government Communications and Public Engagement guidance

New content

• What an information architecture is and how to use it
• Abbreviations for provinces and territories
• How to capitalize Indigenous and local governments
• Context on when to use accordions
• Text alignment
• Using links for phone numbers for calls and sms
• Never using strikethrough in web content
• Additional context on writing for a mobile first approach
• Using 'on this page' anchor links
• Only link to secure content
• Using email address links
• Open links in the same tab
• Linking images for accessibility
• Do not repeat words at the start of each list item
• Writing out fractions
• When and how to use time zones
• Using special characters
• Using FAQs

Updated guidance

• Use sentence case for all headings and page titles. Sentence case is easier to scan and less formal, which aligns with our guidance for the tone of web content to be less formal and more direct. It also aligns with guidance from other government’s style guides
• Do not use ampersands in headings or page titles anymore unless it is part of a formal name (ie M&M’s) or when citing sources (ie Jones & Jones, 2005). Ampersands are more difficult to read and are used inconsistently across the site
• Updated guideline on including file size in links to one decimal place

New content

• Use ‘to’ instead of dashes in date, time and number ranges. Screen readers may not read dashes consistently which can lead to unclear information

Updated guidance

• The phone number format changed from parentheses and dashes, to just dashes. Using parentheses gives the impression that the area code is not required to make a call. Since 2008, only 10-digit calls are connected throughout British Columbia. Removing them makes phone numbers easier to read for people with some learning disabilities

New content

• Do not use italics even for legislation, titles or foreign words. When needed, you may use italics for scientific names. Italics are difficult to read, particularly for people with reading disabilities or low vision