W3C home > Mailing lists > Public > public-wai-age@w3.org > January to March 2009

RE: WAI-AGE task force

From: <Anna.Zhuang@nokia.com>
Date: Wed, 11 Mar 2009 09:29:41 +0100
To: <andrew@w3.org>, <public-wai-age@w3.org>
Message-ID: <D1E1C1C072023846AC4A55088BAA4B03309A3A9884@NOK-EUMSG-04.mgdnok.nokia.com>

 Dear all,

My 0.2 cents and usual regrets for the call.

"Approach.
Here is one way you can approach an organization with an inaccessible website:"

There are 4 points in the numbered list, so this is not "one way" anymore. IMO 1 and 4 are two ways to approach organisations, whereas 2 describes what to do when pursueing path 1 or even 4. And 3 is an aftermath of 1 and 4. So these items together don't form a list and also need to change the preceeding sentence to: "Here are some ways" or "Here is example procedure" (depending on how the item list is organised)

These are different approaches:
1. Directly contact the organisation
2. Seek help from a national disability or older peoples' organization
3. Be more vocal in the press
These are the technicalities very much applicable to all the approaches:
1. What to report (currently well described)
2. How to report (also well described, perhaps need to change the section title from Contacting organisations to Ways to contact organisations or How to contact organisations. Just Contacting organisations does not reflect the substance too well and also is the same as the document title)
3. Possible further actions 

There is a title mismatch currently. 4 is Further actions but down in the document Follow up becomes a higher level title and Further actions is a subsection under it. I think Further actions should be a higher level title.

*****************

It is hard to comment on AGE deliverables without joining a call. I only consider that AGE needs a resource page of its own that needs to be placed under WAI Introducing accessibility. Currently introducing accessibility only introduces techniques for making accessible web but does not introduce and explain disabilities nor explains age related challenges.  

Br, Anna


>-----Original Message-----
>From: public-wai-age-request@w3.org 
>[mailto:public-wai-age-request@w3.org] On Behalf Of ext Andrew Arch
>Sent: Tuesday, March 10, 2009 5:52 PM
>To: public-wai-age@w3.org
>Subject: WAI-AGE task force
>
>Dear Task Force,
>
>Apologies for overlooking this reminder, but as per schedule, 
>we are meeting this Wednesday (11 March) at the usual time in 
>Europe, but 1 hour later for the USA who have started daylight 
>saving ahead of Europe:
>   http://www.w3.org/WAI/EO/wai-age/teleconf.html#meetings
>Teleconference Bridge:
>   +33.4.89.06.34.99 / +44.117.370.6152 / +1.617.761.6200 
>Teleconference code: 9243# (WAGE#)
>IRC: Channel - #waiage; server - irc.w3.org; port - 6665
>Scribe: Nacho (Suzette)
>   http://www.w3.org/WAI/EO/wai-age/teleconf.html#scribes
>
>*Agenda:*
>1. Welcome
>
>2. Responding to Organizations with Inaccessible Websites
>- change-log: http://www.w3.org/WAI/EO/changelogs/cl-responding.html
>- latest draft: http://www.w3.org/WAI/EO/Drafts/responding/
>Just a couple of open items to discuss tomorrow, then we can 
>get EOWG to give it another review and move to publishing.
>
>3. Future work plan
>Discussion of WAI-AGE deliverables
>- http://www.w3.org/WAI/WAI-AGE/deliverables.html
>
>Regards, Andrew
>--
>Andrew Arch
>Web Accessibility and Ageing Specialist
>www.w3.org/WAI/WAI-AGE/
>
>
Received on Wednesday, 11 March 2009 08:30:37 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:51:56 UTC