Thread Subject: Re: URGENT ACTION NEEDED BY COB JUNE 8TH !
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, Jun 04 2007 4:05 PM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: Michaelis, Paul R. (Paul): "Re: URGENT ACTION NEEDED BY COB JUNE 8TH !"
- Previous message in thread: Gunnar Hellström: "Re: URGENT ACTION NEEDED BY COB JUNE 8TH !"
- Messages sorted by: Author | Thread | Date
1) "provided" was used specifically because some of our provisions can't be
met by just the display. They need the display and the software driving
what is displayed. The Terminal Device would need to be all the things
that a user perceives as providing their interface. We don't want to have
one product have to meet the guidelines while another (that looks identical
to the user) does not because the software is implemented differently (one
product uses a remote processor while others use local).
2) Good edits on #2.
How about we use "INPUT" instead of enter though: "Text communication
between two or more end points wherein the characters are transmitted within
1 second of being input."
Input feels a wee bit awkward but "entered" could be confused with hitting
the 'enter' key (to 'enter' the text). So Input is probably better than
both 'entered' and 'created'.
RE Line by line messaging (where you hit an enter key to send). I don't
think we are using it anywhere in a provision. If we did we would have to
Gregg C Vanderheiden Ph.D.
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Jim Tobias
Sent: Monday, June 04, 2007 4:07 PM
To: 'TEITAC Telecommunications Subcommittee'
Subject: Re: [teitac-telecom] URGENT ACTION NEEDED BY COB JUNE 8TH !
Sorry I wasn't on the call.
1. I would accept "Terminal device or devices with which the end user
directly interacts and that provide the user interface" if "provide" was
changed to "present". In many cases the user interface comes from afar.
For example, a router is controlled by a browser running on a computer. The
router is actually providing the user interface, but the computer/browser is
presenting it. A VoIP phone system presents the user interface on the
screen phone, but the interface comes from the VoIP server.
2. Several problems here. First, text conversations can be multiway, not
just 2-way. Second, I don't understand all that middle part. Third, are
characters "created" (outside of fiction)? Couldn't it be "Text
communication between two or more end points wherein the characters are
transmitted within 1 second of being entered." I assume this does not
include line-based text, where you have to hit 'enter' or something to send
the whole message. Are we defining that somewhere else, or ignoring it?
3. I accept the 1% error clarification.
From: Brenda Battat [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Monday, June 04, 2007 4:17 PM
To: TEITAC Telecommunications Subcommittee
Subject: [teitac-telecom] URGENT ACTION NEEDED BY COB JUNE 8TH !
Dear TEITAC Telecommunications Subcommittee Members:
On the call today we discussed definitions that need to be finalized. Please
provide feedback, concerns on the following definitions by COB June 8th.
1. Terminal Device
Keep in mind we do not want to involve gateway. During the discussion it was
felt that the current FCC definition would involve gateway as we know it
Proposed definition for terminal device
"Terminal device or devices with which the end user directly interacts and
that provide the user interface"
- I accept this definition Yes___ No_____
- I offer this definition as an alternative
- Next message in Thread: Michaelis, Paul R. (Paul): "Re: URGENT ACTION NEEDED BY COB JUNE 8TH !"
- Previous message in Thread: Gunnar Hellström: "Re: URGENT ACTION NEEDED BY COB JUNE 8TH !"