Guidance for teams who think they might need an exception to 1 or more of the government's established rules for public-facing digital services and websites.
Why we have established rules for public-facing digital services and websites
We've established rules for public-facing services and websites to make sure:
- we create consistent services and websites that are easy for people to access and use; and
- teams develop products that meet the government’s digital service standards.
Why teams might need an exception
There will be few exceptions to the established rules, but on occasion teams might need to apply for 1 or more exceptions. For instance, teams might have to address unique user needs that cannot currently be addressed. Or they might have a requirement to develop a feature that doesn't currently exist.
Most of the government’s services and websites follow the established brand standards.
Apply for this exception….
- if you meet 1 of the rules for exception listed on the Apply for a brand exemption page.
Who can grant a brand exception?
Executive Council Office communications manages brand exceptions for all public-facing websites. You can email firstname.lastname@example.org to contact their team.
How to apply for a brand exception
French language exception
We've included a French language exception on this page because we get a lot of questions from project teams that do not think their service or website needs to be translated into French.
All public-facing digital services and websites should be available in English and French to meet the government's:
- Policy 1.7
- guidelines on French language services and communications; and
- digital service standard #7 to "Deliver a bilingual service."
Who managers French-language translation?
For questions about the government's requirements around French-language services and information, email the French Language Services Directorate at email@example.com.
Their team will work with you to determine next steps if you cannot comply to digital service standard #7.
Privacy Impact Assessment (PIA) exception
This heading is a bit misleading as there are no exceptions for PIAs, although some agencies don't require PIAs. We've included the PIA on this page because we get a lot of questions about them. Project teams aren't always sure if they have to complete a PIA and it is up to them to determine what their requirements are.
Who manages PIAs?
For questions about the requirements around PIAs, we recommend you contact:
- your department privacy lead; or
- email Corporate Information Management at firstname.lastname@example.org.
Security Threat Risk Assessment (STRA) exception
We've included the STRA on this page because we get questions about the requirements for them. In general, all public-facing digital services ans website should have a completed STRA.
Who manages STRAs?
For questions about the requirements around STRAs, we recommend you email the government's Security Office at email@example.com.
Style Guide and writing for the web exception
All public-facing services and websites should follow the goverment's style guide and writing for the web guidance. This established guidance helps teams produce clear, accessible and consistent guidance to meet the public's needs.
Apply for a style guide and writing for the web exception if your website or service...
- has unique user needs that are not met by the current guidance.
Who can grant an exception?
The style guide and writing for the web guidance are managed by the Executive Council office communications branch.
Technology and common platform component exceptions
The government has established technology and common platform components. We've tested and maintain these components to deliver consistent, secure services and websites.
Apply for a technology and common platform component exception if your website or service…
- cannot meet the user needs you have identified; or
- requires features beyond our current scope.
Who can grant an exception?
eServices for Citizens manages exceptions for all public-facing digital services and websites.
How to apply for a technology and common platform component exception
- Email firstname.lastname@example.org. Describe your project and the user needs you are trying to meet. Include any additional details and links.
- Our team will review your email and get in touch with you to set up a call to talk about your project.
- We will contact you once we make a decision and let you know what your next steps are.
How we make a decision
- We look at the government’s content strategy to determine if there is an existing solution. For example, does it belong on Yukon.ca, a campaign website or is it a transactional service?
- We also look at the user needs you identified and assess if there is an existing solution.
- We will work with you to determine next steps if there is an existing solution or if you need an exception.
What does it mean to have this exception?
It depends. Once we grant an exception, we'll work with you to:
- lay out exactly what you can and cannot do; and
- what you need to do to make sure you meet the government’s digital service standards.
You must follow:
- the government's service delivery process and any required service maturity assessments; and
- all the policies and guidance in the Digital Service Delivery Guide.The only way these policies do not apply, is if you have additional exceptions. For example, if you have this exception, you must follow the brand standards unless you have that exception.
If our UX manager facilitates a Discovery Workshop with your team, they will:
- ask if you have any additional exceptions; and
- they will lay out how you can proceed with your project.