Thread Subject: Reminder: Meeting today

Return to this mailing list's archives

From: Andi Snow-Weaver
Date: Wed, Jan 17 2007 5:40 AM
Subject: Reminder: Meeting today

We will have our regular meeting today at 1 PM Eastern time.

Call-in details and agenda are now available at
http://teitac.org/wiki/Web_and_Software:January_17.

Andi

From: Andi Snow-Weaver
Date: Tue, Jan 30 2007 5:10 AM
Subject: Reminder: Meeting today

Remember that we are meeting today instead of tomorrow this week because
both Curtis and I are unavailable tomorrow.

Call-in details and agenda are now available at
http://teitac.org/wiki/Web_and_Software:January_31

Andi

From: Andi Snow-Weaver
Date: Thu, Feb 08 2007 10:14 AM
Subject: Reminder: Meeting today

Please see the agenda for details on today's meeting. [1]

We will spend an hour or less on the API Requirements proposal. Then we are
privileged to have a guest speaker on cognitive disabilities. Her name is
Nancy Ward, and she is an editor of an online website for disability
benefits information, focused to the needs of persons with cognitive
disabilities. We will allow at least 1/2 hour for discussion and Q&A with
Ms. Ward.

[1] http://teitac.org/wiki/Web_and_Software:_February_7

Andi

From: Bailey Bruce
Date: Thu, Feb 08 2007 10:15 AM
Subject: Re: Reminder: Meeting today

This is Bruce from the meeting room floor at 9:20.
Audio-Video subcommittee started late (no fault of theirs) and Web Soft will probably be a little delayed startup up. You can call into the number now and get the end of the A-V call if you like.

From: Barrett, Don
Date: Thu, Feb 08 2007 10:18 AM
Subject: Re: Reminder: Meeting today

Nancy Ward was wonderful; our big problem is to try and distinguish
actual access issues from usability issues; for the cognitive folks,
many of the issues surround usability issues and would be tough for 508.
I think that is why the original EITAC couldn't wrestle anything 508ish
for the cognitive folks into the standard, although I applaud any effort
to try and simplify Federal information. Lots to think about.


Don Barrett
Section 508 Coordinator
U.S. Department of Education
(202)-205-8245
= EMAIL ADDRESS REMOVED =

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Wednesday, February 07, 2007 7:10 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-websoftware] Reminder: Meeting today


Please see the agenda for details on today's meeting. [1]

We will spend an hour or less on the API Requirements proposal. Then we
are privileged to have a guest speaker on cognitive disabilities. Her
name is Nancy Ward, and she is an editor of an online website for
disability benefits information, focused to the needs of persons with
cognitive disabilities. We will allow at least 1/2 hour for discussion
and Q&A with Ms. Ward.

[1] http://teitac.org/wiki/Web_and_Software:_February_7

Andi

From: Hoffman, Allen
Date: Thu, Feb 08 2007 10:19 AM
Subject: Re: Reminder: Meeting today

I believe the speaker in the afternoon had only a couple viable
suggestions for regulatory items, one of which was to require glossary
functionality for user-interfaces. I suppose this may be doable, and is
certainly testable.



Allen hoffman -- 202-447-0303

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
Barrett, Don
Sent: Wednesday, February 07, 2007 5:16 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Reminder: Meeting today

Nancy Ward was wonderful; our big problem is to try and distinguish
actual access issues from usability issues; for the cognitive folks,
many of the issues surround usability issues and would be tough for 508.
I think that is why the original EITAC couldn't wrestle anything 508ish
for the cognitive folks into the standard, although I applaud any effort
to try and simplify Federal information. Lots to think about.


Don Barrett
Section 508 Coordinator
U.S. Department of Education
(202)-205-8245
= EMAIL ADDRESS REMOVED =

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
Snow-Weaver
Sent: Wednesday, February 07, 2007 7:10 AM
To: = EMAIL ADDRESS REMOVED =
Subject: [teitac-websoftware] Reminder: Meeting today


Please see the agenda for details on today's meeting. [1]

We will spend an hour or less on the API Requirements proposal. Then we
are privileged to have a guest speaker on cognitive disabilities. Her
name is Nancy Ward, and she is an editor of an online website for
disability benefits information, focused to the needs of persons with
cognitive disabilities. We will allow at least 1/2 hour for discussion
and Q&A with Ms. Ward.

[1] http://teitac.org/wiki/Web_and_Software:_February_7

Andi

From: Peter Korn
Date: Thu, Feb 08 2007 10:20 AM
Subject: Re: Reminder: Meeting today

Hi Allen,

> I believe the speaker in the afternoon had only a couple viable
> suggestions for regulatory items, one of which was to require glossary
> functionality for user-interfaces. I suppose this may be doable, and is
> certainly testable.

What I captured in my notes was:

- Cognitive A11y features / Some features are appropriate to require
- alternatives to speeded responses
- word lookup, or compatibility with word lookup tools
- text reading, or compatbiility with text reading tools
- spelling correction for spelling-sensitive interactions
- provision for suppressing unneeded functions

The first of these we already have.

The next three - word lookup (or compatibility with AT), text reading
(or compatibility with AT), and spelling correction [to which I would
add "or compatible with AT"] I believe can *all* be done via compatible
AT using the existing API Requirements Proposal. The set of "Additional
object information needed for objects that contain text" (see
http://teitac.org/wiki/Web_and_Software:Accessibility_API_Requirements_Proposal#Additional_object_information_needed_for_objects_that_contain_text:)
and the set of " Additional object information needed for editable text
objects:" (see
http://teitac.org/wiki/Web_and_Software:Accessibility_API_Requirements_Proposal#Additional_object_information_needed_for_editable_text_objects:)
should provide what is needed to support an add-on AT product that does
those three functions.

That then leaves the provision for suppressing unneeded functions. This
is a very difficult provision to measure, as a determination of what is
unneeded is highly subjective.

Still, if we get 4 out of his 5, I'd say we are significantly advancing
a number of cognitive disability use cases.


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.




>
> Allen hoffman -- 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
> Barrett, Don
> Sent: Wednesday, February 07, 2007 5:16 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Reminder: Meeting today
>
> Nancy Ward was wonderful; our big problem is to try and distinguish
> actual access issues from usability issues; for the cognitive folks,
> many of the issues surround usability issues and would be tough for 508.
> I think that is why the original EITAC couldn't wrestle anything 508ish
> for the cognitive folks into the standard, although I applaud any effort
> to try and simplify Federal information. Lots to think about.
>
>
> Don Barrett
> Section 508 Coordinator
> U.S. Department of Education
> (202)-205-8245
> = EMAIL ADDRESS REMOVED =
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
> Snow-Weaver
> Sent: Wednesday, February 07, 2007 7:10 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] Reminder: Meeting today
>
>
> Please see the agenda for details on today's meeting. [1]
>
> We will spend an hour or less on the API Requirements proposal. Then we
> are privileged to have a guest speaker on cognitive disabilities. Her
> name is Nancy Ward, and she is an editor of an online website for
> disability benefits information, focused to the needs of persons with
> cognitive disabilities. We will allow at least 1/2 hour for discussion
> and Q&A with Ms. Ward.
>
> [1] http://teitac.org/wiki/Web_and_Software:_February_7
>
> Andi
>
>

From: Mike Paciello
Date: Thu, Feb 08 2007 10:20 AM
Subject: Re: Reminder: Meeting today

Thanks very much for capturing this Peter.

For those interested, WebAIM includes a nice 2-part article discussing web &
software design for individuals with cognitive disabilities:

WebAIM: http://www.webaim.org/articles/cognitive/cognitive_too_little/ &
http://www.webaim.org/articles/cognitive/conceptualize/

-Mike


Mike Paciello, TPG
Cell: +1 603.566.7713
e-mail: = EMAIL ADDRESS REMOVED =
web: www.paciellogroup.com

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter Korn
Sent: Wednesday, February 07, 2007 11:14 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Reminder: Meeting today

Hi Allen,

> I believe the speaker in the afternoon had only a couple viable
> suggestions for regulatory items, one of which was to require glossary
> functionality for user-interfaces. I suppose this may be doable, and is
> certainly testable.

What I captured in my notes was:

- Cognitive A11y features / Some features are appropriate to require
- alternatives to speeded responses
- word lookup, or compatibility with word lookup tools
- text reading, or compatbiility with text reading tools
- spelling correction for spelling-sensitive interactions
- provision for suppressing unneeded functions

The first of these we already have.

The next three - word lookup (or compatibility with AT), text reading
(or compatibility with AT), and spelling correction [to which I would
add "or compatible with AT"] I believe can *all* be done via compatible
AT using the existing API Requirements Proposal. The set of "Additional
object information needed for objects that contain text" (see
http://teitac.org/wiki/Web_and_Software:Accessibility_API_Requirements_Propo
sal#Additional_object_information_needed_for_objects_that_contain_text:)
and the set of " Additional object information needed for editable text
objects:" (see
http://teitac.org/wiki/Web_and_Software:Accessibility_API_Requirements_Propo
sal#Additional_object_information_needed_for_editable_text_objects:)
should provide what is needed to support an add-on AT product that does
those three functions.

That then leaves the provision for suppressing unneeded functions. This
is a very difficult provision to measure, as a determination of what is
unneeded is highly subjective.

Still, if we get 4 out of his 5, I'd say we are significantly advancing
a number of cognitive disability use cases.


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.




>
> Allen hoffman -- 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
> Barrett, Don
> Sent: Wednesday, February 07, 2007 5:16 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Reminder: Meeting today
>
> Nancy Ward was wonderful; our big problem is to try and distinguish
> actual access issues from usability issues; for the cognitive folks,
> many of the issues surround usability issues and would be tough for 508.
> I think that is why the original EITAC couldn't wrestle anything 508ish
> for the cognitive folks into the standard, although I applaud any effort
> to try and simplify Federal information. Lots to think about.
>
>
> Don Barrett
> Section 508 Coordinator
> U.S. Department of Education
> (202)-205-8245
> = EMAIL ADDRESS REMOVED =
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
> Snow-Weaver
> Sent: Wednesday, February 07, 2007 7:10 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] Reminder: Meeting today
>
>
> Please see the agenda for details on today's meeting. [1]
>
> We will spend an hour or less on the API Requirements proposal. Then we
> are privileged to have a guest speaker on cognitive disabilities. Her
> name is Nancy Ward, and she is an editor of an online website for
> disability benefits information, focused to the needs of persons with
> cognitive disabilities. We will allow at least 1/2 hour for discussion
> and Q&A with Ms. Ward.
>
> [1] http://teitac.org/wiki/Web_and_Software:_February_7
>
> Andi
>
>

From: Hoffman, Allen
Date: Thu, Feb 08 2007 10:20 AM
Subject: Re: Reminder: Meeting today

I concur.


Allen hoffman -- 202-447-0303

-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter
Korn
Sent: Wednesday, February 07, 2007 11:14 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Reminder: Meeting today

Hi Allen,

> I believe the speaker in the afternoon had only a couple viable
> suggestions for regulatory items, one of which was to require glossary

> functionality for user-interfaces. I suppose this may be doable, and
> is certainly testable.

What I captured in my notes was:

- Cognitive A11y features / Some features are appropriate to require
- alternatives to speeded responses
- word lookup, or compatibility with word lookup tools
- text reading, or compatbiility with text reading tools
- spelling correction for spelling-sensitive interactions
- provision for suppressing unneeded functions

The first of these we already have.

The next three - word lookup (or compatibility with AT), text reading
(or compatibility with AT), and spelling correction [to which I would
add "or compatible with AT"] I believe can *all* be done via compatible
AT using the existing API Requirements Proposal. The set of "Additional
object information needed for objects that contain text" (see
http://teitac.org/wiki/Web_and_Software:Accessibility_API_Requirements_P
roposal#Additional_object_information_needed_for_objects_that_contain_te
xt:)
and the set of " Additional object information needed for editable text
objects:" (see
http://teitac.org/wiki/Web_and_Software:Accessibility_API_Requirements_P
roposal#Additional_object_information_needed_for_editable_text_objects:)
should provide what is needed to support an add-on AT product that does
those three functions.

That then leaves the provision for suppressing unneeded functions. This
is a very difficult provision to measure, as a determination of what is
unneeded is highly subjective.

Still, if we get 4 out of his 5, I'd say we are significantly advancing
a number of cognitive disability use cases.


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.




>
> Allen hoffman -- 202-447-0303
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of
> Barrett, Don
> Sent: Wednesday, February 07, 2007 5:16 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Reminder: Meeting today
>
> Nancy Ward was wonderful; our big problem is to try and distinguish
> actual access issues from usability issues; for the cognitive folks,
> many of the issues surround usability issues and would be tough for
508.
> I think that is why the original EITAC couldn't wrestle anything
508ish
> for the cognitive folks into the standard, although I applaud any
effort
> to try and simplify Federal information. Lots to think about.
>
>
> Don Barrett
> Section 508 Coordinator
> U.S. Department of Education
> (202)-205-8245
> = EMAIL ADDRESS REMOVED =
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andi
> Snow-Weaver
> Sent: Wednesday, February 07, 2007 7:10 AM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [teitac-websoftware] Reminder: Meeting today
>
>
> Please see the agenda for details on today's meeting. [1]
>
> We will spend an hour or less on the API Requirements proposal. Then
we
> are privileged to have a guest speaker on cognitive disabilities. Her
> name is Nancy Ward, and she is an editor of an online website for
> disability benefits information, focused to the needs of persons with
> cognitive disabilities. We will allow at least 1/2 hour for discussion
> and Q&A with Ms. Ward.
>
> [1] http://teitac.org/wiki/Web_and_Software:_February_7
>
> Andi
>
>

From: Andi Snow-Weaver
Date: Wed, Feb 28 2007 6:45 AM
Subject: Reminder: Meeting today

We will have our regularly scheduled conference call today at 1 PM Eastern
time. The agenda and call-in details are now available at

http://teitac.org/wiki/Web_and_Software:_February_28

I haven't completed the minutes from last week yet. I'm in an all-day
meeting but will try to complete it before the meeting. We can delay
approval of last week's minutes if I don't get it done soon.

Andi