WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Do lack of labels for input forms affect users depending on "speech input"

for

From: Birkir R. Gunnarsson
Date: Jul 13, 2016 12:20PM

See, this is why I have a lot of faith in my hindquarters.


On 7/13/16, Lucy Greco < <EMAIL REMOVED> > wrote:
> to confurm that this only works if the lable is asosiated if it is not
> then dragon users must fall back on the mouse grid witch is painfull
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
> On Wed, Jul 13, 2016 at 11:04 AM, Birkir R. Gunnarsson <
> <EMAIL REMOVED> > wrote:
>
>> Re Dragon Naturally speaking, and I may be speaking somewhat out of my
>> hindquarters here.
>> I believe users can tell Dragon to fill in or focus on field "x" where
>> "x" is the text that appears to be the label for the field.
>>
>> If the text is programmatically designated as the label for that
>> field, I expect that process would be more likely to work.
>> Cheers
>> -Birkir
>>
>>
>> On 7/13/16, Lovely, Brian (CONT) < <EMAIL REMOVED> > wrote:
>> > ...and 5. Everybody else.
>> >
>> > It's very easy when developing to forget that you've read the specs,
>> looked
>> > at the designs, asked questions at meetings, but users have not. It's a
>> > separate skill to be able to set aside what you know and then see what
>> the
>> > available information actually tells you. ...and to remember that not
>> > everyone participates in the same culture, so not everyone understands
>> the
>> > same symbols and patterns. Is there really anything about a hamburger
>> menu
>> > that communicates its purpose? A user who is unfamiliar with the
>> > Internet
>> > may not think to click it, or may be afraid to click on things to see
>> what
>> > happens.
>> >
>> > There is no "us and them" in accessibility. (unless I've been spelling
>> > it
>> > incorrectly, which is always a possibility)
>> >
>> >
>> > Brian Lovely
>> > Digital Accessibility Team
>> > <EMAIL REMOVED>
>> >
>> >
>> >
>> > -----Original Message-----
>> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf
>> > Of Srinivasu Chakravarthula
>> > Sent: Wednesday, July 13, 2016 4:04 AM
>> > To: WebAIM Discussion List
>> > Subject: Re: [WebAIM] Do lack of labels for input forms affect users
>> > depending on "speech input"
>> >
>> > Suchuru,
>> > Did you mean users who depend on speech input such as speech recognition
>> > (dranon naturally speaking) or did you actually meant to say users who
>> > depend on speech output (meaning screen reading software such as NVDA,
>> JAWS
>> > etc.,)
>> >
>> > But in general, lack of form labels affects:
>> > 1. Blind users
>> > 2. Low vision users
>> > 3. Users with cognitive disabilities
>> > 4. Users using refreshable Braille displays 5. Elderly
>> >
>> > Hope this helps,
>> > -Srinivasu
>> >
>> > Regards,
>> >
>> > Srinivasu Chakravarthula - Twitter: http://twitter.com/CSrinivasu/
>> > Website: http://www.srinivasu.org | http://serveominclusion.com
>> >
>> > Let's create an inclusive web!
>> >
>> > Lead Accessibility Consultant, Informatica Hon. Joint Secretary, The
>> > National Association for the Blind, Karnataka Branch
>> >
>> > On Wed, Jul 13, 2016 at 12:26 PM, sucharu < <EMAIL REMOVED> >
>> > wrote:
>> >
>> >> Hi All,
>> >> Do lack of labels for input forms affect users depending on speech
>> >> input for their interaction.
>> >> As per WCAG ,
>> >> 1. screen reader users
>> >> 2. low vision/ people with motor impairments get affected.
>> >> Are thereany other disabilities' groups those get affected?
>> >> Best,
>> >> Sucharu
>> >>
>> >> -----Original Message-----
>> >> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> >> Behalf Of Jonathan Cohn
>> >> Sent: Tuesday, July 12, 2016 10:31 PM
>> >> To: WebAIM Discussion List
>> >> Subject: Re: [WebAIM] How JAWS provides labels for unlabelled forms in
>> >> some scenario's
>> >>
>> >> While you are correct that in applications that have accessibility
>> >> designed correctly, there is an Accessibility Label for any graphical
>> >> items of significance to the user.
>> >>
>> >> Beyond the UIA/MSAA/HTML labels used to describe graphics, JAWS can
>> >> In Excel charts glean the information in the chart by querying the
>> >> Chart object, in applications with static graphics, JAWS creates or
>> >> finds a graphic Id that is a number. It is not clear if this Graphic
>> >> ID is based on a hashing of the underlying digital information in the
>> >> graphic, or if it is somehow associated with information within the
>> >> Windows OS. In any case, one can associate individual graphic IDs with
>> >> a text label in the "jcf" file for a specific application. There is a
>> >> JAWS shortcut insert-G that will label the graphic under the mouse when
>> >> you have the JAWS cursor enabled.
>> >> Best Wishes,
>> >>
>> >>
>> >> Jonathan Cohn
>> >>
>> >>
>> >> On 12 July 2016 at 08:57, Birkir R. Gunnarsson <
>> >> <EMAIL REMOVED> >
>> >> wrote:
>> >>
>> >> > I don't think there is anything public about how screen readers
>> >> > guess form field labels (and they should never have to).
>> >> > There are fairly simple things, such as Jaws will likely speak any
>> >> > text that is inside same container as the form field, especially
>> >> > text that preceeds it.
>> >> > In general screen readers will look for text around the form field
>> >> > and announce it.
>> >> > If form field is laid out in a two-colum table with the form field
>> >> > in the second column, Jaws will read the value in the first column
>> >> > of same row as the formfield's label.
>> >> > You can play around with different placements in HTML and figure out
>> >> > what screen readers will do.
>> >> > While it is a somewaht interesting exercise I wouldn't spend too
>> >> > much time on it, since the whole point is that authors should assign
>> >> > the labels explicitly, otherwise the screen readers will all guess,
>> >> > and they will inevitably get it wrong some of the time.
>> >> > -B
>> >> >
>> >> >
>> >> > On 7/12/16, sucharu < <EMAIL REMOVED> > wrote:
>> >> > > Dear All,
>> >> > >
>> >> > > I wish to learn about
>> >> > >
>> >> > > 'how JAWS provides labels for some unlabeled forms in some
>> >> > > situations'.I wish to learn about algorithms that JAWS run in
>> >> > > order to
>> >> meet this.
>> >> > >
>> >> > > Best,
>> >> > >
>> >> > > Sucharu
>> >> > >
>> >> > > >> >> > > >> >> > > archives at http://webaim.org/discussion/archives
>> >> > > >> >> > >
>> >> >
>> >> >
>> >> > --
>> >> > Work hard. Have fun. Make history.
>> >> > >> >> > >> >> > archives at http://webaim.org/discussion/archives
>> >> > >> >> >
>> >> >> >> >> >> archives at http://webaim.org/discussion/archives
>> >> >> >>
>> >> >> >> >> >> archives at http://webaim.org/discussion/archives
>> >> >> >>
>> > >> > >> archives at
>> > http://webaim.org/discussion/archives
>> > >> > >> >
>> > The information contained in this e-mail is confidential and/or
>> proprietary
>> > to Capital One and/or its affiliates and may only be used solely in
>> > performance of work or services for Capital One. The information
>> transmitted
>> > herewith is intended only for use by the individual or entity to which
>> it is
>> > addressed. If the reader of this message is not the intended recipient,
>> you
>> > are hereby notified that any review, retransmission, dissemination,
>> > distribution, copying or other use of, or taking of any action in
>> reliance
>> > upon this information is strictly prohibited. If you have received this
>> > communication in error, please contact the sender and delete the
>> > material
>> > from your computer.
>> > >> > >> > >> > >> >
>>
>>
>> --
>> Work hard. Have fun. Make history.
>> >> >> >> >>
> > > > >


--
Work hard. Have fun. Make history.