WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: edit digits with spellcheck

for

Number of posts in this thread: 4 (In chronological order)

From: Sean Murphy
Date: Wed, Apr 20 2016 12:02AM
Subject: edit digits with spellcheck
No previous message | Next message →

All,

What is people’s experience with rich edit widget’s that allows rich content to be added to a page. I was reviewing a page where they permitted spell checking. This used the MSWord marking functionality. The screen reader using IE11 didn’t detect the misspelled word.

Is the responsibility of accessibility lies on the developer of the widget, the browser or a combination? If so, should aria be be used here? Since ARIA only tells the screen reader the role and state. What about methods within the object (element)?

Sean

From: Jonathan Avila
Date: Mon, Apr 25 2016 7:17PM
Subject: Re: edit digits with spellcheck
← Previous message | Next message →

> What is people’s experience with rich edit widget’s that allows rich content to be added to a page. I was reviewing a page where they permitted spell checking. This used the MSWord marking functionality. The screen reader using IE11 didn’t detect the misspelled word.

In my experience there is not a sufficient text API to communicate information such like there is with for the desktop MS Word, Java Accessibility, etc. Some organizations such as Microsoft and Google have tried to solve around the problem with interesting hacks that sometimes work for rich editing but don't fully address the problem. So while technically it falls under the person procuring or the product or the vendor it is a larger issue that in my opinion must be solved by the community with standards. Perhaps there is someone on the list who has more information about such work.

Jonathan

Jonathan Avila
Chief Accessibility Officer
SSB BART Group 
= EMAIL ADDRESS REMOVED =
703.637.8957 (Office)

Visit us online: Website | Twitter | Facebook | Linkedin | Blog
Check out our Digital Accessibility Webinars!


-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Murphy
Sent: Wednesday, April 20, 2016 2:02 AM
To: WebAIM Discussion List
Subject: [WebAIM] edit digits with spellcheck

All,

What is people’s experience with rich edit widget’s that allows rich content to be added to a page. I was reviewing a page where they permitted spell checking. This used the MSWord marking functionality. The screen reader using IE11 didn’t detect the misspelled word.

Is the responsibility of accessibility lies on the developer of the widget, the browser or a combination? If so, should aria be be used here? Since ARIA only tells the screen reader the role and state. What about methods within the object (element)?

Sean

From: Brian Lovely
Date: Wed, Apr 27 2016 6:28PM
Subject: Re: edit digits with spellcheck
← Previous message | Next message →

It must be difficult to expose all the elements and relationships of a WYSIWYG editor to assistive technology, let alone the results of a spell check. Role=alert could be used in this way, similarly to how it is used to indicate invalid form input. If someone is typing quickly enough (and making enough errors), automatic spell checking could generate multiple alerts that would then have to be negotiated one at a time, presumably by tabbing.

Does anyone know how the user would be alerted to a number of alerts occurring in a short span of time? Being I Mac user, I can test this in VoiceOver, but am curious if anyone has had experience with this.


Brian Lovely
= EMAIL ADDRESS REMOVED =



> On Apr 25, 2016, at 9:17 PM, Jonathan Avila < = EMAIL ADDRESS REMOVED = > wrote:
>
>> What is people’s experience with rich edit widget’s that allows rich content to be added to a page. I was reviewing a page where they permitted spell checking. This used the MSWord marking functionality. The screen reader using IE11 didn’t detect the misspelled word.
>
> In my experience there is not a sufficient text API to communicate information such like there is with for the desktop MS Word, Java Accessibility, etc. Some organizations such as Microsoft and Google have tried to solve around the problem with interesting hacks that sometimes work for rich editing but don't fully address the problem. So while technically it falls under the person procuring or the product or the vendor it is a larger issue that in my opinion must be solved by the community with standards. Perhaps there is someone on the list who has more information about such work.
>
> Jonathan
>
> Jonathan Avila
> Chief Accessibility Officer
> SSB BART Group
> = EMAIL ADDRESS REMOVED =
> 703.637.8957 (Office)
>
> Visit us online: Website | Twitter | Facebook | Linkedin | Blog
> Check out our Digital Accessibility Webinars!
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Sean Murphy
> Sent: Wednesday, April 20, 2016 2:02 AM
> To: WebAIM Discussion List
> Subject: [WebAIM] edit digits with spellcheck
>
> All,
>
> What is people’s experience with rich edit widget’s that allows rich content to be added to a page. I was reviewing a page where they permitted spell checking. This used the MSWord marking functionality. The screen reader using IE11 didn’t detect the misspelled word.
>
> Is the responsibility of accessibility lies on the developer of the widget, the browser or a combination? If so, should aria be be used here? Since ARIA only tells the screen reader the role and state. What about methods within the object (element)?
>
> Sean
> > > > > > >

From: Graham Armfield
Date: Thu, Apr 28 2016 2:41AM
Subject: Re: edit digits with spellcheck
← Previous message | No next message

​On Thu, Apr 28, 2016 at 1:28 AM, Brian Lovely wrote:

>
> Does anyone know how the user would be alerted to a number of alerts
> occurring in a short span of time? Being I Mac user, I can test this in
> VoiceOver, but am curious if anyone has had experience with this.
>

​I have some experience from a client who had client side validation in a
form that inserted an error message after every field that did not
validate. Each of these individual messages was marked up as role="alert".

The results whenever there was more than one error were disappointing -
when using NVDA with Firefox, and Voiceover on an iPad. Occasionally one of
the messages (possibly the first?) got read out partially or completely,
but most often nothing at all was voiced. It seems that multiple 'firings'
in a short space of time just confused the screen reader.

From this I would take that it's desirable to only have one role="alert" on
a page, or if multiple locations are unavoidable, to have some way to
ensure that only one gets 'fired' at any one time.

Regards
Graham Armfield
Coolfields Consulting