View source for Planning/Mapping of Strategic Document Content

== Overview ==

The [[Planning/Background#Approach]] calls for the [http://www.w3.org/WAI/impl/Overview Strategic Planning] to be subsumed into the Planning Roadmap. This document maps the topics and key actions from the Strategic Planning document to the sections and activities within the Roadmap. The aim is to reuse as much content as possible from the Strategic Planning document.

Where a close mapping does not exist, I have put in notes on whether to include another activity to cover this content.

== [http://www.w3.org/WAI/impl/Overview#goal Determine Your Goal and Gather Support] ==

Generally covered by:

* [http://w3c.github.io/wai-dynamic-planning/initiate/ Initiate section]

Key actions:

* Identify and document the project accessibility goals → [http://w3c.github.io/wai-dynamic-planning/initiate/identify_goals.html Identify accessibility goals]
* Explore your organization's current approach, understanding, and view of accessibility → [http://w3c.github.io/wai-dynamic-planning/initiate/review_situation.html Reviewing the current situation], Plan ► Review design and marketing resources, Plan ► Review technical libraries and tools, Nothing on understanding and view within organization
* Identify the key reasons for accessibility and, if needed, develop a business case → [http://w3c.github.io/wai-dynamic-planning/initiate/business_case.html Prepare an accessibility business case]
* Promote awareness within your organization, and seek interested peers → [http://w3c.github.io/wai-dynamic-planning/initiate/communicate.html Communicate accessibility aims and value to wider organization], [http://w3c.github.io/wai-dynamic-planning/initiate/obtain_support.html Obtain support for accessibility activities]
* Secure commitment and backing, ideally from the executive and project management level → [http://w3c.github.io/wai-dynamic-planning/initiate/obtain_support.html Obtain support for accessibility activities]

== [http://www.w3.org/WAI/impl/Overview#resp Establish Roles and Responsibilities] ==

Generally covered by:

?

Key actions:

* Identify roles and assign responsibilities across different areas of the project → Plan ► Identifying important roles (could be in Initiate), Implement ► Assigning people to roles
* Assign responsibility to other organizational areas that impact on the provision of accessible websites → Nothing. <div class="quiet">Note: discusses procurement and other areas, may be a need to create an activity on accessibility champions, or incorporate into Initiate ► Obtain support for accessibility activities.</div>
* Communicate within the project and organization who the responsible parties are → Nothing. <div class="quiet">Note: Concerns espablishing lines of communication and ensuring everyone know about them. May be related to Obtain support for accessibility activities and/or something in Implement.</div>
* Ensure any third-party providers are aware of your accessibility requirements and your expectations → Implement ► Accessible procurement
* Assign responsibility for each jurisdictional region your website spans → Nothing. <div class="quiet">May be something regarding sites with international audience, although this may be considerably bigger than this resource?</div>

== [http://www.w3.org/WAI/impl/Overview#policy Develop and Implement Organizational Policy] ==

Generally covered by:

Plan ► Develop accessibility policy

Key actions:

* Identify any existing policies related to accessibility → [http://w3c.github.io/wai-dynamic-planning/initiate/review_situation.html Reviewing the current situation]
* Establish a policy stating your organization's commitment to web accessibility → Plan ► Develop accessibility policy
* Communicate and promote the policy across relevant parts of the organization → [http://w3c.github.io/wai-dynamic-planning/initiate/communicate.html Communicate accessibility aims and value to wider organization]
* Review related policies and procedures to incorporate the accessibility policy throughout → Plan ► Integrate accessibility into wider policies
* Announce your organizational commitments publicly for accountability → Nothing. <div class="quiet">Covers the publishing of policy and creation of public statement of intent regarding accessibility. May be a need for this somewhere in Initiate as communicating with users is important.</div>

== [http://www.w3.org/WAI/impl/Overview#resource Review Available Tools and Resources] ==

Generally covered by:

Key actions:

* Identify web authoring tools and review how well they support your accessibility goals → Plan ► Review technical libraries and tools
* Review organizational design and development resources → Plan ► Review design and marketing resources
* Research lessons learned from the development of other websites within the organization → Nothing. <div class="quiet">Relates to exploring previous work, may be that nothing is available. Should this be discussed in Monitor, as a part of sharing knowledge? Something that would be needed in initiate. Possible activity: 'Seek out existing knowledge'</div>
* Identify external sources of accessible information and examples → Nothing. <div class="quiet">May not be suitable as says little more than 'search the web', there is no guidance provided for how to rate the resources or which ones are good.</div>

== [http://www.w3.org/WAI/impl/Overview#train Assess Skills and Deliver Training] ==

Generally covered by:

Implement ► Training for accessibility

Key actions:

* Assess expertise and motivation of key project personnel → Nothing. <div class="quiet">Possibly incorporate into Implement ► Training for accessibility.</div>
* Budget and plan general awareness raising and targeted skills building training for team members → Nothing. <div class="quiet">Possibly incorporate into Implement ► Training for accessibility.</div>
* Consider the potential need to recruit personnel with specific accessibility expertise → Implement ► Recruit to improve accessibility
* Include accessibility requirements as standard criteria in the recruitment process → Implement ► Recruit to improve accessibility, Plan ► Integrate accessibility into wider policies

== [http://www.w3.org/WAI/impl/Overview#project Integrate into Project Life Cycle] ==

Generally covered by:

[http://w3c.github.io/wai-dynamic-planning/implement/ Implement]

Key actions:

* Start early and factor for iterative checks → Nothing. <div class="quiet">More of a general point that might be best included as part of the introduction to this section.</div>
* Evaluate all project design assets → Plan ► Review design and marketing resources, Plan ► Review technical libraries and tools
* Review accessibility solutions with key team members → Nothing. <div class="quiet">Include as part of Implement ► Prioritizing identified issues, although that might hide the important point of cross team reviews.</div>
* Evaluate throughout the project and ensure a comprehensive evaluation on completed website → Implement ► Evaluation regime and process
* Plan for a reasonable gap between completion and go-live to address any final barriers → Nothing. <div class="quiet">More of a general point, might be beneficial to have an activity covering sample approaches.</div>

== [http://www.w3.org/WAI/impl/Overview#share Share Knowledge and Outcomes] ==

Generally covered by:

Implement ► Share experience and knowledge

Key actions:

* Report to stakeholders the project accessibility successes and difficulties → Plan ► Feedback loops for stakeholders, Monitor ► Report to stakeholders and management
* Report design and technical achievements and knowledge to other website teams → Nothing. <div class="quiet">Might be useful to include something in Monitor about knowledge sharing.</div>
* Create internal publicity for new website accessibility → Nothing. <div class="quiet">Internal marketing activity, possibly tied to Monitor ► Report to stakeholders and management.</div>
* Consider creating an organization wide accessibility monitoring and reporting framework → Nothing. <div class="quiet">New activity 'Develop accissiblity monitoring and reporting framework'.</div>

== [http://www.w3.org/WAI/impl/Overview#monitor Ensure Ongoing Monitoring and Maintenance] ==

Generally covered by:

[http://w3c.github.io/wai-dynamic-planning/monitor/ Monitor]

Key actions:

* Create a plan for regular checks and audits → Monitor ► Regular reviews of policies, procedures, and resources
* Update publication process to include accessibility checks → Plan ► Integrate accessibility into wider policies
* Implement a public feedback process for accessibility issues → Monitor ► Manage user feedback and provide support
* Schedule regular reviews and updates of policies and processes → Monitor ► Regular website reviews