RE: order of events

Thanks Charles – much appreciated. Making simple things accessible cross-user agent  is all that much harder when key pieces of the jigsaw are obscured from view  … … 

 

 

 

 

From: chaals@yandex-team.ru [mailto:chaals@yandex-team.ru] 
Sent: Tuesday, December 06, 2016 9:22 PM
To: Sean Murphy (seanmmur); Adam Cooper; 'WAI Interest Group'
Subject: Re: order of events

 

But the likely answer to your root question - is this defined somewhere - might well be "No :(".

 

It's a job the Web Platform group could well be tasked to take on - and indeed there are bits of work trying to sort some of that out, e.g. within the work on editing.

 

I'll ping a couple of people who might know this more closely than me and see what I can find out.

 

cheers

 

06.12.2016, 01:56, "Sean Murphy (seanmmur)" <seanmmur@cisco.com>:

Adam,

 

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

 

Sean Murphy

Accessibility Software engineer 

seanmmur@cisco.com

Tel: +61 2 8446 7751       Cisco Systems, Inc.

The Forum 201 Pacific Highway

ST LEONARDS

2065

Australia

cisco.com            

 

 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=/> 

 

 

-- 

Charles McCathie Nevile - standards - Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com

 


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=/>