E-mail List Archives

Search E-mail List Archives for

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

From: Jennifer Sutton
Date: Mon, Apr 25 2016 4:02PM
Subject: search-submit button -- required or not
No previous message | Next message →

Greetings, WebAIM folks:

What's the current thinking regarding whether a search "submit" button
is required? Is there a specific Success Criterion that should be cited?

I'm wondering about this because, increasingly, I'm seeing search edit
boxes that are activated by simply using the enter key.

Is this practice becoming accepted/known?

How do folks who use text-input, such as Dragon Naturally Speaking,
handle the lack of a button (with a name to speak)?

Though it is not relevant to the particular use case I'm currently
looking at, I also find myself thinking about the kinds of search
mechanisms that autocomplete/suggest, as you type. These typically, as
far as I recall, do not have "submit" buttons. I guess the idea with
them is that once you stop typing, you've essentially "submitted." But I
bring these search-suggestion mechanisms up because I wonder if they're
contributing to the perception that "submit" buttons are no longer
necessary for searches (whether or not suggestions are offered).

In the end, I want to be sure I'm clear about whether the lack of a
search submission button is a WCAG 2.0 issue, considered to be a general
usability issue (for people with disabilities and/or people without), or
both?

Thank you.

Best,
Jennifer

From: Snahendu Bhattacharya
Date: Mon, Apr 25 2016 4:10PM
Subject: Re: search-submit button -- required or not
← Previous message | Next message →

Hi Jennifer!

I agree with your observation and had a similar thought too.

Just trying to think other perspective like the user who doesn't have
keyboard to press enter (Mobile users or other AT users)

I thought both should be present. If a user is *not able* to press ENTER
should be able to perform the same action.

Let's see what others think about this.
On Apr 25, 2016 6:02 PM, "Jennifer Sutton" < = EMAIL ADDRESS REMOVED = > wrote:

> Greetings, WebAIM folks:
>
> What's the current thinking regarding whether a search "submit" button is
> required? Is there a specific Success Criterion that should be cited?
>
> I'm wondering about this because, increasingly, I'm seeing search edit
> boxes that are activated by simply using the enter key.
>
> Is this practice becoming accepted/known?
>
> How do folks who use text-input, such as Dragon Naturally Speaking, handle
> the lack of a button (with a name to speak)?
>
> Though it is not relevant to the particular use case I'm currently looking
> at, I also find myself thinking about the kinds of search mechanisms that
> autocomplete/suggest, as you type. These typically, as far as I recall, do
> not have "submit" buttons. I guess the idea with them is that once you stop
> typing, you've essentially "submitted." But I bring these search-suggestion
> mechanisms up because I wonder if they're contributing to the perception
> that "submit" buttons are no longer necessary for searches (whether or not
> suggestions are offered).
>
> In the end, I want to be sure I'm clear about whether the lack of a search
> submission button is a WCAG 2.0 issue, considered to be a general usability
> issue (for people with disabilities and/or people without), or both?
>
> Thank you.
>
> Best,
> Jennifer
> > > > >

From: Birkir R. Gunnarsson
Date: Mon, Apr 25 2016 4:38PM
Subject: Re: search-submit button -- required or not
← Previous message | Next message →

I have called this as a 2.1.1 best practice/usability/minor violation
under 2.1.1 on responsive sites, where I have been asked to audit the
responsive version.
The mobile onscreen keyboard (at least on iOS) has a "go" button which
simulates the enter key behavior.
This becomes an actual 2.1.1 issue for pop-up modal dialogs that
require the escape key to close them (because mobile devices -- at
least iOS -- have no escape key on keyboard and the scrub gesture does
not produce the escape key behavior).
See
http://whenpush.a11yideas.com (the welcome message intro), this is the
html example me and my colleagues wrote for a mobile presentation on
the other thing you asked about, autocomplete searches.



On 4/25/16, Snahendu Bhattacharya < = EMAIL ADDRESS REMOVED = > wrote:
> Hi Jennifer!
>
> I agree with your observation and had a similar thought too.
>
> Just trying to think other perspective like the user who doesn't have
> keyboard to press enter (Mobile users or other AT users)
>
> I thought both should be present. If a user is *not able* to press ENTER
> should be able to perform the same action.
>
> Let's see what others think about this.
> On Apr 25, 2016 6:02 PM, "Jennifer Sutton" < = EMAIL ADDRESS REMOVED = > wrote:
>
>> Greetings, WebAIM folks:
>>
>> What's the current thinking regarding whether a search "submit" button is
>> required? Is there a specific Success Criterion that should be cited?
>>
>> I'm wondering about this because, increasingly, I'm seeing search edit
>> boxes that are activated by simply using the enter key.
>>
>> Is this practice becoming accepted/known?
>>
>> How do folks who use text-input, such as Dragon Naturally Speaking, handle
>> the lack of a button (with a name to speak)?
>>
>> Though it is not relevant to the particular use case I'm currently looking
>> at, I also find myself thinking about the kinds of search mechanisms that
>> autocomplete/suggest, as you type. These typically, as far as I recall, do
>> not have "submit" buttons. I guess the idea with them is that once you
>> stop
>> typing, you've essentially "submitted." But I bring these
>> search-suggestion
>> mechanisms up because I wonder if they're contributing to the perception
>> that "submit" buttons are no longer necessary for searches (whether or not
>> suggestions are offered).
>>
>> In the end, I want to be sure I'm clear about whether the lack of a search
>> submission button is a WCAG 2.0 issue, considered to be a general
>> usability
>> issue (for people with disabilities and/or people without), or both?
>>
>> Thank you.
>>
>> Best,
>> Jennifer
>> >> >> >> >>
> > > > >


--
Work hard. Have fun. Make history.

From: Maxability Accessibility for all
Date: Mon, Apr 25 2016 7:17PM
Subject: Re: search-submit button -- required or not
← Previous message | Next message →

I second you Birkir and I had similar experience what Snahendu had. I don't
remember the version of IOS I was testing few years back but the Go button
was missing in the virtual keyboard. In this case it was extremely
difficult to do the search functionality depending on the native properties
of the operating system. especially with the wide variety of mobile OS's
launching in the market and because they are customized by the mobile
manufacturers.
This will be a definite 2.1.1 violation in my opinion too but the impact
depends on the conditions the assessment is done. The conditions I mean are
responsive/ mobile web , devices in scope, OS and their versions in scope
etc.

Thanks & Regards
Rakesh

On Tue, Apr 26, 2016 at 4:08 AM, Birkir R. Gunnarsson <
= EMAIL ADDRESS REMOVED = > wrote:

> I have called this as a 2.1.1 best practice/usability/minor violation
> under 2.1.1 on responsive sites, where I have been asked to audit the
> responsive version.
> The mobile onscreen keyboard (at least on iOS) has a "go" button which
> simulates the enter key behavior.
> This becomes an actual 2.1.1 issue for pop-up modal dialogs that
> require the escape key to close them (because mobile devices -- at
> least iOS -- have no escape key on keyboard and the scrub gesture does
> not produce the escape key behavior).
> See
> http://whenpush.a11yideas.com (the welcome message intro), this is the
> html example me and my colleagues wrote for a mobile presentation on
> the other thing you asked about, autocomplete searches.
>
>
>
> On 4/25/16, Snahendu Bhattacharya < = EMAIL ADDRESS REMOVED = > wrote:
> > Hi Jennifer!
> >
> > I agree with your observation and had a similar thought too.
> >
> > Just trying to think other perspective like the user who doesn't have
> > keyboard to press enter (Mobile users or other AT users)
> >
> > I thought both should be present. If a user is *not able* to press ENTER
> > should be able to perform the same action.
> >
> > Let's see what others think about this.
> > On Apr 25, 2016 6:02 PM, "Jennifer Sutton" < = EMAIL ADDRESS REMOVED = > wrote:
> >
> >> Greetings, WebAIM folks:
> >>
> >> What's the current thinking regarding whether a search "submit" button
> is
> >> required? Is there a specific Success Criterion that should be cited?
> >>
> >> I'm wondering about this because, increasingly, I'm seeing search edit
> >> boxes that are activated by simply using the enter key.
> >>
> >> Is this practice becoming accepted/known?
> >>
> >> How do folks who use text-input, such as Dragon Naturally Speaking,
> handle
> >> the lack of a button (with a name to speak)?
> >>
> >> Though it is not relevant to the particular use case I'm currently
> looking
> >> at, I also find myself thinking about the kinds of search mechanisms
> that
> >> autocomplete/suggest, as you type. These typically, as far as I recall,
> do
> >> not have "submit" buttons. I guess the idea with them is that once you
> >> stop
> >> typing, you've essentially "submitted." But I bring these
> >> search-suggestion
> >> mechanisms up because I wonder if they're contributing to the perception
> >> that "submit" buttons are no longer necessary for searches (whether or
> not
> >> suggestions are offered).
> >>
> >> In the end, I want to be sure I'm clear about whether the lack of a
> search
> >> submission button is a WCAG 2.0 issue, considered to be a general
> >> usability
> >> issue (for people with disabilities and/or people without), or both?
> >>
> >> Thank you.
> >>
> >> Best,
> >> Jennifer
> >> > >> > >> > >> > >>
> > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >

From: Léonie Watson
Date: Tue, Apr 26 2016 2:05AM
Subject: Re: search-submit button -- required or not
← Previous message | Next message →

> From: WebAIM-Forum on Behalf Of Jennifer Sutton
> Sent: 25 April 2016 23:03
> What's the current thinking regarding whether a search "submit" button is
> required? Is there a specific Success Criterion that should be cited?

Having a search button as a clear call to action (with a suitably clear label) is helpful to people with certain cognitive disabilities. I've heard anecdotally from people on the Autistic spectrum that without such clear instructions, interactions like submitting a search can be difficult/impossible to carry out.

Léonie.

--
@LeonieWatson tink.uk Carpe diem

From: Wright, Eric [USA]
Date: Tue, Apr 26 2016 9:42AM
Subject: Re: search-submit button -- required or not
← Previous message | Next message →

Hi Jenn,

To your question regarding the user experience for someone using speech recognition,

>How do folks who use text-input, such as Dragon Naturally Speaking,
>handle the lack of a button (with a name to speak)?

Dragon (and most speech recognition software) makes it fairly easy to send a keystroke (or combination of keystrokes) by saying, "Press [keys]." "Press Enter Key" can be preferable here to "Click Submit" if there are multiple submit buttons on the screen. In that case, submission involves saying "Click Submit" and then issuing a separate "choose" command to select your desired button among many. "Press Enter Key" takes this two step process and turns it into a one step process.

Still, Leonie's point holds. Submission of the form via the enter key needs to be discoverable and understandable for it to be useful.

Eric Wright
Lead Technologist
Booz Allen Hamilton
Mobile (802) 310-9138
www.boozallen.com

From: WebAIM-Forum [ = EMAIL ADDRESS REMOVED = ] on behalf of Jennifer Sutton [ = EMAIL ADDRESS REMOVED = ]
Sent: Monday, April 25, 2016 6:02 PM
To: WebAIM Discussion List
Subject: [External] [WebAIM] search-submit button -- required or not

Greetings, WebAIM folks:

What's the current thinking regarding whether a search "submit" button
is required? Is there a specific Success Criterion that should be cited?

I'm wondering about this because, increasingly, I'm seeing search edit
boxes that are activated by simply using the enter key.

Is this practice becoming accepted/known?

How do folks who use text-input, such as Dragon Naturally Speaking,
handle the lack of a button (with a name to speak)?

Though it is not relevant to the particular use case I'm currently
looking at, I also find myself thinking about the kinds of search
mechanisms that autocomplete/suggest, as you type. These typically, as
far as I recall, do not have "submit" buttons. I guess the idea with
them is that once you stop typing, you've essentially "submitted." But I
bring these search-suggestion mechanisms up because I wonder if they're
contributing to the perception that "submit" buttons are no longer
necessary for searches (whether or not suggestions are offered).

In the end, I want to be sure I'm clear about whether the lack of a
search submission button is a WCAG 2.0 issue, considered to be a general
usability issue (for people with disabilities and/or people without), or
both?

Thank you.

Best,
Jennifer

From: Jennifer Sutton
Date: Tue, Apr 26 2016 11:17AM
Subject: Re: search-submit button -- required or not
← Previous message | Next message →

Thanks, all, for this thorough and helpful discussion.
I appreciate the range of thoughts and experiences everyone has shared.

Best,
Jennifer

From: Lucy Greco
Date: Tue, Apr 26 2016 11:28AM
Subject: Re: search-submit button -- required or not
← Previous message | Next message →

what is every ones take on the appearing more and more often the icon
font of a magnifying glass with no label i am thinking it is not good for
dragon as well

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 Tue, Apr 26, 2016 at 10:17 AM, Jennifer Sutton < = EMAIL ADDRESS REMOVED = >
wrote:

> Thanks, all, for this thorough and helpful discussion.
> I appreciate the range of thoughts and experiences everyone has shared.
>
>
> Best,
> Jennifer
>
>
> > > > >

From: Wright, Eric [USA]
Date: Wed, Apr 27 2016 9:04AM
Subject: Re: [External]search-submit button -- required or not
← Previous message | Next message →

Hi Lucy,

Just my two cents: it depends on what you mean by "no label." If the magnifying glass has no on-screen label, but has an accessible name and the correct role, a Dragon user should be able to access it by saying "click [name]" or "click [role]."

Just like in the last example, the big issue is discoverability. But that's why it helps to make your labels intuitive, pronounceable and terse.

If there's no programmatic label, period, then the Dragon user's best bet is guessing at the element type (i.e., "click image") or sending keystrokes to focus on it/activate it.

Best,

Eric Wright
Lead Technologist
Booz Allen Hamilton
Mobile (802) 310-9138
www.boozallen.com

From: WebAIM-Forum [ = EMAIL ADDRESS REMOVED = ] on behalf of Lucy Greco [ = EMAIL ADDRESS REMOVED = ]
Sent: Tuesday, April 26, 2016 1:28 PM
To: WebAIM Discussion List
Subject: [External] Re: [WebAIM] search-submit button -- required or not

what is every ones take on the appearing more and more often the icon
font of a magnifying glass with no label i am thinking it is not good for
dragon as well

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 Tue, Apr 26, 2016 at 10:17 AM, Jennifer Sutton < = EMAIL ADDRESS REMOVED = >
wrote:

> Thanks, all, for this thorough and helpful discussion.
> I appreciate the range of thoughts and experiences everyone has shared.
>
>
> Best,
> Jennifer
>
>
> > > > >

From: Birkir R. Gunnarsson
Date: Wed, Apr 27 2016 9:38AM
Subject: Re: [External]search-submit button -- required or not
← Previous message | Next message →

If the icon provides better usability for a group of users (maybe
people with dyslexia) without harming others, it is a usability
improvement, so all good.
So I don't mind a properly labeled control that has an additional
visual identification.
But if the icaon is meant to replace the accessible name or even an
easily discoverable textual label, that's where I start getting
concerned and push back.



On 4/27/16, Wright, Eric [USA] < = EMAIL ADDRESS REMOVED = > wrote:
> Hi Lucy,
>
> Just my two cents: it depends on what you mean by "no label." If the
> magnifying glass has no on-screen label, but has an accessible name and the
> correct role, a Dragon user should be able to access it by saying "click
> [name]" or "click [role]."
>
> Just like in the last example, the big issue is discoverability. But that's
> why it helps to make your labels intuitive, pronounceable and terse.
>
> If there's no programmatic label, period, then the Dragon user's best bet is
> guessing at the element type (i.e., "click image") or sending keystrokes to
> focus on it/activate it.
>
> Best,
>
> Eric Wright
> Lead Technologist
> Booz Allen Hamilton
> Mobile (802) 310-9138
> www.boozallen.com
>
> > From: WebAIM-Forum [ = EMAIL ADDRESS REMOVED = ] on behalf of Lucy
> Greco [ = EMAIL ADDRESS REMOVED = ]
> Sent: Tuesday, April 26, 2016 1:28 PM
> To: WebAIM Discussion List
> Subject: [External] Re: [WebAIM] search-submit button -- required or not
>
> what is every ones take on the appearing more and more often the icon
> font of a magnifying glass with no label i am thinking it is not good for
> dragon as well
>
> 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 Tue, Apr 26, 2016 at 10:17 AM, Jennifer Sutton < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> Thanks, all, for this thorough and helpful discussion.
>> I appreciate the range of thoughts and experiences everyone has shared.
>>
>>
>> Best,
>> Jennifer
>>
>>
>> >> >> >> >>
> > > > > > > > >


--
Work hard. Have fun. Make history.

From: Lucy Greco
Date: Wed, Apr 27 2016 12:00PM
Subject: Re: [External]search-submit button -- required or not
← Previous message | Next message →

eric its more along the lines of berkers example the icon is th the
only thing used there is no on screen text and the screen reader speaks
nothing and at times even skips over the thing. efectivley this becomes a
surtch feeld with out a submit because the screen reader user does not have
any way to know its there at all. hitting enter does actavate it half of
the time but the rest of the time it needs a mouce click i say lable lable
and lable it but i get all kinds of kickback but but it does not need one
every one knows what it means. haha

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, Apr 27, 2016 at 8:38 AM, Birkir R. Gunnarsson <
= EMAIL ADDRESS REMOVED = > wrote:

> If the icon provides better usability for a group of users (maybe
> people with dyslexia) without harming others, it is a usability
> improvement, so all good.
> So I don't mind a properly labeled control that has an additional
> visual identification.
> But if the icaon is meant to replace the accessible name or even an
> easily discoverable textual label, that's where I start getting
> concerned and push back.
>
>
>
> On 4/27/16, Wright, Eric [USA] < = EMAIL ADDRESS REMOVED = > wrote:
> > Hi Lucy,
> >
> > Just my two cents: it depends on what you mean by "no label." If the
> > magnifying glass has no on-screen label, but has an accessible name and
> the
> > correct role, a Dragon user should be able to access it by saying "click
> > [name]" or "click [role]."
> >
> > Just like in the last example, the big issue is discoverability. But
> that's
> > why it helps to make your labels intuitive, pronounceable and terse.
> >
> > If there's no programmatic label, period, then the Dragon user's best
> bet is
> > guessing at the element type (i.e., "click image") or sending keystrokes
> to
> > focus on it/activate it.
> >
> > Best,
> >
> > Eric Wright
> > Lead Technologist
> > Booz Allen Hamilton
> > Mobile (802) 310-9138
> > www.boozallen.com
> >
> > > > From: WebAIM-Forum [ = EMAIL ADDRESS REMOVED = ] on behalf of
> Lucy
> > Greco [ = EMAIL ADDRESS REMOVED = ]
> > Sent: Tuesday, April 26, 2016 1:28 PM
> > To: WebAIM Discussion List
> > Subject: [External] Re: [WebAIM] search-submit button -- required or not
> >
> > what is every ones take on the appearing more and more often the icon
> > font of a magnifying glass with no label i am thinking it is not good
> for
> > dragon as well
> >
> > 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 Tue, Apr 26, 2016 at 10:17 AM, Jennifer Sutton < = EMAIL ADDRESS REMOVED = >
> > wrote:
> >
> >> Thanks, all, for this thorough and helpful discussion.
> >> I appreciate the range of thoughts and experiences everyone has shared.
> >>
> >>
> >> Best,
> >> Jennifer
> >>
> >>
> >> > >> > >> > >> > >>
> > > > > > > > > > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > > >

From: KP
Date: Wed, Apr 27 2016 2:18PM
Subject: Re: [External]search-submit button -- required or not
← Previous message | Next message →

I'll have a proper read later. Always best to ask a busy man

K

Sent from my iPhone

> On 28/04/2016, at 6:00 AM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
>
> eric its more along the lines of berkers example the icon is th the
> only thing used there is no on screen text and the screen reader speaks
> nothing and at times even skips over the thing. efectivley this becomes a
> surtch feeld with out a submit because the screen reader user does not have
> any way to know its there at all. hitting enter does actavate it half of
> the time but the rest of the time it needs a mouce click i say lable lable
> and lable it but i get all kinds of kickback but but it does not need one
> every one knows what it means. haha
>
> 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, Apr 27, 2016 at 8:38 AM, Birkir R. Gunnarsson <
> = EMAIL ADDRESS REMOVED = > wrote:
>
>> If the icon provides better usability for a group of users (maybe
>> people with dyslexia) without harming others, it is a usability
>> improvement, so all good.
>> So I don't mind a properly labeled control that has an additional
>> visual identification.
>> But if the icaon is meant to replace the accessible name or even an
>> easily discoverable textual label, that's where I start getting
>> concerned and push back.
>>
>>
>>
>>> On 4/27/16, Wright, Eric [USA] < = EMAIL ADDRESS REMOVED = > wrote:
>>> Hi Lucy,
>>>
>>> Just my two cents: it depends on what you mean by "no label." If the
>>> magnifying glass has no on-screen label, but has an accessible name and
>> the
>>> correct role, a Dragon user should be able to access it by saying "click
>>> [name]" or "click [role]."
>>>
>>> Just like in the last example, the big issue is discoverability. But
>> that's
>>> why it helps to make your labels intuitive, pronounceable and terse.
>>>
>>> If there's no programmatic label, period, then the Dragon user's best
>> bet is
>>> guessing at the element type (i.e., "click image") or sending keystrokes
>> to
>>> focus on it/activate it.
>>>
>>> Best,
>>>
>>> Eric Wright
>>> Lead Technologist
>>> Booz Allen Hamilton
>>> Mobile (802) 310-9138
>>> www.boozallen.com
>>>
>>> >>> From: WebAIM-Forum [ = EMAIL ADDRESS REMOVED = ] on behalf of
>> Lucy
>>> Greco [ = EMAIL ADDRESS REMOVED = ]
>>> Sent: Tuesday, April 26, 2016 1:28 PM
>>> To: WebAIM Discussion List
>>> Subject: [External] Re: [WebAIM] search-submit button -- required or not
>>>
>>> what is every ones take on the appearing more and more often the icon
>>> font of a magnifying glass with no label i am thinking it is not good
>> for
>>> dragon as well
>>>
>>> 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 Tue, Apr 26, 2016 at 10:17 AM, Jennifer Sutton < = EMAIL ADDRESS REMOVED = >
>>> wrote:
>>>
>>>> Thanks, all, for this thorough and helpful discussion.
>>>> I appreciate the range of thoughts and experiences everyone has shared.
>>>>
>>>>
>>>> Best,
>>>> Jennifer
>>>>
>>>>
>>>> >>>> >>>> >>>> >>> >>> >>> >>> >>> >>> >>> >>> >>
>>
>> --
>> Work hard. Have fun. Make history.
>> >> >> >> > > > >

From: KP
Date: Wed, Apr 27 2016 4:33PM
Subject: Re: [External]search-submit button -- required or not
← Previous message | No next message

Sorry, replied to wrong email :(

Sent from my iPhone

> On 28/04/2016, at 8:18 AM, KP < = EMAIL ADDRESS REMOVED = > wrote:
>
> I'll have a proper read later. Always best to ask a busy man
>
> K
>
> Sent from my iPhone
>
>> On 28/04/2016, at 6:00 AM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> eric its more along the lines of berkers example the icon is th the
>> only thing used there is no on screen text and the screen reader speaks
>> nothing and at times even skips over the thing. efectivley this becomes a
>> surtch feeld with out a submit because the screen reader user does not have
>> any way to know its there at all. hitting enter does actavate it half of
>> the time but the rest of the time it needs a mouce click i say lable lable
>> and lable it but i get all kinds of kickback but but it does not need one
>> every one knows what it means. haha
>>
>> 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, Apr 27, 2016 at 8:38 AM, Birkir R. Gunnarsson <
>> = EMAIL ADDRESS REMOVED = > wrote:
>>
>>> If the icon provides better usability for a group of users (maybe
>>> people with dyslexia) without harming others, it is a usability
>>> improvement, so all good.
>>> So I don't mind a properly labeled control that has an additional
>>> visual identification.
>>> But if the icaon is meant to replace the accessible name or even an
>>> easily discoverable textual label, that's where I start getting
>>> concerned and push back.
>>>
>>>
>>>
>>>> On 4/27/16, Wright, Eric [USA] < = EMAIL ADDRESS REMOVED = > wrote:
>>>> Hi Lucy,
>>>>
>>>> Just my two cents: it depends on what you mean by "no label." If the
>>>> magnifying glass has no on-screen label, but has an accessible name and
>>> the
>>>> correct role, a Dragon user should be able to access it by saying "click
>>>> [name]" or "click [role]."
>>>>
>>>> Just like in the last example, the big issue is discoverability. But
>>> that's
>>>> why it helps to make your labels intuitive, pronounceable and terse.
>>>>
>>>> If there's no programmatic label, period, then the Dragon user's best
>>> bet is
>>>> guessing at the element type (i.e., "click image") or sending keystrokes
>>> to
>>>> focus on it/activate it.
>>>>
>>>> Best,
>>>>
>>>> Eric Wright
>>>> Lead Technologist
>>>> Booz Allen Hamilton
>>>> Mobile (802) 310-9138
>>>> www.boozallen.com
>>>>
>>>> >>>> From: WebAIM-Forum [ = EMAIL ADDRESS REMOVED = ] on behalf of
>>> Lucy
>>>> Greco [ = EMAIL ADDRESS REMOVED = ]
>>>> Sent: Tuesday, April 26, 2016 1:28 PM
>>>> To: WebAIM Discussion List
>>>> Subject: [External] Re: [WebAIM] search-submit button -- required or not
>>>>
>>>> what is every ones take on the appearing more and more often the icon
>>>> font of a magnifying glass with no label i am thinking it is not good
>>> for
>>>> dragon as well
>>>>
>>>> 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 Tue, Apr 26, 2016 at 10:17 AM, Jennifer Sutton < = EMAIL ADDRESS REMOVED = >
>>>> wrote:
>>>>
>>>>> Thanks, all, for this thorough and helpful discussion.
>>>>> I appreciate the range of thoughts and experiences everyone has shared.
>>>>>
>>>>>
>>>>> Best,
>>>>> Jennifer
>>>>>
>>>>>
>>>>> >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>
>>>
>>> --
>>> Work hard. Have fun. Make history.
>>> >>> >>> >>> >> >> >> >> > > > >