Implementation of new CLF 2.0 Standards - Qs and As

CLF 2.0 Standards - Qs and As - Table of Contents

1.0 General

1.1 Why change the Common Look and Feel (CLF) standards now?

The CLF standards were developed by the Treasury Board Secretariat following extensive consultations in 1999/2000. Given the evolution of technology and Web design that has occurred over the past six years since the initial standards came into force, we have revised the standards.

1.2 What existing CLF standards are affected by CLF 2.0?

As part of policy renewal at TBS, many elements as well as the structure of the original CLF standards have changed. Consult the CLF Crosswalk Table for a detailed list of changes.

1.3 Does CLF 2.0 cover such technologies as blogs, wikis, and podcasts?

The CLF standards address the presentation and function of all Web-based content. They are not specific to the technology or the tool that is being used to deliver and/or present the Web content.

1.4 Will the proposed CLF for Intranets/Extranets (CLFIE) be changing as well?

CLF 2.0 addresses public facing Web sites. CLFIE will be addressed at a later date. Institutions are, however, encouraged to apply these standards to their Web sites that are not public facing.

1.5 Are the CLF 2.0 templates compatible with the Government of Canada Content Management System (CMS)? 

Since the Government of Canada Content Management System (CMS) supports XHTML 1.0 Strict and CSS, the CLF 2.0 template can be integrated into the Government of Canada CMS as a custom template.

1.6 How does CLF 2.0 affect collaborative arrangements?

New collaborative arrangements must be negotiated with CLF 2.0 in mind. Existing collaborative arrangements must ensure that future updates of the site and/or revisions to any agreements negotiate the inclusion of CLF 2.0. 

1.7 How should a multi-departmental initiative apply the CLF 2.0 requirement to display the institutional name and URL on the Welcome Page and in the banner?

Multi-departmental initiatives may choose what text to display.  See requirement 4 in Part 3, Common Web Page Formats for more information.

1.8 Does CLF 2.0 have an impact on content?  

The changes in CLF 2.0 are focussed on standards related to presentation and format. Institutions will need to determine the impact these changes have on their existing content. For example, the addition of a third column on main pages presents opportunities to feature new content such as recently published reports, newsworthy announcements, key initiatives, etc. As always with CLF, appropriate content remains the responsibility of the institution.

1.9 Does CLF 2.0 apply to COTS and pre-existing Web applications?

The CLF standards address the presentation and function of all Web-based content. They are not specific to the technology or the tool that is being used to deliver and/or present the Web content. Thus, institutions should apply CLF 2.0 to their Web content, irrespective of the delivery channel.

1.10 How does CLF 2.0 affect COTS assessment tools and validation products such?

These tools will need to be updated by vendors to meet the new CLF 2.0 standards. The CLF Office neither recommends nor prohibits the use of COTS assessment and validation tools and services.

1.11 How frequently will the CLF standards be updated?

Changes to CLF must be made to respond to technical developments and government priorities. The separation of content and presentation, especially through the use of common templates and Cascading Style Sheets will minimize future impacts.

1.12 Will CLF 3.0 be released before the end of the two-year CLF 2.0 implementation timeframe?

The CLF Office will take into consideration the two-year timeframe for CLF 2.0 as the standards evolve.

1.13 What is the process for change management, as a two-year window for implementation could result in significant changes to technology?

The CLF Office has not yet established a change management plan.

1.14 Will the new CLF 2.0 standards apply to Publiservice?

At the moment, CLF 2.0 applies only to Government of Canada public-facing Web sites (in other words those sites that are accessible to the public). Publiservice is not public facing and therefore falls under the definition of an intranet for the purposes of applying CLF (in other words a site that is available only to Government of Canada employees). While there is no plan to address CLF for Web sites that are not public facing at this point in time, institutions are encouraged to implement a single approach for all sites, including a site like Publiservice, where feasible and reasonable.

1.15 What is the definition of a Web site?

The following are the definitions of Web site and sub site for the purpose of defining what must comply upon launch with the CLF 2.0 standards once those standards have been approved:

Web site:

A group of Web pages that collectively represent an institution or initiative

Sub site:

A collection of Web pages with either a local structure or a distinct information space within a larger and more general site, where the collection of Web pages are intended for a particular audience and whose specific purpose is to feature a prominent program or service.

1.16 What is the definition of a collaborative Web site?

A collaborative Web site is one in which the parties involved have shared or compatible objectives, contribute resources (financial or in-kind), share in the benefits, and agree to a fair allocation of risk-taking. Such sites may be between Government of Canada institutions or may involve other levels of government, private sector, etc. and the exact nature of the arrangement will determine how CLF is applied.

1.17 Have the new CLF 2.0 standards been tested for accessibility?

The CLF 2.0 template and CSS files have been tested on a wide range of technologies, both adaptive and otherwise, and with different user configurations to ensure that the new standards are as accessible and usable as possible.

1.18 Have the new CLF 2.0 standards been tested for usability?

Because usability is linked to both content and information architecture, usability testing is best undertaken at the site level by institutions.

1.19 Is a notification page required to inform users of the implications of exiting a secure section of a site or a Web application, where navigating away from that section will cause the client to lose any inputted information or permissions required to use other links other than those in the common menu (e.g. left navigation links)?

The institution should evaluate how best to serve the needs of their visitors and may choose to point to a notification page or even not offer links outside of the secure section or application. Refer to requirement 5.5 in Part 3, Common Web Page Formats regarding the behaviour of links on secure sites and Web application pages.

1.20 - If information is not lost when navigating away from a secure section of a site or a Web application (i.e. the information is stored in a session), is a notification page required?

The notification page is required only where navigating away from a secure section of a site or a Web application will cause the client to lose any inputted information or permissions to use other links.

2.0 Implementation, Monitoring, Compliance and Exemptions

2.1 What is the deadline for implementation of the new CLF 2.0 standards?

Institutions have until December 31, 2008 to implement the new CLF 2.0 standards across all Web sites, including sub sites (e.g. region, business unit, branch, etc.) and program-specific sites.

2.2 Is there a toolbox available to help implement the CLF 2.0 standards?

A toolbox containing CLF 2.0 templates and CSS, along with supporting documentation, is available on the Common Look and Feel site. Institutions are strongly encouraged to make use of the CLF 2.0 template and CSS package to help facilitate compliance with the new CLF 2.0 standards. The IAC Technical Working Group has decided to restrict its efforts to solutions based on the central templates and XHTML 1.0 Strict.

2.3 Are the CLF 2.0 standards being implemented on a "day forward" basis (starting on the date they come into force)? Will departments be expected to retrofit all existing Web sites and applications?

The standards apply to all future and existing content pages and applications on the Web sites of institutions listed in Schedules I, I.1 and II of the Financial Administration Act as of January 1st, 2007. Full compliance is required by December 31, 2008.

2.4 Given the longer life cycle of applications, will Internet applications be given longer than 2 years to comply with CLF 2.0?

Full compliance for applications is required by December 31, 2008 unless specific exemptions have been sought and approved.

2.5 Do existing COTS products, that will be upgraded but not replaced, still have to meet CLF 2.0 standards within the two-year timeframe? 

Full compliance for applications is required by December 31, 2008 unless specific exemptions have been sought and approved.

2.6 Are there monitoring and reporting tools available or will tools need to be developed by institutions?

A checklist is available in the CLF toolbox and institutions are welcome to use the CLF reporting tool as often as they choose, provided the mandatory reporting requirements are met. Automated monitoring tools will not be provided. The CLF Office neither recommends nor prohibits institutions from developing tools or using COTS assessment and validation tools or services.

2.7 Is there a central TBS CLF exemption mechanism for institutions to use on a case-by-case basis when sites or applications cannot be made compliant?

Information on the exemption mechanism can be found in the CLF toolbox.

2.8 Is there a CLF 2.0 template available to help with the implementation of these new standards?

XHTML templates and Cascading Style Sheets (CSS) have been developed by the Internet Advisory Committee Technical Working Group to assist institutions with the implementation of these standards. The templates and CSS are available in the CLF toolbox. Institutions are strongly encouraged to make use of the CLF 2.0 templates and CSS package to help ensure compliance with the new standards and to be well positioned to adapt to any new requirements as might evolve. The IAC Technical Working Group has decided to restrict its efforts to solutions based on the central templates and XHTML 1.0 Strict.

2.9 How do I use the CLF 2.0 template?

Instructions for customizing the templates accompany the template package and are available in the CLF toolbox. The IAC Technical Working Group will be restricting efforts to finding and testing solutions based on the central templates and XHTML 1.0 Strict.

2.10 Must we use the CLF 2.0 template developed by TBS?

Treasury Board Secretariat strongly recommends that institutions adopt the templates and CSS files that are available as part of the CLF toolbox. Doing so will significantly aid institutions in achieving compliance, will allow them to apply a technical solution that has been rigorously tested, and will position them to more efficiently and effectively implement future versions of CLF. In addition, the IAC Technical Working Group will be restricting its efforts to finding and testing solutions based on the central templates and XHTML 1.0 Strict.

2.11 Must we use XHTML 1.0 Strict as our document type definition?

Yes. XHTML 1.0 Strict has been adopted because pages that conform to that document type definition:

• are more compatible with adaptive technologies than standard HTML pages;
• are easier to render on wireless devices, Braille readers and other specialized Web environments than standard HTML pages;
• are easier for search engines to index than standard HTML pages, resulting in better search engine results;
• are easier for browsers to display than standard HTML pages, resulting in better browser/platform support (to support legacy browsers, follow the HTML compatibility guidelines);
• are XML conforming, meaning they are readily viewed, edited and validated with standard XML tools; and
• can be created dynamically by converting XML documents using XSLT.

2.12 We are due to launch a new Web site this winter. Must I apply the new CLF 2.0 Standards prior to launch?

CLF 2.0 standards were promulgated as of January 1, 2007. Any and all Web sites launched after the date of promulgation must apply the new CLF 2.0 Standards. Institutions have until December 31, 2008 to ensure that all of their Web sites, including all sub sites, meet CLF 2.0 Standards. A phased approach for implementing the new standards to avoid unnecessary costs is recommended.

2.13 If currently awarded RFPs for Web sites or applications extend beyond the two-year implementation deadline, will departments be expected to modify the existing RFP?

Full compliance for applications is required by December 31, 2008 unless specific exemptions have been sought and approved.

2.14 Will institutions have access to additional funding to implement these new standards?

No special funding will be made available to institutions to implement these standards. Institutions are expected to make provisions in their annual budgets for the ongoing management of their Web sites. Implementation of these standards should be part of the regular Web content publishing lifecycle and integrated into plans to keep the Web site evergreen.

2.15 What is the process for reporting on the new CLF 2.0 standards and their implementation?

Institutions are expected to report on their implementation plans in June 2007 and on their progress in December 2007 and January 2009. Additional feedback may be sought periodically.

2.16 Will we be expected to report on our compliance with CLF 2.0 following the deadline for implementation as we did with CLF 1.0 in 2003?

Institutions are expected to report on their implementation plans in June 2007 and on their progress in December 2007 and January 2009. Additional feedback may be sought periodically.

2.17 Will compliance be monitored? If so, is this a centralized function with TBS?

Institutions are expected to report on their implementation plans in June 2007 and on their progress in December 2007 and January 2009. Additional feedback may be sought periodically.

2.18 What are the consequences of non-compliance?

CLF 2.0 is a standard of the Government of Canada, which describes how to develop and implement Web sites that respect Government of Canada legislation and related policies (e.g. Official Languages Act, Privacy Act, Access to Information Act, Canadian Charter of Human Rights and Freedoms, etc.). Failure to comply with CLF 2.0 may mean an institution is failing to meet its obligations under these acts. Further details on non-compliance measures are listed with the Standards themselves.

2.19 Does CLF 2.0 apply to extranets?

CLF 2.0 applies to all Government of Canada public-facing Web sites of institutions that are listed in Schedules I, I.1 and II of the Financial Administration Act.

For the purpose of CLF; TBS interprets public-facing Web sites as those sites that are accessible to the public; in other words any Government of Canada Web site that provides communications and/or services to clients (including individuals and entities) external to the Government of Canada, regardless of whether the access is provided through a secure or non-secure mechanism. CLF 2.0 applies to all extranets that fall within this interpretation.

3.0 Design and Presentation

3.1 Can I use a graphic for the institutional banner?

Graphics can be used in the banner. Please consult requirement 4 in Part 3, Common Web Page Formats for guidance regarding the use of graphics.

3.2 What about the current reporting period for CLF 1.1?

The CLF 1.1 reporting exercise scheduled for 2006 for will not be required. Institutions are expected to report on their implementation plans for CLF 2.0 in June 2007 and on their progress in December 2007 and January 2009. Additional feedback may be sought periodically.

3.3 Is the Federal Identity Program (FIP) still in force?

The requirements detailed in FIP with respect to Government of Canada visual identity and its application remains in force. Institutions will still use their institutional signatures according to FIP requirements.

3.4 Must we feature a message from the Minister on the home page?

The changes in CLF 2.0 are focussed on standards related to presentation and format. Content remains the responsibility of the institution. Institutions can feature the content of their choice in the content area, although it should relate to the institution's objectives/priorities.

3.5 Must we have a three-column layout on main pages?

The three-column layout is part of the new standard and aligns Government of Canada Web sites more closely to current practices in Web publishing. The institution's primary menu page and all sub site main pages must apply the three-column layout and associated standards.  Secondary pages can, however, have two columns with a wider content area.

3.6 Is there specific content that I must feature in the left and right menus of the main page?

Institutions must use the left column for navigational elements and must feature a link on their main pages to their Proactive Disclosure section as the final navigational link in the left menu. The right column can contain any content the institution chooses to feature. Sample content could include "What's New" or highlight items, additional navigation to specific content areas, links to other portals or Government of Canada initiatives, a message from the Minister, etc.

3.7 Do the Cascading Style Sheets (CSS) in the CLF 2.0 template use fixed or relative units of measure?

Relative units of measure are used, however, the overall width of the page is fixed.

3.8 Must my Web pages be centred on the screen?

Centring Web pages is part of the new standard. Institutions can also apply an optional coloured background in the open space surrounding the Web pages to complement their institutional colour scheme.

3.9 Must we use the stylized maple leaf graphic in the page header?

All institutions subject to CLF must use this common graphic element.

3.10 Can we maintain our institutional colour scheme?

An institution can maintain its own colour scheme provided the institution ensures a high level of contrast between the background and foreground, when viewed by someone having colour deficits or when viewed on a black and white screen.

3.11 Can Welcome Pages be created for sub sites within an institution's Web site?

There is no requirement to change existing institutional practices with respect to Welcome Pages for sub sites.

3.12 Is the strip of colour in the footer of the Web page required?

The strip of colour is mandatory. Institutions should choose a colour that complements the design scheme of their site.

3.13 Can I put text and images in the right menu? 

Institutions can decide what should appear in the right column in order to best meet their needs, provided all standards are met.

3.14 Can I use the title of a region, program, or branch rather than the title of the institution in the banner?

For institutional sites, the first line of text in the banner must display the institution's applied title for all pages published under an institution's domain. Refer to the list of Schedule I, I.1 and II institutions for guidance on what organizations are entitled to list their title in a banner on institutional sites.

3.15 What would be the name of the institution and the URL displayed on the header of departmental sub sites? If the displayed name and URL are the same as the primary site, how would users know that they are on a sub site and not on the primary site?

For institutional sites, the first line of text in the banner must display the institution's applied title for all pages published under an institution's domain. Refer to the list of Schedule I, I.1 and II institutions for guidance on what organizations are entitled to list their title in a banner on institutional sites.

3.16 Can I add additional text, links or a search box to the banner?

Only the two lines of text plus background colours and images as specified in requirement 4 in Part 3, Common Web Page Formats may appear in the banner. Links, search boxes and other elements must not be used.

3.17 What is the size of the text in the first and second lines of the banner?

The exact text sizes are not specified because of the differing lengths of titles and Web addresses that need to be included.

3.18 The visible portion of the image must be no more than 760 pixels wide by 80 pixels high. The wording "no more" implies that the image could be smaller - does that mean that the image height could be smaller?

The height of the visible portion of an image in the banner area may be less than 80 pixels high but the banner area itself must be 760 pixels wide by 80 pixels high.

3.19 Can I add a secondary banner before or below the black buttons?

No additional banners or buttons are permitted.

3.20 Can graphics be used in the left navigation?

Only text elements are to be used in the left menu navigation links area. Using text elements increases the accessibility and scalability of a Web site's navigational elements. CSS decorative elements are considered to be graphics and are likewise prohibited. Non-text elements must only be placed below the final navigation link.

3.21 What is the depth of the indentation for secondary menu items?

There is no size requirement in the Common Look and Feel standards for the indentation of the secondary menu items. The Government of Canada Common Look and Feel template solution uses an 18-pixel width indentation for secondary menu items.

3.22 Are bullets permissible beside the text elements in the left menu?

Bullets are permitted beside text elements in the left menu as long as they are not image-based.

3.23 Can we use CSS background images in the left menu?

Only text elements are to be used in the left menu navigation links area. Using text elements increases the accessibility and scalability of a Web site's navigational elements. CSS decorative elements are considered to be graphics and are likewise prohibited. Non-text elements must only be placed below the final navigation link.

3.24 Are rounded corners allowed in the right and left menus?

Institutions are free to design right menus as they choose, providing that they respect requirements relating to font style and accessibility.

Rounded corners are only permitted to be used in left menus if they are implemented without using images (including images loaded through CSS).

3.25 Are "tabs" allowed at the top of the centre and right hand columns?

Institutions are free to design the content and right menus as they choose, providing that they respect requirements relating to font type and accessibility.

3.26 Can we use a different background colours, font colours, or colour treatments in the left menu?

Institutions, through the use of style sheets, can specify the background and font colours used in the left menu to complement their design provided the colour combination achieves high contrast, when viewed by someone having colour deficits or when viewed on a black and white screen.

Only text elements are to be used in the left menu navigation links area. Using text elements increases the accessibility and scalability of a Web site's navigational elements. CSS decorative elements are considered to be graphics and are likewise prohibited.

3.27 Can the colour of hyperlinks be complementary to the design or is there a mandatory colour scheme?

Institutions, through the use of style sheets, can specify the colour of hyperlinks to complement their colour scheme and to ensure contrast and readability on-screen.

3.28 Is it mandatory that all text in the left menu be black?

Institutions, through the use of style sheets, can specify the colour of text in the left menu to complement their colour scheme and to ensure contrast and readability on-screen.

3.29 What has been done to address those users whose browsers do not support the fonts specified in CLF 2.0?

To achieve consistency across Government of Canada Web sites, CLF specifies the primary font to be used in three specific areas: Times New Roman for the institution name in the banner, Arial for the URL in the banner, and Verdana for all remaining text elements. Institutions should however specify backup fonts that are universally supported, such as sans-serif, for situations where client devices cannot render these specified fonts.

3.30 What must be the target of the "Proactive Disclosure" link?

The Proactive Disclosure link must link clients to a page where all mandatory institutional proactive disclosure reports can be accessed. For collaborative or cooperative sites, such as portals, gateways and clusters, the "Proactive Disclosure" link must point to the government-wide reporting site.

3.31 Must we provide a link to "Proactive Disclosure" on portal sites?

The "Proactive Disclose" link is mandatory on all main pages.  For collaborative or cooperative sites, such as portals, gateways and clusters, the "Proactive Disclosure" link must point to the government-wide reporting site where all institutional proactive disclosure reports can be accessed.

3.32 Why must the institutional URL be displayed in the banner?

The URL must be displayed in the banner following the institutional name because the complexity of the URL as displayed in the browser address bar is often such that it would not be meaningful to a client. In other cases, institutions use a variety of servers, (e.g. search.institution.gc.ca and transaction.institution.gc.ca) or purely machine-generated code that displays in the browser address bar that would similarly not reinforce the institution's primary Web site address in the mind of the client. 

The use of the URL for the Canada site (i.e. canada.gc.ca) will help clients better understand what the link offers and reinforces what they will have seen in other media.

3.33 Can I use a URL specific to a region, program, branch, or sub site in the banner rather than the institutional URL?

The URL that must appear in the banner for all pages published under an institution's domain is that of the institution as per its applied title. There must be no additional information to the right of the .gc.ca in the URL. Please consult requirement 4 in Part 3, Common Web Page Formats for further details.

3.34 Is the "Top" arrow graphic the same colour for all Government of Canada sites, or can it be complimentary to the design of the site?

The "Top" arrow graphic can be integrated into the institution's overall colour scheme. The arrow graphic, however, must have an appearance that is in keeping with the sample provided with the CLF templates.

3.35 Where will common CLF 2.0 images such as the stylized maple leaf and the top of page arrow be provided?

Copies of common images used in the CLF 2.0 template are available in the toolbox.

3.36 Is the border around the content area in the 3-column layout mandatory?

All dimensional elements of the content area, including the border, are mandatory elements.

3.37 Is date modified in the footer mandatory? If so, is there a common definition of what this means that we can share with users?

All Government of Canada Web pages must have a date indicator to inform visitors of the currency of the content. "Date Modified" is the most recent date on which the content of the document was substantially changed or that it was last reviewed for accuracy. Including a currency indicator is recognized as an industry best practice that users have come to expect, and use of the ISO standard (YYYY-MM-DD) will enhance conformity among Government of Canada sites.

3.38 Why should I provide printer-friendly versions of my Web pages?

Clients who print out Web pages do not require Web site navigation in the printed pages. Excluding these elements will improve the printed result on most printers and will allow clients to conserve both printer paper and ink.

The Government of Canada Common Look and Feel template solution uses a Cascading Style Sheet (CSS) to automatically generate a printer-friendly version when a client prints out a Web page using the template.

3.39 Will pages developed using the CLF 2.0 template print properly?

The CLF 2.0 template and CSS package that is available on the CLF Web site incorporates printer-friendly CSS functionality to ensure that pages will print properly. If the CLF 2.0 template and CSS package is not used, then institutions should either incorporate printer-friendly CSS functionality or develop printer-friendly versions of their Web pages. The IAC Technical Working Group will be restricting efforts to finding and testing solutions based on the central templates and XHTML 1.0 Strict.

3.40 Will TBS provide CLF 2.0 templates and CSS files? Do I have to use them or can I create my own?  

A CLF 2.0 template and CSS package is available on the CLF Web site in the Toolbox section: Institutions are strongly encouraged to make use of the available CLF 2.0 template and CSS when developing new or updating existing Web sites. This will help ensure compliance with all mandatory CLF standards and increase accessibility. The IAC Technical Working Group will be restricting efforts to finding and testing solutions based on the central templates and XHTML 1.0 Strict.

3.41 What does the CLF 2.0 toolbox include?

The CLF Office, the Internet Advisory Committee's Technical Working Group (TWG) and Access Working Group (AWG) will jointly develop solutions and documents for the CLF toolbox. The updated CLF toolbox includes a template/CSS package with supporting documentation, as well as documentation that will help to improve the accessibility, usability and CLF compliance of institutional Web sites position the institution to easily adapt to any new requirements as might evolve.  The IAC Technical Working Group will be restricting efforts to finding and testing solutions based on the central templates and XHTML 1.0 Strict.

3.42 What do we do if we have no content for one of the mandatory common menu bar links?  

The common menu bar is a mandatory element under CLF 2.0. There may be some instances when an institution is unable to provide functionality, such as the unavailability of a search engine, or is not required to offer content in both official languages. Please consult Part 3, requirement 5, Common Web Page Formats for further details.

3.43 Why is TBS recommending that side menus and the common menu bar be coded with <h1> tags? Is it not normal practice for the <h1> tag to be reserved for the heading within a page (i.e. the content of the page)?

The <h1> tag is reserved for the main heading of a document structure and there should only be one <h1> tag per document structure. In CLF 2.0, the common menu bar, the side menu(s) and the content area are distinct and independent document structures. The common menu bar contains links that are common throughout the site, the side menu(s) contain content that are common to more than one page, while the content area contains content that is page specific.

Although the main heading of the page is contained within the content area and must be marked up using an <h1> tag, that heading is not relevant to the common menu bar and the side menu(s) because those are distinct and independent document structures and are not related to the content area <h1> tag. As a result, it is necessary to have separate <h1> tags for the content area, the common menu bar and the side menu(s) to distinguish the document structures.

The use of headings for each of the document structures will help to improve screen reader navigation by allowing a client to quickly navigate the document structures and the major sections using only the headings. Without the heading structure for the common menu bar and the side menu(s), it would be more difficult and time consuming to navigate to areas within those document structures.

3.44 What do we do in the event of browser dependent messaging, certificate warnings, Secure Socket Layer (SSL) network errors and other operating system generated messages that cannot be customized?

The Common Look and Feel standards do not apply to all system-generated messages, only the system-generated messages delivered via Web pages by systems such as Web servers and Web application servers. Where system generated messages delivered via Web pages are difficult to customize, best efforts must be made to deliver messages that are compliant with the Common Look and Feel standards.

3.45 Why was the standard on email included in CLF 2.0?

Communication via email is a key part of Internet usage. The standards reference Internet communications as a whole and not only Web sites.

3.46 Will we have to report on compliance with Part 4, Standard on Email?

Institutions will be expected to report on compliance with the requirements of all Common Look and Feel standards, including those relating to email.

3.47 Can we stack signature blocks so that all English and French content is separate and intact?

Signature blocks are to use mixed languages in order to provide equal treatment to English and French as required by the Official Languages Act and the Federal Identity Program policy.

3.48 Is a separate teletypewriter (TTY) number required for each employee?

Decisions relating to whether an employee needs a separate teletypewriter number are left to institutions and will be made on the requirements and nature of each employee's duties. Most employees will use the institutional TTY number in their signature block.

3.49 Can we put a link to the printable version of the Web page on the right side of the breadcrumb area? Is the breadcrumb area reserved only for the breadcrumb?

A link to the printer-friendly version must not be placed in the area reserved for the breadcrumb. The breadcrumb area is reserved only for the breadcrumb. It is recommended that a Cascading Style Sheet (CSS) be used to automatically generate the printer-friendly version that would be displayed when the client selects "printer friendly version" or simply prints the page.

The Government of Canada Common Look and Feel template solution uses CSS to automatically generate a printer-friendly version.

4.0 Accessibility

4.1 Do the new standards still require accessibility?

Yes, Part 2, Standard on Accessibility, Interoperability and Usability requires institutions to make Web sites accessible for the widest possible audience. Among the requirements in part 2 are the requirement for Web sites to conform to the WCAG 1.0 Priority 1 and Priority 2 checkpoints, to ensure high contrast between the foreground and background, and to have text-based common menu bars and left columns.

4.2 How will the changes to WCAG 2.0 impact CLF 2.0?

The IAC/Access Working Group (AWG) is monitoring the development of WCAG 2.0. Upon their approval, TBS will review the AWG's WCAG 2.0 recommendations and analyze any opportunities to improve the accessibility of Government of Canada Web sites through CLF.

4.3 What impact does adopting XHMTL 1.0 Strict have on older browsers?

Adopting XHTML 1.0 Strict will have no impact on older browsers if the HTML Compatibility Guidelines are followed. When the HTML Compatibility Guidelines are followed, older browsers will interpret XHTML 1.0 Strict as regular HTML.

4.4 How do we make visual identifiers in signature blocks accessible?

At present, visual identifiers can only be made accessible in HTML-based emails through the use of alt text. Where an institution's email system does not support alt text, visual identifiers ("Canada" wordmark and the institutional signature) must be replaced with text-equivalent identifiers.

5.0 Navigation

5.1 Is the top menu fixed in terms of where the links lead a user or can they be contextual? For example, can "Home" be linked to the main page of a sub-section or must it be to linked to the top-level main page of the institution?

We are striving to achieve a higher level of consistency between Government of Canada Web sites with CLF 2.0. Thus the Home, Search and Contact Us links in the common menu bar must direct users to the appropriate top-level institutional pages. This is necessary to enhance usability by providing Canadians with a consistent navigational experience on all government sites.

5.2 What must be the order of the domain names in the banner?

If institutions employ a name or acronym that represents the institution's primary purpose in both official languages, the banners on both English and French pages contain the same URL.

If institutions choose to pair acronyms or names according to requirement 2 in Part 1, Standard on Web Addresses option (b), the order of the two official languages is dictated by the language of the page on which the banner is displayed.

If an institution has registered two pairings of unilingual domain names, each domain name will be displayed according to the language of the page.

5.3 Must I remove the current institutional menu bar?

The institutional menu bar must not appear beneath the common menu bar. Institutions should integrate into the left column any menu items that were previously included in the institutional menu bar.

5.4 Must we feature a link to proactive disclosure on our main page?

A link to "Proactive Disclosure" must be appear at the bottom of the left menu of all main and sub site menu pages.. For collaborative or cooperative sites, such as portals, gateways and clusters, the "Proactive disclosure" link must point to the government-wide reporting site. Please consult requirement 10 in Part 3, Common Web Page Formats for additional information on Proactive Disclosure.

5.5 Are breadcrumbs mandatory?

A breadcrumb navigation trail must be implemented before the end of the 2-year implementation period. Due to the particular technical challenges that a breadcrumb trail may pose, institutions will be permitted to post new and redesigned sites that respect all elements of the standards other than this element in the interim as they develop a solution. By 2008, breadcrumb trails must be available on all Government of Canada Web pages.

5.6 Do I have to use the word "breadcrumbs" on my page? 

The use of the word "breadcrumbs" is intended for demonstration purposes only. Words such as "Home" or "Main" are typically used as the first link in a breadcrumb trail. Another link that is typically used in a breadcrumb trail is the name of the sub site or sub-section, depending on the content structure of the Web site.

5.7 How do I implement breadcrumbs on my site without a database or content management system?

There are many ways to implement a breadcrumb trail on a Web site. Institutions must select a solution that is feasible and meets the two-year implementation deadline for breadcrumb trails.

5.8 If I have to move all of the items from the institutional menu bar to the left menu and consolidate my sites, my left menu will become too long and unusable. How can I fix this?

Institutions can decide what navigation scheme will suit their needs, including whether or not to offer sub site navigation or contextual menus.

5.9 Can the left menu change as you drill down, or does it have to be the same throughout the site?

Institutions can decide what navigation scheme will suit their needs, including whether or not to offer sub site navigation or contextual menus.

6.0 Web addresses

6.1 What does "commonly used Internet top-level domains" mean?

As of January 1, 2007, for the purposes of the Common Look and Feel standards commonly used Internet top-level domains include:

• .ca
• .com
• .info
• .net
• .org

If other top-level domains come into common use, institutions should conduct a risk assessment to determine whether to register in them.

6.2 What are the security implications of the addressing standards?

There are no known security implications with the addressing standards.

6.3 Does the page-addressing requirement include program parameters?

Where feasible, program parameters displayed in URL paths must conform to the page-addressing requirement.