ARCHIVED - CLF 2.0 Assessment Methodology
This information has been archived because it is outdated and no longer relevant.
Archived Content
Information identified as archived on the Web is for reference, research or recordkeeping purposes. It has not been altered or updated after the date of archiving. Web pages that are archived on the Web are not subject to the Government of Canada Web Standards. As per the Communications Policy of the Government of Canada, you can request alternate formats by contacting us.
Table of Contents
- Introduction
- Compliance Criteria for each Requirement and Checkpoint
- Part 1: Standard on Web Addresses
- Part 2: Standard on the Accessibility, Interoperability and Usability of Web Sites
- Part 2, R1 – Compliance with World Wide Web Consortium Priority 1 and Priority 2 checkpoints
- Checkpoint 1.1 (Priority 1): Text Equivalents
- Checkpoint 1.2 (Priority 1): Server-Side Image Maps
- Checkpoint 1.3 (Priority 1): Auditory Descriptions
- Checkpoint 1.4 (Priority 1): Synchronize Equivalents
- Checkpoint 2.1 (Priority 1): Colour
- Checkpoint 2.2 (Priority 2): Colour Contrast
- Checkpoint 3.1 (Priority 2): Bitmap Images
- Checkpoint 3.2 (Priority 2): Valid Documents
- Checkpoint 3.3 (Priority 2): Style Sheets
- Checkpoint 3.4 (Priority 2): Units
- Checkpoint 3.5 (Priority 2): Headings
- Checkpoint 3.6 (Priority 2): Lists
- Checkpoint 3.7 (Priority 2): Quotations
- Checkpoint 4.1 (Priority 1): Natural Languages
- Checkpoint 5.1 (Priority 1): Table Headers
- Checkpoint 5.2 (Priority 1): Table Structures
- Checkpoint 5.3 (Priority 2): Avoid Tables for Layout
- Checkpoint 5.4 (Priority 2): Avoid Tables for Format
- Checkpoint 6.1 (Priority 1): Organize Documents
- Checkpoint 6.2 (Priority 1): Update Dynamic Content
- Checkpoint 6.3 (Priority 1): Programmatic Objects
- Checkpoint 6.4 (Priority 2): Event Handlers
- Checkpoint 6.5 (Priority 2): Accessible Dynamic Content
- Checkpoint 7.1 (Priority 1): Flickering
- Checkpoint 7.2 (Priority 2): Blinking
- Checkpoint 7.3 (Priority 2): Moving Content
- Checkpoint 7.4 (Priority 2): Auto-Refreshing Pages
- Checkpoint 7.5 (Priority 2): Redirected Pages
- Checkpoint 8.1 (Priority 1): Embedded Objects
- Checkpoint 9.1 (Priority 1): Client-Side Image Maps
- Checkpoint 9.2 (Priority 2): Element Interfaces
- Checkpoint 9.3 (Priority 2): Logical Event Handlers
- Checkpoint 10.1 (Priority 2): Pop-up and New Windows
- Checkpoint 10.2 (Priority 2): Form Controls
- Checkpoint 11.1 (Priority 2): W3C Technologies
- Checkpoint 11.2 (Priority 2): Deprecated Elements
- Checkpoint 11.4 (Priority 1): Accessible Equivalents
- Checkpoint 12.1 (Priority 1): Frame Titles
- Checkpoint 12.2 (Priority 2): Frame Relationships
- Checkpoint 12.3 (Priority 2): Information Blocks
- Checkpoint 12.4 (Priority 2): Form Control Labels
- Checkpoint 13.1 (Priority 2): Link Targets
- Checkpoint 13.2 (Priority 2): Metadata
- Checkpoint 13.3 (Priority 2): Site Maps
- Checkpoint 13.4 (Priority 2): Navigation
- Checkpoint 14.1 (Priority 1): Writing Styles
- Part 2, R2 – Baseline technologies
- Part 2, R3 – Accessible alternate format of documents on Web sites
- Part 2, R4 – Offering information in multiple formats
- Part 2, R5 – Contrast
- Part 2, R6 – Assessing accessibility, interoperability and usability
- Part 2, R1 – Compliance with World Wide Web Consortium Priority 1 and Priority 2 checkpoints
- Part 3: Standard on Common Web Page Formats
- Part 3, R1 – Welcome Page elements
- Part 3, R2 – Content page dimensions and layout
- Part 3, R3 – "Canada" wordmark and institutional signature
- Part 3, R4 – Banner
- Part 3, R5 – Common menu bar
- Part 3, R6 – Contact Us page
- Part 3, R7 – Navigation path
- Part 3, R8 – Left menu
- Part 3, R9 – Right menu
- Part 3, R10 – Proactive Disclosure
- Part 3, R11 – Third-party symbols and hyperlinks
- Part 3, R12 – Personal information collection
- Part 3, R13 – Footer elements
- Part 3, R14 – Important Notices page
- Part 3, R15 – Third-party information notice
- Part 3, R16 – Crown copyright symbol
- Part 3, R17 – Web analyzer tools
- Part 3, R18 – Server message pages
- Part 3, Appendix A
- Part 3, Appendix B
- Part 3, Appendix C
- Part 3, Appendix D
- Part 3, Appendix E
- Part 3, Appendix F
- Part 4: Standard on Email
- Individual Weightings
- Determining the level of compliance
- Determining the level of compliance of a Web page
- Determining the level of compliance of a Web page with standard part 1
- Determining the level of compliance of a Web page with standard part 2
- Determining the level of compliance of a Web page with standard part 3
- Determining the level of compliance of a Web page with standard part 4
- Determining the overall level of compliance of a Web page
- Determining the level of compliance of the domain names for a site or sub site
- Determining the level of compliance of an email system
- Determining the level of compliance of an institution
- Determining the level of compliance of an institution with standard part 1
- Determining the level of compliance of an institution with standard part 2
- Determining the level of compliance of an institution with standard part 3
- Determining the level of compliance of an institution with standard part 4
- Determining the overall level of compliance of an institution
- Determining the level of compliance of a Web page
- Glossary
- Resources
Introduction
Purpose
The intention of the Common Look and Feel (CLF) 2.0 Assessment Methodology is to assist Government of Canada (GC) institutions with assessing the level of compliance with CLF 2.0 requirements for Web pages and applications, domain names, and email systems. The Assessment Methodology includes comprehensive compliance criteria for each CLF 2.0 requirement, weightings, and detailed instructions for determining the level of CLF 2.0 compliance.
The compliance criteria provide a common, documented, and consistent interpretation of each requirement and checkpoint of the CLF 2.0 Standards. In order to reflect the relative impact of the level of compliance, weightings are included for each Part, Requirement and checkpoint; and the compliance criteria are categorized by severity (High, Medium, and Low) of the impact.
In addition to assessing compliance, this document can also serve other purposes, such as:
- providing CLF Centres of Expertise with a detailed description of compliance for each requirement and checkpoint
- facilitating detailed discussions related to achieving CLF 2.0 compliance; and
- assisting institutions with developing comprehensive and effective CLF 2.0 quality assurance processes.
Background
One of the major challenges identified during CLF 2.0 implementation was the lack of a common and consistent understanding of what is required to achieve CLF 2.0 compliance. Even though GC institutions found many of the requirements to be clearly defined, they also found that some of the requirements (such as the accessibility requirements) were not as clear. This resulted in assessments and guidance repeatedly being sought from the Treasury Board Secretariat (TBS) CLF Office, the emergence of a variety of interpretations, and CLF 2.0 solutions being developed and assessed differently across the GC.
The Assessment Methodology is intended to be a proactive approach for resolving these issues by providing common interpretations for each CLF 2.0 requirement and checkpoint and by providing a consistent and well-defined process for determining the level of CLF 2.0 compliance.
The Assessment Methodology was developed by the Quality Assurance Working Group (QAWG) and the CLF Office, in consultation with the Access Working Group (AWG), the Technical Working Group (TW), the Internet Advisory Committee (IAC), the CLF Centres of Expertise, and TBS policy centres.
The IAC is an interdepartmental committee that provides a forum on government-wide issues associated with managing use of the Internet and intranets; increasing awareness of Internet and intranet trends and developments; and making it easier to assimilate the Internet and intranets into departments and agencies. The QAWG, AWG, and TWG are interdepartmental working groups that report to the IAC.
The CLF Centres of Expertise are functional experts that are responsible for providing advice and support for all issues relating to CLF within their respective institutions.
Compliance Criteria for each Requirement and Checkpoint
Each CLF 2.0 requirement and checkpoint has compliance criteria which have been grouped according to priority. To achieve 100% compliance with a requirement or checkpoint, all applicable criteria must be met for each priority level (High, Medium, and Low).
Where a requirement or criterion is not applicable, it must not be included in the calculation of the level of compliance.
The level of compliance with a requirement or checkpoint is determined as follows:
| Possible scenarios | All applicable High priority criteria met? | All applicable Medium priority criteria met? | All applicable Low priority criteria met? | Level of compliance |
|---|---|---|---|---|
| Scenario 1 | Yes | Yes | Yes | 100% |
| Scenario 2 | Yes | Yes | No | % compliance indicated in the Low priority section title |
| Scenario 3 | Yes | No | n/a | % compliance indicated in the Medium priority section title |
| Scenario 4 | No | n/a | n/a | 0% |
Part 1: Standard on Web Addresses
Part 1, R1 – Domain names
Part 1, R1.1 – Registration
Part 1, R1.1.1 – GC.CA
Compliance Criteria - Web page
Not included in the assessment of a Web page
Compliance Criteria – Domain names for a site or sub site
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the primary domain name for the site or sub site registered in the .gc.ca sub domain?
- Does the primary domain name resolve to the Welcome Page of the site or sub site?
- Is the primary domain name for the site or sub site composed of one of the following:
- elements or acronyms with the same meaning and spelling in both official languages (such as ec.gc.ca)?
- Bilingual or multilingual site or sub site provided by an office outside of Quebec:
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as tbs-sct.gc.ca)?
- Bilingual or multilingual site or sub site provided by an office inside of Quebec:
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as ainc-inac.gc.ca)?
- Unilingual English site:
- elements or acronyms in English only; or
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as tbs-sct.gc.ca)?
- Unilingual French site:
- elements or acronyms in French only; or
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as ainc-inac.gc.ca)?
- Main institutional site:
- Are domain names incorporating the title or abbreviation of the institution registered in commonly used Internet top-level domains where required based on a risk-based assessment?
- Multidepartment site or a site related to a marketing campaign or government initiative:
- Are domain names incorporating the name or abbreviation of the multidepartment site, marketing campaign, or government initiative registered in commonly used Internet top-level domains where feasible?
- Is each domain name that is registered in a top-level domain and resolves to the site or sub site also registered in the .gc.ca sub domain with both domain names resolving to the same location?
- Are only domain names registered in the .gc.ca sub domain used for advertising, marketing, and promotion of the site or sub site (except where authorization has been obtained via the usual communications approval process in the institution)?
Part 1, R1.1.2 – Additional Web addresses
Compliance Criteria – Web page
Not included in the assessment of a Web page
Compliance Criteria – Domain names for a site or sub site
Situation where applicable: Site
High priority criteria (failure of a criterion results in 0% compliance)
- Bilingual or multilingual site:
- Is at least one intuitive unilingual English domain name registered for the site (such as TreasuryBoardSecretariat.gc.ca)?
- Does each unilingual English domain name resolve to the English main page of the site?
- Is at least one intuitive unilingual French domain name registered for the site (such as SecretariatduConseilduTresor.gc.ca)?
- Does each unilingual French domain name resolve to the French main page of the site?
- Unilingual English site:
- Is at least one intuitive unilingual English domain name (in addition to the primary domain name) registered for the site (such as TreasuryBoardSecretariat.gc.ca)?
- Does each unilingual English domain name (excluding the primary domain name) resolve to the main page of the site or sub site?
- Unilingual French site:
- Is at least one intuitive unilingual French domain name (in addition to the primary domain name) registered for the site (such as SecretariatduConseilduTresor.gc.ca)?
- Does each unilingual French domain name (excluding the primary domain name) resolve to the main page of the site?
Part 1, R1.2 – Cybersquatting
Compliance Criteria – Web page
Not included in the assessment of a Web page
Compliance Criteria – Domain names for a site or sub site
Situation where applicable: Site or sub site where one or more domain names that could be perceived as being associated to the site or sub site are registered by a private individual or entity with apparent bad-faith intent
High priority criteria (failure of a criterion results in 0% compliance)
- Is each domain name that could be perceived as being associated to the site or sub site and is registered by a private individual or entity with apparent bad-faith intent being pursued using the established redress provisions of the governing body that oversees the Internet domain in question (where required based on a risk-based analysis)?
Part 1, R2 – Page addresses
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Are all components of the URL (including the query string), that the browser uses
to access the page (normally displayed in the address bar), implemented using one or more of the following approaches (excluding query parameters and variables that cannot be controlled such as
user-specified search terms and core parameters of 3rd party frameworks):
- English page:
- elements or acronyms in English only where the French version of the page uses equivalent elements or acronyms in French only for the same URL components?
- French page:
- elements or acronyms in French only where the English version of the page consists of equivalent elements or acronyms in English only for the same URL components?
- elements or acronyms spelled the same in both official languages (such as /options/ that could have menu-eng.htm and menu-fra.html within it)?
- Page provided by an office outside of Quebec:
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as /links-liens/ that could have fip-pcim-eng.html and fip-pcim-fra.html files within it)?
- Page provided by an office inside of Quebec:
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as /liens-links/ that could have pcim-fip-fra.html and pcim-fip-eng.html files within it)?
- elements that are language neutral, such as numbers (such as /100/ that could have 123-eng.html and 123-fra.html within it); alphabetic characters (such as /aaa/ that could have abc-eng.html and abc-fra.html within it) or an alphanumeric combination (such as /10aa1/ that could have 34de1-eng.html and 34de1-fra.html within it)?
- English page:
- Bilingual or multilingual page:
- Are all components of the URL (including the query string), that the browser uses to access the page (normally displayed in the address bar), free of elements, acronyms, language suffixes, and language codes that indicate that the page is specific to one language?
- English page:
- Is the language of the page conveyed by at least one of the following approaches:
- the file name is composed exclusively of elements or acronyms in English only that are not spelled the same in French (such as links.html);
-
one of the folder names is "english" or the "eng" three-letter ISO 639-2/T language code with subsequent folder names and the file name being composed exclusively of
at least one of the following:
- elements or acronyms in English only (such as /eng/links.html or /english/links.html);
- elements or acronyms spelled the same in both official languages (such as /eng/menu.html or /english/menu.html); or
- elements that are language neutral, such as numbers (for example, /eng/123.html or /english/123.html); alphabetic characters (for example, /eng/abc.html or /english/abc.html) or an alphanumeric combination (for example, /eng/34de1.html or /english/34de1.html)?
- the file name is terminated by "-eng" (such as menu-eng.html); or
- the "eng" three-letter ISO 639-2/T language code is a parameter or variable in one of the first three parameter/variable pairs of the query string (such as index.cfm?lang=eng)?
- Bilingual or multilingual site:
- Is the approach for conveying the language of the page the same approach that is used to convey the language of the French version of the page?
- Is the language of the page conveyed by at least one of the following approaches:
- French page:
- Is the language of the page conveyed by at least one of the following approaches:
- the file name is composed exclusively of elements or acronyms in French only that are not spelled the same in English (such as liens.html);
-
one of the folder names is "francais" or the "fra" three-letter ISO 639-2/T language code with subsequent folder names and the file name being composed exclusively
of at least one of the following:
- elements or acronyms in French only (such as /fra/liens.html or /francais/liens.html);
- elements or acronyms spelled the same in both official languages (such as /fra/menu.html or /francais/menu.html); or
- elements that are language neutral, such as numbers (for example, /fra/123.html or /francais/123.html); alphabetic characters (for example, /fra/abc.html or /francais/abc.html) or an alphanumeric combination (for example, /fra/34de1.html or /francais/34de1.html)?
- the file name is terminated by "-fra" (such as menu-fra.html); or
- the "fra" three-letter ISO 639-2/T language code is a parameter or variable in one of the first three parameter/variable pairs of the query string (such as index.cfm?lang=fra)?
- Bilingual or multilingual site:
- Is the approach for conveying the language of the page the same approach that is used to convey the language of the English version of the page?
- Is the language of the page conveyed by at least one of the following approaches:
- Page in a language other than English or French:
- Is the language of the page conveyed by at least one of the following approaches:
- the file name is composed exclusively of elements or acronyms in the language of the page (such as nexo.html);
-
one of the folder names is the language of the page (such as "espanol") or the three-letter ISO 639-2/T language code representing the language of the
page (such as "spa") with subsequent folder names and the file name being composed exclusively of at least one of the following:
- elements or acronyms in the language of the page only (such as /spa/nexo.html or /espanol/nexo.html);
- elements or acronyms spelled the same in both official languages (such as /spa/menu.html or /espanol/menu.html); or
- elements that are language neutral, such as numbers (for example, /spa/123.html or /espanol/123.html); alphabetic characters (for example, /spa/abc.html or /espanol/abc.html) or an alphanumeric combination (for example, /spa/34de1.html or /espanol/34de1.html)?
- Page provided by an office outside of Quebec:
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as /spa/links-liens.html or /espanol/links-liens.html)?
- Page provided by an office inside of Quebec:
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as /spa/liens-links.html or /espanol/liens-links.html)?
- the file name is terminated by a hyphen followed by the three-letter ISO 639-2/T language code representing the language of the page (such as menu-spa.html); or
- the three-letter ISO 639-2/T language code representing the language of the page is a parameter or variable in one of the first three parameter/variable pairs of the query string (such as index.cfm?lang=spa)?
- Is the language of the page conveyed by at least one of the following approaches:
Medium priority criteria (failure of a criterion results in no more than 90% compliance)
- English page:
- Is the "eng" three-letter ISO 639-2/T language code the only code that conveys the language of the page in the URL (including the query string), that the browser uses to access the page (normally displayed in the address bar)?
- French page:
- Is the "fra" three-letter ISO 639-2/T language code the only code that conveys the language of the page in the URL (including the query string), that the browser uses to access the page (normally displayed in the address bar)?
- Page in a language other than English or French:
- Is the three-letter ISO 639-2/T language code representing the language of the page (such as "spa"), the only code that conveys the language of the page in the URL (including the query string), that the browser uses to access the page (normally displayed in the address bar)?
- Are all components of the URLs (including the query strings), that the browser uses to access each supporting file associated with the page, implemented
using one or more of the following approaches (excluding query parameters and variables that cannot be controlled such as user-specified search terms and core parameters of 3rd party frameworks):
- English supporting file:
- elements or acronyms in English only where the French version of the supporting file uses equivalent elements or acronyms in French only for the same URL components?
- French supporting file:
- elements or acronyms in French only where the English version of the supporting file consists of equivalent elements or acronyms in English only for the same URL components?
- elements or acronyms spelled the same in both official languages (such as /options/ that could have image-eng.gif and image-fra.gif within it)?
- Supporting file for a page provided by an office outside of Quebec:
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as /links-liens/ that could have fip-pcim-eng.gif and fip-pcim-fra.gif files within it)?
- Supporting file for a page provided by an office inside of Quebec:
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as /liens-links/ that could have pcim-fip-fra.gif and pcim-fip-eng.gif files within it)?
- elements that are language neutral, such as numbers (such as /100/ that could have 123-eng.gif and 123-fra.gif within it); alphabetic characters (such as /aaa/ that could have abc-eng.htm and abc-fra.htm within it) or an alphanumeric combination (such as /10aa1/ that could have 34de1-eng.gif and 34de1-fra.gif within it)?
- English supporting file:
- Bilingual, multilingual, or language neutral supporting files associated with the page:
- Are all components of the URLs (including the query strings), that the browser uses to access each supporting file, free of elements, acronyms, language suffixes, and language codes that indicate that the supporting file is specific to one language?
- English supporting files associated with the page:
- Is the language of each supporting file conveyed by at least one of the following approaches:
- the file name is composed exclusively of elements or acronyms in English only that are not spelled the same in French (such as links.gif);
-
one of the folder names is "english" or the "eng" three-letter ISO 639-2/T language code with subsequent folder names and the file name being composed exclusively of
at least one of the following:
- elements or acronyms in English only (such as /eng/links.gif or /english/links.gif);
- elements or acronyms spelled the same in both official languages (such as /eng/menu.gif or /english/menu.gif); or
- elements that are language neutral, such as numbers (for example, /eng/123.gif or /english/123.gif); alphabetic characters (for example, /eng/abc.gif or /english/abc.gif) or an alphanumeric combination (for example, /eng/34de1.gif or /english/34de1.gif)?
- the file name is terminated by "-eng" (such as menu-eng.gif); or
- the "eng" three-letter ISO 639-2/T language code is a parameter or variable in one of the first three parameter/variable pairs of the query string (such as index.js?lang=eng)?
- Is the "eng" three-letter ISO 639-2/T language code the only code that conveys the language of the page in the URL (including the query string), that the browser uses to access the supporting file?
- Bilingual or multilingual site:
- Is the approach for conveying the language of the supporting file the same approach that is used to convey the language of the French version of the supporting file?
- Is the language of each supporting file conveyed by at least one of the following approaches:
- French supporting files associated with the page:
- Is the language of each supporting file conveyed by at least one of the following approaches:
- the file name is composed exclusively of elements or acronyms in French only that are not spelled the same in English (such as liens.gif);
-
one of the folder names is "francais" or the "fra" three-letter ISO 639-2/T language code with subsequent folder names and the file name being composed exclusively
of at least one of the following:
- elements or acronyms in French only (such as /fra/liens.gif or /francais/liens.gif);
- elements or acronyms spelled the same in both official languages (such as /fra/menu.gif or /francais/menu.gif); or
- elements that are language neutral, such as numbers (for example, /fra/123.gif or /francais/123.gif); alphabetic characters (for example, /fra/abc.gif or /francais/abc.gif) or an alphanumeric combination (for example, /fra/34de1.gif or /francais/34de1.gif)?
- the file name is terminated by "-fra" (such as menu-fra.gif); or
- the "fra" three-letter ISO 639-2/T language code is a parameter or variable in one of the first three parameter/variable pairs of the query string (such as index.js?lang=fra)?
- Is the "fra" three-letter ISO 639-2/T language code the only code that conveys the language of the page in the URL (including the query string), that the browser uses to access the supporting file?
- Bilingual or multilingual site:
- Is the approach for conveying the language of the supporting file the same approach that is used to convey the language of the English version of the supporting file?
- Is the language of each supporting file conveyed by at least one of the following approaches:
- Supporting files associated with the page that are in a language other than English or French:
- Is the language of each supporting file conveyed by at least one of the following approaches:
- the file ironyms in the language of the supporting file (such as nexo.gif);
-
one of the folder names is the language of the supporting file (such as "espanol") or the three-letter ISO 639-2/T language code representing the
language of the supporting file (such as "spa") with subsequent folder names and the file name being composed exclusively of at least one of the following:
- elements or acronyms in the language of the supporting file only (such as /spa/nexo.gif or /espanol/nexo.gif);
- elements or acronyms spelled the same in both official languages (such as /spa/menu.gif or /espanol/menu.gif); or
- elements that are language neutral, such as numbers (for example, /spa/123.gif or /espanol/123.gif); alphabetic characters (for example, /spa/abc.gif or /espanol/abc.gif) or an alphanumeric combination (for example, /spa/34de1.gif or /espanol/34de1.gif)?
- the file name is terminated by a hyphen followed by the three-letter ISO 639-2/T language code representing the language of the supporting file (such as menu-spa.gif); or
- the three-letter ISO 639-2/T language code representing the language of the supporting file is a parameter or variable in one of the first three parameter/variable pairs of the query string (such as index.js?lang=spa)?
- Is the three-letter ISO 639-2/T language code representing the language of the supporting file (such as "spa"), the only code that conveys the language of the page in the URL (including the query string), that the browser uses to access the supporting file?
- Is the language of each supporting file conveyed by at least one of the following approaches:
Compliance Criteria – Domain names for a site or sub site
Not included in the assessment of the domain names for a site or sub site
Part 2: Standard on the Accessibility, Interoperability and Usability of Web Sites
Part 2, R1 – Compliance with World Wide Web Consortium
Priority 1 and Priority 2 checkpoints
The compliance criteria herein reflect the guidance provided in WCAG 1.0 and related techniques. Where sufficient guidance is not provided by WCAG 1.0, the compliance criteria reflects WCAG 2.0 guidance for forwards compatibility.
Please also note that the checkpoints below, in some cases, also include requirements stemming from the "Directive on the Use of Official Languages on Web Sites". They are included for convenience as adherence to Official Languages requirements is mandatory in the Government of Canada context, and Official Languages requirements are included in the CLF Standards. Additionally, they represent an element of accessibility not included in the WCAG 1.0 Checkpoints.
Checkpoint 1.1 (Priority 1): Text Equivalents
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Are "alt" attributes provided for all "img" elements?
- Are text equivalents provided for all meaningful information conveyed by "img" elements?
- Are text equivalents (such as text-based versions or parent container title attribute values) provided for all meaningful information conveyed by images that are loaded through CSS?
- Are text equivalents provided for all meaningful information conveyed by programmatic objects (such as Flash objects, media players, and other interface objects)?
- Are transcripts provided for all meaningful visual and audio information conveyed by multimedia?
- Are text equivalents provided for all programmatic object interface controls (such as media player buttons)?
- Are brief descriptions (alt text) and full descriptions (such as data tables or long descriptions) provided for all images that convey more meaningful information than can be conveyed using alt text alone (such as charts and graphs)?
- English page:
- Are all text equivalents provided in English only?
- French page:
- Are all text equivalents provided in French only?
- Page in a language other than English or French:
- Are all text equivalents provided in only the language of the page?
- Bilingual or multilingual page for a site provided by an office located outside of Quebec:
- Are all text equivalents provided in English first and French second?
- Bilingual or multilingual page for a site provided by an office located inside of Quebec:
- Are all text equivalents provided in French first and English second?
Medium priority criteria (failure of a criterion results in no more than 33.3% compliance)
- Is all meaningful information embedded in images conveyed through the associated text equivalents in the logical reading order?
Low priority criteria (failure of a criterion results in no more than 66.7% compliance)
- Are null (alt="") text equivalents provided for all "img" elements that do not convey meaningful information or are used solely for decorative purposes so they can be ignored by adaptive technologies?
Checkpoint 1.2 (Priority 1): Server-Side Image Maps
Compliance Criteria – Web page
Situation where applicable: Page contains at least one server-side image map
High priority criteria (failure of a criterion results in 0% compliance)
- Are redundant text links provided for the active regions of each server-side image map?
Checkpoint 1.3 (Priority 1): Auditory Descriptions
Compliance Criteria – Web page
Situation where applicable: Page contains multimedia
High priority criteria (failure of a criterion results in 0% compliance)
- Is equivalent information provided through the main audio track or a separate auditory description for all meaningful visual information conveyed through multimedia?
Checkpoint 1.4 (Priority 1): Synchronize Equivalents
Compliance Criteria – Web page
Situation where applicable: Page contains multimedia
High priority criteria (failure of a criterion results in 0% compliance)
- Are equivalent captions provided for all meaningful audio information conveyed through multimedia?
- Are all captions synchronized with the associated meaningful audio information conveyed through multimedia?
- Are all captions at least one phrase in length (where sufficient meaningful audio information exists)?
- Is all equivalent information conveyed through the main audio track and any separate auditory descriptions synchronized with the associated meaningful visual information conveyed through multimedia?
Checkpoint 2.1 (Priority 1): Colour
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of instances where meaningful information is conveyed exclusively through colour (such as which form fields are mandatory)?
Checkpoint 2.2 (Priority 2): Colour Contrast
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Meaningful text that is embedded in an image and is smaller than equivalent 18 point and 14 point bold fonts
(at the normal text size setting):
- Is at least a 4:1 contrast ratio achieved between the meaningful text and the associated backgrounds?
- Meaningful text that is embedded in an image and is at least as large as an equivalent 18 point or 14 point
bold font (at the normal text size setting):
- Is at least a 3:1 contrast ratio achieved between the meaningful text and the associated backgrounds?
- Meaningful information (other than text) embedded in an image:
- Is at least a 3:1 contrast ratio achieved between the meaningful information and the associated backgrounds?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
-
Meaningful text that is embedded in an image and is smaller than
equivalent 18 point and 14 point bold fonts (at the normal text size setting):
- Is at least a 4.25:1 contrast ratio achieved between the meaningful text and the associated backgrounds?
Low priority criteria (failure of a criterion results in no more than 75% compliance)
- Meaningful text that is embedded in an image and is smaller than equivalent 18 point and 14 point bold fonts
(at the normal text size setting):
- Is at least a 4.5:1 contrast ratio achieved between the meaningful text and the associated backgrounds?
Checkpoint 3.1 (Priority 2): Bitmap Images
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of images that are the sole means of visually conveying meaningful information where markup and CSS could be used instead of or at least in addition to the images to convey the same meaningful information (excluding the institutional signature and the "Canada" wordmark)?
Checkpoint 3.2 (Priority 2): Valid Documents
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Page does not contain a frameset:
- Does the page validate to XHTML 1.0 Strict or a language described by World Wide Web Consortium (W3C) Recommendations?
- Page contains a frameset:
- Does the frameset validate to XHTML 1.0 Frameset or a language described by World Wide Web Consortium (W3C) Recommendations?
- Does each frame validate to XHTML 1.0 Strict or a language described by World Wide Web Consortium (W3C) Recommendations?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Does all CSS (including associated CSS files and CSS embedded in the page) validate to the most current and stable version of CSS?
Checkpoint 3.3 (Priority 2): Style Sheets
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of tables used for layout (such as tables used to control the layout and positioning of blocks of text, visual elements, and form controls)?
- Is the page free of deprecated markup that is used to control the page layout or presentation?
Medium priority criteria (failure of a criterion results in no more than 33.3% compliance)
- Is the page free of images that are used solely to control the page layout?
Checkpoint 3.4 (Priority 2): Units
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Are units that are relative to the browser text size setting (%, em, and ex) used to control the size of all text elements? For example, does all text scale in size when using the "Text Size" feature in Internet Explorer?
- Are units that are relative to the browser text size setting (%, em, and ex) used to control the size of all form controls that contain text? For example, do all form controls that can contain text scale in size when using the "Text Size" feature in Internet Explorer?
- Are units that are relative to the browser text size setting (%, em, and ex) used to control the size of all images that convey meaningful information or is markup and CSS used instead of or at least in addition to the images to convey the same meaningful information (excluding the institutional signature and the "Canada" wordmark)?
- Does the page scale to at least 200% of the normal text size setting without overlapping or clipping that negatively impacts the legibility of any meaningful information?
Checkpoint 3.5 (Priority 2): Headings
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is heading markup used?
- Is the page free of duplicate headings at the same heading level in the same section/sub-section? For example, is the page free of level 3 headings ("h3") that contain identical text and are grouped by the same level 2 heading ("h2")?
- Is the page free of heading elements that do not convey both meaningful information and document structure?
- Is the page free of heading elements that are associated to sections that do not contain meaningful information? For example, is the page free of level 2 headings ("h2") where meaningful information has not been provided before the next level 2 ("h2") or level 1 ("h1") heading?
- Is the page free of heading elements that are used solely for visual purposes?
- Are all headings that are hidden using CSS able to be read by screen readers? For example, is the page free of headings that have been hidden using "display: none" or "visibility: hidden"?
- Content page:
- Are "h1" elements provided at the beginning of the common menu bar, the left side menu, and the content area?
- Are all section/sub-section headings provided in only the language of the page?
- Welcome Page for a bilingual or multilingual site provided by an office located outside of Quebec:
- Is an "h1" element provided at the beginning of the message area?
- Are all section/sub-section headings provided in both official languages?
- Are all section/sub-section headings provided in English first and French second?
- Welcome Page for a bilingual or multilingual site provided by an office located inside of Quebec:
- Is an "h1" element provided at the beginning of the message area?
- Are all section/sub-section headings provided in both official languages?
- Are all section/sub-section headings provided in French first and English second?
- Welcome Page for a unilingual site:
- Is an "h1" element provided at the beginning of the message area?
- Are all section/sub-section headings provided in only the language of the page (except for the sub-section heading for the Official Languages notice in the alternate official language)?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Are all section/sub-section headings identified using heading markup?
- Is heading markup used in sequence without skipping levels?
- Are all section/sub-section relationships properly identified using heading markup? For example, if a section begins with a level 3 heading then each sub-section of the level 3 heading section would begin with a level 4 heading, and each sub-section of the level 4 heading sub-sections would begin with a level 5 heading.
Checkpoint 3.6 (Priority 2): Lists
Compliance Criteria – Web page
Situation where applicable: Page contains list markup or at least one list
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of list markup that is used solely for visual purposes (such as indenting)?
- Is the page free of content that visually emulates unordered lists, ordered lists, or definition lists without list markup being used (excluding any content where data tables or heading elements are used instead of list markup)?
- Are all items from the same list grouped together within the same list element ("ol", "ul", or "dl") rather than being split into separate list elements?
- Is each sub list nested correctly in the associated parent list (in other words are the items in each sub list grouped into a new list element that is nested within a list item element of the parent list)?
- Is the page free of nested lists that are not immediately preceded by meaningful information that identifies the contents of the nested list and is contained within the same parent list item as the nested list (in other words is the page free of list item elements that that begin with the list element of a nested list)?
- Is the page free of list item elements ("li", "dt", or "dd") that do not contain any content?
- Is list markup used for all content that is explicitly identified in the surrounding or referring text as being in a list (excluding any content where data tables or heading elements are used instead of list markup)?
Medium priority criteria (failure of a criterion results in no more than 66.7% compliance)
- Is list markup used for each series of like content that conveys meaningful information (such as links, names, or addresses) and is not part of a sentence (excluding any series where data tables or heading elements are used instead of list markup)?
- Is definition list markup used for each series of like title/value pairs that conveys meaningful information (such as term/definition pairs in a glossary or speaker/speech pairs in a transcript) and is not part of a sentence (excluding any series where data tables or heading elements are used instead of list markup)?
Checkpoint 3.7 (Priority 2): Quotations
Compliance Criteria – Web page
Situation where applicable: Page contains quotation markup or at least one quotation
High priority criteria (failure of a criterion results in 0% compliance)
- Are "q" elements used for all inline quotations and "blockquote" elements used for all quotation blocks?
- Is the beginning and end of each quotation identified using quotation markup (in other words does the quotation markup enclose only the quotation and none of the surrounding text)?
- Is the page free of quotation markup that is used solely for visual purposes (such as indenting)?
- Is the "cite" attribute used to identify the source URL for each quotation where a Web page reference exists?
Checkpoint 4.1 (Priority 1): Natural Languages
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Are all changes in the natural language of the page programmatically identified using "
lang" for each element where the language change occurs (excluding language changes that occur within a bilingual or multilingual attribute value)? - Do the values specified for each "
lang" attribute correctly identify the language of the associated content? For example, is a value of "en" used to identify English content and a value of "fr" used to identify French content?
Checkpoint 5.1 (Priority 1): Table Headers
Compliance Criteria – Web page
Situation where applicable: Page contains at least one data table
High priority criteria (failure of a criterion results in 0% compliance)
- Data table:
- Is at least one header cell that conveys meaningful information provided for each data cell?
- Are "th" elements used for each header cell that conveys meaningful information?
- Are "td" elements used for each header cell that does not convey meaningful information (such as empty cells in a header row or column)?
- Are "td" elements used for each data cell?
Checkpoint 5.2 (Priority 1): Table Structures
Compliance Criteria – Web page
Situation where applicable: Page contains at least one data table with two or more logical levels of row or column headers
High priority criteria (failure of a criterion results in 0% compliance)
- Data table with two or more logical levels of row or column headers:
- Is each header cell that conveys meaningful information programmatically associated to the related data cells using attributes such as "scope", "id"/"headers", or "axis"?
Checkpoint 5.3 (Priority 2): Avoid Tables for Layout
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Page is not free of layout tables:
- Is the page free of layout tables that do not make sense when linearized (in other words read left to right, row by row)?
Medium priority criteria (failure of a criterion results in no more than 25% compliance)
- Is the page free of layout tables?
Checkpoint 5.4 (Priority 2): Avoid Tables for Format
Compliance Criteria – Web page
Situation where applicable: Page contains at least one layout table
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of layout tables that include data table-specific structural markup (such as "th", "axis", "scope", "id"/"headers", "thead", "tfoot", "tbody", "col", and "colgroup")?
Checkpoint 6.1 (Priority 1): Organize Documents
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is all meaningful information accessible and perceivable in the correct order when CSS is disabled or not supported (including meaningful information conveyed by images loaded through CSS)?
Checkpoint 6.2 (Priority 1): Update Dynamic Content
Compliance Criteria – Web page
Situation where applicable: Page contains dynamic content
High priority criteria (failure of a criterion results in 0% compliance)
- Are the text equivalents for all non-text dynamic content (such as animated and changing images) always conveying the same meaningful information as the associated non-text dynamic content?
Checkpoint 6.3 (Priority 1): Programmatic Objects
Compliance Criteria – Web page
Situation where applicable: Page contains scripting or at least one programmatic object
High priority criteria (failure of a criterion results in 0% compliance)
- Is all meaningful information conveyed in the correct order when scripting or programmatic objects are disabled or not supported?
- Is all important functionality (or equivalent functionality) provided when scripting or programmatic objects are disabled or not supported?
- Is the page free of objects that do not function correctly when scripting or programmatic objects are disabled or not supported?
Checkpoint 6.4 (Priority 2): Event Handlers
Compliance Criteria – Web page
Situation where applicable: Page contains at least one event handler
High priority criteria (failure of a criterion results in 0% compliance)
- Is all important functionality that is event handler-dependent both accessible and operable when using only a keyboard or keyboard emulation?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Is all functionality that is event handler-dependent implemented using device independent event handlers or a combination of event handlers that enable the functionality to be device-independent (except for keyboard-only functionality such as completing text input fields)?
Checkpoint 6.5 (Priority 2): Accessible Dynamic Content
Compliance Criteria – Web page
Situation where applicable: Page contains inaccessible dynamic content or at least one frameset
High priority criteria (failure of a criterion results in 0% compliance)
- Are alternative accessible presentations for each frameset provided through the "noframes" element?
- Are alternative accessible presentations or links to pages with equivalent information provided for all dynamic content that cannot be made accessible?
Checkpoint 7.1 (Priority 1): Flickering
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of content that flickers (flashes more than three times in any one second period)?
Checkpoint 7.2 (Priority 2): Blinking
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of content that blinks (alternates between visible and invisible at a regular rate)?
Checkpoint 7.3 (Priority 2): Moving Content
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of movement that lasts for more than three seconds or is a mechanism provided to freeze such movement?
- Is the page free of movement that periodically restarts or is a mechanism provided to freeze such movement?
Checkpoint 7.4 (Priority 2): Auto-Refreshing Pages
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of automatic updates (such as automatic page refreshes using meta-refresh or JavaScript) or is a mechanism provided to prevent the automatic updates?
Checkpoint 7.5 (Priority 2): Redirected Pages
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of automatic client-side redirects (such as a meta-refresh redirect)?
Checkpoint 8.1 (Priority 1): Embedded Objects
Compliance Criteria – Web page
Situation where applicable: Page contains scripting or at least one programmatic object
High priority criteria (failure of a criterion results in 0% compliance)
- Is all meaningful information that is conveyed through scripting or programmatic objects both accessible and perceivable when using adaptive technologies (such as screen readers and screen magnification software)?
- Is all important functionality provided through scripting or programmatic objects both accessible and operable when using adaptive technologies (such as screen readers and alternate input devices)?
- Is the page free of scripting and programmatic objects that interfere with adaptive technologies in the following ways:
- trapping focus;
- preventing navigation to an area of the page;
- disrupting adaptive technology functionality;
- providing audio that disrupts or interferes with hearing other audio information;
- changing the context without a user request;
- performing page updates that cannot be detected by screen readers or other adaptive technologies (such as initiating AJAX-based page updates using XMLHttpRequest) without providing an accessible alternative; and
- hiding meaningful information unnecessarily from screen readers and other adaptive technologies (such as using "display: none" or "visibility: hidden")?
Checkpoint 9.1 (Priority 1): Client-Side Image Maps
Compliance Criteria – Web page
Situation where applicable: Page contains at least one image map
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of server-side image maps where the regions can be defined with an available geometric shape?
Checkpoint 9.2 (Priority 2): Element Interfaces
Compliance Criteria – Web page
Situation where applicable: Page contains at least one programmatic object with its own custom interface
High priority criteria (failure of a criterion results in 0% compliance)
- Is all important functionality provided through custom scripting or programmatic object interfaces accessible and operable when using only a keyboard or keyboard emulation?
- Is the page free of custom scripting or programmatic object interfaces that interfere in the following ways when using only a keyboard or keyboard
emulation?
- trapping focus; and
- preventing navigation to an area of the page?
Checkpoint 9.3 (Priority 2): Logical Event Handlers
Compliance Criteria – Web page
Situation where applicable: Page contains at least one event handler
High priority criteria (failure of a criterion results in 0% compliance)
- Is all important functionality that is event handler-dependent both accessible and operable when using only a keyboard or keyboard emulation?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Is all functionality that is event handler-dependent implemented using device-independent event handlers or a combination of event handlers that enable the functionality to be device-independent (except for keyboard-only functionality such as completing text input fields)?
Checkpoint 10.1 (Priority 2): Pop-up and New Windows
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of links that open in new windows or tabs without advance warning?
- Is the page free of new windows, tabs, and JavaScript alerts/dialogs that open when the state of a form control changes (excluding submit buttons)?
- Is the page free of new windows, tabs, and JavaScript alerts/dialogs that open as a result of generic mouse or keyboard actions (such as moving the mouse pointer or pressing a key on the keyboard)?
- Is the page free of new windows, tabs, and JavaScript alerts/dialogs that open as a result of an element gaining or losing focus?
- Is the page free of new windows, tabs, and JavaScript alerts/dialogs that open automatically without an explicit action being performed?
Medium priority criteria (failure of a criterion results in no more than 25% compliance)
- Is the page free of links that open in new windows or tabs where the advance warning is provided near the link but not in the link text or the title value?
Low priority criteria (failure of a criterion results in no more than 50% compliance)
- Is the page free of links that open in new windows or tabs where the advance warning was provided in the link text but not in the non-null title value?
Checkpoint 10.2 (Priority 2): Form Controls
Compliance Criteria – Web page
Situation where applicable: Page contains at least one Web form
High priority criteria (failure of a criterion results in 0% compliance)
- Is at least one unique label that conveys meaningful information provided for each form control?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Is all text that is unique to one form control (including inline error messages) provided immediately preceding the associated form control on either the same line or on the preceding line (excluding radio buttons, checkboxes, submit buttons, reset buttons, and button elements)?
Checkpoint 11.1 (Priority 2): W3C Technologies
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Page does not contain a frameset:
- Is the full DOCTYPE declaration for XHTML 1.0 Strict or the latest supported version of a language described by World Wide Web Consortium (W3C) Recommendations provided as the first element on the page?
- Page contains a frameset:
- Is the full DOCTYPE declaration for XHTML 1.0 Frameset or the latest supported version of a language described by World Wide Web Consortium (W3C) Recommendations provided as the first element for each frameset?
- Is the full DOCTYPE declaration for XHTML 1.0 Strict or the latest supported version of a language described by World Wide Web Consortium (W3C) Recommendations provided as the first element for each frame?
- Is the page free of elements and attributes that are not part of a language described by World Wide Web Consortium (W3C) Recommendations (such as the "embed" element)?
References
Checkpoint 11.2 (Priority 2): Deprecated Elements
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of deprecated elements?
- Is the page free of deprecated attributes?
Checkpoint 11.4 (Priority 1): Accessible Equivalents
Compliance Criteria – Web page
Situation where applicable: Page contains at least one non-W3C technology that is causing a large proportion of the page to be inaccessible
High priority criteria (failure of a criterion results in 0% compliance)
- Is an alternative page provided which uses World Wide Web Consortium (W3C) technologies, is accessible, has equivalent information and functionality, and is updated as often as the inaccessible (original) page?
- Is a link to the alternative page prominently displayed at the top of the content area?
Checkpoint 12.1 (Priority 1): Frame Titles
Compliance Criteria – Web page
Situation where applicable: Page contains at least one frameset
High priority criteria (failure of a criterion results in 0% compliance)
- Are title attribute values that facilitate frame identification and navigation provided for all frames in each frameset?
Checkpoint 12.2 (Priority 2): Frame Relationships
Compliance Criteria – Web page
Situation where applicable: Page contains at least one frameset
High priority criteria (failure of a criterion results in 0% compliance)
- Is the purpose of each frame and how the frames relate to each other obvious from frame title attribute values alone or is this information available through "longdesc" attributes that are provided for all frames in each frameset?
Checkpoint 12.3 (Priority 2): Information Blocks
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is heading markup used?
- Are data tables used for all tabular data?
- Is the page free of duplicate headings at the same heading level in the same section/sub-section? For example, is the page free of level 3 headings ("h3") that contain identical text and are grouped by the same level 2 heading ("h2")?
- Is the page free of heading elements that do not convey both meaningful information and document structure?
- Is the page free of heading elements that are associated to sections that do not contain meaningful information? For example, is the page free of level 2 headings ("h2") where meaningful information has not been provided before the next level 2 ("h2") or level 1 ("h1") heading?
- Is the page free of heading elements that are used solely for visual purposes?
- Are all headings that are hidden using CSS able to be read by screen readers? For example, is the page free of headings that have been hidden using "display: none" or "visibility: hidden"?
- Content page:
- Are "h1" elements provided at the beginning of the common menu bar, the left side menu, and the content area?
- Are all section/sub-section headings provided in only the language of the page?
- Welcome Page for a bilingual or multilingual site provided by an office located outside of Quebec:
- Is an "h1" element provided at the beginning of the message area?
- Are all section/sub-section headings provided in both official languages?
- Are all section/sub-section headings provided in English first and French second?
- Welcome Page for a bilingual or multilingual site provided by an office located inside of Quebec:
- Is an "h1" element provided at the beginning of the message area?
- Are all section/sub-section headings provided in both official languages?
- Are all section/sub-section headings provided in French first and English second?
- Welcome Page for a unilingual site:
- Is an "h1" element provided at the beginning of the message area?
- Are all section/sub-section headings provided in only the language of the page (except for the sub-section heading for the Official Languages notice in the alternate official language)?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Are all section/sub-section headings identified using heading markup?
- Is the page logically grouped into sections using heading markup?
- Are all section/sub-section relationships properly identified using heading markup? For example, if a section begins with a level 3 heading then each sub-section of the section would begin with a level 4 heading, and each sub-section of these sub-sections would begin with a level 5 heading.
- Is heading markup used in sequence without skipping levels?
- Are all closely related form controls logically grouped using "fieldset" and "legend"?
- Is each sub list nested correctly in the associated parent list (in other words are the items in each sub list grouped into a new list element that is nested within a list item element of the parent list)?
- Is list markup used for each series of like content that conveys meaningful information (such as links, names, or addresses) and is not part of a sentence (excluding any series where data tables or heading elements are used instead of list markup)?
- Is definition list markup used for each series of like title/value pairs that conveys meaningful information (such as term/definition pairs in a glossary or speaker/speech pairs in a transcript) and is not part of a sentence (excluding any series where data tables or heading elements are used instead of list markup)?
- Is the page free of very large blocks of text where it would be natural and appropriate to divide each of those blocks of text into more manageable groups?
- Is the page free of very large and complex tables (such as compound tables) where it would be natural and appropriate to divide each of those tables into less complex and more manageable tables?
- Is the paragraph element ("p") used to identify the beginning and ending of each paragraph?
Checkpoint 12.4 (Priority 2): Form Control Labels
Compliance Criteria – Web page
Situation where applicable: Page contains at least one Web form
High priority criteria (failure of a criterion results in 0% compliance)
- Is all text that is enclosed by the "form" element and is unique to one form control (including inline error messages) programmatically associated to the relevant form control? For example, are all labels that are unique to one form control programmatically associated to the relevant form control using the "label" element?
- Is all text that is enclosed by the "form" element that is not unique to one form control programmatically associated to the relevant form controls using "fieldset" and "legend"?
- Is all text that is enclosed by the "form" element programmatically associated to at least one form control?
Checkpoint 13.1 (Priority 2): Link Targets
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of links where the targets are not explicitly identified through the link text or the title values alone (such as a "More" link with no title value)?
- Is the page free of links where the targets cannot be programmatically determined from the link text alone or from the link text together with content from the same paragraph, the same list, the same table cell, or an associated table header cell?
- Is the page free of links with different targets that are not differentiable through link text or title values alone (such as multiple "Help" links with different targets and the same title values)?
- Is the page free of links with different targets that are not differentiable through link text alone or from the link text together with content from the same paragraph, the same list, the same table cell, or an associated table header cell?
- Is the page free of links with different targets, different link text, and non-null title values that are not differentiable through title values alone (such as multiple links with different link text but only "Help" for the title value)?
- Is the page free of links with non-null title values that provide less information than the link text (such as links with "Meetings in June" for the link text and "Meetings" for the title value)?
- Are all links valid (in other words not broken and targeting the correct page in the correct language)?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Is the page free of links with a URL for the link text where the target is not explicitly identified through the title value (excluding link text that includes only the domain names such as "canada.gc.ca" or "privcom.gc.ca")?
- Is a text indication of the format provided in the link text or title value for each link to a non-XHTML/HTML format?
- Is the page free of link text and title values that do not use white-space or hyphens in between words (such as using underscores or no white-space at all)?
Checkpoint 13.2 (Priority 2): Metadata
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is semantic information provided using at least one metadata element (such as "dc.description", "description", "dcterms.subject", or "keywords")?
- Is semantic information identifying the contents of the Web page provided using the title element (<title></title>)?
Checkpoint 13.3 (Priority 2): Site Maps
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is information about the general layout of the site (such as site maps, A-Z indexes, or tables of contents) available from the current page or a page linked to from the current page (such as the Contact Us page)?
Checkpoint 13.4 (Priority 2): Navigation
Compliance Criteria – Web page
Situation where applicable: Page contains at least one navigation mechanism
High priority criteria (failure of a criterion results in 0% compliance)
- Are advance warnings for the opening of new windows implemented consistently throughout the page?
- Is the naming convention for form control labels implemented consistently throughout the page?
- Is the naming convention for link text and title values implemented consistently throughout the page?
- Are navigational mechanisms implemented consistently throughout the page?
- Are advance warnings for the opening of new windows implemented on the page consistent with the rest of the site or sub site?
- Is the naming convention for form control labels implemented on the page consistent with the rest of the site or sub site?
- Is the naming convention for link text and title values implemented on the page consistent with the rest of the site or sub site?
- Are navigational mechanisms implemented on the page consistent with the rest of the site or sub site?
Checkpoint 14.1 (Priority 1): Writing Styles
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is all content using the plainest and clearest language that is appropriate for the site?
- Is the page free of unnecessarily complex terminology and sentence structures?
Part 2, R2 – Baseline technologies
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Page does not use frames:
- Is the full DOCTYPE declaration for XHTML 1.0 Strict or a more recent World Wide Web Consortium (W3C) (X)HTML markup language provided as the first element on the page?
- Does the page validate to XHTML 1.0 Strict or a more recent World Wide Web Consortium (W3C) (X)HTML markup language?
- Page uses frames:
- Is the full DOCTYPE declaration for XHTML 1.0 Frameset or a more recent World Wide Web Consortium (W3C) (X)HTML markup language provided as the first element for each frameset?
- Does the frameset validate to XHTML 1.0 Frameset or a more recent World Wide Web Consortium (W3C) (X)HTML markup language?
- Is the full DOCTYPE declaration for XHTML 1.0 Strict or a more recent World Wide Web Consortium (W3C) (X)HTML markup language provided as the first element for each frame?
- Does each frame validate to XHTML 1.0 Strict or a more recent World Wide Web Consortium (W3C) (X)HTML markup language?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Does all CSS (including associated CSS files and CSS embedded in the page) validate to the most current and stable version of CSS?
Part 2, R3 – Accessible alternate format of documents on Web sites
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Document is not represented in XHTML 1.0 Strict or a language described by World Wide Web Consortium (W3C) Recommendations:
- Is an Accessibility Notice provided immediately preceding the content or application that is not represented in XHTML 1.0 Strict or a language described by World Wide Web Consortium (W3C) Recommendations?
- Is an Accessibility Notice provided on the "Help" page(s) of the Web site?
Medium priority criteria (failure of a criterion results in no more than 10% compliance)
- Is the document represented in XHTML 1.0 Strict or a language described by World Wide Web Consortium (W3C) Recommendations?
Part 2, R4 – Offering information in multiple formats
Compliance Criteria – Web page
Situation where applicable: Page contains non-XHTML content or at least one link to a non-XHTML document
High priority criteria (failure of a criterion results in 0% compliance)
- Is a link provided to a site where an appropriate viewer or plug-in can be obtained for each non-XHTML format that requires specialized software and is in use on the current page (excluding non-XHTML formats that the site visitor already has the required specialized software for)?
- Is a link provided to a site where an appropriate viewer or plug-in can be obtained for each non-XHTML format that requires specialized software and is in use by one or more documents linked to from the current page?
- Is a text indication of the format, file type, and size provided for each link to a non-XHTML document?
- Is the first format encountered by a visitor the XHTML version? For example, is the current page the XHTML version or is the XHTML version the first entry in the list of available formats?
Part 2, R5 – Contrast
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Meaningful textual information is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size setting):
- Is at least a 4:1 contrast ratio achieved between the meaningful textual information and the associated backgrounds?
- Meaningful textual information is at least as large as an equivalent 18 point or 14 point bold font (at the
normal text size setting):
- Is at least a 3:1 contrast ratio achieved between the meaningful textual information and the associated backgrounds?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Meaningful textual information is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size setting):
- Is at least a 4.25:1 contrast ratio achieved between the meaningful textual information and the associated backgrounds?
Low priority criteria (failure of a criterion results in no more than 75% compliance)
- Meaningful textual information is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size setting):
- Is at least a 4.5:1 contrast ratio achieved between the meaningful textual information and the associated backgrounds?
Part 2, R6 – Assessing accessibility, interoperability and usability
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is a validation methodology employed to ensure the page is accessible, interoperable, and usable for the widest possible audience and the broadest possible range of hardware and software platforms (including browser software, operating systems, internet-enabled devices, and adaptive technologies)?
- Is testing with site visitors, current or potential, performed to ensure ease of use, navigation, comprehension, and user satisfaction?
- Page does not contain a frameset:
- Does the page validate to XHTML 1.0 Strict or a more recent World Wide Web Consortium (W3C) (X)HTML markup language?
- Page contains a frameset:
- Does the frameset validate to XHTML 1.0 Frameset or a more recent World Wide Web Consortium (W3C) (X)HTML markup language?
- Does each frame validate to XHTML 1.0 Strict or a more recent World Wide Web Consortium (W3C) (X)HTML markup language?
Part 3: Standard on Common Web Page Formats
Part 3, R1 – Welcome Page elements
Compliance Criteria – Web page
Situation where applicable: Main point of entry to a site
High priority criteria (failure of a criterion results in 0% compliance)
- Is a Welcome Page incorporated at the main point of entry to the site?
Part 3, R1.1 – "Canada" wordmark and signature
Compliance Criteria – Web page
Situation where applicable: Welcome Page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the "Canada" wordmark displayed in the lower right position of the page?
- Is the institutional signature displayed in the upper left position of the page?
- Welcome Page for a bilingual or multilingual site provided by an office located outside of Quebec:
- Is the order of the official languages for bilingual institutional signatures English on the left and French on the right?
- Welcome Page for a bilingual or multilingual site provided by an office located inside of Quebec:
- Is the order of the official languages for bilingual institutional signatures French on the left and English on the right?
- Welcome Page for a unilingual English site:
- Is the order of the official languages for bilingual institutional signatures English on the left and French on the right?
- Welcome Page for a unilingual French site:
- Is the order of the official languages for bilingual institutional signatures French on the left and English on the right?
Part 3, R1.2 – Dimensions and page structure
Compliance Criteria – Web page
Situation where applicable: Welcome Page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page displayed in the centre of the browser window?
- Is the default background colour white (#FFFFFF) for the main content area?
- Is the default background colour white (#FFFFFF) for the open space surrounding the Web page?
- Is the page 760 pixels wide?
- Is all content visible at 800 pixels by 600 pixels resolution without scrolling?
- Are the left and right margins of the page 80 pixels wide?
- Are the top and bottom margins of the page 20 pixels wide?
- Is the institutional message space 600 pixels wide by 250 pixels high?
- Is the right edge of the "Canada" wordmark aligned with the right margin of the page?
- Welcome Page for a bilingual or multilingual site:
- Are the institutional signature, institutional message space, language choice links and important notices links left aligned?
- Are the language choice links positioned 30 pixels below the institutional message space?
- Are the language choice links presented side by side with a 30 pixel separation (at the normal text size setting)?
- Are the language choice links to the left of the "Canada" wordmark?
- Is the top edge of the "Canada" wordmark aligned with the top edge of the language choice links?
- Is the English important notices link provided with the link text "Important Notices"?
- Is the French important notices link provided with the link text "Avis importants"?
- Is the English important notices link positioned under and left aligned with the left edge of the English language choice link?
- Is the French important notices link positioned under and left aligned with the left edge of the French language choice link?
- Is the target of the English important notices link one of the following:
- the English primary important notices page of the main institutional site; or
- the English primary important notices page of the current site or sub site?
- Is the target of the French important notices link one of the following:
- the French primary important notices page of the main institutional site; or
- the French primary important notices page of the current site or sub site?
- Welcome Page for a unilingual English site:
- Are the institutional signature, institutional message space, language choice links, and site entry link left aligned?
- Is the site entry link positioned 30 pixels below the institutional message space?
- Is the site entry link to the left of the "Canada" wordmark?
- Is the important notices link provided with the link text "Important Notices"?
- Is the English important notices link positioned under and left aligned with the left edge of the bilingual message regarding content in only one language?
- Is the target of the important notices link one of the following:
- the English primary important notices page of the main institutional site; or
- the English primary important notices page of the current site or sub site?
- Welcome Page for a unilingual French site:
- Are the institutional signature, institutional message space, language choice links, and site entry link left aligned?
- Is the site entry link positioned 30 pixels below the institutional message space?
- Is the site entry link to the left of the "Canada" wordmark?
- Is the important notices link provided with the link text "Avis importants"?
- Is the important notices link positioned under and left aligned with the left edge of the bilingual message regarding content in only one language?
- Is the target of the important notices link one of the following:
- the French primary important notices page of the main institutional site; or
- the French primary important notices page of the current site or sub site?
Part 3, R1.3 – Institutional message space
Compliance Criteria – Web page
Situation where applicable: Welcome Page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the institutional message space one of the following:
- an image measuring 600 pixels wide by 130 pixels high positioned directly above a rectangular field measuring 600 pixels wide by 120 pixels high with introductory text in both official languages in the foreground; or
- a background image measuring 600 pixels wide by 250 pixels high with introductory text in both official languages?
- Text elements are smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4:1 contrast ratio achieved between the text elements and the background colour or image?
- Text elements are at least as large as an equivalent 18 point or 14 point bold font (at the
normal text size
setting):
- Is at least a 3:1 contrast ratio achieved between the text elements and the background colour or image?
- Is the introductory text in both official languages provided in a single level 1 heading element ("h1")?
Medium priority criteria (failure of a criterion results in no more than 50% compliance)
- Text elements are smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4.25:1 contrast ratio achieved between the text elements and the background colour or image?
- Are lower level heading elements ("h2", "h3", "h4", "h5", and "h6") used in sequential order as required?
- Are the sizes of all visible headings relative to the position in the heading hierarchy, that is level 1 heading element ("h1") text is larger than level 2 heading element ("h2") text and so on?
Low priority criteria (failure of a criterion results in no more than 75% compliance)
- Text elements are smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4.5:1 contrast ratio achieved between the text elements and the background colour or image?
Part 3, R1.4 – Language
Part 3, R1.4.1 – Bilingual sites
Compliance Criteria – Web page
Situation where applicable: Welcome Page for a bilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- Welcome Page provided by an office outside of Quebec:
- Is the order of the official languages for the page content, including the introductory text, the language choice links, the Universal Resource Locator (URL), and alternative text (alt text), English on the left and French on the right?
- Is
langused to set the language type of the page as "en"? - Is
langused to set the language type of French content as "fr"?
- Welcome Page provided by an office inside of Quebec:
- Is the order of the official languages for the page content, including the introductory text, the language choice links, the Universal Resource Locator (URL), and alternative text (alt text), French on the left and English on the right?
- Is
langused to set the language type of the page as "fr"? - Is
langused to set the language type of English content as "en"?
- Is an English language choice link provided with the link text "English"?
- Is the target of the English language choice link the English main page of the site?
- Is a French language choice link provided with the link text "Français"?
- Is the target of the French language choice link the French main page of the site?
- Is the default font colour white (#FFFFFF) for each language choice link?
- Are the dimensions 120 pixels wide by 30 pixels high (at the normal text size setting) for the rectangular field surrounding each language choice link?
- Is the default background colour red (#FF0000) for the rectangular field surrounding each language choice link?
- Are the borders 2 pixels wide for the rectangular field surrounding each language choice link?
- Is the default border colour #FF6666 for the top and left borders of the rectangular field surrounding each language choice link?
- Is the default border colour #CC3333 for the bottom and right borders of the rectangular field surrounding each language choice link?
- Is the page free of effects that change the appearance or behaviour of either the language choice links or the rectangular field surrounding each language choice link?
Part 3, R1.4.2 – Unilingual sites
Compliance Criteria – Web page
Situation where applicable: Welcome Page for unilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- Welcome Page for a unilingual English site:
- Is a site entry link provided with the link text "Enter"?
- Welcome Page for a unilingual French site:
- Is a site entry link provided with the link text "Entrer"?
- Is the target of the site entry link the main page of the site?
- Is the default font colour white (#FFFFFF) for the site entry link?
- Are the dimensions 120 pixels wide by 30 pixels high (at the normal text size setting) for the rectangular field surrounding the site entry link?
- Is the default background colour red (#FF0000) for the rectangular field surrounding the site entry link?
- Are the borders 2 pixels wide for the rectangular field surrounding the site entry link?
- Is the default border colour #FF6666 for the top and left borders of the rectangular field surrounding the site entry link?
- Is the default border colour #CC3333 for the bottom and right borders of the rectangular field surrounding the site entry link?
- Is the page free of effects that change the appearance or behaviour of either the site entry link or the rectangular field surrounding the site entry link?
- Is a bilingual message placed directly below the site entry link which informs site visitors that, under the Official Languages Act, the site provides information in one official language only and provides a link to another site of the same institution that provides general information in both official languages?
Part 3, R1.4.3 – Multilingual sites
Compliance Criteria – Web page
Situation where applicable: Welcome Page for a multilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- Welcome Page provided by an office outside of Quebec:
- Is the order of the official languages for the page content, including the introductory text, the language choice links, the Universal Resource Locator (URL), and alternative text (alt text), English on the left and French on the right?
- Is
langused to set the language type of the page as "en"? - Is
langused to set the language type of non-English content?
- Welcome Page provided by an office inside of Quebec:
- Is the order of the official languages for the page content, including the introductory text, the language choice links, the Universal Resource Locator (URL), and alternative text (alt text), French on the left and English on the right?
- Is
langused to set the language type of the page as "fr"? - Is
langused to set the language type of non-French content?
- Is an English language choice link provided with the link text "English"?
- Is the target of the English language choice link the English main page of the site?
- Is a French language choice link provided with the link text "Français"?
- Is the target of the French language choice link the French main page of the site?
- Is a language choice link provided for each alternate language with the link text being the name of the language (in the language and characters of that language, such as "Español")?
- Is the target of the language choice link for each alternate language the main page of the site in that language?
- English or French language choice link:
- Is the default font colour white (#FFFFFF) for the language choice link?
- Are the dimensions 120 pixels wide by 30 pixels high (at the normal text size setting) for the rectangular field surrounding the language choice link?
- Is the default background colour red (#FF0000) for the rectangular field surrounding the language choice link?
- Are the borders 2 pixels wide for the rectangular field surrounding the language choice link?
- Is the default border colour #FF6666 for the top and left borders of the rectangular field surrounding the language choice link?
- Is the default border colour #CC3333 for the bottom and right borders of the rectangular field surrounding the language choice link?
- Is the page free of effects that change the appearance or behaviour of either the language choice links or the rectangular field surrounding the language choice link?
- Language choice link for a language other than English or French:
- Is the default font colour red (#FF0000) for the language choice link?
- Are the dimensions 120 pixels wide by 30 pixels high (at the normal text size setting) for the rectangular field surrounding the language choice link?
- Is the default background colour white (#FFFFFF) for the rectangular field surrounding the language choice link?
- Is the page free of effects that change the appearance or behaviour of either the language choice links or the rectangular field surrounding the language choice link?
Part 3, R2 – Content page dimensions and layout
Part 3, R2.1 – Page dimensions
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the width of the page 760 pixels?
- Exceptional cases where specific content, including maps, large tables, charts and graphs cannot adjust by way of wrapping to the standard 760 pixel
width or by altering the content and its structure:
- Is the content only extended to the right?
- Are site visitors informed that the content area is larger than usual?
Part 3, R2.2 – Page layout
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the content page centered and presented in one of three designs: a three-column layout, a two-column layout, or a one-column layout?
Part 3, R2.2.1 – Three-column layout
Compliance Criteria – Web page
Situation where applicable: Content page with a three-column layout or a main page for a site or sub site
High priority criteria (failure of a criterion results in 0% compliance)
- Is the left column 150 pixels wide?
- Is the middle column 405 pixels wide?
- Is the right column 195 pixels wide?
- Is the padding between the three columns 5 pixels wide?
Part 3, R2.2.2 – Two-column layout
Compliance Criteria – Web page
Situation where applicable: Content page with a two-column layout
High priority criteria (failure of a criterion results in 0% compliance)
- Is the left column 150 pixels wide?
- Is the right column 605 pixels wide?
- Is the padding between the two columns 5 pixels wide?
Part 3, R2.2.3 – One-column layout
Compliance Criteria – Web page
Situation where applicable: Content page with a one-column layout
High priority criteria (failure of a criterion results in 0% compliance)
- Is this page an exceptional case where content cannot be made to fit in the two-column layout by adjusting its format or structure?
- Is the column 760 pixels wide?
Part 3, R2.3 – Background
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page displayed in the centre of the browser window?
- Is the default background colour white (#FFFFFF) for the 760 pixel wide page?
- Is a colour in the Web-Smart colour palette used for the background colour of the open space surrounding the Web page?
- Is the open space surrounding the Web page free of foreground and background images?
Part 3, R2.4 – Header structure
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Are heading elements used to convey document structure?
- Is a level 1 heading element ("h1") used to identify the beginning of the common menu bar?
- Is a level 1 heading element ("h1") used to identify the beginning of the content area?
- Are level 2, 3, 4, 5, and 6 heading elements ("h2", "h3", "h4", "h5", and "h6") used in sequential order to identify all sections of the content area?
- Are level 2, 3, 4, 5, and 6 heading elements ("h2", "h3", "h4", "h5", and "h6") used to clarify the hierarchical structure of the content area?
- Content page with a two-column or three-column layout:
- Is a level 1 heading element ("h1") used to identify the beginning of the left side menu?
- Are level 2, 3, 4, 5, and 6 heading elements ("h2", "h3", "h4", "h5", and "h6") used in sequential order to identify all sections of the side menu(s)?
- Are level 2, 3, 4, 5, and 6 heading elements ("h2", "h3", "h4", "h5", and "h6") used to clarify the hierarchical structure of the side menu(s)?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Is the page free of heading elements that are used solely for visual purposes?
- Are the sizes of all visible headings relative to the position in the heading hierarchy, that is level 1 heading element ("h1") text is larger than level 2 heading element ("h2") text and so on?
Part 3, R2.5 – Font
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the font face for text elements in the content area specified using CSS with Verdana as the default?
- Content page with a two-column or three-column layout:
- Is the font face for text elements in the side menu(s) specified using CSS with Verdana as the default?
- Meaningful textual
information is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4:1 contrast ratio achieved between the meaningful textual information and the background colour or image?
- Meaningful textual information is at least as large as an equivalent 18 point or 14 point bold font (at the
normal text size setting):
- Is at least a 3:1 contrast ratio achieved between the meaningful textual information and the background colour or image?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Meaningful textual information is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size setting):
- Is at least a 4.25:1 contrast ratio achieved between the meaningful textual information and the background colour or image?
Low priority criteria (failure of a criterion results in 75% compliance)
- Meaningful textual information is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size setting):
- Is at least a 4.5:1 contrast ratio achieved between the meaningful textual information and the background colour or image?
Part 3, R2.6 – Printer friendly versions
Compliance Criteria – Web page
Situation where applicable: Printer friendly version of a content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the "Canada" wordmark displayed in the upper right position of the page?
- Is the institutional signature displayed in the upper left position of the page?
- English content page:
- Is the order of the official languages for bilingual institutional signatures English on the left and French on the right?
- Is a content date indicator provided in the form "Date Modified: YYYY-MM-DD" to follow the ISO standard format for all-numeric date display?
- French content page:
- Is the order of the official languages for bilingual institutional signatures French on the left and English on the right?
- Is a content date indicator provided in the form "Date de modification : AAAA‑MM‑JJ" to follow the ISO standard format for all-numeric date display?
- Content page in a language other than English or French for a site provided by an office located outside of Quebec:
- Is the order of the official languages for bilingual institutional signatures English on the left and French on the right?
- Is a content date indicator provided in the ISO standard format for all-numeric date display (YYYY-MM-DD)?
- Content page in a language other than English or French for a site provided by an office located inside of Quebec:
- Is the order of the official languages for bilingual institutional signatures French on the left and English on the right?
- Is a content date indicator provided in the ISO standard format for all-numeric date display (YYYY-MM-DD)?
- Is the date specified by the content date indicator the most recent date on which the content was formally issued, substantially changed, or reviewed?
- Is the content date indicator left aligned with the left margin of the page and included in the final line of content of the page?
- Is the font face for the content date indicator specified using CSS with Verdana as the default and sans-serif as an alternate font?
- Is the default background colour white (#FFFFFF) for the content date indicator?
- Is at least a 4:1 contrast ratio achieved between the content date indicator and the associated background?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Is at least a 4.25:1 contrast ratio achieved between the content date indicator and the associated background?
Low priority criteria (failure of a criterion results in 75% compliance)
- Is at least a 4.5:1 contrast ratio achieved between the content date indicator and the associated background?
Part 3, R3 – "Canada" wordmark and institutional signature
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Is the "Canada" wordmark displayed in the upper right position of the page?
- Is the institutional signature displayed in the upper left position of the page?
- English content page:
- Is the order of the official languages for bilingual institutional signatures English on the left and French on the right?
- French content page:
- Is the order of the official languages for bilingual institutional signatures French on the left and English on the right?
- Are the "Canada" wordmark and the institutional signature not hyperlinked?
Part 3, R4 – Banner
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is an institutional banner applied to the page?
Part 3, R4.1 – Maple leaf
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the common red maple leaf provided on the institutional banner?
- Is the common red maple leaf 65 pixels high and 65 pixels wide?
- Is the common red maple leaf displayed over the banner background, with the top 35 pixels of the leaf image extending above the background?
- Is the top of the common red maple leaf placed 5 pixels below the bottom of the final text in the institutional signature?
- Is the stem of the common red maple leaf centered on the page, 380 pixels from the left border of the page?
Part 3, R4.2 – Banner background
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the banner background implemented using either a background colour or a background image?
Part 3, R4.2.1 – Background colour
Compliance Criteria – Web page
Situation where applicable: Content page using a background colour for the banner background
High priority criteria (failure of a criterion results in 0% compliance)
- Banner text is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4:1 contrast ratio achieved between the banner text and the background colour?
- Banner text is at least as large as an equivalent 18 point or 14 point bold font (at the
normal text size
setting):
- Is at least 3:1 contrast ratio achieved between the banner text and the background colour?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Banner text is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4.25:1 contrast ratio achieved between the banner text and the background colour?
Low priority criteria (failure of a criterion results in 75% compliance)
- Banner text is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4.5:1 contrast ratio achieved between the banner text and the background colour?
Part 3, R4.2.2 – Banner image
Compliance Criteria – Web page
Situation where applicable: Content page using a background image for the banner background
High priority criteria (failure of a criterion results in 0% compliance)
- Is the file size of the background image optimized to allow the page to load quickly for users without high speed Internet access?
- Is the visible portion of the background image no more than 760 pixels wide by 80 pixels high at the normal font size (100%)?
- Banner text is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4:1 contrast ratio achieved between the banner text and the background image?
- Banner text is at least as large as an equivalent 18 point or 14 point bold font (at the
normal text size
setting):
- Is at least a 3:1 contrast ratio achieved between the banner text and the background image?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Banner text is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4.25:1 contrast ratio achieved between the banner text and the background image?
Low priority criteria (failure of a criterion results in 75% compliance)
- Banner text is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4.5:1 contrast ratio achieved between the banner text and the background colour?
Part 3, R4.3 – Multimedia elements
Compliance Criteria – Web page
Situation where applicable: Content page with banner multimedia elements
High priority criteria (failure of a criterion results in 0% compliance)
- Are the banner multimedia elements fully contained with the 760 pixels wide by 80 pixels high banner dimensions?
- Is the banner text perceivable and readable with and without adaptive technologies when multimedia support is enabled?
- Is the banner text perceivable and readable with and without adaptive technologies when multimedia support is not enabled or is not available on the site visitor's system?
- Are the banner multimedia elements free of content that flickers (flashes more than three times in any one second period)?
Part 3, R4.4 – Text
Part 3, R4.4.1 – First line of text
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional site or sub site (excluding multidepartment sites and sites related to a marketing campaign or government initiative):
- Is the first line of text in the banner the institution's applied title?
- Is the font face for the first line of text in the banner specified using CSS with Times New Roman as the default and sans-serif as an alternate font?
- Is the default font colour white (#FFFFFF) for the first line of text in the banner?
- Is the first line of text in the banner presented in mixed case?
- Is the first line of text in the banner centered?
- Is the first line of text in the banner not hyperlinked?
Part 3, R4.4.2 – Second line of text
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional site or sub site (excluding multidepartment sites and sites related to a marketing campaign or government initiative):
- Main institutional site:
-
Is the second line of text in the banner one of the following:
- a domain composed of elements or acronyms with the same meaning and spelling in both official languages (such as ec.gc.ca)?
-
English content page:
- a domain composed of elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as tbs-sct.gc.ca); or
- a domain composed of elements or acronyms in English only (such as pwgsc.gc.ca)?
-
French content page:
- a domain composed of elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as ainc-inac.gc.ca); or
- a domain composed of elements or acronyms in French only (such as tpsgc.gc.ca)?
-
Is the second line of text in the banner one of the following:
- Site or sub site other than the main institutional site:
-
English content page:
- Is the second line of text in the banner the same text used for the second line of text in the main institutional site English banner?
-
French content page:
- Is the second line of text in the banner the same text used for the second line of text in the main institutional site French banner?
-
Content page in a language other than English or French provided by an office located outside of Quebec:
-
Second line of text in the main institutional site English banner is a domain name that is composed of elements or acronyms with the same meaning and spelling
in both official languages (such as ec.gc.ca) or a domain name composed of elements or acronyms in both official languages (such as tbs-sct.gc.ca):
- Is the second line of text in the banner the same text used for the second line of text in the main institutional site English banner?
-
Second line of text in the main institutional site English banner is a domain name that is composed of elements or acronyms in English only (such as
cra.gc.ca):
- Is the second line of text in the banner a domain name that is composed of the elements and acronyms in the second line of text in the main institutional site English and French banners in the order of English on the left and French on the right with a hyphen separating the two languages (such as cra-arc.gc.ca)?
-
Second line of text in the main institutional site English banner is a domain name that is composed of elements or acronyms with the same meaning and spelling
in both official languages (such as ec.gc.ca) or a domain name composed of elements or acronyms in both official languages (such as tbs-sct.gc.ca):
-
Content page in a language other than English or French provided by an office located inside of Quebec:
-
Second line of text in the main institutional site French banner is a domain name that is composed of elements or acronyms with the same meaning and spelling
in both official languages (such as ec.gc.ca) or a domain name composed of elements or acronyms in both official languages (such as sct-tbs.gc.ca):
- Is the second line of text in the banner the same text used for the second line of text in the main institutional site French banner?
-
Second line of text in the main institutional site banner is a domain name that is composed of elements or acronyms in French only (such as
pwgsc.gc.ca):
- Is the second line of text in the banner a domain name that is composed of the elements and acronyms in the second line of text in the main institutional site English and French banners in the order of French on the left and English on the right with a hyphen separating the two languages (such as tpsgc-pwgsc.gc.ca)?
-
Second line of text in the main institutional site French banner is a domain name that is composed of elements or acronyms with the same meaning and spelling
in both official languages (such as ec.gc.ca) or a domain name composed of elements or acronyms in both official languages (such as sct-tbs.gc.ca):
-
English content page:
- Is the second line of text implemented with a smaller font size than the first line of text?
- Is the font face for the second line of text in the banner specified using CSS with Arial as the default and sans-serif as an alternate font?
- Is the default font colour white (#FFFFFF) for the first line of text in the banner?
- Main institutional site:
- Is the second line of text in the banner centered?
- Is the second line of text in the banner not hyperlinked?
Part 3, R4.4.3 – High level of contrast
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Banner text is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4:1 contrast ratio achieved between the banner text and the associated backgrounds (including the default background colour when a background image is used)?
- Banner text is at least as large as an equivalent 18 point or 14 point bold font (at the
normal text size
setting):
- Is at least a 3:1 contrast ratio achieved between the banner text and the associated backgrounds (including the default background colour when a background image is used)?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Banner text is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4.25:1 contrast ratio achieved between the banner text and the associated backgrounds (including the default background colour when a background image is used)?
Low priority criteria (failure of a criterion results in 75% compliance)
- Banner text is smaller than equivalent 18 point and 14 point bold fonts (at the
normal text size
setting):
- Is at least a 4.5:1 contrast ratio achieved between the banner text and the associated backgrounds (including the default background colour when a background image is used)?
Part 3, R5 – Common menu bar
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is a common menu bar provided?
Part 3, R5.1 – Bilingual Web sites
Compliance Criteria – Web page
Situation where applicable: Content page for a bilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- English content page:
- Are the following six links arrayed from left to right in the following order in the common menu bar: Français, Home, Contact Us, Help, Search, canada.gc.ca?
- French content page:
- Are the following six links arrayed from left to right in the following order in the common menu bar: English, Accueil, Contactez-nous, Aide, Recherche, canada.gc.ca?
Part 3, R5.2 – Unilingual Web sites
Compliance Criteria – Web page
Situation where applicable: Content page for a unilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- English content page:
- Are the following six links arrayed from left to right in the following order in the common menu bar: Avertissement, Home, Contact Us, Help, Search, canada.gc.ca?
- French content page:
- Are the following six links arrayed from left to right in the following order in the common menu bar: Notice, Accueil, Contactez-nous, Aide, Recherche, canada.gc.ca?
Part 3, R5.3 – Sites offering content in other languages
Compliance Criteria – Web page
Situation where applicable: Content page in a language other than English or French
High priority criteria (failure of a criterion results in 0% compliance)
- Are both English and French common menu bars provided?
- Content page for a site provided by an office outside of Quebec:
- Is the English common menu bar provided immediately above the French common menu bar?
- Content page for a site provided by an office inside of Quebec:
- Is the French common menu bar provided immediately above the English common menu bar?
- Are the following six links arrayed from left to right in the following order in the English common menu bar: Français, Home, Contact Us, Help, Search, canada.gc.ca?
- Are the following six links arrayed from left to right in the following order in the French common menu bar: English, Accueil, Contactez-nous, Aide, Recherche, canada.gc.ca?
Part 3, R5.4 – Specifications
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the total width of the common menu bar(s) 760 pixels?
- Is the default font colour white (#FFFFFF) for each navigation link in the common menu bar(s)?
- Is each navigation link in the common menu bar(s) presented in scalable text?
- Is each navigation link in the common menu bar(s) left aligned?
- Is the font face for all navigation links in the common menu bar(s) specified using CSS with Verdana as the default and sans-serif as an alternate font?
- Is the size for all navigation links in the common menu bar(s) equal to or greater than a 9 point Verdana font (at the normal text size setting) and specified using CSS?
- Are all navigation links in the common menu bar(s) (except for the right-most links(s)) contained within rectangular fields of 126 pixels by 20 pixels (at the normal text size setting)?
- Are the right-most links in the common menu bar(s) contained within rectangular fields of 125 pixels by 20 pixels (at the normal text size setting)?
- Is the default background colour black (#000000) for each rectangular field in the common menu bar(s)?
- Are 1-pixel-wide vertical spacers, that are white (#FFFFFF) in colour, used to separate each rectangular field in the common menu bar(s)?
- Is/are the common menu bar(s) free of effects that change the appearance or the behaviour of the common menu bar(s) themselves including the associated text, navigation links, and rectangular fields?
- Is/are the common menu bar(s) free of graphical buttons?
Part 3, R5.5 – Behaviour of links on secure sites and Web application pages
Compliance Criteria – Web page
Situation where applicable: Content page for a secure section of a site or Web application where navigating away from the content page will cause the visitor to lose information inputs or access
High priority criteria (failure of a criterion results in 0% compliance)
- Are the links from the common menu bar(s) (excluding the language link(s)) directed to interstitial pages where the site visitor is informed of the repercussions of leaving and can then choose to continue to the intended destination or return to the previous page?
Part 3, R5.6 – Absence on downloadable versions of documents
Compliance Criteria – Web page
Situation where applicable: Content page contains a link to a non-XHTML document
High priority criteria (failure of a criterion results in 0% compliance)
- Are all non-XHTML documents linked to from the page compliant with requirements relating to official languages?
- Are all non-XHTML documents linked to from the page compliant with requirements relating to the Federal Identify Program?
Part 3, R5.7 – Prohibition of institutional menu bars
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is the page free of secondary or institutional menu bars outside of the content area and the side menu(s)?
Part 3, R5.8 – Language link
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- English content page for a bilingual site:
- Is the target of the "Français" common menu bar link a page with identical content in French?
- French content page for a bilingual site:
- Is the target of the "English" common menu bar link a page with identical content in English?
- English content page for a unilingual site:
- Is the target of the "Avertissement" common menu bar link a page that provides a bilingual message which informs site visitors that, under the Official Languages Act, the site provides information in English only and provides a link to another site of the same institution that provides general information in both official languages?
- French content page for a unilingual site:
- Is the target of the "Notice" common menu bar link a page that provides a bilingual message which informs site visitors that, under the Official Languages Act, the site provides information in French only and provides a link to another site of the same institution that provides general information in both official languages?
- Content page in a language other than English or French:
- Is the target of the "Français" English common menu bar link a page with identical content in French?
- Is the target of the "English" French common menu bar link a page with identical content in English?
Part 3, R5.9 – Home
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional site or sub site (excluding multidepartment sites and sites related to a marketing campaign or government initiative):
- English content page:
- Is the target of the "Home" common menu bar link the English main page of the main institutional site?
- French content page:
- Is the target of the "Accueil" common menu bar link the French main page of the main institutional site?
- Content page in a language other than English or French:
- Is the target of the "Home" English common menu bar link the English main page of the main institutional site?
- Is the target of the "Accueil" French common menu bar link the French main page of the main institutional site?
- English content page:
- Multidepartment site or a site related to a marketing campaign or government initiative:
- English content page:
- Is the target of the "Home" common menu bar link the English main page of the current site?
- French content page:
- Is the target of the "Accueil" common menu bar link the French main page of the current site?
- Content page in a language other than English or French:
- Is the target of the "Home" English common menu bar link the English main page of the current site?
- Is the target of the "Accueil" French common menu bar link the French main page of the current site?
- English content page:
Part 3, R5.10 – Contact Us
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional site or sub site (excluding multidepartment sites and sites related to a marketing campaign or government initiative):
- English content page:
- Is the target of the "Contact Us" common menu bar link the English primary contact page of the main institutional site?
- French content page:
- Is the target of the "Contactez-nous" common menu bar link the French primary contact page of the main institutional site?
- Content page in a language other than English or French:
- Is the target of the "Contact Us" English common menu bar link the English primary contact page of the main institutional site?
- Is the target of the "Contactez-nous" French common menu bar link the French primary contact page of the main institutional site?
- English content page:
- Multidepartment site or a site related to a marketing campaign or government initiative:
- English content page:
- Is the target of the "Contact Us" common menu bar link the English primary contact page of the current site or the main institutional site?
- French content page:
- Is the target of the "Contactez-nous" common menu bar link the French primary contact page of the current site or the main institutional site?
- Content page in a language other than English or French:
- Is the target of the "Contact Us" English common menu bar link the English primary contact page of the current site or the main institutional site?
- Is the target of the "Contactez-nous" French common menu bar link the French primary contact page of the current site or the main institutional site?
- English content page:
Part 3, R5.11 – Help
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional site or sub site (excluding multidepartment sites and sites related to a marketing campaign or government initiative):
- English content page:
- Is the target of the "Help" common menu bar link the English primary help page of the main institutional site?
- French content page:
- Is the target of the "Aide" common menu bar link the French primary help page of the main institutional site?
- Content page in a language other than English or French:
- Is the target of the "Help" English common menu bar link the English primary help page of the main institutional site?
- Is the target of the "Aide" French common menu bar link the French primary help page of the main institutional site?
- Primary help page:
- Is an overview of any accessibility features available on the Web site provided?
-
Government of Canada CLF 2.0 Common Template used:
- Is a link to client-side CSS instructions for over-riding visual formatting in the template provided?
- English content page:
- Multidepartment site or site related to a marketing campaign or government initiative:
- English content page:
- Is the target of the "Help" common menu bar link the English primary help page of the current site or the main institutional site?
- French content page:
- Is the target of the "Aide" common menu bar link the French primary help page of the current site or the main institutional site?
- Content page in a language other than English or French:
- Is the target of the "Help" English common menu bar link the English primary help page of the current site or the main institutional site?
- Is the target of the "Aide" French common menu bar link the French primary help page of the current site or the main institutional site?
- Primary help page:
- Is an overview of any accessibility features available on the Web site provided?
-
Government of Canada CLF 2.0 Common Template used:
- Is a link to client-side CSS instructions for over-riding visual formatting in the template provided?
- English content page:
Part 3, R5.12 – Search
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Institution is unable to provide search functionality:
- English content page:
- Is the target of the "Search" common menu bar link an English page that explains that search functionality is unavailable and provides a link to the English Canada Site search page?
- French content page:
- Is the target of the "Recherche" common menu bar link a French page that explains that search functionality is unavailable and provides a link to the French Canada Site search page?
- Content page in a language other than English or French:
- Is the target of the "Search" English common menu bar link an English page that explains that search functionality is unavailable and provides a link to the English Canada Site search page?
- Is the target of the "Recherche" French common menu bar link a French page that explains that search functionality is unavailable and provides a link to the French Canada Site search page?
- English content page:
- Institution is able to provide search functionality:
- Institutional site or sub site (excluding multidepartment sites and sites related to a marketing campaign or government initiative):
-
English content page:
- Is the target of the "Search" common menu bar link the English primary search page of the main institutional site?
-
French content page:
- Is the target of the "Recherche" common menu bar link the French primary search page of the main institutional site?
-
Content page in a language other than English or French:
- Is the target of the "Search" English common menu bar link the English primary search page of the main institutional site?
- Is the target of the "Recherche" French common menu bar link the French primary search page of the main institutional site?
-
English content page:
- Multidepartment site or a site related to a marketing campaign or government initiative:
-
English content page:
- Is the target of the "Search" common menu bar link the English primary search page of the current site or the main institutional site?
-
French content page:
- Is the target of the "Recherche" common menu bar link the French primary search page of the current site or the main institutional site?
-
Content page in a language other than English or French:
- Is the target of the "Search" English common menu bar link the English primary search page of the current site or the main institutional site?
- Is the target of the "Recherche" French common menu bar link the French primary search page of the current site or the main institutional site?
-
English content page:
- Institutional site or sub site (excluding multidepartment sites and sites related to a marketing campaign or government initiative):
Part 3, R5.13 – canada.gc.ca
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- English content page:
- Is the target of the "canada.gc.ca" common menu bar link the English main page of the Government of Canada's Web portal?
- French content page:
- Is the target of the "canada.gc.ca" common menu bar link the French main page of the Government of Canada's Web portal?
- Content page in a language other than English or French:
- Is the target of the "canada.gc.ca" English common menu bar link the English main page of the Government of Canada's Web portal?
- Is the target of the "canada.gc.ca" French common menu bar link the French main page of the Government of Canada's Web portal?
Part 3, R6 – Contact Us page
Compliance Criteria – Web page
Situation where applicable: Contact Us page
High priority criteria (failure of a criterion results in 0% compliance)
- Is an email address for contacting the institution provided?
- Is a telephone number for contacting the institution provided?
- Is a teletypewriter (TTY) number for contacting the institution provided?
- Is a facsimile number for contacting the institution provided?
- Are civic and postal addresses for contacting the institution provided?
- Is all relevant contact information provided, including information that could assist individuals with disabilities or special needs?
- Are service standards (where available) provided to site visitors so that they understand the process and know what to expect when requesting service?
- Are links to frequently requested materials provided, such as frequently asked questions, site maps, A to Z indices, and employee directories?
- Are site visitors reminded that, unless otherwise identified, email and Web forms are not secure forms of transmission and therefore must not be used to transmit sensitive personal information?
Part 3, R6.1 – Acknowledgement of correspondence
Compliance Criteria – Web page
Situation where applicable: Page contains a Web form or a generic email address that is provided as a means of contacting the institution
High priority criteria (failure of a criterion results in 0% compliance)
- Are site visitors informed that their comments have been received each time they successfully submit any of the Web forms on the page that are provided as a means of contacting the institution?
- Is an automatic acknowledgement that the correspondence has been received sent each time a site visitor contacts the institution through any of the generic email addresses listed on the page?
Part 3, R7 – Navigation path
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is a navigation path (breadcrumb trail) provided immediately below the common menu bar(s)?
- Is the font face for the text in the navigation path specified using CSS with Verdana as the default and sans-serif as an alternate font?
- Are all links in the navigation path separated by a space, the greater than relational operator (>), followed by another space?
- Are targets of all links in the navigation path explicitly identified through the link text or the title values alone?
- Are all acronyms and abbreviations in the navigation path spelled out or marked up using the HTML acronym or abbr element?
Part 3, R8 – Left menu
Compliance Criteria – Web page
Situation where applicable: Content page with a two-column or three-column layout
High priority criteria (failure of a criterion results in 0% compliance)
- Is navigation provided in the left menu?
- Is the font face for all text elements in the left menu specified using CSS with Verdana as the default and sans-serif as an alternate font?
- Are all headings and navigation links in the left menu provided in scalable text exclusively?
- Is the area in the left menu above the final navigation link free of graphical buttons decorative items implemented using images (including images loaded through CSS)?
- Are all non-text elements in the left menu placed below the final navigation link?
- Meaningful textual information is smaller than 18 point and 14 point bold Verdana fonts (at the
normal text size setting):
- Is at least a 4:1 contrast ratio achieved in the left menu between the meaningful textual information and the associated backgrounds?
- Meaningful textual information is at least as large as an 18 point or 14 point bold Verdana font (at the
normal text size setting):
- Is at least a 3:1 contrast ratio achieved in the left menu between the meaningful textual information and the associated backgrounds?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Meaningful textual information is smaller than 18 point and 14 point bold Verdana fonts (at the
normal text size setting):
- Is at least a 4.25:1 contrast ratio achieved in the left menu between the meaningful textual information and the associated backgrounds?
Low priority criteria (failure of a criterion results in 75% compliance)
- Meaningful textual information is smaller than 18 point and 14 point bold Verdana fonts (at the
normal text size setting):
- Is at least a 4.5:1 contrast ratio achieved in the left menu between the meaningful textual information and the associated backgrounds?
Part 3, R9 – Right menu
Compliance Criteria – Web page
Situation where applicable: Content page with a three-column layout
High priority criteria (failure of a criterion results in 0% compliance)
- Is content provided in the right menu?
- Is the font face for all text elements in the right menu specified using CSS with Verdana as the default and sans-serif as an alternate font?
- Meaningful textual information is smaller than 18 point and 14 point bold Verdana fonts (at the
normal text size setting):
- Is at least a 4:1 contrast ratio achieved in the right menu between the meaningful textual information and the associated backgrounds?
- Meaningful textual information is at least as large as an 18 point or 14 point bold Verdana font (at the
normal text size setting):
- Is at least a 3:1 contrast ratio achieved in the right menu between the meaningful textual information and the associated backgrounds?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Meaningful textual information is smaller than 18 point and 14 point bold Verdana fonts (at the
normal text size setting):
- Is at least a 4.25:1 contrast ratio achieved in the right menu between the meaningful textual information and the associated backgrounds?
Low priority criteria (failure of a criterion results in 75% compliance)
- Meaningful textual information is smaller than 18 point and 14 point bold Verdana fonts (at the
normal text size setting):
- Is at least a 4.5:1 contrast ratio achieved in the right menu between the meaningful textual information and the associated backgrounds?
Part 3, R10 – Proactive Disclosure
Compliance Criteria – Web page
Situation where applicable: Main page for a site or sub site
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional site or sub site (excluding multidepartment sites and sites related to a marketing campaign or government initiative):
- English main page for a site or sub site:
- Is a text-based Proactive Disclosure link with link text of "Proactive Disclosure" provided as the last navigation link in the left menu?
- Is the target of the Proactive Disclosure link the institution's English Proactive Disclosure reporting page?
- French main page for a site or sub site:
- Is a text-based Proactive Disclosure link with link text of "Divulgation proactive" provided as the last navigation link in the left menu?
- Is the target of the Proactive Disclosure link the institution's French Proactive Disclosure reporting page?
- English main page for a site or sub site:
- Multidepartment site or a site related to a marketing campaign or government initiative:
- English main page for a site or sub site:
- Is a text-based Proactive Disclosure link with link text of "Proactive Disclosure" provided as the last navigation link in the left menu?
- Is the target of the Proactive Disclosure link the English main page of the Government-Wide Reporting site?
- French main page for a site or sub site:
- Is a text-based Proactive Disclosure link with link text of "Divulgation proactive" provided as the last navigation link in the left menu?
- Is the target of the Proactive Disclosure link the French main page of the Government-Wide Reporting site?
- English main page for a site or sub site:
Part 3, R11 – Third-party symbols and hyperlinks
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Page is not dedicated to one or more partnering or collaborative arrangements:
- Is the page free of icons, symbols, or logos that represent any person, organization or entity outside of government, apart from Treasury Board approved symbols for government-wide use?
- Page is dedicated to one or more partnering or collaborative arrangements:
- Is the page free of icons, symbols, or logos that represent any person, organization or entity outside of government that:
- are not involved in one of the partnering or collaborative arrangements that the page is dedicated to;
- include promotional lines or tag lines;
- appear to endorse or promote the commercial products or services of any person, organization or entity outside of government; or
- do not include a clear explanation for why they are displayed?
- Is the page free of icons, symbols, or logos that represent any person, organization or entity outside of government that:
- Are all links to third-party sites text-based links?
Part 3, R12 – Personal information collection
Compliance Criteria – Web page
Situation where applicable: Page contains at least one online form where personal information is meant to be entered or the page leads to subsequent pages where at least one persistent cookie occurs
High priority criteria (failure of a criterion results in 0% compliance)
- Page contains at least one online form where personal information is meant to be entered:
- Is a Personal Information Collection Statement prominently placed immediately before each online form where personal information is meant to be entered?
- Page leads to subsequent pages where at least one persistent
cookie occurs:
- Is a Personal Information Collection Statement prominently placed immediately before each mechanism (such as a link or Submit button) that leads to a subsequent page where at least one persistent cookie occurs?
- Is each Personal Information Collection Statement informing individuals about the
following:
- that personal information will be collected about them;
- how the personal information will be used;
- whether provision of the personal information is mandatory or discretionary;
- how long the personal information will be kept;
- the Personal Information Bank number where the information will be kept (where applicable);
- how they can obtain access to the personal information;
- how they can make requests for correction of the personal information; and
- other methods available for submitting personal information (where applicable), such as by phone or in-person?
Part 3, R13 – Footer elements
Part 3, R13.1 – Colour strip
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- Is a strip of colour measuring 760 pixels wide by 15 pixels high provided as the first element in the footer?
- Is the strip of colour presented using a single colour in the Web-Smart colour palette?
- Is the strip of colour free of graphics including images loaded through CSS?
Part 3, R13.2 – Content date indicator
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- English content page:
- Is a content date indicator provided immediately below the colour strip in the footer, in the form "Date Modified: YYYY-MM-DD" to follow the ISO standard format for all-numeric date display?
- French content page:
- Is a content date indicator provided immediately below the colour strip in the footer, in the form "Date de modification : AAAA-MM-JJ" to follow the ISO standard format for all-numeric date display?
- Content page in a language other than English or French:
- Is a content date indicator provided in the ISO standard format for all-numeric date display (YYYY-MM-DD)?
- Is the date specified by the content date indicator the most recent date on which the content was formally issued, substantially changed, or reviewed?
- Is the content date indicator left aligned with the left margin of the page and included in the final line of content of the page?
- Is the font face for the content date indicator specified using CSS with Verdana as the default and sans-serif as an alternate font?
- Is the default background colour white (#FFFFFF) for the content date indicator?
- Is at least a 4:1 contrast ratio achieved between the content date indicator and the associated background?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Is at least a 4.25:1 contrast ratio achieved between the content date indicator and the associated background?
Low priority criteria (failure of a criterion results in 75% compliance)
- Is at least a 4.5:1 contrast ratio achieved between the content date indicator and the associated background?
Part 3, R13.3 – Top of page link
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- English content page:
- Is the top of page link provided in the footer, consisting of a triangle graphic and the text "Top of Page"?
- French content page:
- Is the top of page link provided in the footer, consisting of a triangle graphic and the text "Haut de la page"?
- Is the target of the top of page link the area immediately before the institutional signature at the top of the current page?
- Is the top of page link centered on the page and included in the final line of content of the page?
- Is the font face for the top of page link specified using CSS with Verdana as the default and sans-serif as an alternate font?
- Is the default background colour white (#FFFFFF) for the top of page link?
- Is at least a 4:1 contrast ratio achieved between the top of page link and the associated background?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Is at least a 4.25:1 contrast ratio achieved between the top of page link and the associated background?
Low priority criteria (failure of a criterion results in 75% compliance)
- Is at least a 4.5:1 contrast ratio achieved between the top of page link and the associated background?
Part 3, R13.4 – Important Notices link
Compliance Criteria – Web page
Situation where applicable: Content page
High priority criteria (failure of a criterion results in 0% compliance)
- English content page:
- Is the important notices link provided in the footer with the link text "Important Notices"?
- Is the target of the important notices link one of the following:
- the English primary important notices page of the main institutional site; or
- the English primary important notices page of the current site or sub site?
- French content page:
- Is the important notices link provided in the footer with the link text "Avis importants"?
- Is the target of the important notices link one of the following:
- the French primary important notices page of the main institutional site; or
- the French primary important notices page of the current site or sub site?
- Content page in a language other than English or French:
- Is the English important notices link provided in the footer with the link text "Important Notices"?
- Is the French important notices link provided in the footer with the link text "Avis importants"?
- Is the target of the English important notices link one of the following:
- the English primary important notices page of the main institutional site; or
- the English primary important notices page of the current site or sub site?
- Is the target of the French important notices link one of the following:
- the French primary important notices page of the main institutional site; or
- the French primary important notices page of the current site or sub site?
- Is the important notices link right aligned with the right margin of the page and included in the final line of content of the page?
- Is the font face for the important notices link specified using CSS with Verdana as the default and sans-serif as an alternate font?
- Is the default background colour white (#FFFFFF) for the important notices link?
- Is at least a 4:1 contrast ratio achieved between the important notices link and the associated background?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Is at least a 4.25:1 contrast ratio achieved between the important notices link and the associated background?
Low priority criteria (failure of a criterion results in 75% compliance)
- Is at least a 4.5:1 contrast ratio achieved between the important notices link and the associated background?
Part 3, R14 – Important Notices page
Part 3, R14.1 – Government of Canada Privacy Notice
Compliance Criteria – Web page
Situation where applicable: Important Notices page
High priority criteria (failure of a criterion results in 0% compliance)
- Is a privacy notice provided that includes the following elements even if no personal information is collected through the
site:
- Identification of the organization and how it can be contacted, including the name or position title of the person to contact with any Web site privacy concerns, usually the institution's Privacy Coordinator;
- A clear description of any personal information that is collected automatically, a statement that such information is protected under the Privacy Act, the purpose for which it is collected, who will have access to it, how long it is kept, where it is kept and how individuals can access and correct their own personal information;
- A statement explaining that should the site visitor choose to provide personal information through email or other means, such information is protected under the Privacy Act and will only be used for the specific purposes for which it has been provided, such as to respond to a specific request, or where required by law, how long it is kept, where it is kept and how to obtain access and request corrections;
- A statement that non-identifiable or statistical information may be collected for audit purposes, for use in maximizing effectiveness, or for another purpose specified here, if this is the case;
- An explanation of any security use of information for purposes such as tracking suspected intrusions or the source of a computer virus, or controlling access to the system;
- A statement concerning whether cookies, or any other data, are placed on the site visitor's machine, the type of cookies used (session or persistent), a definition of each type and how they are used;
- A description of any privacy-enhancing technologies in use or available for use, such as the Public Key Infrastructure (PKI) or Secure Socket Layer (SSL);
- A statement that individuals may contact the Office of the Privacy Commissioner if they are dissatisfied with the response they receive from the institution privacy contact on a privacy concern with the Web site;
- Where applicable, a statement regarding any specific institutional policy on collecting information from children online; and
- A statement reminding site visitors that, unless specifically noted otherwise, neither electronic systems nor email are secure information transmission methods, and that it is not recommended that sensitive personal information be transmitted electronically?
- Institution uses an outside service provider as a Webmaster and provides a link for sending a message to the Webmaster:
- Is the outside service provider under a contractual obligation to treat any personal information as though it were covered by the Privacy Act?
- Is it made clear to site visitors that they are sending information outside the institution?
Part 3, R14.2 – Official Languages Notice
Compliance Criteria – Web page
Situation where applicable: Important Notices page
High priority criteria (failure of a criterion results in 0% compliance)
- Is an Official Languages Notice provided to inform Web site visitors of their right to receive information and to interact with the Government of Canada in the official language of their choice?
Part 3, R14.3 – Hyperlinking Notice
Compliance Criteria – Web page
Situation where applicable: Important Notices page
High priority criteria (failure of a criterion results in 0% compliance)
- Is a Hyperlinking Notice provided to inform site visitors of what expectations they should have about links to other Web sites, including accuracy, currency, and official languages?
- Is a statement that there are no official languages obligations for non-Government Canada sites provided in the Hyperlinking Notice?
Part 3, R14.4 – Copyright / Permission to Reproduce Notice
Compliance Criteria – Web page
Situation where applicable: Important Notices page
High priority criteria (failure of a criterion results in 0% compliance)
- Is a Copyright / Permission to Reproduce Notice provided to inform site visitors of content ownership and the conditions associated with reproduction of materials posted on Government of Canada Web sites?
Part 3, R14.5 – Reproduction of Government Symbols
Compliance Criteria – Web page
Situation where applicable: Important Notices page
High priority criteria (failure of a criterion results in 0% compliance)
- Is a Reproduction of Government Symbols Notice provided to inform site visitors that the official symbols of the Government of Canada, including the "Canada" wordmark, the Arms of Canada, and the flag symbol may not be reproduced, whether for commercial or non-commercial purposes, without written authorization?
Part 3, R15 – Third-party information notice
Compliance Criteria – Web page
Situation where applicable: Page contains third-party information
High priority criteria (failure of a criterion results in 0% compliance)
- Are third-party information liability disclaimers, that describe the type of information to which the disclaimer applies, directly attached to all externally sourced information?
Part 3, R16 – Crown copyright symbol
Compliance Criteria – Web page
Situation where applicable: Page contains specific material that needs to be protected by the Crown copyright symbol
High priority criteria (failure of a criterion results in 0% compliance)
- English page:
- Is one of the following provided for all English material that needs to be protected by the Crown copyright symbol:
- © Government of Canada, YYYY-MM-DD; or
- © Your English institution name, YYYY-MM-DD?
- Is one of the following provided for all English material that needs to be protected by the Crown copyright symbol:
- French page:
- Is one of the following provided for all French material that needs to be protected by the Crown copyright symbol:
- © Gouvernement du Canada, AAAA-MM-JJ; or
- © Your French institution name, AAAA-MM-JJ?
- Is one of the following provided for all French material that needs to be protected by the Crown copyright symbol:
- Bilingual or multilingual page:
- Is one of the following provided for all English material that needs to be protected by the Crown copyright symbol:
- © Government of Canada, YYYY-MM-DD; or
- © Your English institution name, YYYY-MM-DD?
- Is one of the following provided for all French material that needs to be protected by the Crown copyright symbol:
- © Gouvernement du Canada, AAAA-MM-JJ; or
- © Your French institution name, AAAA-MM-JJ?
- Is one of the following provided for all English material that needs to be protected by the Crown copyright symbol:
Part 3, R17 – Web analyzer tools
Compliance Criteria – Web page
Situation where applicable: Always
High priority criteria (failure of a criterion results in 0% compliance)
- Are important statistics for the page gathered unobtrusively by using Web analyzer tools to collect site usage data?
- Is the page free of counters that gather Web site statistics or collect site usage data?
Part 3, R18 – Server message pages
Compliance Criteria – Web page
Situation where applicable: Server message page
High priority criteria (failure of a criterion results in 0% compliance)
- Bilingual or multilingual site:
- Is a bilingual server message page provided?
- Unilingual English site:
- Is a unilingual English or bilingual server message page provided?
- Unilingual French site:
- Is a unilingual French or bilingual server message page provided?
- Is the "Canada" wordmark displayed in the upper right position of the page?
- Is the institutional signature displayed in the upper left position of the page?
- Are the "Canada" wordmark and the institutional signature not hyperlinked?
- Is a strip of colour measuring 760 pixels wide by 15 pixels high provided as the first element in the footer?
- Is the strip of colour presented using a single colour in the Web-Smart colour palette?
- Is the strip of colour free of graphics including images loaded through CSS?
- English server message page:
- Is the order of the official languages for bilingual institutional signatures English on the left and French on the right?
- Is the text of the server message, including instructions, permissions, confirmations and errors left aligned under the institutional signature?
- Is a content date indicator provided immediately below the colour strip in the footer, in the form "Date Modified: YYYY-MM-DD" to follow the ISO standard format for all-numeric date display?
- Is the content date indicator left aligned with the left margin of the page and included in the final line of content of the page?
- Is the date specified by the content date indicator the most recent date on which the content was formally issued, substantially changed, or reviewed?
- Is the important notices link provided in the footer with the link text "Important Notices"?
- Is the important notices link right aligned with the right margin of the page, vertically aligned with the content date indicator, and included in the final line of content of the page?
- Is the target of the important notices link one of the following:
- the English primary important notices page of the main institutional site; or
- the English primary important notices page of the current site or sub site?
- French server message page:
- Is the order of the official languages for bilingual institutional signatures French on the left and English on the right?
- Is the text of the server message, including instructions, permissions, confirmations and errors left aligned under the institutional signature?
- Is a content date indicator provided immediately below the colour strip in the footer, in the form "Date de modification : AAAA-MM-JJ" to follow the ISO standard format for all-numeric date display?
- Is the content date indicator left aligned with the left margin of the page and included in the final line of content of the page?
- Is the date specified by the content date indicator the most recent date on which the content was formally issued, substantially changed, or reviewed?
- Is the important notices link provided in the footer with the link text "Avis importants"?
- Is the important notices link right aligned with the right margin of the page, vertically aligned with the content date indicator, and included in the final line of content of the page?
- Is the target of the important notices link one of the following:
- the French primary important notices page of the main institutional site; or
- the French primary important notices page of the current site or sub site?
- Bilingual server message page provided by an office located outside of Quebec:
- Is the order of the official languages for bilingual institutional signatures English on the left and French on the right?
- Is the text of the server message, including instructions, permissions, confirmations and errors presented in two columns with the English server message in the left column and the French server message in the right column?
- Is the text of the English server message left aligned under the institutional signature?
- Is an English content date indicator provided immediately below the colour strip in the footer, in the form "Date Modified: YYYY-MM-DD" to follow the ISO standard format for all-numeric date display?
- Is a French content date indicator provided immediately below the colour strip in the footer, in the form "Date de modification : AAAA-MM-JJ" to follow the ISO standard format for all-numeric date display?
- Is the English content date indicator left aligned with the left margin of the page?
- Is the French content date indicator right aligned with the right margin of the page?
- Are the dates specified by the content date indicators the most recent date on which the content was formally issued, substantially changed, or reviewed?
- Is the English important notices link provided in the footer with the link text "Important Notices"?
- Is the French important notices link provided in the footer with the link text "Avis importants"?
- Is the English important notices link provided immediately below the English content date indicator, left aligned with the left margin of the page, and included in the final line of content of the page?
- Is the French important notices link provided immediately below the French content date indicator, right aligned with the right margin of the page, and included in the final line of content of the page?
- Is the target of the English important notices link one of the following:
- the English primary important notices page of the main institutional site; or
- the English primary important notices page of the current site or sub site?
- Is the target of the French important notices link one of the following:
- the French primary important notices page of the main institutional site; or
- the French primary important notices page of the current site or sub site?
- Bilingual server message page provided by an office located inside of Quebec:
- Is the order of the official languages for bilingual institutional signatures French on the left and English on the right?
- Is the text of the server message, including instructions, permissions, confirmations and errors presented in two columns with the French server message in the left column and the English server message in the right column?
- Is the text of the French server message left aligned under the institutional signature?
- Is a French content date indicator provided immediately below the colour strip in the footer, in the form "Date de modification : AAAA-MM-JJ" to follow the ISO standard format for all-numeric date display?
- Is an English content date indicator provided immediately below the colour strip in the footer, in the form "Date Modified: YYYY-MM-DD" to follow the ISO standard format for all-numeric date display?
- Is the French content date indicator left aligned with the left margin of the page?
- Is the English content date indicator right aligned with the right margin of the page?
- Are the dates specified by the content date indicators the most recent date on which the content was formally issued, substantially changed, or reviewed?
- Is the French important notices link provided in the footer with the link text "Avis importants"?
- Is the English important notices link provided in the footer with the link text "Important Notices"?
- Is the French important notices link provided immediately below the French content date indicator, left aligned with the left margin of the page, and included in the final line of content of the page?
- Is the English important notices link provided immediately below the English content date indicator, right aligned with the right margin of the page, and included in the final line of content of the page?
- Is the target of the French important notices link one of the following:
- the French primary important notices page of the main institutional site; or
- the French primary important notices page of the current site or sub site?
- Is the target of the English important notices link one of the following:
- the English primary important notices page of the main institutional site; or
- the English primary important notices page of the current site or sub site?
Part 3, Appendix A
Compliance Criteria – Web page
Situation where applicable: Welcome Page for a bilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional signature includes the flag symbol:
- Is the flag symbol in the institutional signature 20 pixels high?
- Institutional signature includes the Coat of Arms:
- Is the Coat of Arms in the institutional signature 50 pixels high?
- Is the institutional message space positioned 10 pixels below the institutional signature?
- Is the English important notices link positioned 10 pixels below the English language choice link?
- Is the French important notices link positioned 10 pixels below the French language choice link?
- Is the "Canada" wordmark 80 pixels wide by 20 pixels high?
Part 3, Appendix B
Compliance Criteria – Web page
Situation where applicable: Welcome Page for a unilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional signature includes the flag symbol:
- Is the flag symbol in the institutional signature 20 pixels high?
- Institutional signature includes the Coat of Arms:
- Is the Coat of Arms in the institutional signature 50 pixels high?
- Is the institutional message space positioned 10 pixels below the institutional signature?
- Is the bilingual message related to the Official Languages Act positioned 30 pixels below the site entry link (at the normal text size setting)?
- Welcome Page for a unilingual English site:
- Is the English part of the bilingual message related to the Official Languages Act provided above the French part of the same message?
- Welcome Page for a unilingual French site:
- Is the French part of the bilingual message related to the Official Languages Act provided above the English part of the same message?
- Is the "Canada" wordmark 80 pixels wide by 20 pixels high?
Part 3, Appendix C
Compliance Criteria – Web page
Situation where applicable: Welcome Page for a multilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional signature includes the flag symbol:
- Is the flag symbol in the institutional signature 20 pixels high?
- Institutional signature includes the Coat of Arms:
- Is the Coat of Arms in the institutional signature 50 pixels high?
- Is the institutional message space positioned 10 pixels below the institutional signature?
- Are additional language choice link(s) presented below the English and French language choice links?
- Are additional language choice link(s) presented with 20 pixel vertical separation between rows (at the normal text size setting)?
- Are no more than three additional language choice link(s) presented on each row?
- Is the English important notices link positioned 10 pixels below the bottom-most language choice link that is left aligned with the English language choice link?
- Is the French important notices link positioned 10 pixels below the bottom-most language choice link that is left aligned with the French language choice link?
- Is the "Canada" wordmark 80 pixels wide by 20 pixels high?
Part 3, Appendix D
Compliance Criteria – Web page
Situation where applicable: English or French content page for a bilingual or multilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional signature includes the flag symbol:
- Is the flag symbol in the institutional signature 20 pixels high?
- Institutional signature includes the Coat of Arms:
- Is the Coat of Arms in the institutional signature 50 pixels high?
- Is the "Canada" wordmark 80 pixels wide by 20 pixels high?
- Are the left, right, and top margins of the page 10 pixels?
- Is the institutional banner 760 pixels wide by 80 pixels high (at the normal text size setting)?
- Are the top of the side menu(s) and the content area positioned 20 pixels below the common menu bar (at the normal text size setting)?
- Content page with a three-column layout:
- Is a visible 1-pixel-wide border provided surrounding the content in the content area?
- Are the left, right, and top edges of the visible 1-pixel-wide border positioned at the left, right, and top edges of the content area?
- Main page for a site or sub site:
- Is a strip of colour measuring 150 pixels wide by 15 pixels high provided immediately above the Proactive Disclosure link?
- Is the strip of colour presented using a single colour in the Web-Smart colour palette?
- Is the strip of colour free of graphics including images loaded through CSS?
- Is the triangle graphic in the top of page link vertically oriented and 19 pixels wide by 12 pixels high (at the normal text size setting)?
- Are the content date indicator, top of page link, and important notices link positioned 5 pixels below the colour strip in the footer?
Part 3, Appendix E
Compliance Criteria – Web page
Situation where applicable: Content page for a unilingual site
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional signature includes the flag symbol:
- Is the flag symbol in the institutional signature 20 pixels high?
- Institutional signature includes the Coat of Arms:
- Is the Coat of Arms in the institutional signature 50 pixels high?
- Is the "Canada" wordmark 80 pixels wide by 20 pixels high?
- Are the left, right, and top margins of the page 10 pixels?
- Is the institutional banner 760 pixels wide by 80 pixels high (at the normal text size setting)?
- Are the top of the side menu(s) and the content area positioned 20 pixels below the common menu bar (at the normal text size setting)?
- Content page with a three-column layout:
- Is a visible 1-pixel-wide border provided surrounding the content in the content area?
- Are the left, right, and top edges of the visible 1-pixel-wide border positioned at the left, right, and top edges of the content area?
- Main page for a site or sub site:
- Is a strip of colour measuring 150 pixels wide by 15 pixels high provided immediately above the Proactive Disclosure link?
- Is the strip of colour presented using a single colour in the Web-Smart colour palette?
- Is the strip of colour free of graphics including images loaded through CSS?
- Is the triangle graphic in the top of page link vertically oriented and 19 pixels wide by 12 pixels high (at the normal text size setting)?
- Are the content date indicator, top of page link, and important notices link positioned 5 pixels below the colour strip in the footer?
Part 3, Appendix F
Compliance Criteria – Web page
Situation where applicable: Content page in a language other than English or French
High priority criteria (failure of a criterion results in 0% compliance)
- Institutional signature includes the flag symbol:
- Is the flag symbol in the institutional signature 20 pixels high?
- Institutional signature includes the Coat of Arms:
- Is the Coat of Arms in the institutional signature 50 pixels high?
- Is the "Canada" wordmark 80 pixels wide by 20 pixels high?
- Are the left, right, and top margins of the page 10 pixels?
- Is the institutional banner 760 pixels wide by 80 pixels high (at the normal text size setting)?
- Navigation path is provided in the language of the page:
- Are the top of the side menu(s) and the content area positioned 20 pixels below the common menu bars (at the normal text size setting)?
- Navigation path is not provided in the language of the page:
- Are the top of the side menu(s) and the content area positioned 40 pixels below the common menu bars (at the normal text size setting)?
- Multilingual site provided by an office outside of Quebec:
- Is the English navigation path provided above the French navigation path?
- Multilingual site provided by an office inside of Quebec:
- Is the French navigation path provided above the English navigation path?
- Multilingual site provided by an office outside of Quebec:
- Is the English important notices link provided above the French important notices link?
- Multilingual site provided by an office inside of Quebec:
- Is the French important notices link provided above the English important notices link?
- Content page with a three-column layout:
- Is a visible 1-pixel-wide border provided surrounding the content in the content area?
- Are the left, right, and top edges of the visible 1-pixel-wide border positioned at the left, right, and top edges of the content area?
- Main page for a site or sub site:
- Is a strip of colour measuring 150 pixels wide by 15 pixels high provided immediately above the Proactive Disclosure link?
- Is the strip of colour presented using a single colour in the Web-Smart colour palette?
- Is the strip of colour free of graphics including images loaded through CSS?
- Is the triangle graphic in the top of page link vertically oriented and 19 pixels wide by 12 pixels high (at the normal text size setting)?
- Are the content date indicator, top of page link, and important notices link positioned 5 pixels below the colour strip in the footer?
Part 4: Standard on Email
Part 4, R1 – Email Addresses
Part 4, R1.1 – Naming convention
Compliance Criteria – Web page
Situation where applicable: Page contains at least one email address associated with a Government of Canada employee
High priority criteria (failure of a criterion results in 0% compliance)
- Is the portion of the email address preceding the @ sign for each email address associated with a Government of Canada employee in the order of the employee's given name on the left and family name on the right with a period separating the two names and including any additional characters needed to resolve naming conflicts (such as John.Smith@)?
Compliance Criteria – Email system
Situation where applicable: Email account associated with a Government Canada employee
High priority criteria (failure of a criterion results in 0% compliance)
- Is the portion of the email address preceding the @ sign for the "From" and "Reply-To" email addresses for each email account associated with a Government of Canada employee in the order of the employee's given name on the left and family name on the right with a period separating the two names and including any additional characters needed to resolve naming conflicts (such as John.Smith@)?
Part 4, R1.2 – Domain name
Compliance Criteria – Web page
Situation where applicable: Page contains at least one email address associated with a Government of Canada employee
High priority criteria (failure of a criterion results in 0% compliance)
- Is the domain name in the .gc.ca sub domain for each email address associated with a Government of Canada employee?
- Is the domain name one of the following for each email address associated with a Government of Canada employee:
- domain name used for either the "From" or "Reply-To" email address of the email account associated with the Government of Canada employee?
- Employee of a unilingual institution:
- primary domain name of the main institutional Web site?
- Employee of a bilingual institution:
-
Primary domain name of the main institutional site has the same meaning and spelling in both official languages (such as ec.gc.ca):
- primary domain name of the main institutional Web site (such as @ec.gc.ca)?
-
Primary domain name of the main institutional site is in both official languages
with a hyphen separating the two languages (such as
tbs-sct.gc.ca):
- English page:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca); or
- unilingual English version of the primary domain name of the main institutional Web site (such as @tbs.gc.ca or @inac.gc.ca)?
- French page:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca); or
- unilingual French version of the primary domain name of the main institutional Web site (such as @sct.gc.ca or @ainc.gc.ca)?
- Bilingual or multilingual page provided by an office outside of Quebec:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca)?
- Bilingual or multilingual page provided by an office inside of Quebec:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca)?
- Page in a language other than English or French provided by an office outside of Quebec:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca)?
- Page in a language other than English or French provided by an office inside of Quebec:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca)?
- English page:
-
Primary domain name of the main institutional site has the same meaning and spelling in both official languages (such as ec.gc.ca):
Compliance Criteria – Email system
Situation where applicable: Email account associated with a Government of Canada employee
High priority criteria (failure of a criterion results in 0% compliance)
- Is the domain name in the .gc.ca sub domain used for the "From" and "Reply-To" email addresses of each email account associated with a Government of Canada employee?
- Are the domain names the same and one of the following for the "From" and "Reply-To" email addresses of each email account associated
with a Government of Canada employee:
- Employee of a unilingual institution:
- primary domain name of the main institutional Web site?
- Employee of a bilingual institution:
-
Primary domain name of the main institutional site has the same meaning and spelling in both official languages (such as ec.gc.ca):
- primary domain name of the main institutional Web site (such as @ec.gc.ca)?
-
Primary domain name of the main institutional site is in both official languages
with a hyphen separating the two languages (such as
tbs-sct.gc.ca):
- Employee located in a bilingual office outside of Quebec:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca)?
- Employee located in a bilingual office inside of Quebec:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca)?
- Employee located in a unilingual English office:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca); or
- unilingual English version of the primary domain name of the main institutional Web site (such as @tbs.gc.ca or @inac.gc.ca)?
- Employee located in a unilingual French office:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca); or
- unilingual French version of the primary domain name of the main institutional Web site (such as @sct.gc.ca or @ainc.gc.ca)?
- Employee located in a bilingual office outside of Quebec:
-
Primary domain name of the main institutional site has the same meaning and spelling in both official languages (such as ec.gc.ca):
- Employee of a unilingual institution:
Part 4, R2 – Generic email addresses
Compliance Criteria – Web page
Situation where applicable: Page contains at least one generic Government of Canada email address
High priority criteria (failure of a criterion results in 0% compliance)
- Is the domain name in the .gc.ca sub domain for each generic Government of Canada email address?
- Is the portion of the email address preceding the @ sign one of the following for each generic Government of Canada email address:
- portion of the email address preceding the @ sign for either the "From" or "Reply-To" email address of the associated generic Government of Canada email account?
- Email address associated with a unilingual English office:
- elements or acronyms in English only (such as clf@)?
- Email address associated with a unilingual French office:
- elements or acronyms in French only (such as nsi@)?
- English page:
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as clf-nsi@); or
- elements or acronyms in English only (such as clf@)?
- French page:
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as nsi-clf@); or
- elements or acronyms in French only (such as nsi@)?
- Bilingual or multilingual page provided by an office outside of Quebec:
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as clf-nsi@)?
- Bilingual or multilingual page provided by an office inside of Quebec:
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as nsi-clf@)?
- Page in a language other than English or French provided by an office outside of Quebec:
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as clf-nsi@)?
- Page in a language other than English or French provided by an office inside of Quebec:
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as nsi-clf@)?
- Is the domain name one of the following for each generic Government of Canada email address
- domain name used for either the "From" or "Reply-To" email address of the associated generic Government of Canada email account?
- Email address associated with a unilingual institution:
- primary domain name of the main institutional Web site?
- Email address associated with a bilingual institution:
-
Primary domain name of the main institutional site has the same meaning and spelling in both official languages (such as ec.gc.ca):
- primary domain name of the main institutional Web site (such as @ec.gc.ca)?
-
Primary domain name of the main institutional site is in both official languages
with a hyphen separating the two languages (such as
tbs-sct.gc.ca):
- English page:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca); or
- unilingual English version of the primary domain name of the main institutional Web site (such as @tbs.gc.ca or @inac.gc.ca)?
- French page:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca); or
- unilingual French version of the primary domain name of the main institutional Web site (such as @sct.gc.ca or @ainc.gc.ca)?
- Bilingual or multilingual page provided by an office outside of Quebec:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca)?
- Bilingual or multilingual page provided by an office inside of Quebec:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca)?
- Page in a language other than English or French provided by an office outside of Quebec:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca)?
- Page in a language other than English or French provided by an office inside of Quebec:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca)?
- English page:
-
Primary domain name of the main institutional site has the same meaning and spelling in both official languages (such as ec.gc.ca):
Compliance Criteria – Email system
Situation where applicable: Generic Government of Canada email account
High priority criteria (failure of a criterion results in 0% compliance)
- Is the domain name in the .gc.ca sub domain used for the "From" and "Reply-To" email addresses of each generic Government of Canada email account?
- Are the portions of the email addresses preceding the @ sign either the same or different (such as clf-nsi@ and re-clf-nsi@) and one of the following for the
"From" and "Reply-To" email addresses of each generic Government of Canada email account:
- elements or acronyms with the same meaning and spelling in both official languages (such as service@)?
- Email account associated with a bilingual office outside of Quebec:
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as clf-nsi@)?
- Email account associated with a bilingual office inside of Quebec:
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as nsi-clf@)?
- Email account associated with a unilingual English office:
- elements or acronyms in both official languages in the order of English on the left and French on the right with a hyphen separating the two languages (such as clf-nsi@); or
- elements or acronyms in English only (such as clf@)?
- Email account associated with a unilingual French office:
- elements or acronyms in both official languages in the order of French on the left and English on the right with a hyphen separating the two languages (such as nsi-clf@); or
- elements or acronyms in French only (such as nsi@)?
- Are the domain names the same and one of the following for the "From" and "Reply-To" email addresses for each generic Government of
Canada email account:
- Email account associated with a unilingual institution:
- primary domain name of the main institutional Web site?
- Email account associated with a bilingual institution:
-
Primary domain name of the main institutional site has the same meaning and spelling in both official languages (such as ec.gc.ca):
- primary domain name of the main institutional Web site (such as @ec.gc.ca)?
-
Primary domain name of the main institutional site is in both official languages
with a hyphen separating the two languages (such as
tbs-sct.gc.ca):
- Email account associated with a bilingual office outside of Quebec:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca)?
- Email account associated with a bilingual office inside of Quebec:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca)?
- Email account associated with a unilingual English office:
- primary domain name of the main institutional Web site with the order of English on the left and French on the right (such as @tbs-sct.gc.ca or @inac-ainc.gc.ca); or
- unilingual English version of the primary domain name of the main institutional Web site (such as @tbs.gc.ca or @inac.gc.ca)?
- Email account associated with a unilingual French office:
- primary domain name of the main institutional Web site with the order of French on the left and English on the right (such as @sct-tbs.gc.ca or @ainc-inac.gc.ca); or
- unilingual French version of the primary domain name of the main institutional Web site (such as @sct.gc.ca or @ainc.gc.ca)?
- Email account associated with a bilingual office outside of Quebec:
-
Primary domain name of the main institutional site has the same meaning and spelling in both official languages (such as ec.gc.ca):
- Email account associated with a unilingual institution:
Part 4, R3 – Email signature blocks
Part 4, R3.1 – Contact information for individuals
Compliance Criteria – Web page
Not included in the assessment of a Web page
Compliance Criteria – Email system
Situation where applicable: Email account associated with a Government of Canada employee
High priority criteria (failure of a criterion results in 0% compliance)
- Is the signature block for the email account associated with a Government of Canada employee included in the initial email, response, or forward of any email thread involving one or more non-Government of Canada recipients?
- Employee located in a bilingual office outside of Quebec:
- Are all signature block elements provided in both official languages in the order of English on the left and French on the right with a vertical bar separating the two languages (such as "Telephone | Téléphone")?
- Employee located in a bilingual office inside of Quebec:
- Are all signature block elements provided in both official languages in the order of French on the left and English on the right with a vertical bar separating the two languages (such as "Téléphone | Telephone")?
- Employee located in a unilingual English office:
- Is the signature block one of the following:
- signature block elements in both official languages in the order of English on the left and French on the right with a vertical bar separating the two languages (such as "Telephone | Téléphone"); or
- signature block elements in English only (such as "Telephone")?
- Is the signature block one of the following:
- Employee located in a unilingual French office:
- Is the signature block one of the following:
- signature block elements in both official languages in the order of French on the left and English on the right with a vertical bar separating the two languages (such as "Téléphone | Telephone"); or
- signature block elements in French only (such as "Téléphone")?
- Is the signature block one of the following:
- Are the following elements included in the signature block at a minimum:
- the sender's given name or initial(s);
- the sender's family name;
- the sender's organizational information (such as the individual's title, branch, or division);
- the "From" email address;
- Employee located in a bilingual office outside of Quebec:
- the telephone number with area code in the format 123-456-7890 and extension number preceded by the words "Telephone | Téléphone";
- the teletypewriter number with area code in the format 123-456-7890 preceded by the words "Teletypewriter | Téléimprimeur";
- the facsimile number with area code in the format 123-456-7890 preceded by the words "Facsimile | Télécopieur";
- the text "Government of Canada | Gouvernement du Canada";
- Employee located in a bilingual office inside of Quebec:
- the telephone number with area code in the format 123-456-7890 and extension number preceded by the words "Téléphone | Telephone";
- the teletypewriter number with area code in the format 123-456-7890 preceded by the words "Téléimprimeur | Teletypewriter";
- the facsimile number with area code in the format 123-456-7890 preceded by the words "Télécopieur | Facsimile";
- the text "Gouvernement du Canada | Government of Canada";
- Employee located in a unilingual English office:
- the telephone number with area code in the format 123-456-7890 and extension number preceded by the words "Telephone | Téléphone" or "Telephone";
- the teletypewriter number with area code in the format 123-456-7890 preceded by the words "Teletypewriter | Téléimprimeur" or "Teletypewriter";
- the facsimile number with area code in the format 123-456-7890 preceded by the words "Facsimile | Télécopieur" or "Facsimile";
- the text "Government of Canada | Gouvernement du Canada" or "Government of Canada";
- Employee located in a unilingual French office:
- the telephone number with area code in the format 123-456-7890 and extension number preceded by the words "Téléphone | Telephone" or "Téléphone";
- the teletypewriter number with area code in the format 123-456-7890 preceded by the words "Téléimprimeur | Teletypewriter" or "Téléimprimeur";
- the facsimile number with area code in the format 123-456-7890 preceded by the words "Télécopieur | Facsimile" or "Télécopieur";
- the text "Gouvernement du Canada | Government of Canada" or "Gouvernement du Canada";
- the postal address; and
- the institution's applied title?
Part 4, R3.2 – Contact information for a program or service
Compliance Criteria – Web page
Not included in the assessment of a Web page
Compliance Criteria – Email system
Situation where applicable: Generic Government of Canada email account
High priority criteria (failure of a criterion results in 0% compliance)
- Is the signature block for the generic Government of Canada email account included in the initial email, response, or forward of any email thread involving one or more non-Government of Canada recipients?
- Email account associated with a bilingual office outside of Quebec:
- Are all signature block elements provided in both official languages in the order of English on the left and French on the right with a vertical bar separating the two languages (such as "Telephone | Téléphone")?
- Email account associated with a bilingual office inside of Quebec:
- Are all signature block elements provided in both official languages in the order of French on the left and English on the right with a vertical bar separating the two languages (such as "Téléphone | Telephone")?
- Email account associated with a unilingual English office:
- Is the signature block one of the following:
- signature block elements in both official languages in the order of English on the left and French on the right with a vertical bar separating the two languages (such as "Telephone | Téléphone"); or
- signature block elements in English only (such as "Telephone")?
- Is the signature block one of the following:
- Email account associated with a unilingual French office:
- Is the signature block one of the following:
- signature block elements in both official languages in the order of French on the left and English on the right with a vertical bar separating the two languages (such as "Téléphone | Telephone"); or
- signature block elements in French only (such as "Téléphone")?
- Is the signature block one of the following:
- Are the following elements included in the signature block at a minimum:
- the program or service name;
- the "From" email address;
- Email account associated with a bilingual office outside of Quebec:
- the telephone number with area code in the format 123-456-7890 and extension number preceded by the words "Telephone | Téléphone";
- the teletypewriter number with area code in the format 123-456-7890 preceded by the words "Teletypewriter | Téléimprimeur";
- the facsimile number with area code in the format 123-456-7890 preceded by the words "Facsimile | Télécopieur";
- the text "Government of Canada | Gouvernement du Canada";
- Email account associated with a bilingual office inside of Quebec:
- the telephone number with area code in the format 123-456-7890 and extension number preceded by the words "Téléphone | Telephone";
- the teletypewriter number with area code in the format 123-456-7890 preceded by the words "Téléimprimeur | Teletypewriter";
- the facsimile number with area code in the format 123-456-7890 preceded by the words "Télécopieur | Facsimile";
- the text "Gouvernement du Canada | Government of Canada";
- Email account associated with a unilingual English office:
- the telephone number with area code in the format 123-456-7890 and extension number preceded by the words "Telephone | Téléphone" or "Telephone";
- the teletypewriter number with area code in the format 123-456-7890 preceded by the words "Teletypewriter | Téléimprimeur" or "Teletypewriter";
- the facsimile number with area code in the format 123-456-7890 preceded by the words "Facsimile | Télécopieur" or "Facsimile";
- the text "Government of Canada | Gouvernement du Canada" or "Government of Canada";
- Generic email account associated with a unilingual French office:
- the telephone number with area code in the format 123-456-7890 and extension number preceded by the words "Téléphone | Telephone" or "Téléphone";
- the teletypewriter number with area code in the format 123-456-7890 preceded by the words "Téléimprimeur | Teletypewriter" or "Téléimprimeur";
- the facsimile number with area code in the format 123-456-7890 preceded by the words "Télécopieur | Facsimile" or "Télécopieur";
- the text "Gouvernement du Canada | Government of Canada" or "Gouvernement du Canada";
- the postal address; and
- the institution's applied title?
Part 4, R3.3 – Visual identifiers
Compliance Criteria – Web page
Not included in the assessment of a Web page
Compliance Criteria – Email system
Situation where applicable: Institution's email system supports the incorporation of visual identifiers in an accessible manner
High priority criteria (failure of a criterion results in 0% compliance)
- Are the institutional signature and the "Canada" wordmark included in the signature block?
- HTML-format email system:
- Are text equivalents provided in the form of alt text for the institutional signature and the "Canada" wordmark?
- Email account associated with a bilingual office outside of Quebec:
- Is the order of the official languages for the alt text English on the left and French on the right?
- Email account associated with a bilingual office inside of Quebec:
- Is the order of the official languages for the alt text French on the left and English on the right?
- Email account associated with a bilingual office outside of Quebec:
- Is the order of the official languages for bilingual institutional signatures English on the left and French on the right?
- Email account associated with a bilingual office inside of Quebec:
- Is the order of the official languages for bilingual institutional signatures French on the left and English on the right?
- Email account associated with a unilingual English office:
- Is the order of the official languages for bilingual institutional signatures English on the left and French on the right?
- Email account associated with a unilingual French office:
- Is the order of the official languages for bilingual institutional signatures French on the left and English on the right?
Part 4, R3.4 – Presentation of signature block
Compliance Criteria – Web page
Not included in the assessment of a Web page
Compliance Criteria – Email system
Situation where applicable: Institution's email system supports configuration of the font face, the font size, or the foreground/background colours of any signature block elements
High priority criteria (failure of a criterion results in 0% compliance)
- Is a sans-serif font face (such as Verdana or Arial) used for all text included in the signature block?
- Is a font size in the range of 10 to 16 points used for all text included in the signature block?
- Are the foreground and background colours neutral (such as black and white) for all meaningful information and the associated backgrounds in the signature block?
- Is there at least a 4:1 contrast ratio between all meaningful information and the associated backgrounds in the signature block?
Medium priority criteria (failure of a criterion results in 50% compliance)
- Is there at least a 4.25:1 contrast ratio between all meaningful information and the associated backgrounds in the signature block?
Low priority criteria (failure of a criterion results in 75% compliance)
- Is there at least a 4.5:1 contrast ratio between all meaningful information and the associated backgrounds in the signature block?
References
- Email Signature Block Examples
- Contrast Analyser (the paciello group)
- Effective Colour Contrast (Lighthouse)
- Making Text Legible (Lighthouse)
- Vischeck: About Vischeck (Vischeck)
- G18: Ensuring that a contrast ratio of at least 4.5:1 exists between text (and images of text) and background behind the text (WCAG 2.0)
- G145: Ensuring that a contrast ratio of at least 3:1 exists between text (and images of text) and background behind the text (WCAG 2.0)
- Contrast ratio (Glossary)
- Meaningful information (Glossary)
- Normal text size setting (Glossary)
Part 4, R3.5 – Consistency in application
Compliance Criteria – Web page
Not included in the assessment of a Web page
Compliance Criteria – Email system
Situation where applicable: Feasible for the institution's email system administrators to manage the fulfillment of Part 4, Requirements 3.1, 3.2, and 3.3
High priority criteria (failure of a criterion results in 0% compliance)
- Is the fulfillment of Part 4, Requirements 3.1, 3.2, and 3.3 managed by the institution's email system administrators rather than by individual employees?
Part 4, R4 – Third-party references
Compliance Criteria – Web page
Not included in the assessment of a Web page
Compliance Criteria – Email system
Situation where applicable: Signature block and message footer for each Government of Canada email account included in the initial email, response, or forward of any email thread involving one or more non-Government of Canada recipients
High priority criteria (failure of a criterion results in 0% compliance)
- Are the signature block and message footer free of any references to third-party software and hardware vendors?
Individual Weightings
Individual Weightings for each Standard Part
| Part | Weighting (%) |
|---|---|
| Part 1: Standard on Web Addresses | 10% |
| Part 2: Standard on the Accessibility, Interoperability and Usability of Web Sites | 50% |
| Part 3: Standard on Common Web Page Formats | 35% |
| Part 4: Standard on Email | 5% |
Individual Weightings for each Requirement and Checkpoint
Part 1: Standard on Web Addresses
| Requirement | Web page | Domain names for a site or sub site |
Weighting (1 to 5, lowest to highest) | ||
|---|---|---|---|---|---|
| Include in the assessment? | Situation where applicable | Include in the assessment? | Situation where applicable | ||
| Part 1, R1 | n/a | n/a | n/a | n/a | n/a |
| Part 1, R1.1 | n/a | n/a | n/a | n/a | n/a |
| Part 1, R1.1.1 | No | n/a | Yes | Always | 5 |
| Part 1, R1.1.2 | No | n/a | Yes | Site | 3 |
| Part 1, R1.2 | No | n/a | Yes | Site or sub site where one or more domain names that could be perceived as being associated to the site or sub site are registered by private individuals or entities with apparent bad-faith intent | 3 |
| Part 1, R2 | Yes | Always | No | n/a | 4 |
Part 2: Standard on the Accessibility, Interoperability and Usability of Web Sites
| Requirement / Checkpoint | Priority | Web page | Weighting (1 to 5, lowest to highest) | |
|---|---|---|---|---|
| Include in the assessment? | Situation where applicable | |||
| Part 2, R1 | n/a | n/a | n/a | n/a |
| Part 2, R1 – 1.1 | 1 | Yes | Always | 5 |
| Part 2, R1 – 1.2 | 1 | Yes | Page contains at least one server-side image map | 5 |
| Part 2, R1 – 1.3 | 1 | Yes | Page contains multimedia | 5 |
| Part 2, R1 – 1.4 | 1 | Yes | Page contains multimedia | 5 |
| Part 2, R1 – 2.1 | 1 | Yes | Always | 5 |
| Part 2, R1 – 2.2 | 2 | Yes | Always | 4 |
| Part 2, R1 – 3.1 | 2 | Yes | Always | 4 |
| Part 2, R1 – 3.2 | 2 | Yes | Always | 5 |
| Part 2, R1 – 3.3 | 2 | Yes | Always | 4 |
| Part 2, R1 – 3.4 | 2 | Yes | Always | 4 |
| Part 2, R1 – 3.5 | 2 | Yes | Always | 4 |
| Part 2, R1 – 3.6 | 2 | Yes | Page contains list markup or at least one list | 3 |
| Part 2, R1 – 3.7 | 2 | Yes | Page contains quotation markup or at least one quotation | 3 |
| Part 2, R1 – 4.1 | 1 | Yes | Always | 5 |
| Part 2, R1 – 5.1 | 1 | Yes | Page contains at least one data table | 4 |
| Part 2, R1 – 5.2 | 1 | Yes | Page contains at least one data table with two or more logical levels of row or column headers | 4 |
| Part 2, R1 – 5.3 | 2 | Yes | Always | 4 |
| Part 2, R1 – 5.4 | 2 | Yes | Page contains at least one layout table | 4 |
| Part 2, R1 – 6.1 | 1 | Yes | Always | 4 |
| Part 2, R1 – 6.2 | 1 | Yes | Page contains dynamic content | 5 |
| Part 2, R1 – 6.3 | 1 | Yes | Page contains scripting or at least one programmatic object | 5 |
| Part 2, R1 – 6.4 | 2 | Yes | Page contains at least one event handler | 4 |
| Part 2, R1 – 6.5 | 2 | Yes | Page contains inaccessible dynamic content or at least one frameset | 3 |
| Part 2, R1 – 7.1 | 1 | Yes | Always | 5 |
| Part 2, R1 – 7.2 | 2 | Yes | Always | 3 |
| Part 2, R1 – 7.3 | 2 | Yes | Always | 3 |
| Part 2, R1 – 7.4 | 2 | Yes | Always | 4 |
| Part 2, R1 – 7.5 | 2 | Yes | Always | 2 |
| Part 2, R1 – 8.1 | 1 | Yes | Page contains scripting or at least one programmatic object | 5 |
| Part 2, R1 – 9.1 | 1 | Yes | Page contains at least one image map | 4 |
| Part 2, R1 – 9.2 | 2 | Yes | Page contains scripting or at least one programmatic object with its own custom interface | 4 |
| Part 2, R1 – 9.3 | 2 | Yes | Page contains at least one event handler | 4 |
| Part 2, R1 – 10.1 | 2 | Yes | Always | 3 |
| Part 2, R1 – 10.2 | 2 | Yes | Page contains at least one Web form | 5 |
| Part 2, R1 – 11.1 | 2 | Yes | Always | 3 |
| Part 2, R1 – 11.2 | 2 | Yes | Always | 4 |
| Part 2, R1 – 11.4 | 1 | Yes | Page contains at least one non-W3C technology that is causing a large proportion of the page to be inaccessible | 5 |
| Part 2, R1 – 12.1 | 1 | Yes | Page contains at least one frameset | 5 |
| Part 2, R1 – 12.2 | 2 | Yes | Page contains at least one frameset | 4 |
| Part 2, R1 – 12.3 | 2 | Yes | Always | 4 |
| Part 2, R1 – 12.4 | 2 | Yes | Always | 5 |
| Part 2, R1 – 13.1 | 2 | Yes | Always | 5 |
| Part 2, R1 – 13.2 | 2 | Yes | Always | 1 |
| Part 2, R1 – 13.3 | 2 | Yes | Content page | 2 |
| Part 2, R1 – 13.4 | 2 | Yes | Page contains at least one navigation mechanism | 4 |
| Part 2, R1 – 14.1 | 1 | Yes | Always | 3 |
| Part 2, R2 | n/a | Yes | Always | 5 |
| Part 2, R3 | n/a | Yes | Always | 5 |
| Part 2, R4 | n/a | Yes | Page contains non-XHTML content or at least one link to a non-XHTML document | 4 |
| Part 2, R5 | n/a | Yes | Always | 4 |
| Part 2, R6 | n/a | Yes | Always | 5 |
Part 3: Standard on Common Web Page Formats
| Requirement | Web page | Weighting (1 to 5, lowest to highest) | |
|---|---|---|---|
| Include in the assessment? | Situation where applicable | ||
| Part 3, R1 | Yes | Main point of entry to a site | 4 |
| Part 3, R1.1 | Yes | Welcome Page | 4 |
| Part 3, R1.2 | Yes | Welcome Page | 4 |
| Part 3, R1.3 | Yes | Welcome Page | 3 |
| Part 3, R1.4 | n/a | n/a | n/a |
| Part 3, R1.4.1 | Yes | Welcome Page for a bilingual site | 3 |
| Part 3, R1.4.2 | Yes | Welcome Page for a unilingual site | 3 |
| Part 3, R1.4.3 | Yes | Welcome Page for a multilingual site | 3 |
| Part 3, R2 | n/a | n/a | n/a |
| Part 3, R2.1 | Yes | Content page | 3 |
| Part 3, R2.2 | Yes | Content page | 2 |
| Part 3, R2.2.1 | Yes | Content page with a three-column layout or a main page for a site or sub site | 4 |
| Part 3, R2.2.2 | Yes | Content page with a two-column layout | 4 |
| Part 3, R2.2.3 | Yes | Content page with a one-column layout | 4 |
| Part 3, R2.3 | Yes | Content page | 2 |
| Part 3, R2.4 | Yes | Content page | 5 |
| Part 3, R2.5 | Yes | Content page | 4 |
| Part 3, R2.6 | Yes | Printer friendly version of a content page | 4 |
| Part 3, R3 | Yes | Always | 4 |
| Part 3, R4 | Yes | Content page | 3 |
| Part 3, R4.1 | Yes | Content page | 2 |
| Part 3, R4.2 | Yes | Content page | 3 |
| Part 3, R4.2.1 | Yes | Content page with a background colour for the banner background | 3 |
| Part 3, R4.2.2 | Yes | Content page with a background image for the banner background | 3 |
| Part 3, R4.3 | Yes | Content page with banner multimedia elements | 4 |
| Part 3, R4.4 | n/a | n/a | n/a |
| Part 3, R4.4.1 | Yes | Content page | 3 |
| Part 3, R4.4.2 | Yes | Content page | 3 |
| Part 3, R4.4.3 | Yes | Content page | 4 |
| Part 3, R5 | Yes | Content page | 5 |
| Part 3, R5.1 | Yes | Content page for a bilingual site | 5 |
| Part 3, R5.2 | Yes | Content page for a unilingual site | 5 |
| Part 3, R5.3 | Yes | Content page in a language other than English or French | 5 |
| Part 3, R5.4 | Yes | Content page | 4 |
| Part 3, R5.5 | Yes | Content page for a secure section of a site or a Web application | 3 |
| Part 3, R5.6 | Yes | Content page contains a link to a non-XHTML document | 3 |
| Part 3, R5.7 | Yes | Content page | 4 |
| Part 3, R5.8 | Yes | Content page | 5 |
| Part 3, R5.9 | Yes | Content page | 4 |
| Part 3, R5.10 | Yes | Content page | 4 |
| Part 3, R5.11 | Yes | Content page | 4 |
| Part 3, R5.12 | Yes | Content page | 4 |
| Part 3, R5.13 | Yes | Content page | 4 |
| Part 3, R6 | Yes | Contact Us page | 5 |
| Part 3, R6.1 | Yes | Page contains a Web form or a generic email address that is provided as a means of contacting the institution | 3 |
| Part 3, R7 | Yes | Content page | 3 |
| Part 3, R8 | Yes | Content page with a two-column or three-column layout | 3 |
| Part 3, R9 | Yes | Content page with a three-column layout | 3 |
| Part 3, R10 | Yes | Main page for a site or sub site | 4 |
| Part 3, R11 | Yes | Always | 3 |
| Part 3, R12 | Yes | Page contains at least one online form where personal information is meant to be entered or the page leads to subsequent pages where at least one persistent cookie occurs | 5 |
| Part 3, R13 | n/a | n/a | n/a |
| Part 3, R13.1 | Yes | Content page | 2 |
| Part 3, R13.2 | Yes | Content page | 3 |
| Part 3, R13.3 | Yes | Content page | 2 |
| Part 3, R13.4 | Yes | Content page | 4 |
| Part 3, R14 | n/a | n/a | n/a |
| Part 3, R14.1 | Yes | Important Notices page | 5 |
| Part 3, R14.2 | Yes | Important Notices page | 5 |
| Part 3, R14.3 | Yes | Important Notices page | 3 |
| Part 3, R14.4 | Yes | Important Notices page | 5 |
| Part 3, R14.5 | Yes | Important Notices page | 5 |
| Part 3, R15 | Yes | Page contains third-party information | 4 |
| Part 3, R16 | Yes | Page contains specific material that needs to be protected by the Crown copyright symbol | 4 |
| Part 3, R17 | Yes | Always | 2 |
| Part 3, R18 | Yes | Server message page | 4 |
| Part 3, Appendix A | Yes | Welcome Page for a bilingual site | 3 |
| Part 3, Appendix B | Yes | Welcome Page for a unilingual site | 3 |
| Part 3, Appendix C | Yes | Welcome Page for a multilingual site | 3 |
| Part 3, Appendix D | Yes | English or French content page for a bilingual or multilingual site | 3 |
| Part 3, Appendix E | Yes | Content page for a unilingual site | 3 |
| Part 3, Appendix F | Yes | Content page in a language other than English or French | 3 |
Part 4: Standard on Email
| Requirement | Web page | Email system | Weighting (1 to 5, lowest to highest) | ||
|---|---|---|---|---|---|
| Include in the assessment? | Situation where applicable | Include in the assessment? | Situation where applicable | ||
| Part 4, R1 | n/a | n/a | n/a | n/a | n/a |
| Part 4, R1.1 | Yes | Page contains an email address for a Government of Canada employee | Yes | Email account associated with a Government of Canada employee | 3 |
| Part 4, R1.2 | Yes | Page contains a Government of Canada email address | Yes | Email account associated with a Government of Canada employee | 5 |
| Part 4, R2 | Yes | Page contains a Government of Canada generic email address | Yes | Generic Government of Canada email account | 5 |
| Part 4, R3 | n/a | n/a | n/a | n/a | n/a |
| Part 4, R3.1 | No | n/a | Yes | Email account associated with a Government of Canada employee | 4 |
| Part 4, R3.2 | No | n/a | Yes | Generic Government of Canada email account | 4 |
| Part 4, R3.3 | No | n/a | Yes | Institution's email system supports the incorporation of visual identifiers in an accessible manner | 4 |
| Part 4, R3.4 | No | n/a | Yes | Institution's email system supports configuration of the font face, the font size, or the foreground/background colours of any signature block elements | 3 |
| Part 4, R3.5 | No | n/a | Yes | Feasible for the institution's email system administrators to manage the fulfillment of Part 4, Requirements 3.1, 3.2, and 3.3 | 3 |
| Part 4, R4 | No | n/a | Yes | Signature block and message footer for each Government of Canada email account included in the initial email, response, or forward of any email thread involving one or more non-Government of Canada recipients | 3 |
Determining the level of compliance
Determining the level of compliance of a Web page
Determining the level of compliance of a Web page with standard part 1
- Determine the % compliance for each applicable standard part 1 requirement by assessing the page using the Web page compliance criteria for standard part 1.
- Determine the weighting for each applicable standard part 1 requirement using the individual weightings table for standard part 1.
- Calculate the weighted score for each applicable standard part 1 requirement by multiplying the associated % compliance from step 1 by the associated weighting from step 2.
- Calculate the maximum possible weighted score by adding together the weightings from step 2.
- Calculate the total weighted score by adding together the weighted scores from step 3.
- Calculate the level of compliance of a Web page with standard part 1 by dividing the total weighted score from step 5 by the maximum possible weighted score from step 4 then multiplying by 100.
Example calculation
- % Compliance:
- R2 = 100%
- Weightings:
- R2 = 4
- Weighted scores:
- R2 = 100% x 4 = 4
- Maximum possible weighted score = 4
- Total weighted score = 4
- Level of compliance of a Web page with standard part 1 = (4 / 4) x 100 = 100%
Determining the level of compliance of a Web page with standard part 2
- Determine the % compliance for each applicable standard part 2 requirement by assessing the page using the Web page compliance criteria for standard part 2.
- Determine the weighting for each applicable standard part 2 requirement and checkpoint using the individual weightings table for standard part 2.
- Calculate the weighted score for each applicable standard part 2 requirement and checkpoint by multiplying the associated % compliance from step 1 by the associated weighting from step 2.
- Calculate the maximum possible weighted score by adding together the weightings from step 2.
- Calculate the total weighted score by adding together the weighted scores from step 3.
- Calculate the level of compliance of a Web page with standard part 2 by dividing the total weighted score from step 5 by the maximum possible weighted score from step 4 then multiplying by 100.
Example calculation
- % Compliance:
- R1.1 Checkpoint 1.1 = 66.7%
- R1.1 Checkpoint 1.2 = n/a
- ...
- R5 = 50%
- R6 = 100%
- Weightings:
- R1.1 Checkpoint 1.1 = 5
- R1.1 Checkpoint 1.2 = n/a
- ...
- R5 = 4
- R6 = 5
- Weighted scores:
- R1.1 Checkpoint 1.1 = 66.7% x 5 = 3.335
- R1.1 Checkpoint 1.2 = n/a
- ...
- R5 = 50% x 4 = 2
- R6 = 100% x 5 = 5
- Maximum possible weighted score = 5 + n/a + ... + 4 + 5 = 193
- Total weighted score = 3.335 + n/a + ... + 2 + 5 = 163.335
- Level of compliance of a Web page with standard part 2 = (163.335 / 193) x 100 = 84.63%
Determining the level of compliance of a Web page with standard part 3
- Determine the % compliance for each applicable standard part 3 requirement by assessing the page using the Web page compliance criteria for standard part 3.
- Determine the weighting for each applicable standard part 3 requirement using the individual weightings table for standard part 3.
- Calculate the weighted score for each applicable standard part 3 requirement by multiplying the associated % compliance from step 1 by the associated weighting from step 2.
- Calculate the maximum possible weighted score by adding together the weightings from step 2.
- Calculate the total weighted score by adding together the weighted scores from step 3.
- Calculate the level of compliance of a Web page with standard part 3 by dividing the total weighted score from step 5 by the maximum possible weighted score from step 4 then multiplying by 100.
Example calculation
- % Compliance:
- R1 = n/a
- R1.1 = n/a
- ...
- R2.4 = 100%
- R2.5 = 50%
- ...
- R13.1 = 100%
- R13.2 = 50%
- ...
- Appendix D = 100%
- Appendix E = n/a
- Appendix F = n/a
- Weightings:
- R1 = n/a
- R1.1 = n/a
- ...
- R2.4 = 5
- R2.5 = 4
- ...
- R13.1 = 2
- R13.2 = 3
- ...
- Appendix D = 3
- Appendix E = n/a
- Appendix F = n/a
- Weighted scores:
- R1 = n/a
- R1.1 = n/a
- ...
- R2.4 = 100% x 5 = 5
- R2.5 = 50% x 4 = 2
- ...
- R13.1 = 100% x 2 = 2
- R13.2 = 50% x 3 = 1.5
- ...
- Appendix D = 100% x 3 = 3
- Appendix E = n/a
- Appendix F = n/a
- Maximum possible weighted score = n/a + n/a + ... + 5 + 2 + .. + 2 + 1.5 + ... + 3 + n/a + n/a = 171.1
- Total weighted score = 3.335 + n/a + ... + 2 + 5 = 222
- Level of compliance of a Web page with standard part 3 = (171.1 / 222) x 100 = 77.07%
Determining the level of compliance of a Web page with standard part 4
- Determine the % compliance for each applicable standard part 4 requirement by assessing the page using the Web page compliance criteria for standard part 4.
- Determine the weighting for each applicable standard part 4 requirement using the individual weightings table for standard part 4.
- Calculate the weighted score for each applicable standard part 4 requirement by multiplying the associated % compliance from step 1 by the associated weighting from step 2.
- Calculate the maximum possible weighted score by adding together the weightings from step 2.
- Calculate the total weighted score by adding together the weighted scores from step 3.
- Calculate the level of compliance of a Web page with standard part 4 by dividing the total weighted score from step 5 by the maximum possible weighted score from step 4 then multiplying by 100.
Example calculation
- % Compliance:
- R1.1 = 0%
- R1.2 = 100%
- R2 = n/a
- Weightings:
- R1.1 = 3
- R1.2 = 5
- R2 = n/a
- Weighted scores:
- R1.1 = 0% x 3 = 0
- R1.2 = 100% x 5 = 5
- R2 = n/a
- Maximum possible weighted score = 3 + 5 + n/a = 8
- Total weighted score = 0 + 5 + n/a = 5
- Level of compliance of a Web page with standard part 4 = (5 / 8) x 100 = 62.5%
Determining the overall level of compliance of a Web page
- Multiply the level of compliance of a Web page with standard part 1 by the weighting for standard part 1 in the Individual Weightings for each Standard Part section.
- Multiply the level of compliance of a Web page with standard part 2 by the weighting for standard part 2 in the Individual Weightings for each Standard Part section.
- Multiply the level of compliance of a Web page with standard part 3 by the weighting for standard part 3 in the Individual Weightings for each Standard Part section.
- Multiply the level of compliance of a Web page with standard part 4 by the weighting for standard part 4 in the Individual Weightings for each Standard Part section.
- Calculate the overall level of compliance of a Web page by adding up the results from steps 1, 2, 3, and 4.
Example calculation
- 100% x 10% = 10%
- 84.63% x 50% = 42.315%
- 77.07% x 35% = 26.9745%
- 62.5% x 5% = 3.125%
- Overall level of compliance of a Web page = 10% + 42.315% + 26.9745% + 3.125% = 82.4145%
Determining the level of compliance of the domain names for a site or sub site
- Determine the % compliance for each applicable standard part 1 requirement by assessing each site and sub site that the institution is accountable for using the domain names compliance criteria for standard part 1.
- Determine the weighting for each applicable standard part 1 requirement using the individual weightings table for standard part 1.
- Calculate the weighted score for each applicable standard part 1 requirement by multiplying the associated % compliance from step 1 by the associated weighting from step 2.
- Calculate the maximum possible weighted score by adding together the weightings from step 2.
- Calculate the total weighted score by adding together the weighted scores from step 3.
- Calculate the level of compliance of the domain names for a site or sub site by dividing the total weighted score from step 5 by the maximum possible weighted score from step 4 then multiplying by 100.
Example calculation
- % Compliance:
- R1.1.1 = 100%
- R1.1.2 = 0%
- R1.2 = n/a
- Weightings:
- R1.1.1 = 5
- R1.1.2 = 3
- R1.2 = n/a
- Weighted scores:
- R1.1.1 = 100% x 5 = 5
- R1.1.2 = 0% x 3 = 0
- R1.2 = n/a
- Maximum possible weighted score = 5 + 3 + n/a = 8
- Total weighted score = 5 + 0 + n/a = 5
- Level of compliance of the domain names for a site or sub site = (5 / 8) x 100 = 62.5%
Determining the level of compliance of an email system
- Determine the % compliance for each applicable standard part 4 requirement by assessing the email system using the email system compliance criteria for standard part 4.
- Determine the weighting for each applicable standard part 4 requirement using the individual weightings table for standard part 4.
- Calculate the weighted score for each applicable standard part 4 requirement by multiplying the associated % compliance from step 1 by the associated weighting from step 2.
- Calculate the maximum possible weighted score by adding together the weightings from step 2.
- Calculate the total weighted score by adding together the weighted scores from step 3.
- Calculate the level of compliance of an email system by dividing the total weighted score from step 5 by the maximum possible weighted score from step 4 then multiplying by 100.
Example calculation
- % Compliance:
- R1.1 = 0%
- R1.2 = 100%
- ...
- R3.5 = 0%
- R4 = 100%
- Weightings:
- R1.1 = 3
- R1.2 = 5
- ...
- R3.5 = 3
- R4 = 3
- Weighted scores:
- R1.1 = 0% x 3 = 0
- R1.2 = 100% x 5 = 5
- ...
- R3.5 = 0% x 3 = 0
- R4 = 100% x 3 = 3
- Maximum possible weighted score = 3 + 5 + ... + 3 + 3 = 34
- Total weighted score = 0 + 5 + ... + 0 + 3 = 22
- Level of compliance of domain names = (22 / 34) x 100 = 64.71%
Determining the level of compliance of an institution
Determining the level of compliance of an institution with standard part 1
- Add up the level of compliance of a Web page with standard part 1 for all Web pages included in the assessment.
- Divide the result from step 1 by the number of Web pages included in the assessment.
- Add up the level of compliance of the domain names for a site or sub site with standard part 1 for all sites and sub sites included in the assessment.
- Divide the result from step 3 by the number of sites and sub sites included in the assessment.
- Calculate the level of compliance of an institution with part 1 by adding the result from step 2 to the result from step 4 then dividing the result by 2.
Example calculation
- 100% + 100% + ... + 0% + 100% = 70000%
- 70000% / 10000 = 70%
- 62.5% + 100% + ... + 100% + 62.5% = 15600%
- 15600% / 200 = 78%
- Level of compliance of an institution with standard part 1 = (70% + 78%) / 2 = 74%
Determining the level of compliance of an institution with standard part 2
- Add up the level of compliance of a Web page with standard part 2 for all Web pages included in the assessment.
- Calculate the level of compliance of an institution with part 2 by dividing the result from step 1 by the number of Web pages included in the assessment.
Example calculation
- 84.63% + 63.45% + ... + 91.24% + 56.87% = 68234.34%
- Level of compliance of an institution with standard part 2 = 68234.34% / 10000 = 68.23%
Determining the level of compliance of an institution with standard part 3
- Add up the level of compliance of a Web page with standard part 3 for all Web pages included in the assessment.
- Calculate the level of compliance of an institution with part 3 by dividing the result from step 1 by the number of Web pages included in the assessment.
Example calculation
- 77.07% + 73.45% + ... + 81.24% + 86.87% = 79123.45%
- Level of compliance of an institution with standard part 3 = 79123.45% / 10000 = 79.12%
Determining the level of compliance of an institution with standard part 4
- Add up the level of compliance of a Web page with standard part 4 for all Web pages included in the assessment.
- Divide the result from step 1 by the number of Web pages included in the assessment.
- Calculate the weighted level of compliance for each email system administered by the institution by multiplying the level of compliance of an email system by the number of email accounts associated with the email system.
- Add up the weighted levels of compliance for all email systems administered by the institution.
- Divide the result from step 4 by the total number of email accounts administered by the institution.
- Calculate the level of compliance of an institution with part 4 by adding the result from step 2 to the result from step 5 then dividing the result by 2.
Example calculation
- 62.5% + 78.4% + ... + 56.67% + 95.67% = 69345.23%
- 69345.23% / 10000 = 69.34523%
- Weighted levels of compliance:
- Email system 1: 64.71% * 10000 = 647100%
- Email system 2: 73.45% * 500 = 36725%
- 647100% + 36725% = 683825%
- 683825% / (10000 + 500) = 65.12619%
- Level of compliance of an institution with standard part 4 = (69.34523% + 65.12619%) / 2 = 67.24%
Determining the overall level of compliance of an institution
- Multiply the level of compliance of an institution with standard part 1 by the weighting for standard part 1 in the Individual Weightings for each Standard Part section.
- Multiply the level of compliance of an institution with standard part 2 by the weighting for standard part 2 in the Individual Weightings for each Standard Part section.
- Multiply the level of compliance of an institution with standard part 3 by the weighting for standard part 3 in the Individual Weightings for each Standard Part section.
- Multiply the level of compliance of an institution with standard part 4 by the weighting for standard part 4 in the Individual Weightings for each Standard Part section.
- Calculate the overall level of compliance of an institution by adding up the results from steps 1, 2, 3, and 4.
Example calculation
- 74% x 10% = 7.4%
- 68.23% x 50% = 34.115%
- 79.12% x 35% = 27.692%
- 69.21% x 5% = 3.4605%
- Overall level of compliance of an institution = 7.4% + 34.115% + 27.692% + 3.4605% = 72.67%
Glossary
Contrast ratio
Ratio of the luminance of the brightest colour to that of the darkest color in foreground/background colour pairs. Contrast ratios can range from 21:1 (white and black) to 1:1 (white and white).
Reference: Contrast ratio (WCAG 2.0)
Cookie
A data file sent by a Web server to the web browser on a client's computer that the Web server uses to track visitors and remember information about them. Typically, a cookie will only remember information that a client provides. The data stored within a cookie can only be read by the Web server that originally sent it.
CSS validation
CSS validation is the process of verifying whether the CSS used to control the presentation of a document follows the grammar, vocabulary, and syntax for the CSS recommendation used by the document. The tool used for validating CSS is called a validator and a document that passes this process with success is called valid.
Reference: W3C CSS Validation Service
Deprecated
A deprecated element or attribute is one that has been outdated by newer constructs. Use style sheets to achieve stylistic and formatting effects rather than HTML presentational attributes. HTML presentational attributes have been deprecated when style sheet alternatives exist.
Reference: Alternatives for Deprecated Elements and Attributes
DOCTYPE declaration
Element at the beginning of a Web page that declares the Document Type Definition (DTD) that is in use. A DTD is a machine-readable grammar that defines the rules for a markup language.
Reference: Document Type Definition (DTD)
Dynamic content
Dynamic content is content that changes without a page refresh. This change can be initiated by a user action or by triggers unrelated to the user (such as time expiring).
Image map
Image maps allow authors to specify regions of an image or object and assign a specific action to each region (e.g., retrieve a document, run a program, etc.) When the region is activated by the user, the action is executed.
An image map is created by associating an object with a specification of sensitive geometric areas on the object.
There are two types of image maps:
- Client-side: When a user activates a region of a client-side image map with a mouse, the pixel coordinates are interpreted by the user agent. The user agent selects a link that was specified for the activated region and follows it.
- Server-side: When a user activates a region of a server-side image map with a mouse, the pixel coordinates of the click are sent to the server-side agent specified by the href attribute of the A element. The server-side agent interprets the coordinates and performs some action.
Client-side image maps are preferred over server-side image maps for at least two reasons: they are accessible to people browsing with non-graphical user agents and they offer immediate feedback as to whether or not the pointer is over an active region.
Important functionality
Any functionality which is integral to the navigation or operation of a Web page or Web page element (such as links, navigation mechanisms, and revealing hidden information).
Markup validation
Markup validation is the process of verifying whether a document follows the grammar, vocabulary, and syntax for the markup language used to describe the document. The tool used for validating markup is called a validator and a document that passes this process with success is called valid.
Reference: W3C Markup Validation Service
Meaningful Information
Any information which is integral to the understanding, navigation, or operation of a Web page or Web page element is considered to be meaningful information.
Visual content that is pure decoration, is used only for visual formatting, or is not presented to users is not considered to be meaningful information.
Audio content that does not assist with the understanding of information conveyed through multimedia (such as ambient noise and random sounds in the background) is not considered to be meaningful information.
Normal text size setting
The default text size setting for a browser. For most browsers this setting is either "Normal" or "100%" and is equivalent to 100% of the baseline font size.
Supporting file
A file that controls, modifies, or enhances the visual presentation or behaviour of a Web page (such as a CSS, image, or script file). A supporting file is normally referenced in the source code of a Web page or another supporting file.
Top-level domain
A top-level domain (TLD) is the last part of an Internet domain name; that is, the letters following the final dot of any domain name, for example, .ca, .com, .org, .net, .info.
Web-Smart colour palette
The Web-Smart colour palette includes 4,096 colours created using a combination of the following hexadecimal values for red, green, and blue: 00, 11, 22, 33, 44, 55, 66, 77, 88, 99, AA, BB, CC, DD, EE, and FF (for example, #00AA66, #33EE11, and #444444). Colours from the Web-smart colour palette display consistently on most 16-bit and 24-bit colour monitors.
Reference: Web-Smart colour palette (moreCrayons)
Resources
- Client-side CSS:
- Client-side CSS instructions for over-riding visual formatting in the template (http://www.tbs-sct.gc.ca/clf2-nsi2/ahlpaacc-eng.asp#accfsc)
- Contrast ratio:
- Contrast ratio (WCAG 2.0) (http://www.w3.org/TR/WCAG20/#contrast-ratiodef)
- Deprecated elements and attributes:
- Alternatives for Deprecated Elements and Attributes (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/td-dt/adea-sread-eng.asp)
- DOCTYPE declaration:
- DOCTYPE declaration for XHTML 1.0 Strict (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/td-dt/dtd-eng.asp#p2)
- DOCTYPE declaration for XHTML 1.0 Frameset (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/td-dt/dtd-eng.asp#p2)
- Important Notices:
- Copyright / Permission to Reproduce Notice - Sample (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/cprp-acdar-eng.asp)
- Hyperlinking Notice - Sample (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/hn-eh-eng.asp)
- Official Languages Notice - Sample (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/oln-aclo-eng.asp)
- Privacy Notices - Sample (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/gcpn-acgc-eng.asp)
- Reproduction of Government Symbols Notice - Sample (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/cprp-acdar-eng.asp#cn_rgcs)
- ISO 639-2/T:
- Personal Information Collection Statement:
- Personal Information Collection Statement - Sample (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/pics-ecrp-eng.asp)
- Third-party Information Notice:
- Third-party Information Notice - Sample (http://www.tbs-sct.gc.ca/clf2-nsi2/tb-bo/tpild-edrcipt-eng.asp)
- Validation:
- W3C Markup Validation Service (http://validator.w3.org/)
- W3C CSS Validation Service (http://jigsaw.w3.org/css-validator/)
- Web Content Accessibility Guidelines (WCAG
1.0):
- Web Content Accessibility Guidelines 1.0 (http://www.w3.org/TR/WCAG10)
- Web-Smart Colour Palette:
- Web-Smart colour palette (moreCrayons) (http://www.morecrayons.com/palettes/webSmart/)
- World Wide Web Consortium (W3C):
- World Wide Web Consortium Web site (http://www.w3.org/)