WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: role="alert" not being read on page load

for

From: Isabel Holdsworth
Date: Jun 14, 2019 8:36AM

Hi Joseph,

> If we put the error messages after h1 and h2 and some instructions, should we set focus to the error message div on page load?

No. If you do that, then you're moving the focus past some important
instructions that the user presumably needs to read, and screenreader
users may never move back up the DOM and so may never read your
instructions.

If you position the error just after the H1, blind users will find it
straight away. If you hide it further down in the page, they may not.

The fact that an error has occurred is surely the most important
information on the page. If you don't make it prominent, other users
might miss it too. For example, if the page is zoomed up so the text
is quite large, say twice its normal size, is the error still in the
viewport?

Cheers, Isabel

On 14/06/2019, Joseph Sherman < <EMAIL REMOVED> > wrote:
> If we put the error messages after h1 and h2 and some instructions, should
> we set focus to the error message div on page load?
>
>
>
> Joseph
>
> -----Original Message-----
> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
> Isabel Holdsworth
> Sent: Friday, June 14, 2019 4:03 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] role="alert" not being read on page load
>
> Hi Joseph,
>
> This error doesn't need to be an alert, so long as it's positioned somewhere
> in the DOM where it can be easily found, for example just after the page's
> H1 heading.
>
> It would also be helpful to mention in the window title and H1 heading that
> there's an error.
>
> Cheers, Isabel
>
> On 13/06/2019, Bryan Garaventa < <EMAIL REMOVED> > wrote:
>> Hi,
>> ARIA live regions are only meant to fire new content events when
>> content is dynamically added to them, so it's not surprising that
>> nothing is occurring when this is added to a static webpage like this.
>>
>> This is described in the section 3.5.4: Live Region Caveats,
>> http://whatsock.com/training/#hd28
>>
>> This training document was written when ARIA 1.0 was the primary
>> reference, however the guidance here is still valid even with 1.1. I
>> plan to update the reference urls and related sections in the future
>> as 1.1 and 1.2 changes are resolved.
>>
>> All the best,
>> Bryan
>>
>>
>> Bryan Garaventa
>> Principal Accessibility Architect
>> Level Access, Inc.
>> <EMAIL REMOVED>
>> 415.624.2709 (o)
>> www.LevelAccess.com
>>
>> -----Original Message-----
>> From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of
>> Joseph Sherman
>> Sent: Thursday, June 13, 2019 1:26 PM
>> To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
>> Subject: [WebAIM] role="alert" not being read on page load
>>
>> CAUTION: This email originated from outside of the organization. Do
>> not click links or open attachments unless you recognize the sender
>> and know the content is safe.
>>
>>
>> Hello. I have a form where after the user submits incorrect
>> information, the page refreshes with an error message with
>> role="alert". However I find the error text is not being read in
>> FireFox with JAWS or NVDA. Code below. Are we doing something wrong?
>>
>> <div role="alert" class="alert alert-error alert-danger"> <ul><li>More
>> than one user was found that matches the information you provided.
>> Please contact your college support team and tell them you received
>> this error.</li></ul></div>
>>
>>
>>
>> Joseph
>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >> >> >> archives at http://webaim.org/discussion/archives
>> >>
> > > http://webaim.org/discussion/archives
> > > > > >