W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > April to June 2013

Re: EOWG: What to call these things?

From: Victoria Menezes Miller <menezesmiller@gmail.com>
Date: Fri, 19 Apr 2013 12:05:36 +0200
Message-ID: <CAAKOS2ooS6JE+xkA3mp+VzTk3UJi45oLRUiAxba3FGjfkxtiKw@mail.gmail.com>
To: Sylvie Duchateau <sylvie.duchateau@snv.jussieu.fr>
Cc: "Schantz, Paul A" <paul.schantz@csun.edu>, "EOWG (E-mail)" <w3c-wai-eo@w3.org>
Hi, Everyone,

My suggestions. "Accessibility guides for WCAG 2.0" or simply
"Accessibility tutorials for WCAG 2.0".

When searching, think of the terms, the language you would use to search.
I've done some testing through search in Google in order to shed some
light/food for thought on search results following some of the suggestions
received:

"*Accessibility tutorials*"
provides in the first 3 results:

   1. *Accessibility Tutorials* for Microsoft
Products<http://www.microsoft.com/enable/training/>
   *
   Accessibility tutorials* introduce you to new and commonly used
   accessibility features and options in Windows, Office and other Microsoft
   products.
   2.
    Web *Accessibility* Presentations and *Tutorials* -
W3C<http://www.w3.org/WAI/train.html>
   Web *Accessibility* Presentations and *Tutorials*. Most of the material
   linked from this page is primarily for trainers; however, the presentations
   and Before-After ...
   3.
    WebAIM: Articles <http://webaim.org/articles/>


"*Accessibility how to*" suggests the following filters:

iphone accessibility how to scroll
iphone accessibility how to turn off
web accessibility how to
ipad accessibility how to scroll

If I select "*web accesssibility how to*", the following top 3 results
appear:

   1. *Web accessibility* - Wikipedia, the free
encyclopedia<http://en.wikipedia.org/wiki/Web_accessibility>
   *
   Web accessibility refers to the inclusive practice of making websites
   usable by people of all abilities and disabilities. When sites are
   correctly designed, ...
   You've visited this page 2 times. Last visit: 2/11/09*
   2. * *
    * *WebAIM: *Web Accessibility* In Mind <http://webaim.org/>**
   Information, training, resources, guidelines and standards for *Web
   accessibility* and disability access to the Web.
   3.
    WebAIM: Introduction to *Web Accessibility* <http://webaim.org/intro/>

If I search for "*accessibility how to guides*", the following top 3
results appear:*
*

   1. *Accessibility Guides*| Transport for
London<http://www.tfl.gov.uk/tfl/gettingaround/accessibility-guides/default..aspx>
   *
   Accessibility guides. We produce a range of guides in alternative
   formats to help you plan and make journeys. All of the guides can be
   obtained free of charge by ...
   *
   2. * *
    * *Transport *accessibility* | Transport for
London<http://www.tfl.gov.uk/gettingaround/transportaccessibility/1167.aspx>
   Getting Around London *guide*. Our Getting around London *guide* (PDF
   5.47MB) describes all the *accessibility* features on the Tube, bus, DLR
   and tram.
   3.
    *Accessibility Guide* for Educators -
Microsoft<http://www.microsoft.com/enable/education/>
   *
   Accessibility* resources for educators including “*Accessible*Technology: A
   *Guide* for Educators,” information on computer technology in special
   education

Best,

Vicki


On Fri, Apr 19, 2013 at 10:07 AM, Sylvie Duchateau <
sylvie.duchateau@snv.jussieu.fr> wrote:

> Hello all,
> I don't why I don't like how tos. But practical guides suggested by Denis
> or "Accessibility quick start Guides" proposed by Paul sound better to me..
> Best
> Sylvie
>
> Le 19/04/2013 01:38, Schantz, Paul A a écrit :
>
>> The primary scenario examples identify professionals who need practical
>> information immediately.
>>
>> How about a variation like "Accessibility Quick Start Guides"
>>
>> This suggests practical bite-sized chunks of information that can be put
>> to use right away.
>>
>>
>> ------------------------------**---------------------------
>> Paul Schantz
>> Director, Web and Technology Services
>> Division of Student Affairs
>> California State University, Northridge
>> phone: 818.677.3839
>> e-mail: pschantz@csun.edu <mailto:pschantz@csun.edu>
>> twitter: @paulschantz
>> www.linkedin.com/in/**paulschantz<http://www.linkedin.com/in/paulschantz><
>> http://www.linkedin.com/in/**paulschantz<http://www.linkedin.com/in/paulschantz>
>> >
>>
>>
>> www.csun.edu/sait
>> System notifications: @CSUN_SAIT
>>
>> Input | Intellection | Responsibility | Connectedness | Individualization
>>
>>
>>
>>
>>
>> On Apr 17, 2013, at 2:02 PM, Shawn Henry wrote:
>>
>>  Old working names: Application Notes, Tutorials
>>> Drafts: http://www.w3.org/WAI/EO/**Drafts/app-notes/<http://www.w3.org/WAI/EO/Drafts/app-notes/>(Tables, Forms,
>>> Images have content; the others do not)
>>> Analysis: http://www.w3.org/WAI/EO/**changelogs/cl-app-notes<http://www..w3.org/WAI/EO/changelogs/cl-app-notes>- see
>>> brainstorms under "Naming the notes"
>>>
>>> So what are they: Application Notes? naw. Tutorials? naw.
>>>
>>> Other ideas???
>>>
>>> Please think about this and:
>>> * reply to this e-mail with more ideas
>>> * prepare to discuss it at this week's EOWG telecon
>>>
>>> Thanks!
>>>
>>> ~Shawn
>>>
>>>
>>>
>>>
>>
> --
> Sylvie Duchateau
> Association BrailleNet
> Tél.: +33 (0) 1 44 27 26 25 / Fax : +33 (0) 1 44 27 34 38
> www.braillenet.org / www.accessiweb.org
>
>
Received on Friday, 19 April 2013 10:15:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:56:01 UTC