W3C home > Mailing lists > Public > w3c-wai-eo@w3.org > January to March 2010

Re: EOWG deadline 22 March: Making Presentations Accessible [Review Draft]

From: Liam McGee <liam.mcgee@communis.co.uk>
Date: Tue, 23 Mar 2010 10:14:32 +0000
Message-ID: <4BA89488.2070000@communis.co.uk>
To: w3c-wai-eo@w3.org
Hi all. Date and time reviewed:  $Date: 2010/03/22 21:03:56 $

First, to add to the title brainstrom: How To Make Presentations Accessible

This How to [verb] format is far more common in search queries than the 
gerund (-ing) form.

> * Is anything missing? Are their areas where we want to provide more
> specific or detailed guidance? (Keep in mind the limited scope and
> desire to keep it short.)

Ensure the facility is accessible.
Suggest: add in check that there is a hearing loop and that it is 
working order.

> * Should anything be cut out to simplify and shorten the document?

I think the length is appropriate to the subject

> * What do you think about the terminology options: Presentations, Talks,
> Meetings, Training, Sessions? (Note what is included in the scope and
> what is out of scope, at
> http://www.w3.org/WAI/EO/changelogs/cl-training#accessible )

I think that meetings are too different to presentations to be covered 
here. Likewise, training covers whole areas that presentations do ont. 
Suggest keeping it focused on chalk-and-talk style (OK, click and talk) 
presentations. 'Talks' might be an appropriate synonym.

> * What about the title? Should we have a short title with only one term,
> and then in the first sentence clarify that it applies to different
> situations, using more of the terms? See title ideas at
> http://www.w3.org/WAI/EO/changelogs/cl-training#title2

Say what it does. If it is to cover training and meetings as weell, it 
should say so in the title.

> * What do you think about each editorial question throughout the draft
> document? They are highlighted green and surrounded by: [@@ question ?]

Provide material ahead of time.
Suggest that we recommend it is provided in html format, to WCAG2 AA

Consider activities.
Yes, it is too vague. Give examples. Typical might be arranging sticky 
notes in groups, voting buttons, splitting off to do group work.

Work with interpreter or CART typist.
I think that detail here is not necessary - the interpreter or CART 
typist will be the person to bring these sorts of issues to the person's 
attention.

Use an easy to read font face.
Sans is not *always* easier to read than serif - too much of a 
generalisation. Suggest mentioning a few commonly available fonts by 
name instead.

Caption or otherwise make available audio...
Well, if CART is not available then a transcript after the event would 
be a good fallback.

Preparing Handouts
Could mention font size, line length, line spacing, colours and 
contrast. Mention different ways of presenting data - graphical, 
tabulated, narrative description.



Sorry this is late!

Regards to you all

Liam
Received on Tuesday, 23 March 2010 10:15:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 10:33:56 GMT