W3C home > Mailing lists > Public > public-eo-plan@w3.org > January to March 2018

Re: Selecting Authoring Tools - needs

From: Sharron Rush <srush@knowbility.org>
Date: Thu, 15 Mar 2018 10:38:39 -0500
Message-ID: <CA++nJxqWfSyWtncErzRgdEqbC++_ndn4NDkAP3A2z9iQBwEV1A@mail.gmail.com>
To: Shawn Henry <shawn@w3.org>
Cc: Nic Steenhout <nic@knowbility.org>, EO Planning <public-eo-plan@w3.org>
Yes let's bring to the group for consideration. I strongly agree with Nic
that the community of tool developers is an important target group and also
appreciate that resources are most effective when they are tightly focused.

On Mar 15, 2018 10:33 AM, "Shawn Henry" <shawn@w3.org> wrote:

> Agree to use the repo -- can use the wiki in the repo.
>
> I think we are talking about 2 different things:
> 1. people purchasing and using authoring tools
> 2. people developing authoring tools
>
> I think this resource was primarily for #1.
>
> We might want different material for #2. fyi, We did a promotion campaign
> for this audience a while back <https://www.w3.org/WAI/EO/wik
> i/Outreach_for_ATAG_2.0> I think it would be good to do another.
>
> I think we don't want the same resource for both audiences -- although I
> don't feel strongly at this point, and would be happy for the group to
> consider it.
>
> Happy to discuss! That's what the Requirements Analysis is for -- to "get
> on the same page".
>
> (Also, another thought I had "in the shower", was that maybe we don't need
> the sections "Limitations of Existing Authoring Tools" and "Examples of
> strategies to work around limitations of existing authoring tools" anymore?
> I did not read it to decide if I have a suggestion for or against. I just
> wanted to mention it so that you don't feel you *have* to keep that info...)
>
> Looking forward to working on it with you and the group in a few days!
>
> Cheers,
> ~Shawn
>
>
> On 3/15/2018 10:16 AM, Nicolas Steenhout wrote:
>
>> Hi Shawn,
>>
>> Thanks for the feedback.
>>
>> As it turns out, Eric did create a repo for the resouce (from the plane
>> over the Atlantic, no less!!!). I'm happy enough to use the Wiki, but I'm
>> thinking long term, it might be better if all the information was in one
>> place, being able to see the discussion via issues, etc, rather than having
>> multiple places to check for information about the document and the work
>> being done.
>>
>> I'll do more work on the plan, based on your feedback.
>>
>> Just to address your comment quickly about CMS, LMS, CRM developers not
>> being a target audience. I think they are. They are a subset of "web
>> developers". Having been on the core team of a major FOSS CMS (Joomla!),
>> and having interacted with many other teams working on other CMS, I can
>> tell you that they have a lot of things to consider when it comes to
>> accessible authoring tools. And with the reach they have, they are probably
>> one of the most important target group to reach - For example, recent
>> numbers show that WordPress is used on nearly 1/4 of all sites on the web.
>>
>> And I'm happy about relaxing the timeline :)
>>
>> Cheers
>>
>> Nic
>>
>> On Wed, Mar 14, 2018 at 9:41 PM, Shawn Henry <shawn@w3.org <mailto:
>> shawn@w3.org>> wrote:
>>
>>     Great start, Nic!
>>
>>     Attached please find my comments in-line as tracked changes.
>>
>>     To facilitate group work and not require a repo yet, I suggest
>> putting the info here for now:
>>     * https://www.w3.org/WAI/EO/wiki/Selecting_Authoring_Tools_
>> Requirements_Analysis <https://www.w3.org/WAI/EO/wik
>> i/Selecting_Authoring_Tools_Requirements_Analysis>
>> (purpose/goals/objectives, audience)
>>     * https://www.w3.org/WAI/EO/wiki/Selecting_Authoring_Tools_
>> Project_Info <https://www.w3.org/WAI/EO/wiki/Selecting_Authoring_Tools_
>> Project_Info> (schedule, project team)
>>
>>     Best,
>>     ~Shawn
>>
>>     On 3/14/2018 4:46 PM, Nicolas Steenhout wrote:
>>
>>         Hello everyone,
>>
>>         Please find attached the proposed plan for this resource.
>>
>>         In theory, I think most of the work can be achieved relatively
>> quickly. Perhaps even have a first draft for people to stick their noses in
>> at F2F.
>>
>>         I'm proposing an informal survey of several developers I know
>> that implement authoring tools in their system, to get a feel for what
>> they'd find useful on that page. This might take a bit more time, so maybe
>> do a first draft and adjust based on that feedback.
>>
>>         Cheers
>>
>>         Nic
>>
>>         On Wed, Mar 14, 2018 at 10:23 AM, Shawn Henry <shawn@w3.org
>> <mailto:shawn@w3.org> <mailto:shawn@w3.org <mailto:shawn@w3.org>>> wrote:
>>
>>              I moved this on the F2F page, and sending it in e-mail so
>> you have it easily:
>>
>>              * '''Selecting Authoring Tools''' &mdash; [
>> https://www.w3.org/WAI/impl/software <https://www.w3.org/WAI/impl/s
>> oftware> <https://www.w3.org/WAI/impl/software <
>> https://www.w3.org/WAI/impl/software>> Selecting and Using Authoring
>> Tools for Web Accessibility] needs significant updating and revision. Maybe
>> would be good to have conceptual discussion at F2F *if* we have an editor
>> ready to take it on and they can have a draft Requirements Analysis before
>> the F2F. Here is old [https://www.w3.org/WAI/EO/Dra
>> fts/eval/selectingtools-changelog <https://www.w3.org/WAI/EO/Dra
>> fts/eval/selectingtools-changelog> <https://www.w3.org/WAI/EO/Dra
>> fts/eval/selectingtools-changelog <https://www.w3.org/WAI/EO/Dra
>> fts/eval/selectingtools-changelog>> Changelog] with very limited
>> Requirements Analysis. Here's [https://www.w3.org/WAI/EO/wik
>> i/Resource_Development_Life_Cycle/Stage_1._Requirements#
>> Requirements_Document
>>         <https://www.w3.org/WAI/EO/wiki/Resource_Development_Life_
>> Cycle/Stage_1._Requirements#Requirements_Document> <
>> https://www.w3.org/WAI/EO/wiki/Resource_Development_Life_
>> Cycle/Stage_1._Requirements#Requirements_Document <
>> https://www.w3.org/WAI/EO/wiki/Resource_Development_Life_
>> Cycle/Stage_1._Requirements#Requirements_Document>> Example Requirements
>> Analysis] (Shawn from charter)
>>
>>
>>
>>
>
Received on Thursday, 15 March 2018 15:39:03 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 15 March 2018 15:39:04 UTC