W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > October to December 2001

Fwd: Implementation Plan revised

From: Judy Brewer <jbrewer@w3.org>
Date: Fri, 07 Dec 2001 00:41:12 -0500
Message-Id: <5.1.0.14.2.20011207003516.020e24e0@localhost>
To: EOWG <w3c-wai-eo@w3.org>
EOWG:

I'm forwarding, with Sarah's permission, a revision that she did to 
"Implementation Plan for Web Accessibility"

It should appear as an attachment to this message, and also be archived in 
the mailing list
         http://lists.w3.org/Archives/Public/w3c-wai-eo/

Her description about the changes follows, for those who want the details. 
But it may be easier to just look at the attachment, where the revisions 
are all integrated.

I think that this revision version reads much better!

Let's discuss this at our meeting today.

- Judy


>Date: 04 Dec 2001 22:34:40 EST
>From: Sarah.Horton@Dartmouth.EDU (Sarah Horton)
>Subject: Implementation Plan revised
>To: jbrewer@w3.org
>
>Hi Judy.
>
>I've enclosed an HTML version of the Implementation Plan document with my 
>revisions (implementation-SH.html). I also list the edits I made below, 
>with the original sentence first and my edit following, preceded by an 
>asterisk. I wasn't certain what your established procedures are re> 
>revisions so I tried to be really thorough in keeping track of any changes 
>I made.
>
>The main thing I did was to remove the categories, or to incorporate them 
>into the item where appropriate. Many times I found that the qualifier was 
>simply not necessary, but there were instances where one was needed and 
>for those I pulled it into the sentence. The other thing I did was to 
>standardize the language so that the level 1 bullets are more cryptic 
>(e.g., no articles) and the level 2 bullets are full sentences. That 
>seemed to be the convention so I just tried to apply it consistently 
>throughout the document.
>
>I think this is a highly useful document and I enjoyed getting to know it 
>better!
>
>Best regards,
>Sarah
>
>------------
>To return to the outline version of this page, select "collapse all", or 
>in the navigation bar above.
>*To return to the outline version of this page, select "collapse all" here 
>or in the navigation bar above.
>
>Identify a high-level champion for Web accessibility
>*Identify high-level champion for Web accessibility
>
>corporations: accessibility champions are most effective if at least at 
>the level of senior vice president
>*accessibility champions are most effective if at the level of upper 
>administration
>
>Assign a lead coordinator
>*Assign lead coordinator
>
>small organizations: it may be sufficient to designate a "point person" 
>for Web accessibility
>*for small organizations, it may be sufficient to designate a "point 
>person" for Web accessibility
>
>corporations: departments might include marketing, Web development, 
>technical support, usability, etc.
>*departments might include marketing, Web development, technical support, 
>usability, etc.
>
>education: in decentralized systems, include representatives from each 
>school jurisdiction
>*in decentralized organizations, include representatives from each 
>jurisdiction
>
>Web design businesses: may want to designate someone to track new 
>techniques for accessibility
>*designate a team member to track new techniques for accessibility
>
>Establish a coordination team with communication plan
>*Establish coordination team with communication plan
>
>decentralized organizations: coordination may need to be flexible when Web 
>development is decentralized
>*coordination may need to be flexible when Web development is decentralized
>
>Conduct an initial assessment of organization's Web site, using 
>Preliminary Review method
>*Conduct initial assessment of organization's Web site, using Preliminary 
>Review method
>
>quick review of the Web site can provide information about potential 
>extent of problems
>*a quick review of the Web site can provide information about the 
>potential extent of the problems
>
>Assess current awareness of need for Web accessibility by survey or 
>interviews within the organization
>*Assess current awareness of need for Web accessibility by survey or 
>interviews within organization
>
>large organizations: survey individuals in departments with different 
>roles relating to the Web site
>*in large organizations, survey individuals in departments with different 
>roles relating to the Web site
>
>decentralized organizations: organizations with decentralized software 
>procurement practices will need to review more products
>*organizations with decentralized software procurement practices will need 
>to review more products
>
>Find out whether the organization is subject to external requirements 
>regarding Web accessibility
>*Find out whether organization is subject to external requirements 
>regarding Web accessibility
>
>government and commercial sites: check requirements early in the process
>*check requirements early in the process, particularly for government and 
>commercial sites
>
>Find out whether the organization has an existing policy on Web site 
>design and technologies
>*Find out whether organization has existing policy on Web site design and 
>technologies
>
>large organizations: note whether some department is already developing a 
>general policy for Web site management, and if so what the timeline is
>*in large organizations, note whether some department is already 
>developing a general policy for Web site management, and if so what their 
>timeline is
>
>Establish an organizational policy on Web accessibility, organizational 
>policy on Web accessibility
>*Establish organizational policy on Web accessibility
>
>important to address issues such as conformance level, scope of site, use 
>of proprietary formats, milestones, etc.
>*address issues such as conformance level, scope of site, use of 
>proprietary formats, milestones, etc.
>
>government and commercial sites: organizational policy should at least 
>reflect minimum accessibility requirement by government
>*organizational policy should reflect at least the minimum accessibility 
>requirements mandated by the government, particularly for government and 
>commercial sites
>
>large organizations: a concise high-level statement of commitment, plus a 
>comprehensive implementation-oriented statement, may both be useful
>*a concise high-level statement of commitment, plus a comprehensive 
>implementation-oriented statement, may both be useful, particularly in 
>large organizations
>
>for large organizations may need executive briefings
>*large organizations may need to provide executive briefings
>
>Select authoring software that conforms to as many of the Authoring Tool 
>Accessibility Guidelines 1.0 (ATAG 1.0) as possible
>*Select authoring software most conformant to Authoring Tool Accessibility 
>Guidelines 1.0 (ATAG 1.0)
>
>decentralized organizations: organizations with decentralized software 
>procurement practices may need guidance on selection process rather than 
>centralized purchase of software
>*organizations with decentralized software procurement practices may need 
>guidance on the selection process rather than centralized purchase of software
>
>If current authoring software does not support production of accessible 
>sites, ask vendors when it will
>*if current authoring software does not support production of accessible 
>sites, ask vendors when it will
>[I moved this down a level under Select authoring software]
>
>Develop and distribute accessible templates usable with the new authoring 
>software
>*Develop and distribute accessible templates usable with new authoring 
>software
>
>decentralized organizations: templates for a variety of authoring tools 
>may be particularly helpful in achieving a consistent level of accessibility
>*templates for a variety of authoring tools may be particularly helpful in 
>achieving a consistent level of accessibility, particularly for 
>decentralized organizations
>
>decentralized organizations: a centralized evaluation resource page may be 
>useful
>*a centralized evaluation resource page may be useful, particularly for 
>decentralized organizations
>
>Plan a range of training options to meet needs of people with different 
>roles in the organization
>*Plan range of training options to meet needs of people with different 
>roles in organization
>
>large organizations: conduct training sessions for Web masters and Web 
>content developers in different departments
>*conduct training sessions for Web masters and Web content developers in 
>different departments
>
>large organizations: publicize training and reference resources to Web masters
>*publicize training and reference resources to Web masters
>
>large organizations: develop an internal Web site with accessibility 
>information and resources
>*develop an internal Web site with accessibility information and resources
>
>large organizations: provide online resources to address technical questions
>*provide online resources to address technical questions
>
>small organizations: look for outside training resources if needed
>*if in-house training is not feasible, look for outside training resources
>
>Web design businesses: training should include business case talking 
>points for clients as well as technical training
>*for Web design businesses, training should include business case talking 
>points for clients as well as technical training
>
>Specify evaluation process to be used, and ensure quality of Web site 
>evaluation process
>*Specify Web site evaluation process to be used, and ensure quality of process
>
>if using accessibility logos, monitoring should include some verification 
>of logo use
>*if using accessibility logos, monitoring should include verification of 
>logo use
>
>decentralized organizations: may need some kind of centralized 
>accountability or enforcement
>*decentralized organizations may need some kind of centralized 
>accountability or enforcement
>
>escalate to champion and/or reinforcing organizational policy as needed as 
>needed
>*escalate to champion and/or reinforcing organizational policy as needed

-- 
Judy Brewer    jbrewer@w3.org    +1.617.258.9741    http://www.w3.org/WAI
Director, Web Accessibility Initiative (WAI), World Wide Web Consortium (W3C)
MIT/LCS Room NE43-355, 200 Technology Square, Cambridge, MA,  02139,  USA

Received on Friday, 7 December 2001 00:48:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:55:49 UTC