E-mail List Archives

Search E-mail List Archives for

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

From: sucharu
Date: Wed, Jul 13 2016 12:56AM
Subject: Do lack of labels for input forms affect users depending on "speech input"
No previous message | Next message →

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

From: Srinivasu Chakravarthula
Date: Wed, Jul 13 2016 2:04AM
Subject: Re: Do lack of labels for input forms affect users depending on "speech input"
← Previous message | Next message →

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 ADDRESS 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
>
>

From: Lovely, Brian (CONT)
Date: Wed, Jul 13 2016 6:52AM
Subject: Re: Do lack of labels for input forms affect users depending on "speech input"
← Previous message | Next message →

...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 ADDRESS REMOVED =

From: Birkir R. Gunnarsson
Date: Wed, Jul 13 2016 12:04PM
Subject: Re: Do lack of labels for input forms affect users depending on "speech input"
← Previous message | Next message →

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 ADDRESS 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 ADDRESS REMOVED =
>
>
>
>

From: Lucy Greco
Date: Wed, Jul 13 2016 12:17PM
Subject: Re: Do lack of labels for input forms affect users depending on "speech input"
← Previous message | Next message →

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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED =
> >
> >
> >
> >

From: Birkir R. Gunnarsson
Date: Wed, Jul 13 2016 12:20PM
Subject: Re: Do lack of labels for input forms affect users depending on "speech input"
← Previous message | Next message →

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


On 7/13/16, Lucy Greco < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED =
>> >
>> >
>> >
>> >

From: Marc Solomon
Date: Wed, Jul 13 2016 12:33PM
Subject: Re: Do lack of labels for input forms affect users depending on "speech input"
← Previous message | Next message →

In my experience, the user can also say "click" followed by an input type (e.g. text field, check box, etc.). Dragon will then number all of the controls with that role on the page. The user can then say "choose 1" or "choose 2". This technique is not as efficient as saying "click <label>" to focus a form field directly. But, it should be more efficient than using the mouse grid.
HTH,
Marc

From: sucharu
Date: Thu, Jul 14 2016 4:50AM
Subject: Re: Do lack of labels for input forms affect users depending on "speech input"
← Previous message | Next message →

Hello All,
I wish to learn whether Jaws has a role in making flash accessible as I experience NVDA crashes with flash player more often as compared to JAWS.

From: _mallory
Date: Thu, Jul 14 2016 12:18PM
Subject: Re: Do lack of labels for input forms affect users depending on "speech input"
← Previous message | No next message

Also at times I've set focus on a focusable before the unreachable and
tell it to "click tab" as well.
_mallory
On Wed, Jul 13, 2016 at 06:33:57PM +0000, Marc Solomon wrote:
> In my experience, the user can also say "click" followed by an input type (e.g. text field, check box, etc.). Dragon will then number all of the controls with that role on the page. The user can then say "choose 1" or "choose 2". This technique is not as efficient as saying "click <label>" to focus a form field directly. But, it should be more efficient than using the mouse grid.
> HTH,
> Marc