WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Readonly Field Problem with IE 11 and JAWS 16

for

From: Andrew Normand
Date: Oct 25, 2015 5:11PM

Disabled radio buttons and check boxes, that are selected, are not identified correctly when using NVDA + IE11.

NVDA + FF and NVDA + Chrome read the disabled fields correctly. JAWS also reads them out correctly when using IE11, FF and Chrome.

You can try it for yourself here:
http://www.unimelb.edu.au/accessibility/testing/disabled.html

NVDA developers are aware of the issue: "As if there weren't enough stupid bugs in IE's accessibility implementation, IE doesn't expose the fact that radio buttons or check boxes are checked via accessibility APIs when they are disabled." See: http://community.nvda-project.org/ticket/3674


Andrew Normand  
Web Accessibility Lead
The University of Melbourne
T: +61 3 9035 4867   E:  <EMAIL REMOVED>   
unimelb.edu.au/accessibility



-----Original Message-----
From: Birkir R. Gunnarsson [mailto: <EMAIL REMOVED> ]
Sent: Sunday, 25 October 2015 9:42 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Readonly Field Problem with IE 11 and JAWS 16

If, for some reason, you find bugs with the html readonly attribute, you could mark the fields using aria-readonly="true" but that means you have to visually indicate its read-only state, and use Javascript to ensure user cannot type into the field.
Basically a lot of extra work to achieve same functionality.




On 10/23/15, Moore,Michael (Accessibility) (HHSC) < <EMAIL REMOVED> > wrote:
> Thanks,
>
> I was leaning toward treating this as a problem on our side. We are
> also getting keyboard traps in edit fields in FF. Something appears to
> be wrong with some of our scripting.
>
> Mike Moore
> Accessibility Coordinator
> Texas Health and Human Services Commission Civil Rights Office
> (512) 438-3431 (Office)
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Sailesh Panchang
> Sent: Friday, October 23, 2015 1:54 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] Readonly Field Problem with IE 11 and JAWS 16
>
> I do not experience what you do. Maybe there is a coding problem in
> your page?
> The following code works fine in forms / non-forms mode.
> I tried it with NVDA too.
> <p><label>Account# (implicit label):<input type="text" readonly
> name="accName1" id="accName1" value="2421223259" /></label></p>
> <p><label for="accName2">Account#:</label> <input type="text" readonly name="accName2"
> id="accName2" value="2421223259" /></p>
>
> IE 11.0.960
> JFW 16.0.4463
>
> Regards and best wishes
>
> Sailesh Panchang
>
>
> On 10/23/15, Moore,Michael (Accessibility) (HHSC)
> < <EMAIL REMOVED> > wrote:
>> Help!
>>
>> I am testing an application where some fields are presented as
>> readonly. The problem that we are finding is that for the readonly
>> field in IE 11 if you are using reading commands the label is read
>> but the field is skipped, the field does not show up in a form field
>> list either but it is included in the tab ring. When you tab to it
>> the value is not reported and the label is reported as the label of
>> the next field of the form.
>>
>> If I review the page with either FF or Chrome (latest release) then
>> the readonly field is reported correctly by JAWS.
>>
>> This application is in a development environment and I cannot share a
>> URL.
>>
>> Is this a known bug in IE 11?
>>
>> Mike Moore
>> Accessibility Coordinator
>> Texas Health and Human Services Commission Civil Rights Office
>> (512) 438-3431 (Office)
>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >>
> > > archives at http://webaim.org/discussion/archives
> > > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.