E-mail List Archives
Thread: Read only Inputs and screen readers
Number of posts in this thread: 3 (In chronological order)
From: Nancy Johnson
Date: Thu, Feb 06 2014 11:54AM
Subject: Read only Inputs and screen readers
No previous message | Next message →
How does a screen reader handle readonly modes for inputs?
Thanks
Nancy
From: Don Mauck
Date: Thu, Feb 06 2014 11:57AM
Subject: Re: Read only Inputs and screen readers
← Previous message | Next message →
Depends on whether they are in a table or just stand alone. If in a table you can use table reading commands to read, if however, it is stand alone text, you would need to use the arrow keys to find and read it. It is always more of a challenge if there is no HTML headings or some other way of at least getting to the right area of the read only text.
-----Original Message-----
From: Nancy Johnson [mailto: = EMAIL ADDRESS REMOVED = ]
Sent: Thursday, February 06, 2014 11:54 AM
To: WebAIM Discussion List
Subject: [WebAIM] Read only Inputs and screen readers
How does a screen reader handle readonly modes for inputs?
Thanks
Nancy
From: Patrick H. Lauke
Date: Thu, Feb 06 2014 12:01PM
Subject: Re: Read only Inputs and screen readers
← Previous message | No next message
On 06/02/2014 18:54, Nancy Johnson wrote:
> How does a screen reader handle readonly modes for inputs?
Generally, they will let users TAB to them as with normal focusable form
controls (as opposed to inputs/controls that are disabled, rather than
readonly, which DON'T receive focus), will announce the label/value, but
also announce that it's a read-only input.
P
--
Patrick H. Lauke
re·dux (adj.): brought back; returned. used postpositively
[latin : re-, re- + dux, leader; see duke.]
www.splintered.co.uk | www.photographia.co.uk
http://redux.deviantart.com | http://flickr.com/photos/redux/
twitter: @patrick_h_lauke | skype: patrick_h_lauke