WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Keyboard behavior with JAWS

for

From: pratik roy
Date: Aug 26, 2015 11:26AM

Correct guess!

Our developers are using <div> with tabindex="0" and role="button", so you
can say these are fake buttons.

Thanks & Regards
PRATIK ROY

On Tue, Aug 25, 2015 at 11:30 PM, < <EMAIL REMOVED> >
wrote:

> Send WebAIM-Forum mailing list submissions to
> <EMAIL REMOVED>
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://list.webaim.org/mailman/listinfo/webaim-forum
> or, via email, send a message with subject or body 'help' to
> <EMAIL REMOVED>
>
> You can reach the person managing the list at
> <EMAIL REMOVED>
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
>
> Today's Topics:
>
> 1. Question about tagged PDF (Ócsvári Áron)
> 2. Re: Question about tagged PDF (_mallory)
> 3. Re: Question about tagged PDF (Duff Johnson)
> 4. Re: Keyboard behavior with JAWS (_mallory)
> 5. making search input field accessible without a <label>
> (Angela French)
> 6. Re: making search input field accessible without a <label>
> (Léonie Watson)
> 7. Re: making search input field accessible without a <label>
> (Angela French)
> 8. Re: making search input field accessible without a <label>
> (Angela French)
> 9. Re: making search input field accessible without a <label>
> (Birkir R. Gunnarsson)
> 10. Re: Question about tagged PDF (_mallory)
> 11. Re: making search input field accessible without a <label>
> (Chaals McCathie Nevile)
> 12. Slack for accessibility policy geeks! (Jon Metz)
> 13. Re: Question about tagged PDF (Duff Johnson)
>
>
> ---------- Forwarded message ----------
> From: "Ócsvári Áron" < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Mon, 24 Aug 2015 21:11:10 +0200
> Subject: [WebAIM] Question about tagged PDF
> Hello,
> I've created a web-application, and I generate pdf files. The biggest
> problem is that these files are not tagged. I know I can add tags with
> Adobe softvare, but it would be great if I can do it automaticaly. A year
> ago I've tried to TcPdf (it is a php-based Pdf generator), but it didn't
> support the tagging function. Is there any script which can generate an
> accessible pdf file from a html document?
> Thanks for your help!
> Regards,
> Aron
>
>
>
> ---------- Forwarded message ----------
> From: _mallory < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Mon, 24 Aug 2015 21:12:20 +0200
> Subject: Re: [WebAIM] Question about tagged PDF
> On Mon, Aug 24, 2015 at 09:11:10PM +0200, Ócsvári Áron wrote:
> > Hello,
> > I've created a web-application, and I generate pdf files. The
> > biggest problem is that these files are not tagged. I know I can add
> > tags with Adobe softvare, but it would be great if I can do it
> > automaticaly.
>
> It would be great if I could tag on Linux, or anywhere I want, without
> specifically Adobe software. </offtopic>
>
>
>
>
> ---------- Forwarded message ----------
> From: Duff Johnson < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Mon, 24 Aug 2015 15:25:16 -0400
> Subject: Re: [WebAIM] Question about tagged PDF
> > On Mon, Aug 24, 2015 at 09:11:10PM +0200, Ócsvári Áron wrote:
> >> Hello,
> >> I've created a web-application, and I generate pdf files. The
> >> biggest problem is that these files are not tagged. I know I can add
> >> tags with Adobe softvare, but it would be great if I can do it
> >> automaticaly.
> >
> > It would be great if I could tag on Linux, or anywhere I want, without
> > specifically Adobe software. </offtopic>
>
> PDF is an ISO standardized technology. You do not need "specifically Adobe
> software" to author "born tagged" PDF documents. There are a wide variety
> of non-Adobe options.
>
> - On the desktop, tools such as Apache Open Office (including for Linux).
> - Application developers can choose from a range of toolkits to produce
> tagged PDF documents.
>
> Duff.
>
>
> ---------- Forwarded message ----------
> From: _mallory < <EMAIL REMOVED> >
> To: <EMAIL REMOVED> , WebAIM Discussion List <
> <EMAIL REMOVED> >
> Cc:
> Date: Mon, 24 Aug 2015 21:59:53 +0200
> Subject: Re: [WebAIM] Keyboard behavior with JAWS
> On Mon, Aug 24, 2015 at 01:19:41PM +0100, Léonie Watson wrote:
> > > From: WebAIM-Forum On Behalf Of pratik roy
> > > Sent: 24 August 2015 11:05
> > >
> > > In our webpage, we have some button elements and onclick of those
> > > buttons, it is performing some action. We have used onkeypress event
> with
> > > keycode="13" (Enter) to handle the functionality. But when I hit Enter
> it is
> > > not even firing the event but working absolutely normal with
> "Alt+Enter".
> >
> > You don't need to use the keypress handler. When the <button> element is
> used with a click handler, the browser automatically handles keyboard
> interaction for you.
> >
>
> Unless they're fake buttons... are they?
> _mallory
>
>
>
> ---------- Forwarded message ----------
> From: Angela French < <EMAIL REMOVED> >
> To: "WebAim Forum ( <EMAIL REMOVED> )" <
> <EMAIL REMOVED> >
> Cc:
> Date: Mon, 24 Aug 2015 20:49:55 +0000
> Subject: [WebAIM] making search input field accessible without a <label>
> I am trying to validate to WCAG 2.0 AA. I'm getting the error that I am
> missing an associated label on my search field.
>
> I have tried aria-label="search" and title="search" but neither one kept
> the error from being thrown. Are these not true solutions? Or must I
> have a <label> tag?
>
> Thanks
>
> Angela French
> Internet Specialist
> Washington State Board for Community and Technical Colleges
> 360-704-4316
> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
> www.checkoutacollege.com<;http://www.checkoutacollege.com/>;
> www.sbctc.edu<;http://www.sbctc.edu/>;
>
>
>
>
> ---------- Forwarded message ----------
> From: "Léonie Watson" < <EMAIL REMOVED> >
> To: "'WebAIM Discussion List'" < <EMAIL REMOVED> >
> Cc:
> Date: Mon, 24 Aug 2015 22:11:30 +0100
> Subject: Re: [WebAIM] making search input field accessible without a
> <label>
> > From: WebAIM-Forum On Behalf Of Angela French
> > Sent: 24 August 2015 21:50
> > I am trying to validate to WCAG 2.0 AA. I'm getting the error that I am
> missing
> > an associated label on my search field.
> >
> > I have tried aria-label="search" and title="search" but neither one
> kept the
> > error from being thrown. Are these not true solutions? Or must I have
> a
> > <label> tag?
>
> These are both valid techniques. Technique ARIA14 describes how to use
> aria-label to provide a label [1], and technique H65 describes how to use
> the title attribute [2].
>
> The proviso (in both cases) being that the purpose of the field is
> apparent to sighted users based on context. The nearby search button being
> the visible cue in this situation.
>
> Sounds like it might be worth filing a bug with the vendors of the
> checking tool you're using though?
>
> HTH.
> Léonie.
> [1] http://www.w3.org/TR/WCAG20-TECHS/aria#ARIA14
> [2] http://www.w3.org/TR/WCAG20-TECHS/H65.html
>
>
>
>
> ---------- Forwarded message ----------
> From: Angela French < <EMAIL REMOVED> >
> To: " <EMAIL REMOVED> " < <EMAIL REMOVED> >, WebAIM
> Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Mon, 24 Aug 2015 21:23:28 +0000
> Subject: Re: [WebAIM] making search input field accessible without a
> <label>
> Actually, I didn't realize/forgot there were two search fields on the page
> and so I was seeing the error for the other one. The fact that there are
> two search fields is another issue.
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Léonie Watson
> Sent: Monday, August 24, 2015 2:12 PM
> To: 'WebAIM Discussion List'
> Subject: Re: [WebAIM] making search input field accessible without a
> <label>
>
> > From: WebAIM-Forum On Behalf Of Angela French
> > Sent: 24 August 2015 21:50
> > I am trying to validate to WCAG 2.0 AA. I'm getting the error that I
> > am missing an associated label on my search field.
> >
> > I have tried aria-label="search" and title="search" but neither one
> kept the
> > error from being thrown. Are these not true solutions? Or must I have
> a
> > <label> tag?
>
> These are both valid techniques. Technique ARIA14 describes how to use
> aria-label to provide a label [1], and technique H65 describes how to use
> the title attribute [2].
>
> The proviso (in both cases) being that the purpose of the field is
> apparent to sighted users based on context. The nearby search button being
> the visible cue in this situation.
>
> Sounds like it might be worth filing a bug with the vendors of the
> checking tool you're using though?
>
> HTH.
> Léonie.
> [1] http://www.w3.org/TR/WCAG20-TECHS/aria#ARIA14
> [2] http://www.w3.org/TR/WCAG20-TECHS/H65.html
>
> > > at http://webaim.org/discussion/archives
> >
>
> ---------- Forwarded message ----------
> From: Angela French < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Mon, 24 Aug 2015 21:27:08 +0000
> Subject: Re: [WebAIM] making search input field accessible without a
> <label>
> Actually, I take that back. I have added aria-label="search" to both form
> elements and it is still failing on the Achecker. Still shows error about
> missing an associated label. Is the AChecker not so good to use?
>
>
> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf Of Léonie Watson
> Sent: Monday, August 24, 2015 2:12 PM
> To: 'WebAIM Discussion List'
> Subject: Re: [WebAIM] making search input field accessible without a
> <label>
>
> > From: WebAIM-Forum On Behalf Of Angela French
> > Sent: 24 August 2015 21:50
> > I am trying to validate to WCAG 2.0 AA. I'm getting the error that I
> > am missing an associated label on my search field.
> >
> > I have tried aria-label="search" and title="search" but neither one
> kept the
> > error from being thrown. Are these not true solutions? Or must I have
> a
> > <label> tag?
>
> These are both valid techniques. Technique ARIA14 describes how to use
> aria-label to provide a label [1], and technique H65 describes how to use
> the title attribute [2].
>
> The proviso (in both cases) being that the purpose of the field is
> apparent to sighted users based on context. The nearby search button being
> the visible cue in this situation.
>
> Sounds like it might be worth filing a bug with the vendors of the
> checking tool you're using though?
>
> HTH.
> Léonie.
> [1] http://www.w3.org/TR/WCAG20-TECHS/aria#ARIA14
> [2] http://www.w3.org/TR/WCAG20-TECHS/H65.html
>
> > > at http://webaim.org/discussion/archives
> >
>
> ---------- Forwarded message ----------
> From: "Birkir R. Gunnarsson" < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Mon, 24 Aug 2015 17:37:00 -0400
> Subject: Re: [WebAIM] making search input field accessible without a
> <label>
> You may want to switch to an accessibility checker that understands
> and incorporates ARIA.
> Also make sure the checker is checking the DOM/accessibility tree, not
> just the static html.
> I can't speak for aChecker specifically, but last time I looked it
> appeared not to have been updated since its 2008 release.
> You can view a decent (but not entirely compirhensive) list of tools
> here: http://www.w3.org/WAI/ER/tools/
>
>
>
> On 8/24/15, Angela French < <EMAIL REMOVED> > wrote:
> > Actually, I take that back. I have added aria-label="search" to both
> form
> > elements and it is still failing on the Achecker. Still shows error
> about
> > missing an associated label. Is the AChecker not so good to use?
> >
> >
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
> Behalf
> > Of Léonie Watson
> > Sent: Monday, August 24, 2015 2:12 PM
> > To: 'WebAIM Discussion List'
> > Subject: Re: [WebAIM] making search input field accessible without a
> > <label>
> >
> >> From: WebAIM-Forum On Behalf Of Angela French
> >> Sent: 24 August 2015 21:50
> >> I am trying to validate to WCAG 2.0 AA. I'm getting the error that I
> >> am missing an associated label on my search field.
> >>
> >> I have tried aria-label="search" and title="search" but neither one
> kept
> >> the
> >> error from being thrown. Are these not true solutions? Or must I have
> >> a
> >> <label> tag?
> >
> > These are both valid techniques. Technique ARIA14 describes how to use
> > aria-label to provide a label [1], and technique H65 describes how to use
> > the title attribute [2].
> >
> > The proviso (in both cases) being that the purpose of the field is
> apparent
> > to sighted users based on context. The nearby search button being the
> > visible cue in this situation.
> >
> > Sounds like it might be worth filing a bug with the vendors of the
> checking
> > tool you're using though?
> >
> > HTH.
> > Léonie.
> > [1] http://www.w3.org/TR/WCAG20-TECHS/aria#ARIA14
> > [2] http://www.w3.org/TR/WCAG20-TECHS/H65.html
> >
> > > > > archives at
> > http://webaim.org/discussion/archives
> > > > > > > > > > > >
>
>
> --
> Work hard. Have fun. Make history.
>
>
>
> ---------- Forwarded message ----------
> From: _mallory < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Tue, 25 Aug 2015 08:15:32 +0200
> Subject: Re: [WebAIM] Question about tagged PDF
> On Mon, Aug 24, 2015 at 03:25:16PM -0400, Duff Johnson wrote:
> > PDF is an ISO standardized technology. You do not need "specifically
> Adobe software" to author "born tagged" PDF documents. There are a wide
> variety of non-Adobe options.
> >
> > - On the desktop, tools such as Apache Open Office (including for Linux).
>
> Wait, I have Open Office, I haven't seen anything there for tagging.
> If it's in there, I will go look again because til now I've been
> booting a slow laggy virtual box for all this!
> _mallory
>
>
>
> ---------- Forwarded message ----------
> From: Chaals McCathie Nevile < <EMAIL REMOVED> >
> To: "'WebAIM Discussion List'" < <EMAIL REMOVED> >, "Léonie
> Watson" < <EMAIL REMOVED> >
> Cc:
> Date: Tue, 25 Aug 2015 16:20:23 +0200
> Subject: Re: [WebAIM] making search input field accessible without a
> <label>
> On Mon, 24 Aug 2015 23:11:30 +0200, Léonie Watson <
> <EMAIL REMOVED> > wrote:
>
> From: WebAIM-Forum On Behalf Of Angela French
>>> Sent: 24 August 2015 21:50
>>> I am trying to validate to WCAG 2.0 AA. I'm getting the error that I am
>>> missing an associated label on my search field.
>>>
>>> I have tried aria-label="search" and title="search" but neither one
>>> kept the error from being thrown. Are these not true solutions? Or
>>> must I have a <label> tag?
>>>
>>
>> These are both valid techniques. Technique ARIA14 describes how to use
>> aria-label to provide a label [1], and technique H65 describes how to use
>> the title attribute [2].
>>
>> The proviso (in both cases) being that the purpose of the field is
>> apparent to sighted users based on context. The nearby search button being
>> the visible cue in this situation.
>>
>
> Which is worth repeating, because it really is important.
>
> The aria/title thing is fine for screenreader users - who are likely to be
> a very small minority of users with vision-related accessibility
> requirements. But as Léonie said, it needs to be clear there is a search
> box without relying on ARIA.
>
> A blue box with some icon on it may or may not do the job (again, you need
> proper alt if you use that) - I am not a fan. And it should be available in
> more or less any layout - what WCAG says about zooming 200% is manifestly
> insufficient for *accessibility* - as opposed to conformance.
>
> Sounds like it might be worth filing a bug with the vendors of the
>> checking tool you're using though?
>>
>
> Yeah, or two.
>
> cheers
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> <EMAIL REMOVED> - - - Find more at http://yandex.com
>
>
>
> ---------- Forwarded message ----------
> From: Jon Metz < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Tue, 25 Aug 2015 11:01:50 -0400
> Subject: [WebAIM] Slack for accessibility policy geeks!
> Hi all,
>
> Sorry if this is really inappropriate to post this here.
>
> To answer the really awesome technical-focused Slack communities created by
> the venerable Marcy Sutton & Steve Faulkner, I¹ve created a Slack
> specifically for Policy geeks to commune and talk shop. I didn¹t feel like
> there was enough places for those of us who have an odd obsession with
> specifications and regulations. It could also serve as a place to help
> others understand the often murky wording of standards. If you¹re itching
> to learn more about the impetus for this Slack, feel free to read my blog
> post about it at
> https://metzessible.com/introducing-accessibility-policy-social-hour (I¹m
> still working out some accessibility kinks, so bear that in mind).
>
> You can get an invite by signing up on my website (thanks to Sina Bahram
> for
> setting this up!): https://a11ywonks.metzessible.com.
>
> If you use a screen reader, I recommend either using the Slack iPhone app
> or
> connecting via IRC. When you get your invite worked out, go to
> https://a11ywonks.slack.com/account/gateways and under the H3 ³Getting
> Started² use the information for Host, User, and Pass accordingly. Remember
> to connect with SSL on your IRC Client.
>
> Thanks, and I look forward to chatting with you!
>
> Jon Metz
> metzessible.com
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Duff Johnson < <EMAIL REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Tue, 25 Aug 2015 11:54:20 -0400
> Subject: Re: [WebAIM] Question about tagged PDF
>
> > On Aug 25, 2015, at 02:15, _mallory < <EMAIL REMOVED> > wrote:
> > Wait, I have Open Office, I haven't seen anything there for tagging.
> > If it's in there, I will go look again because til now I've been
> > booting a slow laggy virtual box for all this!
> > _mallory
>
> The "Tagged PDF" option in the "Exporting to PDF" dialog is documented (in
> a manner of speaking) here:
>
>
> https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/Getting_Started/Exporting_to_PDF
>
> You'll find the resulting PDF includes tags in logical order (for simpler
> documents) automatically. Structure elements (headings, lists, tables, etc)
> will be present and correct based on the author's choice/ability to use
> appropriate styles.
>
> Selecting PDF/A-1 in addition ensures that fonts are embedded and that, in
> general, the file is in good shape.
>
> Duff.
>
>
>
> > > > >
>