Re: [orca-list] Is this an Orca bug?

[Mallory <stommepoes stommepoes nl>]

Live regions need to exist before changes happen, yeah.

That is, the Vue folks should start with an empty container on page load, and fill with text dynamically for 
that first message. If instead they're creating the container at the same time as the message, no browser 
should be announcing that for any screen readers.

cheers,
_mallory

On Tue, May 7, 2019, at 3:11 PM, Nolan Darilek wrote:
> Hey folks,
>
>
> I'm working on a web app that uses Bootstrap-Vue. The Bootstrap-Vue 
> folks try hard to do accessibility right, but sometimes they mess up, 
> and I'm not sure if this is one of those instances.
>
>
> They have a toast component that displays popup notifications. The 
> notifications use ARIA attributes,and there's a mechanism to dynamically 
> make toasts appear, but that mechanism only reads any toasts subsequent 
> to the first. So I'm wondering if the first toast appears with an ARIA 
> live region and isn't read because it appears out of nowhere, and 
> subsequent updates read fine because they're updating an existing region?
>
>
> To see what I mean, visit 
> https://bootstrap-vue.js.org/docs/components/toast/ and navigate to the 
> demo under the "Toasts on demand" header and click the "Show toast" 
> button. The first click speaks nothing, while the second click speaks 
> both the current and previous toast.
>
>
> If they're doing something wrong here, please let me know and I'll 
> submit a PR. Thanks!
>
> _______________________________________________
> orca-list mailing list
> orca-list gnome org
> https://mail.gnome.org/mailman/listinfo/orca-list
> Orca wiki: https://wiki.gnome.org/Projects/Orca
> Orca documentation: https://help.gnome.org/users/orca/stable/
> GNOME Universal Access guide: 
> https://help.gnome.org/users/gnome-help/stable/a11y.html
> Log bugs and feature requests at http://bugzilla.gnome.org