W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2013

RE: Virtual Buffer Refresh

From: Jonathan Avila <jon.avila@ssbbartgroup.com>
Date: Thu, 25 Apr 2013 13:31:18 -0400
Message-ID: <a9c2fe5a6dbc5410932aa7cb1bab643c@mail.gmail.com>
To: Greg Davies <GDavies@jackhenry.com>, Alastair Campbell <alastc@gmail.com>
Cc: w3c-wai-ig@w3.org
ō  within the program, at least thatís our request.

You can through the JAS scripting language.  Technically you could also
through a web page if you create a COM object with JavaScript and the JAWS
API is installed on the machine you can then call JAWS scripts and
functions from a web page using JavaScript.  We donít recommend this though
as you need the API to be installed and it would be JAWS specific.


*From:* Greg Davies [mailto:GDavies@jackhenry.com]
*Sent:* Thursday, April 25, 2013 1:25 PM
*To:* Alastair Campbell
*Cc:* w3c-wai-ig@w3.org
*Subject:* RE: Virtual Buffer Refresh

We have opened an inquiry with JAWS to explore this specific situation, but
beyond that we want a solid solution to updating the virtual buffer from
within the code.  If you can do it from the keyboard, you should be able to
do it from within the program, at least thatís our request.

Greg Davies

*From:* Alastair Campbell [mailto:alastc@gmail.com <alastc@gmail.com>]
*Sent:* Thursday, April 25, 2013 12:21 PM
*To:* Greg Davies
*Cc:* w3c-wai-ig@w3.org
*Subject:* Re: Virtual Buffer Refresh

Ah, really does sounds like a user-agent issue then. If the code *should*
work, and does in most UAs, and (icing on the cake) did work before, then
it is a JAWs issue.

Perhaps add a visually-hidden note above that section to say "If you are
using JAWs encounter issues with this section please try refreshing the
virtual buffer with INS and escape", or something like that.


NOTICE: This electronic mail message and any files transmitted with it are
exclusively for the individual or entity to which it is addressed. The
together with any attachment, may contain confidential and/or privileged
Any unauthorized review, use, printing, saving, copying, disclosure or
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
Received on Thursday, 25 April 2013 17:31:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:36:44 UTC