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: Wed, 24 Apr 2013 18:53:49 -0400
Message-ID: <23c52cf323943ed9456c9d7939bcc9c4@mail.gmail.com>
To: Greg Davies <GDavies@jackhenry.com>, w3c-wai-ig@w3.org
> .  The issue I am having is once the postback is complete, the screen
reader announces every subsequent input type as the same type as the
control that changed originally to effect the postback.

One thing that I have learned from working with AT vendors is that
controls should never change roles.  For example, a control that was a
button should not become a checkbox.  AT and perhaps accessibility APIs do
not handle that situation well.  I am not sure if that is what is
occurring in your situation or not.

Jonathan

-----Original Message-----
From: Greg Davies [mailto:GDavies@jackhenry.com]
Sent: Wednesday, April 24, 2013 6:41 PM
To: Jonathan Avila; w3c-wai-ig@w3.org
Subject: RE: Virtual Buffer Refresh

Unfortunately I have already tried using the role="region"
aria-live="polite" and even added aria-atomic="true" with only limited
success.  The issue I am having is once the postback is complete, the
screen reader announces every subsequent input type as the same type as
the control that changed originally to effect the postback.  If I do a
"hard" refresh of the buffer from the keyboard (ins+esc) everything is
fine.  I was hoping there was some way I could do a hard refresh using
javascript or some combination of aria tags.

Greg Davies

-----Original Message-----
From: Jonathan Avila [mailto:jon.avila@ssbbartgroup.com]
Sent: Wednesday, April 24, 2013 2:14 PM
To: Greg Davies; w3c-wai-ig@w3.org
Subject: RE: Virtual Buffer Refresh

> Does anyone have a way of refreshing the virtual buffer through either
ARIA tags, or javascript.  I can force a refresh

Use of aria-live regions or certain roles that are implicit live regions
should work with ARIA supported assistive technologies and browsers.
Freedom Scientific also produced a tech support notice many years ago that
listed many possible techniques.

Some of the techniques are listed on webAccessibility.com and include
changing values in hidden input fields, removing and adding nodes in the
DOM, and changing attributes on elements.

https://www.webaccessibility.com/best_practices.php?best_practice_id=968

Adding and removing nodes in the DOM is likely the best method.

Jonathan

-----Original Message-----
From: Greg Davies [mailto:GDavies@jackhenry.com]
Sent: Wednesday, April 24, 2013 2:56 PM
To: w3c-wai-ig@w3.org
Subject: Virtual Buffer Refresh

Everyone,

Does anyone have a way of refreshing the virtual buffer through either
ARIA tags, or javascript.  I can force a refresh from the keyboard and
that clears up the problem  but I have not been able to force a refresh
through code.  I have tried aria-live but that solution is only partially
successful.  Thank you in advance.

Greg Davies
NOTICE: This electronic mail message and any files transmitted with it are
intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution is strictly prohibited. If you have received this message in
error, please immediately advise the sender by reply email and delete all
copies.
NOTICE: This electronic mail message and any files transmitted with it are
intended exclusively for the individual or entity to which it is
addressed. The message, together with any attachment, may contain
confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or
distribution 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 Wednesday, 24 April 2013 22:54:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:48 UTC