Thread Subject: Group A distinguishing
Note
This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.
From: Gregg Vanderheiden
Date: Mon, Oct 23 2006 3:40 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Jim Thatcher: "Re: Group A distinguishing"
- Previous message in thread: Barrett, Don: "Re: Group A distinguishing"
- Messages sorted by: Author | Thread | Date
FYI
Gregg
-- ------------------------------
Gregg C Vanderheiden Ph.D.
_____
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Michael R.
Burks
Sent: Monday, October 23, 2006 11:54 AM
To: 'TEITAC Web/Software Subcommittee'
Subject: Re: [teitac-websoftware] Group A distinguishing
Currently:
1194.21(a): Keyboard accessibility. Poster child and most wanted in web.
Can be rewritten to include many categories, for example
(all): When EIT is designed to use a keyboard as a means of (insert
functionality), (insert keyboard accessibility requirements here). I left
blanks here on purpose to not define all the categories right now and start
any debate there, nor the specific set of actual keyboard requirements
either. I just want to float this scoping concept for any thoughts you all
may have. i think it might lend some clarity to how to approach software,
web, and content requirements.
I agree with Al. This looks like the best way to do this.
Mike Burks
919 870 8788 - Office
703-254-3881 - Cell
_____
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Hoffman,
Allen
Sent: Monday, October 23, 2006 12:28 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Group A distinguishing
all:
here are some thoughts regarding how we might think about scoping of
requirements. We will have to work through this challenge, and if we can
find a common approach for all maybe that would expedite this process.
As I'm sure the general subcommittee is discussing, there are a set of core
requirements that can be applied across the board. then there are
requirements that apply to subsets of all. If we label each standard with
the scope it applies to, then this can be a much simpler process.
for example:
Currently:
1194.21(a): Keyboard accessibility. Poster child and most wanted in web.
Can be rewritten to include many categories, for example
(all): When EIT is designed to use a keyboard as a means of (insert
functionality), (insert keyboard accessibility requirements here). I left
blanks here on purpose to not define all the categories right now and start
any debate there, nor the specific set of actual keyboard requirements
either. I just want to float this scoping concept for any thoughts you all
may have. i think it might lend some clarity to how to approach software,
web, and content requirements.
Allen Hoffman
Department of homeland Security
Office On Accessible Systems & Technology
v: 202-447-0303 office-TTY: 202-401-0725
- Next message in Thread: Jim Thatcher: "Re: Group A distinguishing"
- Previous message in Thread: Barrett, Don: "Re: Group A distinguishing"
WebAIM is an initiative of:
