Re: Seeking user and developer feedback on ARIA live region technology before redesign

Ok, we'll know for next time. TBH this was not intentional. We talk to
Microsoft a lot because we share the same codebase, and I wanted them to
get actual dev/user feedback before they started on a design or prototype.
Previously, when Travis Leithead was working on this project, they were
going to go ahead with a design and prototype without gathering that info
at all. So, somehow in the process of being more open, we look less open!

On Mon, Apr 3, 2023 at 2:51 PM James Craig <jcraig@apple.com> wrote:

> It’s unfortunate that the survey ended up as a Microsoft-specific site,
> since it’d be more difficult for the ARIA group to promote as a
> collaborative effort, than if it had been a W3C survey.
>
>
> On Apr 3, 2023, at 11:44 AM, Aaron Leventhal <aleventhal@google.com>
> wrote:
>
> And just to clarify, this is a standards initiative, despite it mentioning
> specific vendors. Ideas and participation from all parties is only a plus,
> obviously .... nobody wants to come back for Live Regions 3.0 in 10 years!
>
> On Mon, Apr 3, 2023 at 2:05 PM Aaron Leventhal <aleventhal@google.com>
> wrote:
>
>> Hi all, the Google Chrome team is working together with Microsoft to try
>> to create a new standard currently called ariaNotify, which we hope will
>> solve some of the issues with ARIA live regions. We realized it would be
>> best to first get user and developer feedback on use cases, pain points,
>> etc. so that we solve the actual problems out there. If you love or hate
>> live regions, we want to hear from you!
>>
>> Developer feedback about Live Regions <http://aka.ms/LiveRegionDevSurvey>
>>
>> Technical screen reader feedback about Live Regions
>> <http://aka.ms/LiveRegionScreenReaderSurvey>
>>
>>
>>
>> These surveys are open to anyone—feel free to forward around to people
>> that might be interested.
>>
>>
>> Thanks for your time and encouragement!
>>
>>
>> Aaron
>>
>
>