EOWG 22 Sep 2006

Components of Web Accessibility: A Mini-Tutorial

<justin> ACTION: changelog - style make alt example with styling [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action01]

AC: Noticed that there are two levels, one a higher level concpet, and a concrete example, on each slide.

<Harvey> Concern for possible need for longdesc

AC: Need to be presented as different, in a consistent way.

SH: Want to talk about overall concept, whether there's too much, too little.

DS: Seems well balanced.

WL: Easy to understand.

HS: Good as an introduction.

SH: For example, imagine you're dealing with policy makers, and you want to get them to adopt ATAG and UAAG, not just WCAG.

LM: We deal with marketing and non-technical people. Would be good for them.
... Explains that web accessibility is for all, not just for disabled.

WL: Have we discussed use of word 'components'?

SH: Yes.

<Harvey> Presumably, eventually images will gain alt-text. Will they also need longdes [which paraphrase the content... and which would be highly repetitive; could they be just identifying the addition of the new one?

WD: Could put a note at top to say that it came from other document Essential Components.

SH: There's alink at end of document.

<Harvey> Use of the A key: Seems to need Ctrl-A.

WD: Might not have seen the link but it's probably OK.

AA: Link disappears.

SH: Change links to be underlined, and hover colour.

<justin> ACTION: changelog - make links underlined, change the hover color, focus [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action02]

LM: There's a keyboard shortcut conflict in Opera

<justin> ACTION: changelog - check conflicts with keyboards such as A toggles one web page in javascript and in opera jumps to next link and s jumps to headings [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action03]

WL: In permission to use, should be an object in sentence. To use what..

<justin> ACTION: changelog - in about page match permission to use from the first slide [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action04]

SH: Comments on "See also"
... What about the use of A key to see all content on one page?

LM: Shouldn't be in 'see also'

SH: Put something on footer bar for see all.

HB: Using Ctrl+A turns it on but it turns off again as soon as I do anything.

[Nobody against removing 'See also']

<justin> ACTION: changelog - take off the words "see also: " [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action05]

SH: Please comment on content at top.

WL: Just delete first sentence.

HS: Put it second.

<justin> ACTION: changelog - change this tutorial introduces to this tutorial tells you how [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action06]

SH: What goes in frst slide?

AA: Different components.

SH: didn't want to introduce those terms so early on.
... How about 'Why you might want to read this'

WD: Maybe say 'Technologies and people' as well as components.

<justin> ACTION: changelog - make the intro answer why am I here and what am I going to get...perhaps use the words technologies and people...see the minutes for further ideas [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action07]

<LiamMcGee> Web accessibility depends on more than the Web content developer. This tutorial introcudes how the different components -- people and technologies -- each have a vital role in Web Accessibility.

AC: Mybe use 'roles'

LM: Web accessibility depends on more than the Web content developer. This tutorial introcudes how the different components -- people and technologies -- each have a vital role in Web Accessibility.

JT: Might not know waht an authoring tool is.

WL: How about a popup baloon to explain.
... User agent is overloaded term.

HB: Put links to where they're discussed further on.

JT: Maybe give a quick example

SH: Say that terms will be explained later on.

JT: Put a summary at the beginning.

<justin> ACTION: changelog - add a second slide that gives an overview of the slides - like first we are going to give intro to the components and later more indepth into each component [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action08]

SH: 'Alt Text is' slide

LM: Say 'information' rather than 'meaning'

SH: Remove [functional], leave sub-bullet

<justin> ACTION: changelog - in the alt text is slide, leave word functional, leave sub bullet, and change meaning to information [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action09]

<Andrew> scribe: Andrew

Shawn: Comment on the "alt text is" bullet?

Andrew: how about "alt text will be" for second bullet

<justin> ACTION: changelog - in alt text is, consider changing second bullet to alt text will be [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action10]

Andrew: See - http://www.w3.org/TR/mobile-bp/

<Wayne> Wayne must leave early today. Goodbye

<justin> ACTION: changelog - alt text is slide - ideas last bullet add ", which is common in mobile browsing" or add a fourth bullet [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action11]

Andrew: four short bullets is easier to read the three longer ones

Shawn: look at slide 5 & 11 - use of "developers" vs "content developers"

All: just use "developers"

<justin> ACTION: changelog - just developers not content developers [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action12]

<justin> ACTION: changelog - authoring tools - just multimedia tools [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action13]

<justin> ACTION: changelog - authoring tools - delete desktop publishing software, considering adding presentation software [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action14]

Andrew: can we add "presentation tools"?
... slide 17 - title has mismatch with content

<justin> ACTION: changelog - web accessibility defined perhaps responsibility for web accessibility, and supposed with a D [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action15]

Shawn: please send ideas for slide 17 title and content to list
... and final comments?

Andrew: consider not centreing the text on those slides that do this

Shawn: will probably not put out as a draft - but invite feedback afterwards
... what are we calling this document? Slides? or ??

Options suggested included: mini-tutorial & walkthrough

Shawn: Options suggested included: mini-tutorial & walkthrough

William: what about "primer"

Liam: what about "10 Minute tutorial"

All: like "10 Minute tutorial"

<Harvey> Brief Tutorial

<justin> ACTION: think about name - tutorial, brief tutorial, primer, 10 minute tutorial [recorded in http://www.w3.org/2006/09/22-eo-minutes.html#action16]

Shawn: please think about collection titles - Primer / mini tutorial / 10 minute tutorial / brief tutorial

Image alt in W3C WAI process intro doc

<shawn> http://www.w3.org/WAI/intro/w3c-process

<shawn> http://lists.w3.org/Archives/Public/w3c-wai-eo/2006JulSep/0130.html

Shawn: Lets look at the images

Andrew: found the images add visual noise, especially as there were numbers as well

Henny: add some colour to break up the text

William: add value, are delightful

Doyle: no comment

Justin: like the page being broken up by some images

Liam: improves the ease of understanding - some are better than others

Harvey: add nothing, happy to get rid of them

William: think they do actually convey information

Shawn: acknowledging diffrent opinions. Including images better meets the goals of the doc, tone wanted

Subtopic: Alt text (and CSS option)

Discussion about alt text for the images. Some points:

[DRAFT NOTES IN PROGRESS]

• is it useful to know that their are images there at all?
• if purpose of images to lighten up document, that is not needed for screen readers; aesthetic function is not relevent
• keep noise down for screen reader users
  • most people will read this doc once, maybe twice, so not as much of an issue as say alt in a nav bar (e.g., Search icon in WAI nav)
• not providing alt text leaves people out, they don't know there are images there at all
• I would talk about the images to another person, including a person who is blind, thus need some indication of them
• when reading through with alt as is:
  • the summary being attributed to the images does not sit neatly where it is sematically. if we want a summary, then try changing the list to a series of headings and add a summary.
    • headings don't work semantically. those aren't the next level headings of the sections of the page.
  • images provide summary overview, which is nice to have w/o images (alt) as well, a few word intro
  • adding colon at end of alt helps
• include any key information in the text
• (Shawn: I got email from people who thought we missed alt on decorative bridge image in WAI site masthead)

Shawn: Some opposite opinions. Obviously there is no clear right or wrong answer. The nuances of alt are an art, not exact science. Appreciate all of the input! We will probably use the least problematic option.