français

Through collaboration with the Government's Web communities, the Web Experience toolkit is being developed for use by all departments to build accessible, usable and interoperable websites.

[To]

1. Raise awareness of the Web Experience toolkit within key stakeholder groups. 2. Educate and engage stakeholders in order to effect smooth and efficient adoption and implementation of the tool. 3. Develop an understanding of the need for shared technical tools by informing stakeholders of the benefits associated with adoption. 4. Build confidence in the WET development and review process to support operational excellence by providing staff with high-quality tools and resources to ensure superior implementation. 5. Maintain accountability and transparency by providing clarity on details and documentation to ensure key stakeholders and user community have a clear and comprehensive understanding of the Web Experience toolkit, and more specifically the changes in version 4.

 TARGET AUDIENCES 

ACTION PLAN 1. Develop messaging for specified target audiences. Messaging will be consistent across audiences and hierarchal levels; however, level of detail may vary. A matrix is presented in Appendix A to illustrate the messaging based on each of the components of the new update. 2. Use established channels and products to communicate relevant news to specific audiences within the GC Web Community by using Twitter, Communications Community Office Newsletter, GCPEDIA, GCForums, the Web Standards Web site, governance committees, presentations and networking events such as #w2p mixer, Meet-ups, CIO Summit. 3. Build capacity within GC Web Community to develop and maintain accessible and usable websites using the Web Experience Toolkit by coordinating CodeFest (Appendix B) 4. Build awareness and encourage collaboration by of our

TECHNIQUES AND TOOLS o Web Standards website – guidelines, clarifying roles & responsibilities, cross-referencing between related policy instruments, surfacing the most relevant content to specific audiences of interest. o Twitter - tweets from WET accounts - use #w2p #goc #goc20 #WxT #clf hashtags o Newsletters & emails to our target audiences (e.g CCO Newsletter to 2000 government communicators). o Participate in events and speaking engagements – UXCamp 2012, GTEC 2012, W3C Meet-up, etc. o Training and information sessions, including CodeFest. o GCPEDIA – feature spotlight, link to content in emails. o GCForums – Discussion groups with COEs, Working Groups, WET contributors.

Appendix A: Audience specific messages about the Web Experience Toolkit

Senior Managers Functional Managers & Communications Strategists Web Programmers & Developers Vendors & External Collaborators Media • WET saves money as it is developed collaboratively across the GC. It can be applied to any GC website (internal or external). • WET assists with the development of Websites. It's a code library that allows departments to work on the business of developing more usable, accessible and interoperable websites. • WET allows you to have usable, accessible and interoperable websites by using ready-made code. WET also includes standard themes and a mobile view.

• If you're interested in participating, find us on GitHub and GCForums • "No longer supporting" means we don't continue developing, it doesn't mean we can't answer questions or that we eliminate those projects (for example, old browsers, previous version of WET) • If you're planning on developing a website or testing a website adopt the Web Experience Toolkit to assist you in building usable, interoperable and accessible websites. • If you're interesting in contributing, testing, reviewing or patching the Web Experience Toolkit. Find us on GitHub. • WET is a community-drive open source software framework, that aims to build usable, interoperable and accessible code for reuse on Government of Canada Websites and external website. • Connection to Open Government

APPENDIX B: GCPEDIA FEATURES We will aim to highlight our work with the community using a GCPEDIA Spotlight feature on the home page approximately once per month. The spotlight must link to an up-to-date GCPEDIA page in both official languages. Possible topics include:

• WET CodeFest (June 20, 2012) – May/June • WET Beta Testing – (re-purpose previous beta testing announcement shown below) • Web Experience Toolkit – Launch version 4 – August/September 20123

APPENDIX C: USING TWITTER TO COMMUNICATE EXTERNALLY Purpose of tweeting: The primary purpose of our tweets is to increase collaboration with external communities. A secondary purpose is to communicate with both internal and external communities. What we tweet: • Only information that is publicly available, such as: o New content added to website o Member of Web Standards Office speaking at a public event • Links to TBS website • Using hashtags - #w2p #goc #goc20 #WxT #clf #cco #gcpedia #a11y #ucd #usability

How we tweet: • In both official languages at the same time. o In English on the English account o In French on the French account

How tweets will be approved: Tweets will be drafted in advance and approved by Manager, Policy Development, Web Standards Office. Once approved, they are translated and scheduled for the upcoming week or month.

APPENDIX D: Bloggers to engage & Newsletters to write for APPENDIX E: Presentations & Speaking Engagements