W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2016

RE: order of events

From: Sean Murphy (seanmmur) <seanmmur@cisco.com>
Date: Tue, 6 Dec 2016 00:48:19 +0000
To: Adam Cooper <cooperad@bigpond.com>, "'WAI Interest Group'" <w3c-wai-ig@w3.org>
Message-ID: <3c9be606cd0a41eab897c40330cf170c@XCH-RCD-001.cisco.com>

There is a tool by TPG called Aviewer which might help with your query.

Sean Murphy
Accessibility Software engineer
Tel: +61 2 8446 7751       Cisco Systems, Inc.
The Forum 201 Pacific Highway
 Think before you print.
This email may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply email and delete all copies of this message.

From: Adam Cooper [mailto:cooperad@bigpond.com]
Sent: Monday, 5 December 2016 8:25 PM
To: 'WAI Interest Group' <w3c-wai-ig@w3.org>
Subject: order of events

Hi everyone,

I'm trying to make the firing of a simple HTML success message reliable cross browser/cross screen reader using toastr.js.

It's in the context of a really lumpy CRM product in which script execution/network performance/event timings/redundant post requests are influential on whether screen readers announce the insertion of a text node within a <div> with aria-live='assertive' and role='alert'.

Is there anything out there that specifies what order these 'event's fire in or defines a contract between DOM + accessibility API + screen reader etc.? Thus far, I have 3 different behaviours across 5 versions of a popular screen reader  ...

This email has been scanned by BullGuard antivirus protection.
For more info visit www.bullguard.com<http://www.bullguard.com/tracking.aspx?affiliate=bullguard&buyaffiliate=smtp&url=/>
Received on Tuesday, 6 December 2016 00:49:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:37:01 UTC