W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > October to December 2011

irc logs nov 2011 face to face part 2

From: Jim Allan <jimallan@tsbvi.edu>
Date: Thu, 17 Nov 2011 10:58:22 -0600
Message-ID: <CA+=z1WkHXinaBUSdahHM3FyU9CixsAAYzhyiOjwE+3NZM4vr8A@mail.gmail.com>
To: WAI-ua <w3c-wai-ua@w3.org>
 Status#uaX[Master Draft ->
http://www.w3.org/WAI/UA/2011/ED-UAAG20-20111103/MasterUAAG20111103.html][02:24]
== jallan [qw3birc@128.30.52.28] has joined #ua[02:25] <Jan> Intent
2.5.1 (moving to 2.3.X): The user of a keyboard interface can both
discover and be reminded of keystrokes. Some of these users may be
using assistive technologies enabling communication of the keystrokes
by programmatic means, while other users will need visual indicators,
such as underlines.[02:25] <jallan> rrsagent, make minutes[02:25]
<RRSAgent> I have made the request to
generatehttp://www.w3.org/2011/11/03-ua-minutes.html jallan[02:27]
<jallan> Resolution: move 2.5.1 to 2.3.x[02:27] <Jan> Intent 2.5.1
(moving to 2.3.X): The user of a keyboard interface needs to be able
to discover and be reminded of keystrokes. Some of these users may be
using assistive technologies enabling communication of the keystrokes
by programmatic means, while other users will need visual indicators,
such as underlines.[02:29] <jallan> topic: 2.11.8[02:29] <Jan> 2.11.8
Semantic Navigation of Time-Based Media: The user can navigate by
semantic structure within the time-based media, such as by chapters or
scenes present in the media (Level AA)[02:29] <Jan> Intent 2.11.8: To
allow users to navigate time-based media in ways that are more
meaningful than arbitrary time increments.[02:29] <Jan> BUT is this a
sub-class of (2.3.1 Direct Navigation to Important Elements)[02:30]
<Jan> Intent 2.11.8: Users need to be able to navigate time-based
media in ways that are more meaningful than arbitrary time
increments.[02:33] <jallan> users with disabilities need to
efficiently navigate through chunks (chapters, scenes) of media[02:35]
== JohnS [qw3birc@128.30.52.28] has quit [Ping timeout][02:35]
<jallan> topic: 2.11.9[02:36] <Jan> 2.11.9 Track Enable/Disable of
Time-Based Media: During time-based media playback, the user can
determine which tracks are available and select or deselect tracks.
These selections may override global default settings for captions,
audio descriptions, etc. (Level AA)[02:36] <Jan> Intent 2.11.9: To
give users the ability to choose the tracks to meet their
accessibility needs when authors have provided many
alternatives.[02:36] <Jan> NOTE similarity to 1.1.2 Browse and
Render[02:37] <jallan> Some users with disabilities need to choose
different languages or audio tracks (descriptive video)[02:37] <Jan>
Intent 2.11.9: Users need the ability to choose the tracks that best
meet their accessibility needs (e.g. the caption track in their own
language) when authors have provided many alternatives.[02:38] ==
JohnS [qw3birc@128.30.52.28] has joined #UA[02:39] <mhakkinen> 2.7.1
Change Preference Settings[02:39] <mhakkinen> The user can change
settings that impact accessibility. (Level A)[02:39] <mhakkinen> Users
have a variety of needs when it comes to customization of a user
agent.  This success criteria ensures that a user can customize
settings offered by the  user agent to meet those needs.[02:41]
<jallan> the document has many SC that say specify, configure, etc.
this allows the changing.[02:42] <mhakkinen> 2.7.2 Persistence of
Settings Affecting Accessibility[02:42] <mhakkinen> User agent
accessibility preference settings persist between sessions. (Level
A)[02:42] <mhakkinen> When a user has customized settings within the
user agent to maximize  accessibility, this success criteria ensures
that customization is saved between  browsing sessions.  The user can
then have those settings automatically used in  subsequent browsing
sessions.[02:42] <jallan> @@remove 2.7.1[02:43] <jallan> Resolution:
Remove 2.7.1[02:44] <jallan> topic: 2.7.2 persistence of a11y
settings[02:45] <jallan> 2.7.2 Persistence of Settings Affecting
Accessibility-- User agent accessibility preference settings persist
between sessions. (Level A)     Intent: When a user has customized
settings within the user agent to maximize  accessibility, this
success criteria ensures that customization is saved between  browsing
sessions.  The user can then have those settings automatically used in
 subsequent browsing sessions.[02:46] <jallan> discussion of whether
this applies to multiple users[02:47] <jallan> the intent is a per
user basis.[02:47] <mhakkinen> 2.7.3 Restore all to default: The user
can restore all preference settings to  default values. (Level
A)[02:47] <jallan> topic: 2.7.3[02:47] <mhakkinen> Users who customize
settings may find that their chosen settings are not  suitable and
decide to restore these settings to their default values.  For some
users, it may be difficult to easily recall all modified settings
while others  may find it difficult to navigate to each modified
setting, especially if a  particular setting may have impacted their
ability to do so. This success  criteria provides a means for a user
to easily restore all preference setting[02:49] <mhakkinen> This
success  criteria provides a means for a user to easily restore all
preference settings  to their default values using a single function
or action.  [02:51] <mhakkinen> For some  users, it may be difficult
to easily recall all modified settings while others  may find it
difficult to navigate to each modified setting, especially if a
particular setting may have impacted their ability to do so. Users who
customize settings may find that their chosen settings are not
suitable and decide to restore these settings to their default values.
  This success  criteria provides a means for a user to easily restore
all preference settin[02:51] <mhakkinen> revised intent:[02:51]
<mhakkinen> tion or action.[02:51] <jallan> topic: 2.7.4[02:51]
<JohnS> 2.7.4 Multiple Sets of Preference Settings:  The user can save
and retrieve multiple sets of user agent preference settings. (Level
AA)[02:52] <JohnS> Intent  Some users may need to change their setting
preferences under different circumstances such as varying levels of
user fatigue or changes in environmental noise or lighting conditions.
Providing an easy method for saving and switching between a set of
preferences helps the user complete intended tasks in different
situations.  (2.7.4)[02:52] <JohnS> 2.7.5 Restore related preferences
to default:  The user can restore groups of related preference
settings to default values (e.g. reset keyboard shortcuts, reset
colors and sizes of rendered content). (Level AA)[02:52] <jallan>
topic: 2.7.5[02:53] <Jan> scribe: Jan[02:53] <Jan> John: In mobile
space this isn't really possible...[02:54] <Jan> KF: We should
remove[02:54] <Jan> JS: Agreed[02:54] <Jan> John: Recommend
remove[02:55] <Jan> GL: is this the only one that talks about groups
of settings...[02:55] <Jan> GL: e.g. the ability to send someone an
appearance scheme[02:56] <Jan> John: I agree re: modifying but not
resetting[02:56] <Jan> GL: Useful on windows - appearance
scheme[02:56] <Jan> GL: Not as useful if it was ALL settings[02:56]
<Jan> KP: e.g. in GMail addon to change keyboard shortcuts[02:57]
<greg> This is not directly about 2.7, but it is beneficial for
programs to allow users to save, distribute, and load groups of
related settings without having it carry ALL settings with it.[02:57]
<Jan> Resolution: Remove 2.7.5[02:59] <JohnS> 2.7.6 Change preference
setting outside the UI:  The user can adjust preference settings from
outside the user agent user interface. (Level AA)[02:59] <jallan>
topic: 2.7.6[02:59] <jallan> scribe: jallan[03:00] <jallan> john: on
mobile platforms there is no way to do this[03:00] <JohnS> Intent:
When the user inadvertently selects a setting that renders the UI
inaccessible, a method must be provided to allow the user to reset the
UI.[03:00] <JohnS> Examples: 1. On a desktop device, there is a
command line interface to reset the accessibility parameters.  2. On a
mobile a hard button could be used to reset the accessibility
parameters on user command.[03:03] <jallan> greg: concerned about
using only 'reset', prefers adjust[03:04] <jallan> use 'user
preferences' instead of a11y parameters[03:06] <JohnS> The user should
have the ability to set user preferences to enable accessibility
features of a UA prior to launching the UA.[03:07] <jallan> jan: the
control settings for the UA chrome[03:09] <jallan> ...if chrome slaved
to the settings of the os. the user could change the OS to affect the
UA UI so the user has ....[03:09] <JohnS> he user should have the
ability to set user preferences to enable the controls of the
accessibility features of a UA.[03:10] <jallan> ^^ new intent[03:11]
<JohnS> 2.7.7 Portable Preference settings: The user can transfer
preference settings onto a compatible system. (Level AAA)[03:11]
<jeanne> action: Jeanne to smith the IER for 2.7.6[03:11]  * trackbot
noticed an ACTION. Trying to create it.[03:11]  * RRSAgent records
action 6[03:11] <@trackbot> Created ACTION-640 - Smith the IER for
2.7.6 [on Jeanne F Spellman - due 2011-11-10].[03:11] <jallan> topic:
2.7.7[03:12] <JohnS> Intent: A user can migrate preference setting
from one device to another in order to maintain accessibility
parameters.[03:13] <jallan> A user who has spent time customizing
accessibility preferences to meet their needs, they can easily migrate
preference setting to another device in order to maintain
accessibility of other user agents[03:14] <JohnS> Intent: User will
spend time customizing a UA to maximize accessibility, the user should
be able to migrate the customization to maintain accessibility when
using a compatible system. This will also allow rehabilitation
professional of setting the required setting once.[03:14] <jallan>
jan: Portable Preference settings: The user can transfer preference
settings onto a compatible user agent.[03:15] <Jan> jan: Portable
Preference settings: The user can transfer preference settings between
instances of the user agent[03:16] <jallan> kelly: if you have
portable preference settings you must include accessibility preference
settings.[03:17] <jallan> kelly: wants to remove this. it is only
about a11y settings[03:20] <jallan> kim and greg have use registry
files to help users with accessibility[03:21] <jallan> kelly says this
will not fly[03:21] <jallan> jeanne: this is AAA, it is planting a
seed.[03:22] <jallan> mark: chome has this feature,
synchronization[03:22] <jeanne> I think that if this is a step toward
GPII, it is a good thing to include it at AAA[03:23] <jallan> proposed
rewording: Portable Preference settings: The user can transfer
preference settings between instances of the user agent[03:23]
<jallan> this is roaming preferences[03:24] <jallan> Intent: User will
spend time customizing a UA to maximize accessibility, the user should
be able to migrate the customization to maintain accessibility when
using a compatible system. This will also allow rehabilitation
professional of setting the required setting once.[03:25] <jallan>  A
user who has spent time customizing accessibility preferences to meet
their needs, they can easily migrate preference setting to another
device in order to maintain accessibility of other user agents[03:25]
== JohnS [qw3birc@128.30.52.28] has quit [Quit: Page closed][03:26]
<jallan> rrsagent, make minutes[03:26] <RRSAgent> I have made the
request to generatehttp://www.w3.org/2011/11/03-ua-minutes.html
jallan[03:42] <jallan> action: jeanne to wordsmith 2.7.7[03:42]  *
trackbot noticed an ACTION. Trying to create it.[03:42]  * RRSAgent
records action 7[03:42] <@trackbot> Created ACTION-641 - Wordsmith
2.7.7 [on Jeanne F Spellman - due 2011-11-10].[03:44] <jallan> topic:
2.11.3[03:44] <greg> 2.11.3 Execution Placeholder: The user can render
a placeholder instead of executable content that would normally be
contained within an on-screen area (e.g. Applet, Flash), until
explicit user request to execute. (Level A)[03:44] <greg> Intent:
Documents that do things automatically when loaded can delay,
distract, or interfere with user's ability to continue with a task. In
the case of embedded objects, applets and media, replacing the
executable content with a placeholder tells the user what has been
blocked and provides a mechanism (e.g. a play button) for unblocking
when the user is ready.[03:44] <greg> Note: It is generally
recommended that the placeholder take up the same space as the object
it is replacing, so that the presentation does not need to be reflowed
when the execution is started. However, users on mobile devices or
using screen enlargers, or who have difficulty with scroll commands
may benefit from having the option of a smaller placholder.[03:44]
<greg>  [03:44] <greg> Examples:[03:44] <greg> Jane has difficulty
concentrating. In order to concentrate on the text of a document she
wants to hide any multimedia content, and only trigger execution of
that content when she feels it's appropriate. An icon on the status
bar tells him that scripts have been blocked, and by clicking it he
can select which scripts to run.[03:44] <greg> Evan is blind. He sets
the option in his browser so that when a web page loads it does not
automatically run executable object, so that any or music or speech
they play won't interfere with his ability to hear his screen reader.
An icon on the status bar tells him that scripts have been blocked,
and by clicking it she can select which scripts to run.[03:48] <greg>
Jane has difficulty concentrating. In order to concentrate on the text
of a document she wants to hide any multimedia content, and only
trigger execution of that content by clicking on the placeholder she
feels it's appropriate.[03:48] <greg> Evan is blind. He sets the
option in his browser so that when a web page loads it does not
automatically run executable object, so that any or music or speech
they play won't interfere with his ability to hear his screen reader.
When he is ready to start it playing he navigates to the placeholder
and presses the Enter key to activate it.[03:50] <jallan> topic:
2.11.4[03:50] <greg> 2.11.4 Execution Toggle: The user can turn on/off
the execution of executable content that would not normally be
contained within a particular area (e.g. Javascript). (Level A)[03:50]
<greg> Intent: Documents that do things automatically when loaded can
delay, distract, or interfere with user's ability to continue with a
task. The user needs to be able to specify that executable content
(e.g. scripts) be blocked when a document loads, be told which content
has been blocked, and be able to selectively execute the content at a
later time.[03:50] <greg> Examples:[03:50] <greg> Jane has difficulty
concentrating. In order to concentrate on the text of a document she
wants to prevent any animations, media, or dynamic content from
executing until she is ready. An icon on the status bar tells him that
scripts have been blocked, and by clicking it she can select which
scripts to run.[03:50] <greg> Evan is blind. He sets the option in his
browser so that when a web page loads it does not automatically start
running scripts that might play sounds that would interfere with his
ability to hear his screen reader. An icon on the status bar tells him
that scripts have been blocked, and by clicking it he can select which
scripts to run.[03:51] <greg> Jane has difficulty concentrating. In
order to concentrate on the text of a document she wants to prevent
any animations, media, or dynamic content from executing until she is
ready. An icon on the status bar tells her that scripts have been
blocked, and by clicking it she can select which scripts to
run.[03:52] <jallan> kelly: has issues with this sc. can already turn
on/off javascript. browsers have 'filtering' can turn on/off active
X.[03:53] <jallan> ... can not selectively turn on js or active x
items.[03:54] <jallan> jan: the intent in informational. so the
selectivity is implied[03:54] <jallan> ... need a note that javascript
is ubiquitious and no content may appear on the page[03:54] <greg>
Note: Some web applications and document may be essentially empty
until scripts are run. However, it is still important for users to
have this level of control.[03:56] <greg> Evan is blind. He sets the
option in his browser so that when a web page loads it does not
automatically start running scripts that might play sounds that would
interfere with his ability to hear his screen reader. An icon on the
status bar tells him that scripts have been blocked, and by activating
it he can select which scripts to run.[03:57] <jallan> only 2.11.8 and
2.11.9 still to write intents!![03:57] <jallan> this is
incorrect[03:57] <jallan> topic 2.11.6[03:58] <greg> 2.11.6
Stop/Pause/Resume Time-Based Media: The user can stop, pause, and
resume rendered audio and animation content (including video and
animated images) that last three or more seconds at their default
playback rate. (Level A)[03:58] <greg> Time-based media such as audio
and video can delay, distract, or interfere with user's ability to
continue with a task. When media is playing, the user may realize that
it is interfering with her ability to carry out other tasks. She may
also need to pause and resume playback to allow her to keep up or
carry out other tasks at the same time.[03:58] <greg> Examples:[03:58]
<greg> * Evan is blind and wants to pause the audio in order to carry
out another task without it interfering with his ability to hear their
screen reader.[03:58] <greg> * Marla starts playing a video and
realizes user with seizure disorders realizes the video is
uncomfortable, so she presses the space bar to pause it.[03:59] <greg>
Those are just a start, not finished yet.[04:00] <jallan> action: greg
to smith the 2.11.6 intent/examples[04:00]  * RRSAgent records action
8[04:00]  * trackbot noticed an ACTION. Trying to create it.[04:00]
<@trackbot> Created ACTION-642 - Smith the 2.11.6 intent/examples [on
Greg Lowney - due 2011-11-10].[04:00] <mhakkinen> 2.11.6 Intent -
Users with sensory, attentional, or cognitive impairments may have
difficulty following or understanding multimedia content.  By allowing
time-based media to be stopped, paused, and resumed, users are able
control the presentation, providing time to understand or act upon
presented content before continuing, or to stop potentially
distracting information.[04:05] <jallan> topic: 2.11.7[04:05] <jallan>
2.11.7 Navigate Time-Based Media: The user can navigate along the
timebase using a continuous scale, and by relative time units within
rendered audio and animations (including video and animated images)
that last three or more seconds at their default playback rate. (Level
A)[04:06] <greg> If I could not understand what this meant, I think a
lot of our readers will have similar problems.[04:06] <greg> Too much
jargon.[04:07] <jallan> action: mark to smith 2.11.7 with jeanne to
explain to greg, and write and intent[04:07]  * RRSAgent records
action 9[04:07]  * trackbot noticed an ACTION. Trying to create
it.[04:07] <@trackbot> Created ACTION-643 - Smith 2.11.7 with jeanne
to explain to greg, and write and intent [on Markku Hakkinen - due
2011-11-10].[04:07] <greg> (Note that I don't think we have an
equivalent for normal visual content.)[04:07] <greg> (e.g. scrolling
by lines and pages, and jumping to the 5th page).[04:17] <jallan>
topic: 3.1.2[04:18] <jallan> jim: not sure what a low priority
message[04:19] <jallan> kelly: can do this with ARIA, seems to say
support ARIA politeness.[04:21] <jallan> kelly: kick this out. ask in
next update @@does UAAG do enough to support WAI ARIA, canvas
accessibility, etc@@[04:22] <jallan> jan: thinks it should go[04:24]
<jallan> kim: this is important[04:25] <jallan> kim: provides user
examples[04:26] <jallan> greg: user has ability to turn off
announcements[04:26] <jallan> gregory rosmaita[04:26] <jallan> 3.1.2
NO[04:28] <jallan> topic: 3.2.1[04:28] <greg> Back button and Undo (in
editing) could be SC in 3.2, as could spell checking.[04:28] <jallan>
what about adding sc for spell check, backspace, spell checking[04:28]
<Jan> Action: JR to add SC on Undo[04:28]  * trackbot noticed an
ACTION. Trying to create it.[04:28]  * RRSAgent records action
10[04:28] <@trackbot> Created ACTION-644 - Add SC on Undo [on Jan
Richards - due 2011-11-10].[04:29] <Jan> Action: Greg to add SC re:
Back button[04:29]  * RRSAgent records action 11[04:29]  * trackbot
noticed an ACTION. Trying to create it.[04:29] <@trackbot> Created
ACTION-645 - Add SC re: Back button [on Greg Lowney - due
2011-11-10].[04:32] <jallan> need an example for clicking on the
submit button and asking for confirmation.[04:32] <jallan> action:
greg to write examples for 3.2.1 example for clicking on the submit
button and asking for confirmation.[04:32]  * trackbot noticed an
ACTION. Trying to create it.[04:32]  * RRSAgent records action
12[04:32] <@trackbot> Created ACTION-646 - Write examples for 3.2.1
example for clicking on the submit button and asking for confirmation.
[on Greg Lowney - due 2011-11-10].[04:33] <jallan> topic: 3.3.1
accessible documentation[04:34] <jallan> all ok[04:34] <jallan> topic:
3.3.2 document accessibilty features[04:35] <jallan> kelly: its ok for
product to not have documentation[04:36] <jallan> greg: if the UA
doesn't tell you about the accessibility features it should fail
uaag[04:36] <jallan> kelly: remove the word ALL[04:37] <Jan> A.4.2.1
Document Accessibility Features: All features of the authoring tool
that must be present to meet Part A of ATAG 2.0 (e.g., keyboard
shortcuts, text search) are documented. (Level A)[04:38] <Jan>
Reworking for UAAG: Document Accessibility Features: All features of
the user agent that must be present to meet the other UAAG 2.0 success
criteria (e.g., keyboard shortcuts, text search) are documented.
(Level A)[04:38] <Jan> Reworking for UAAG: Document Accessibility
Features: All features of the user agent that must be present to meet
the other UAAG 2.0 success criteria are documented. (Level A)[04:38]
<Jan> Reworking for UAAG: Document Accessibility Features: Features of
the user agent that must be present to meet the other UAAG 2.0 success
criteria are documented. (Level A)[04:40] <Jan> Reworking for UAAG:
Document Accessibility Features: All features of the user agent that
must be present to meet the other UAAG 2.0 success criteria are
documented. (Level A)[04:41] <Jan> Reworking for UAAG: Document
Accessibility Features: All features of the user agent that are
present to meet the other UAAG 2.0 success criteria are documented.
(Level A)[04:42] <Jan> Reworking for UAAG: Document Accessibility
Features: All features of the user agent that meet the other UAAG 2.0
success criteria are documented. (Level A)[04:42] <Jan> Reworking for
UAAG: Document Accessibility Features: All features of the user agent
that meet UAAG 2.0 success criteria are documented. (Level A)[04:44]
<jallan> topic: 3.3.3 changes between definitions[04:44] <jallan> jan:
this could go away[04:44] <jallan> kim: this is important[04:45]
<jallan> jan: this should be AAA[04:45] <jallan> kelly: +1, change
wording to reflect language in 3.3.2[04:46] <jallan> kim: new version
of UA, do you click on what's new, shouldn't the accessibility
features be included in the what's new[04:48] <jallan> jan: they will
have already documented the changes. this says please inform the user
of a11y changes.[04:49] <jallan> kim: this is really hard for users to
discover the changes[04:50] <jallan> greg: so its ok to read a 500
page manual to find the removal of the one feature that you
need.[04:51] <jallan> jan: its not in wcag or atag[04:52] <jallan>
change to aaa[04:53] <jallan> topic 3.3.4[04:53] <jallan> ok[04:54]
<jallan> topic: 3.3.5[04:54] <jallan> jan and others: should be
removed[04:54] <jallan> all agree[04:55] <greg> What we're removing is
3.3.5 Context Sensitive Help: There is context-sensitive help on all
user agent features that benefit accessibility. (Level AAA)[04:57]
<jallan> topic: 3.4.1[04:57] == Jan_ [chatzilla@63.145.238.4] has
joined #ua[04:59] == Jan [chatzilla@63.145.238.4] has quit [Ping
timeout][04:59] == Jan_ has changed nick to Jan[05:00] <jallan> cross
reference this with 1.8.6, 1.8.7[05:00] <jallan> topic 3.4.2[05:01]
<jallan> greg: this is in ISO[05:03] <greg> Jan is correct that this
should only include things the UA does, not things the content does
that the UA cannot know about.[05:05] <jallan> this is different that
checkbox behavior[05:07] <Jan>
http://www.w3schools.com/html/tryit.asp?filename=tryhtml_form_radio[05:08]
<greg> ISO 9241-171 includes 9.3.14 Separate keyboard navigation and
activation:[05:08] <greg> Software shall allow users to move the
keyboard focus without triggering any effects other than the
presentation of information (e.g. scrolling or pop-ups that do not
change the focus or selection). An explicit keystroke or similar user
action shall be provided to trigger any other user-initiated
effect.[05:10] <jallan> big discussion.[05:12] <jallan> kelly:
software does not work this way[05:12] <jallan> kim: this is a huge
problem for speech input users.[05:13] <jallan> if you jump to a radio
button group, it will select the first one.[05:14] <jallan> jan: need
disclaimer for things that the ua recognizes[05:15] <jallan> kelly:
touch interface you see it you touch it, you select it.[05:15]
<jallan> kim: there is no speech control of phones because of this
problem[05:16] <jallan> jan: the behavior of arrowing through radio
buttons should select them. but can CTRL arrow to not select.[05:16]
<Jan> http://www.w3.org/TR/wai-aria-practices/#radiobutton[05:26]
<jallan> rrsagent, make minutes[05:26] <RRSAgent> I have made the
request to generatehttp://www.w3.org/2011/11/04-ua-minutes.html
jallan[05:26] <jallan> rrsagent, set logs public[05:26] <RRSAgent> I
have made the request, jallan[05:29] == kford [chatzilla@63.145.238.4]
has quit [Ping timeout][05:29] <jallan> rrsagent, make minutes[05:29]
<RRSAgent> I have made the request to
generatehttp://www.w3.org/2011/11/04-ua-minutes.html jallan[05:35]
<jeanne> http://www.w3.org/2011/11/03-ua-irc.html________________________________________@trackbotAdmingregjallanJanjeannemhakkinenRRSAgent

-- 
Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Thursday, 17 November 2011 16:59:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 17 November 2011 16:59:01 GMT