Thread Subject: Re: Proposal remote access requirements

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: Tom Brett
Date: Wed, Jun 20 2007 6:25 PM

The intention, as I understand it, is to provide a method for assistive
technology to access an agency's servers and data. This would primarily be
for federal employees who use assistive technology and who telecommute or
are otherwise unable to get to their work area because of a disaster.

Web conferencing would be covered by a different provision. Since the
Government would need to procure the web conferencing service that service
would need to meet all of the other software provisions.

Tom Brett


-----Original Message-----
From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Peter
Wallack
Sent: Wednesday, June 20, 2007 7:21 PM
To: TEITAC Web/Software Subcommittee
Subject: Re: [teitac-websoftware] Proposal remote access requirements

Can someone please clarify whether this definition is intended to
include or exclude web conferencing (like WebEx)

Peter Wallack
Accessibility Program Director
Oracle Corporation



Tom Brett wrote:
> I propose that we say:
>
> When software provides either server or client functionality for remote
> access to a specific graphical user interface, such software MUST make
> available interface element accessibility information from the server to
the
> client to be inspected by assistive technologies.
>
>
> Tom Brett
>
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
> [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Hoffman,
> Allen
> Sent: Wednesday, June 20, 2007 1:40 PM
> To: TEITAC Web/Software Subcommittee
> Subject: Re: [teitac-websoftware] Proposal remote access requirements
>
> The following are ideas and discussion items regarding accessibility
> requirements for remote access applications.
>
> Background:
>
> Currently often remote access from one system to another is implemented
> using text-based terminal emulation such as VT100, or 3270 protocols and
> clients, graphical user interfaces such as X-windows, and
> remote-desktop-protocol, and variations of each. For text-based remote
> access, scrolling text windows can be problematic for some assistive
> technologies to handle as much of that type of access was dropped when
> such technologies migrated from text-based OS(s) to graphical user
> interfaces. In graphical user interfaces such as X-windows,
> remote-desktop-protocol, etc, often assistive technologies must be
> operated on the server end, with sound being transmitted to the client.
> What is needed is that the client receives enough of the underlying
> accessibility information for each interface element from the remote end
> to pass to the assistive technology on the client end.
>
> Proposed standard:
>
> When software provides either server or client functionality for remote
> access to a specific graphical user interface, such software MUST pass
> interface element accessibility information from (proposed 21D) from the
> server to the client to then be passed to or inspected by assistive
> technologies.
>
> Note:
> I think we can exempt web browsers from this requirement as there are
> already other specific requirements for how content shall work in that
> context.
>
> I hope this is a start for discussion that we can wrap up fairly
> quickly.
> Sean, if you can comment on how RDP functions that would be
> enlightening.
> Peter, when you are back from vacation, a comment on how Gnome works
> during remote access would help.
>
>
>

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University