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

Re: Strategic Plan intro

From: Shawn Henry <shawn@w3.org>
Date: Thu, 16 Oct 2014 12:57:44 -0500
Message-ID: <54400718.8040301@w3.org>
To: Kevin White <kevin@w3.org>, "EOWG (E-mail)" <w3c-wai-eo@w3.org>
Thanks. Additional replies below.

On 10/15/2014 4:56 AM, Kevin White wrote:
> Hi Shawn,
>
> I certainly like the succinctness of this. There are a couple of
> points that I included in the existing introduction that I think are
> quite important and could be included in your suggestion:
>
>  Suggesting that accessibility is an intrinsic and ongoing activity
> and comparing to something like security. The aim is to promote the
> idea that accessibility is not a bolt on or a separate activity but
> should be seen as an integral part.

Perhaps starting out "A successful plan for web accessibility addresses many areas of your organization and projects: training, quality assurance, recruiting, purchasing, marketing, content development, visual design, and more." conveys that?

(fyi, "intrinsic activity" doesn't work for me :-)

>  Permission to explore the topics in any order and to revisit areas
> as things develop.

Right. However, I wonder if by changing the title from "Implementation Plan" to "... Guidance for Developing a Plan for Your..." and saying "This document provides ... guidance on what to consider in developing ...", that is no longer necessary?

>
> As a minor point, is this content suitable for CIOs? I could have
> thought it would be something dealt with by a subordinate to that
> office?

And Shadi notes that we try to avoid titles, so CIO isn't good anyway. I do think we need something higher-level than "project managers, team leaders, small business owners, and accessibility consultants". Maybe "IT managers" or "web managers"? What functional role(s) will often do this level of strategic planing?

>
> Thanks
>
> Kevin

Best,
~Shawn

>
> On 15 Oct 2014, at 02:16, Shawn Henry <shawn@w3.org> wrote:
>
>> Hi Kevin & EOWG folks,
>>
>> Below is an idea for the introduction to:
>> http://w3c.github.io/wai-planning-and-implementation/Overview.html
>>
>> <h1>Strategic Planning for Web Accessibility Guidance for
>> Developing a Plan for Your Organization or Project</h1>
>>
>> A successful plan for web accessibility addresses many areas of
>> your organization and projects: training, quality assurance,
>> recruiting, purchasing, marketing, content development, visual
>> design, and more.
>>
>> This document provides CIOs, project managers, small business
>> owners, accessibility consultants, and others with guidance on what
>> to consider in developing an effective web accessibility plan for
>> your specific organization or project.
>>
>> [+] expand all key actions below  [-] collapse all key actions
>> below
>>
>> </end suggestion>
>>
>> Some rationale: * The first sentence gives them an idea of the
>> range of areas to entice them into reading the document -- e.g.,
>> "hum, I hadn't thought about [xyz area], I'd better read on to see
>> what I need to think about there." * The subtitle now says
>> "Guidance for" and this intro idea has "guidance on what to
>> consider" which I think is enough to cover the point we wanted to
>> get across. * The [+] expand buttons in this document are all on
>> "Key actions" points, and the first one is just a short paragraph
>> below the buttons (and thus visible in many configuration).
>> Therefore, I think we can change the button text to: "expand all
>> key actions below", "collapse all key actions below" and then not
>> need any extra explanation.
>>
>> What other important or useful info do you think is needed in the
>> intro of this doc?
>>
>> Best, ~Shawn
>>
>>
>>
>>
>>
>>
>
>
>
Received on Thursday, 16 October 2014 17:57:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:29:50 UTC