Thread Subject: Re: Proposal remote access requirements
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.
There are two ways we can make a remote desktop session accessible through
AT to a local workstation:
1. Run the AT remotely as well
2. Run the AT locally, and have it communicate accessibility information
with the remote app
I think we need standard language that recognizes at least these two ways
of solving this problem, and allows an implementation of either one to be
acceptable for meeting the standard.
<end of Peter's comments>
This kind of feels like an applicability issue to me. Remote access
software needs to pay attention to the AT interoperability provision we
already have and make sure it works, end to end, in the remote access
scenario. But, as Peter points out, we don't need to prescribe how this is
How about if we add a note to the AT Interoperability provision (3-U) or
include something in the expanatory material? Something like:
Note: Software that provides remote access to graphical user interfaces
(GUIs) must ensure that AT has access to the information required by this
provision. There are two known ways to accomplish this: run the AT remotely
as well or run the AT locally and provide a mechanism for it to communicate
accessibility information with the remote GUI.
Does this address the issue?