E-mail List Archives

Thread: Keyboard behavior with JAWS

for

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

From: pratik roy
Date: Mon, Aug 24 2015 4:04AM
Subject: Keyboard behavior with JAWS
No previous message | Next message →

Recently, I faced a scenario where keyboard "Enter" key is not functioning
as expected and we have to press "Alt+Enter" in order to make it work.

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".

After that, I tried to do console.log() and saw that all key stock action
is working normally if I press any key with "Alt".

Now, my problem is, I am not sure whether that key combination is common
for screen reader user or not.

If anyone can share user experience for this kind of senario or a solution
of this problem, that will be GREAT Help.

Note: All keyboard keys are working fine with role="application" but I
don't want to make it a application region. :)

Thanks & Regards
PRATIK ROY

On Sat, Aug 22, 2015 at 11:30 PM, < = EMAIL ADDRESS REMOVED = >
wrote:

> Send WebAIM-Forum mailing list submissions to
> = EMAIL ADDRESS 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 ADDRESS REMOVED =
>
> You can reach the person managing the list at
> = EMAIL ADDRESS REMOVED =
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of WebAIM-Forum digest..."
>
> Today's Topics:
>
> 1. Re: WCAG Extensions (Kroon, Kurtis@FTB)
> 2. Re: WCAG Extensions (Chagnon | PubCom)
> 3. Re: Developing an Accessibility Team (Kline, Jeff)
> 4. a few recent links related to CAPTCHA (Jennifer Sutton)
> 5. Re: W3C-WAI Low Vision Accessibility Task Force - Seeking
> Participation (Chaals McCathie Nevile)
>
>
> ---------- Forwarded message ----------
> From: "Kroon, Kurtis@FTB" < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Fri, 21 Aug 2015 18:33:47 +0000
> Subject: Re: [WebAIM] WCAG Extensions
> -----Original Message-----
> From: _mallory [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Thursday, August 20, 2015 10:27
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] WCAG Extensions
>
> A split? Something that's okay to be somewhat stale for the lawyers and
> something that is aware of new technology and new needs and new services,
> for developers, vendors and spec-writers to lean on?
>
> [KK]
> IANAL, but as I understand it, that's how it already works for regulations:
>
> "Incorporation by reference of a publication is limited to the edition of
> the publication that is approved. Future amendments or revisions of the
> publication are not included."[1]
>
> So, once the regulation incorporates by reference, say, WCAG 2.0 as
> published on 11 December 2008[2], the W3C can extend, update, fold,
> spindle, or mangle their recommendations (to WCAG ∞) and it won't affect
> the regulation one jot.
>
> I find it interesting that, to my knowledge, no federal agency has decided
> "Section 508 is getting long in the tooth -- let's use the Equivalent
> Facilitation clause[3] and choose WCAG 2.0 as our new accessibility
> standard."
>
> Regards,
>
> Kurt
> Web Services
> Franchise Tax Board
> State of California
>
> Citations:
>
> [1]: 1 CFR §51.1(f)
> [2]: http://www.w3.org/TR/2008/REC-WCAG20-20081211/
> [3]: 36 CFR §1194.5
>
> > CONFIDENTIALITY NOTICE: This email from the State of California is for the
> sole use of the intended recipient and may contain confidential and
> privileged information. Any unauthorized review or use, including
> disclosure or distribution, is prohibited. If you are not the intended
> recipient, please contact the sender and destroy all copies of this email.
>
>
>
> ---------- Forwarded message ----------
> From: "Chagnon | PubCom" < = EMAIL ADDRESS REMOVED = >
> To: "'WebAIM Discussion List'" < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Fri, 21 Aug 2015 15:08:06 -0400
> Subject: Re: [WebAIM] WCAG Extensions
> Kurt wrote:
> " I find it interesting that, to my knowledge, no federal agency has
> decided "Section 508 is getting long in the tooth -- let's use the
> Equivalent Facilitation clause[3] and choose WCAG 2.0 as our new
> accessibility standard." "
>
> FYI, most federal agencies here in Washington DC don't have a clue what
> "508" is.
> Those that do have a 508 policy are lucky and have made some progress, but
> the political appointees who head up the agencies are still clueless.
> So it's unlikely they'll make any decision on implementing 508 within
> their agency in the near future.
>
> And now that's it's election season, not much will change for the next 2
> years...after the election and new top brass are appointed by the president
> to head up the agencies. Timeline:
> Nov 2016, election
> Jan 2017, inauguration
> Jan 2018, final appointments of agency heads.
> June 2018, real work commences at the agencies.
>
> Here in DC, we all are just trading water for the next 18-24 months. Same
> ol' same ol'. On this point, it doesn't matter which party is elected,
> either.
>
> —Bevi Chagnon
>
> — — —
> Bevi Chagnon | www.PubCom.com
> Technologists, Consultants, Trainers, Designers, and Developers
> for publishing & communication
> | Acrobat PDF | Digital Media | XML and Automated Workflows
> | GPO | Print | Desktop Publishing | Sec. 508 Accessibility | EPUBs
> — — —
>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: "Kline, Jeff" < = EMAIL ADDRESS REMOVED = >
> To: " = EMAIL ADDRESS REMOVED = " < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Fri, 21 Aug 2015 19:10:20 +0000
> Subject: Re: [WebAIM] Developing an Accessibility Team
> There can be many dimensions to developing an accessibility team and
> program. It is important to develop the key elements of the program first
> to understand how and where to effectively staff it.
>
>
>
> My book on this topic<
> http://www.amazon.com/Strategic-Accessibility-Organization-Jeff-Kline/dp/1936909189/ref=sr_1_sc_1?ie=UTF8&;qid40184031&sr=8-1-spell&keywords=strategic+it+accessiiblity>
> provides insight and guidance on developing such a program. The book is
> directed primarily and large organizations, but is easily scaled to smaller
> ones.
>
>
>
>
>
>
>
> Jeff Kline
>
> Program Director
>
> Statewide EIR Accessibility
>
> Texas Department of Information Resources
>
> Phone 512.463.3248
>
> Mobile 512.426.9779
>
>
>
>
>
>
>
> -----Original Message-----
> From: Dennis Deacon [mailto: = EMAIL ADDRESS REMOVED = ]
> Sent: Thursday, August 20, 2015 4:54 PM
> To: = EMAIL ADDRESS REMOVED =
> Subject: [WebAIM] Developing an Accessibility Team
>
>
>
> Our organization has been engaged in a digital accessibility remediation
> project. In parallel, we've also been working on developing an ongoing
> program.
>
>
>
> One aspect that we're working on is building an accessibility team. As
> part of that, we're initially interested in a few things:
>
>
>
> - Do most companies have a full-time team?
>
> - How is the team organized?
>
> - How did other organizations get support from management for a team?
>
>
>
> Any other information on building an accessibility team would be greatly
> appreciated. Our organization is in the transportation industry with an
> eCommerce website and mobile app.
>
>
>
> Thanks in advance.
>
>
>
> Dennis Deacon
>
>
>
>
> ---------- Forwarded message ----------
> From: Jennifer Sutton < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Fri, 21 Aug 2015 17:25:15 -0700
> Subject: [WebAIM] a few recent links related to CAPTCHA
> WebAIM list members:
>
> Since CAPTCHAS are such a frequent topic on the list, I thought I'd post
> two resources, below my name, that have been circulating on Twitter.
>
> Hope they help.
>
> Jennifer
>
>
> 9 CAPTCHA Alternatives That Won’t Wreck Your UX
> http://www.dtelepathy.com/blog/design/captcha-alternatives-better-ux
>
>
>
> Captcha Alternatives and thoughts - WCAG WG
> https://www.w3.org/WAI/GL/wiki/Captcha_Alternatives_and_thoughts
>
> Looks like I may have a replacement for my usual post on this topic:
> In Search Of The Perfect CAPTCHA Smashing Coding
>
> http://coding.smashingmagazine.com/2011/03/04/in-search-of-the-perfect-captcha/
>
>
>
>
> ---------- Forwarded message ----------
> From: Chaals McCathie Nevile < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >, lcmcevoy <
> = EMAIL ADDRESS REMOVED = >
> Cc:
> Date: Sat, 22 Aug 2015 17:58:57 +0200
> Subject: Re: [WebAIM] W3C-WAI Low Vision Accessibility Task Force -
> Seeking Participation
> On Thu, 20 Aug 2015 05:03:52 +0200, lcmcevoy < = EMAIL ADDRESS REMOVED = > wrote:
>
> So glad to hear about this. I’ve felt the needs of low vision users have
>> been overlooked. Thanks for this Jim.
>>
>
> Indeed, and thank you for reaching out widely.
>
> Now to find network so I can join up, and time to do work.
>
> cheers
>
> Laurie
>>
>>
>> On Aug 19, 2015, at 5:05 PM, Jim Allan < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> The W3C Web Accessibility Initiative (WAI) has established a Low Vision
>>> Accessibility Task Force to develop more specific guidance on low vision
>>> accessibility related to content (WCAG 2.0) and browsers (UAAG 2.0).[1]
>>>
>>>
>>> The Low Vision Accessibility Task Force home page is:
>>>
>>> http://www.w3.org/WAI/GL/low-vision-a11y-tf/
>>>
>>>
>>> The Low Vision Accessibility Task Force expects to:
>>>
>>> * Document requirements for low vision users;
>>>
>>> * Identify gaps in the above requirements between user needs and how
>>> they are met by web sites that conform to WCAG 2.0;
>>>
>>> * Document sufficient and advisory techniques and failures for WCAG 2.0
>>> to meet low vision user needs;
>>>
>>> * Define low vision use cases which user agents need to support;
>>>
>>> * Develop an extension to WCAG 2.0 to address low-vision user needs
>>> effectively;
>>>
>>> * Develop support materials to explain the issues and implementation of
>>> the above resources effectively.
>>>
>>>
>>> The Task Force seeks to bring together individuals and organizations to
>>> contribute to this W3C/WAI work.
>>>
>>>
>>> We *invite you to contribute to the Low Vision Accessibility Task Force*.
>>>
>>> * Active participation in the Task Force takes about 4 hours per week,
>>> including teleconferences.
>>>
>>> * Participation is through either the WCAG Working Group or the UAAG
>>> Working Group.
>>>
>>> * More about participation is at <
>>> http://www.w3.org/WAI/GL/low-vision-a11y-tf/#participation>;
>>>
>>> If you cannot commit that much time, you can still review draft
>>> documents.
>>> To get announcements of drafts for review, see <
>>> http://www.w3.org/WAI/about/announcements>;.
>>>
>>>
>>> [1] WCAG & UAAG:
>>>
>>> * WCAG, the Web Content Accessibility Guidelines, is introduced at <
>>> http://www.w3.org/WAI/intro/wcag>;.
>>>
>>> * UAAG, the User Agent Accessibility Guidelines for browsers and other
>>> 'user agents', is introduced at <http://www.w3.org/WAI/intro/uaag>;.
>>>
>>> Please let us know if you have any questions.
>>>
>>>
>>> Feel free to circulate this message to other lists; please avoid
>>> cross-postings where possible.
>>>
>>>
>>> Regards,
>>>
>>> Jim Allan, LVTF Facilitator, UAWG Chair
>>> Andrew Kirkpatrick LVTF Facilitator, WCAG Co-Chair
>>>
>>> Joshue O Connor, WCAG WG Co-Chair
>>>
>>> Michael Cooper, WCAG WG Team Contact
>>> Jeanne Spellman, UAWG Team Contact
>>>
>>> --
>>> [image: http://www.tsbvi.edu] <http://www.tsbvi.edu>;Jim Allan,
>>> Accessibility Coordinator
>>> Texas School for the Blind and Visually Impaired
>>> 1100 W. 45th St., Austin, Texas 78756
>>> voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
>>> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>>> >>> >>> >>> >>>
>>
>> >> >> >> >>
>
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> = EMAIL ADDRESS REMOVED = - - - Find more at http://yandex.com
>
>
> > > > >
>

From: Birkir R. Gunnarsson
Date: Mon, Aug 24 2015 4:15AM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →

Patrick
Jaws/NVDA in browse mode activate the element's onclick event when
enter is pressed with focus on that element (not the onKey events). In
application/forms mode howver, the onKey events are triggered when
user presses enter.
If you change the function trigger to be the onClick event, you should be fine.



On 8/24/15, pratik roy < = EMAIL ADDRESS REMOVED = > wrote:
> Recently, I faced a scenario where keyboard "Enter" key is not functioning
> as expected and we have to press "Alt+Enter" in order to make it work.
>
> 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".
>
> After that, I tried to do console.log() and saw that all key stock action
> is working normally if I press any key with "Alt".
>
> Now, my problem is, I am not sure whether that key combination is common
> for screen reader user or not.
>
> If anyone can share user experience for this kind of senario or a solution
> of this problem, that will be GREAT Help.
>
> Note: All keyboard keys are working fine with role="application" but I
> don't want to make it a application region. :)
>
> Thanks & Regards
> PRATIK ROY
>
> On Sat, Aug 22, 2015 at 11:30 PM, < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> Send WebAIM-Forum mailing list submissions to
>> = EMAIL ADDRESS 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 ADDRESS REMOVED =
>>
>> You can reach the person managing the list at
>> = EMAIL ADDRESS REMOVED =
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of WebAIM-Forum digest..."
>>
>> Today's Topics:
>>
>> 1. Re: WCAG Extensions (Kroon, Kurtis@FTB)
>> 2. Re: WCAG Extensions (Chagnon | PubCom)
>> 3. Re: Developing an Accessibility Team (Kline, Jeff)
>> 4. a few recent links related to CAPTCHA (Jennifer Sutton)
>> 5. Re: W3C-WAI Low Vision Accessibility Task Force - Seeking
>> Participation (Chaals McCathie Nevile)
>>
>>
>> ---------- Forwarded message ----------
>> From: "Kroon, Kurtis@FTB" < = EMAIL ADDRESS REMOVED = >
>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Fri, 21 Aug 2015 18:33:47 +0000
>> Subject: Re: [WebAIM] WCAG Extensions
>> -----Original Message-----
>> From: _mallory [mailto: = EMAIL ADDRESS REMOVED = ]
>> Sent: Thursday, August 20, 2015 10:27
>> To: WebAIM Discussion List
>> Subject: Re: [WebAIM] WCAG Extensions
>>
>> A split? Something that's okay to be somewhat stale for the lawyers and
>> something that is aware of new technology and new needs and new services,
>> for developers, vendors and spec-writers to lean on?
>>
>> [KK]
>> IANAL, but as I understand it, that's how it already works for
>> regulations:
>>
>> "Incorporation by reference of a publication is limited to the edition of
>> the publication that is approved. Future amendments or revisions of the
>> publication are not included."[1]
>>
>> So, once the regulation incorporates by reference, say, WCAG 2.0 as
>> published on 11 December 2008[2], the W3C can extend, update, fold,
>> spindle, or mangle their recommendations (to WCAG ∞) and it won't affect
>> the regulation one jot.
>>
>> I find it interesting that, to my knowledge, no federal agency has decided
>> "Section 508 is getting long in the tooth -- let's use the Equivalent
>> Facilitation clause[3] and choose WCAG 2.0 as our new accessibility
>> standard."
>>
>> Regards,
>>
>> Kurt
>> Web Services
>> Franchise Tax Board
>> State of California
>>
>> Citations:
>>
>> [1]: 1 CFR §51.1(f)
>> [2]: http://www.w3.org/TR/2008/REC-WCAG20-20081211/
>> [3]: 36 CFR §1194.5
>>
>> >> CONFIDENTIALITY NOTICE: This email from the State of California is for the
>> sole use of the intended recipient and may contain confidential and
>> privileged information. Any unauthorized review or use, including
>> disclosure or distribution, is prohibited. If you are not the intended
>> recipient, please contact the sender and destroy all copies of this email.
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: "Chagnon | PubCom" < = EMAIL ADDRESS REMOVED = >
>> To: "'WebAIM Discussion List'" < = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Fri, 21 Aug 2015 15:08:06 -0400
>> Subject: Re: [WebAIM] WCAG Extensions
>> Kurt wrote:
>> " I find it interesting that, to my knowledge, no federal agency has
>> decided "Section 508 is getting long in the tooth -- let's use the
>> Equivalent Facilitation clause[3] and choose WCAG 2.0 as our new
>> accessibility standard." "
>>
>> FYI, most federal agencies here in Washington DC don't have a clue what
>> "508" is.
>> Those that do have a 508 policy are lucky and have made some progress, but
>> the political appointees who head up the agencies are still clueless.
>> So it's unlikely they'll make any decision on implementing 508 within
>> their agency in the near future.
>>
>> And now that's it's election season, not much will change for the next 2
>> years...after the election and new top brass are appointed by the
>> president
>> to head up the agencies. Timeline:
>> Nov 2016, election
>> Jan 2017, inauguration
>> Jan 2018, final appointments of agency heads.
>> June 2018, real work commences at the agencies.
>>
>> Here in DC, we all are just trading water for the next 18-24 months. Same
>> ol' same ol'. On this point, it doesn't matter which party is elected,
>> either.
>>
>> —Bevi Chagnon
>>
>> — — —
>> Bevi Chagnon | www.PubCom.com
>> Technologists, Consultants, Trainers, Designers, and Developers
>> for publishing & communication
>> | Acrobat PDF | Digital Media | XML and Automated Workflows
>> | GPO | Print | Desktop Publishing | Sec. 508 Accessibility | EPUBs
>> — — —
>>
>>
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: "Kline, Jeff" < = EMAIL ADDRESS REMOVED = >
>> To: " = EMAIL ADDRESS REMOVED = " < = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Fri, 21 Aug 2015 19:10:20 +0000
>> Subject: Re: [WebAIM] Developing an Accessibility Team
>> There can be many dimensions to developing an accessibility team and
>> program. It is important to develop the key elements of the program first
>> to understand how and where to effectively staff it.
>>
>>
>>
>> My book on this topic<
>> http://www.amazon.com/Strategic-Accessibility-Organization-Jeff-Kline/dp/1936909189/ref=sr_1_sc_1?ie=UTF8&;qid40184031&sr=8-1-spell&keywords=strategic+it+accessiiblity>
>> provides insight and guidance on developing such a program. The book is
>> directed primarily and large organizations, but is easily scaled to
>> smaller
>> ones.
>>
>>
>>
>>
>>
>>
>>
>> Jeff Kline
>>
>> Program Director
>>
>> Statewide EIR Accessibility
>>
>> Texas Department of Information Resources
>>
>> Phone 512.463.3248
>>
>> Mobile 512.426.9779
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Dennis Deacon [mailto: = EMAIL ADDRESS REMOVED = ]
>> Sent: Thursday, August 20, 2015 4:54 PM
>> To: = EMAIL ADDRESS REMOVED =
>> Subject: [WebAIM] Developing an Accessibility Team
>>
>>
>>
>> Our organization has been engaged in a digital accessibility remediation
>> project. In parallel, we've also been working on developing an ongoing
>> program.
>>
>>
>>
>> One aspect that we're working on is building an accessibility team. As
>> part of that, we're initially interested in a few things:
>>
>>
>>
>> - Do most companies have a full-time team?
>>
>> - How is the team organized?
>>
>> - How did other organizations get support from management for a team?
>>
>>
>>
>> Any other information on building an accessibility team would be greatly
>> appreciated. Our organization is in the transportation industry with an
>> eCommerce website and mobile app.
>>
>>
>>
>> Thanks in advance.
>>
>>
>>
>> Dennis Deacon
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Jennifer Sutton < = EMAIL ADDRESS REMOVED = >
>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Fri, 21 Aug 2015 17:25:15 -0700
>> Subject: [WebAIM] a few recent links related to CAPTCHA
>> WebAIM list members:
>>
>> Since CAPTCHAS are such a frequent topic on the list, I thought I'd post
>> two resources, below my name, that have been circulating on Twitter.
>>
>> Hope they help.
>>
>> Jennifer
>>
>>
>> 9 CAPTCHA Alternatives That Won’t Wreck Your UX
>> http://www.dtelepathy.com/blog/design/captcha-alternatives-better-ux
>>
>>
>>
>> Captcha Alternatives and thoughts - WCAG WG
>> https://www.w3.org/WAI/GL/wiki/Captcha_Alternatives_and_thoughts
>>
>> Looks like I may have a replacement for my usual post on this topic:
>> In Search Of The Perfect CAPTCHA Smashing Coding
>>
>> http://coding.smashingmagazine.com/2011/03/04/in-search-of-the-perfect-captcha/
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Chaals McCathie Nevile < = EMAIL ADDRESS REMOVED = >
>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >, lcmcevoy <
>> = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Sat, 22 Aug 2015 17:58:57 +0200
>> Subject: Re: [WebAIM] W3C-WAI Low Vision Accessibility Task Force -
>> Seeking Participation
>> On Thu, 20 Aug 2015 05:03:52 +0200, lcmcevoy < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> So glad to hear about this. I’ve felt the needs of low vision users have
>>> been overlooked. Thanks for this Jim.
>>>
>>
>> Indeed, and thank you for reaching out widely.
>>
>> Now to find network so I can join up, and time to do work.
>>
>> cheers
>>
>> Laurie
>>>
>>>
>>> On Aug 19, 2015, at 5:05 PM, Jim Allan < = EMAIL ADDRESS REMOVED = > wrote:
>>>
>>> The W3C Web Accessibility Initiative (WAI) has established a Low Vision
>>>> Accessibility Task Force to develop more specific guidance on low vision
>>>> accessibility related to content (WCAG 2.0) and browsers (UAAG 2.0).[1]
>>>>
>>>>
>>>> The Low Vision Accessibility Task Force home page is:
>>>>
>>>> http://www.w3.org/WAI/GL/low-vision-a11y-tf/
>>>>
>>>>
>>>> The Low Vision Accessibility Task Force expects to:
>>>>
>>>> * Document requirements for low vision users;
>>>>
>>>> * Identify gaps in the above requirements between user needs and how
>>>> they are met by web sites that conform to WCAG 2.0;
>>>>
>>>> * Document sufficient and advisory techniques and failures for WCAG
>>>> 2.0
>>>> to meet low vision user needs;
>>>>
>>>> * Define low vision use cases which user agents need to support;
>>>>
>>>> * Develop an extension to WCAG 2.0 to address low-vision user needs
>>>> effectively;
>>>>
>>>> * Develop support materials to explain the issues and implementation
>>>> of
>>>> the above resources effectively.
>>>>
>>>>
>>>> The Task Force seeks to bring together individuals and organizations to
>>>> contribute to this W3C/WAI work.
>>>>
>>>>
>>>> We *invite you to contribute to the Low Vision Accessibility Task
>>>> Force*.
>>>>
>>>> * Active participation in the Task Force takes about 4 hours per week,
>>>> including teleconferences.
>>>>
>>>> * Participation is through either the WCAG Working Group or the UAAG
>>>> Working Group.
>>>>
>>>> * More about participation is at <
>>>> http://www.w3.org/WAI/GL/low-vision-a11y-tf/#participation>;
>>>>
>>>> If you cannot commit that much time, you can still review draft
>>>> documents.
>>>> To get announcements of drafts for review, see <
>>>> http://www.w3.org/WAI/about/announcements>;.
>>>>
>>>>
>>>> [1] WCAG & UAAG:
>>>>
>>>> * WCAG, the Web Content Accessibility Guidelines, is introduced at <
>>>> http://www.w3.org/WAI/intro/wcag>;.
>>>>
>>>> * UAAG, the User Agent Accessibility Guidelines for browsers and other
>>>> 'user agents', is introduced at <http://www.w3.org/WAI/intro/uaag>;.
>>>>
>>>> Please let us know if you have any questions.
>>>>
>>>>
>>>> Feel free to circulate this message to other lists; please avoid
>>>> cross-postings where possible.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Jim Allan, LVTF Facilitator, UAWG Chair
>>>> Andrew Kirkpatrick LVTF Facilitator, WCAG Co-Chair
>>>>
>>>> Joshue O Connor, WCAG WG Co-Chair
>>>>
>>>> Michael Cooper, WCAG WG Team Contact
>>>> Jeanne Spellman, UAWG Team Contact
>>>>
>>>> --
>>>> [image: http://www.tsbvi.edu] <http://www.tsbvi.edu>;Jim Allan,
>>>> Accessibility Coordinator
>>>> Texas School for the Blind and Visually Impaired
>>>> 1100 W. 45th St., Austin, Texas 78756
>>>> voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
>>>> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
>>>> >>>> >>>> >>>> >>>>
>>>
>>> >>> >>> >>> >>>
>>
>>
>> --
>> Charles McCathie Nevile - web standards - CTO Office, Yandex
>> = EMAIL ADDRESS REMOVED = - - - Find more at http://yandex.com
>>
>>
>> >> >> >> >>
>>
> > > > >


--
Work hard. Have fun. Make history.

From: Léonie Watson
Date: Mon, Aug 24 2015 6:19AM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →

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


Léonie.

--
GDS Accessibility consultant +44.7921168551 @LeonieWatson

From: Jonathan Avila
Date: Mon, Aug 24 2015 7:46AM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →

> Jaws/NVDA in browse mode activate the element's onclick event when enter is pressed with focus on that element (not the onKey events). In application/forms mode howver, the onKey events are triggered when user presses enter.

Correct, and as an FYI to new people -- for other elements (not buttons and anchors) such as divs, adding an onlick and tabindex is not enough to provide keyboard access -- an author would need an onlick and keyboard event handlers to support both the click from a screen reader in browse mode and keyboard access.

Jonathan

--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
= EMAIL ADDRESS REMOVED =

703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R. Gunnarsson
Sent: Monday, August 24, 2015 6:15 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Keyboard behavior with JAWS

Patrick
Jaws/NVDA in browse mode activate the element's onclick event when enter is pressed with focus on that element (not the onKey events). In application/forms mode howver, the onKey events are triggered when user presses enter.
If you change the function trigger to be the onClick event, you should be fine.



On 8/24/15, pratik roy < = EMAIL ADDRESS REMOVED = > wrote:
> Recently, I faced a scenario where keyboard "Enter" key is not
> functioning as expected and we have to press "Alt+Enter" in order to make it work.
>
> 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".
>
> After that, I tried to do console.log() and saw that all key stock
> action is working normally if I press any key with "Alt".
>
> Now, my problem is, I am not sure whether that key combination is
> common for screen reader user or not.
>
> If anyone can share user experience for this kind of senario or a
> solution of this problem, that will be GREAT Help.
>
> Note: All keyboard keys are working fine with role="application" but I
> don't want to make it a application region. :)
>
> Thanks & Regards
> PRATIK ROY
>
> On Sat, Aug 22, 2015 at 11:30 PM,
> < = EMAIL ADDRESS REMOVED = >
> wrote:
>
>> Send WebAIM-Forum mailing list submissions to
>> = EMAIL ADDRESS 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 ADDRESS REMOVED =
>>
>> You can reach the person managing the list at
>> = EMAIL ADDRESS REMOVED =
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of WebAIM-Forum digest..."
>>
>> Today's Topics:
>>
>> 1. Re: WCAG Extensions (Kroon, Kurtis@FTB)
>> 2. Re: WCAG Extensions (Chagnon | PubCom)
>> 3. Re: Developing an Accessibility Team (Kline, Jeff)
>> 4. a few recent links related to CAPTCHA (Jennifer Sutton)
>> 5. Re: W3C-WAI Low Vision Accessibility Task Force - Seeking
>> Participation (Chaals McCathie Nevile)
>>
>>
>> ---------- Forwarded message ----------
>> From: "Kroon, Kurtis@FTB" < = EMAIL ADDRESS REMOVED = >
>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Fri, 21 Aug 2015 18:33:47 +0000
>> Subject: Re: [WebAIM] WCAG Extensions -----Original Message-----
>> From: _mallory [mailto: = EMAIL ADDRESS REMOVED = ]
>> Sent: Thursday, August 20, 2015 10:27
>> To: WebAIM Discussion List
>> Subject: Re: [WebAIM] WCAG Extensions
>>
>> A split? Something that's okay to be somewhat stale for the lawyers
>> and something that is aware of new technology and new needs and new
>> services, for developers, vendors and spec-writers to lean on?
>>
>> [KK]
>> IANAL, but as I understand it, that's how it already works for
>> regulations:
>>
>> "Incorporation by reference of a publication is limited to the
>> edition of the publication that is approved. Future amendments or
>> revisions of the publication are not included."[1]
>>
>> So, once the regulation incorporates by reference, say, WCAG 2.0 as
>> published on 11 December 2008[2], the W3C can extend, update, fold,
>> spindle, or mangle their recommendations (to WCAG ∞) and it won't
>> affect the regulation one jot.
>>
>> I find it interesting that, to my knowledge, no federal agency has
>> decided "Section 508 is getting long in the tooth -- let's use the
>> Equivalent Facilitation clause[3] and choose WCAG 2.0 as our new
>> accessibility standard."
>>
>> Regards,
>>
>> Kurt
>> Web Services
>> Franchise Tax Board
>> State of California
>>
>> Citations:
>>
>> [1]: 1 CFR §51.1(f)
>> [2]: http://www.w3.org/TR/2008/REC-WCAG20-20081211/
>> [3]: 36 CFR §1194.5
>>
>> >> _ CONFIDENTIALITY NOTICE: This email from the State of California is
>> for the sole use of the intended recipient and may contain
>> confidential and privileged information. Any unauthorized review or
>> use, including disclosure or distribution, is prohibited. If you are
>> not the intended recipient, please contact the sender and destroy all
>> copies of this email.
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: "Chagnon | PubCom" < = EMAIL ADDRESS REMOVED = >
>> To: "'WebAIM Discussion List'" < = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Fri, 21 Aug 2015 15:08:06 -0400
>> Subject: Re: [WebAIM] WCAG Extensions Kurt wrote:
>> " I find it interesting that, to my knowledge, no federal agency has
>> decided "Section 508 is getting long in the tooth -- let's use the
>> Equivalent Facilitation clause[3] and choose WCAG 2.0 as our new
>> accessibility standard." "
>>
>> FYI, most federal agencies here in Washington DC don't have a clue
>> what "508" is.
>> Those that do have a 508 policy are lucky and have made some
>> progress, but the political appointees who head up the agencies are still clueless.
>> So it's unlikely they'll make any decision on implementing 508 within
>> their agency in the near future.
>>
>> And now that's it's election season, not much will change for the
>> next 2 years...after the election and new top brass are appointed by
>> the president to head up the agencies. Timeline:
>> Nov 2016, election
>> Jan 2017, inauguration
>> Jan 2018, final appointments of agency heads.
>> June 2018, real work commences at the agencies.
>>
>> Here in DC, we all are just trading water for the next 18-24 months.
>> Same ol' same ol'. On this point, it doesn't matter which party is
>> elected, either.
>>
>> —Bevi Chagnon
>>
>> — — —
>> Bevi Chagnon | www.PubCom.com
>> Technologists, Consultants, Trainers, Designers, and Developers for
>> publishing & communication
>> | Acrobat PDF | Digital Media | XML and Automated Workflows GPO |
>> | Print | Desktop Publishing | Sec. 508 Accessibility | EPUBs
>> — — —
>>
>>
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: "Kline, Jeff" < = EMAIL ADDRESS REMOVED = >
>> To: " = EMAIL ADDRESS REMOVED = " < = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Fri, 21 Aug 2015 19:10:20 +0000
>> Subject: Re: [WebAIM] Developing an Accessibility Team There can be
>> many dimensions to developing an accessibility team and program. It
>> is important to develop the key elements of the program first to
>> understand how and where to effectively staff it.
>>
>>
>>
>> My book on this topic<
>> http://www.amazon.com/Strategic-Accessibility-Organization-Jeff-Kline
>> /dp/1936909189/ref=sr_1_sc_1?ie=UTF8&qid40184031&sr=8-1-spell&keyw
>> ords=strategic+it+accessiiblity> provides insight and guidance on
>> developing such a program. The book is directed primarily and large
>> organizations, but is easily scaled to smaller ones.
>>
>>
>>
>>
>>
>>
>>
>> Jeff Kline
>>
>> Program Director
>>
>> Statewide EIR Accessibility
>>
>> Texas Department of Information Resources
>>
>> Phone 512.463.3248
>>
>> Mobile 512.426.9779
>>
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Dennis Deacon [mailto: = EMAIL ADDRESS REMOVED = ]
>> Sent: Thursday, August 20, 2015 4:54 PM
>> To: = EMAIL ADDRESS REMOVED =
>> Subject: [WebAIM] Developing an Accessibility Team
>>
>>
>>
>> Our organization has been engaged in a digital accessibility
>> remediation project. In parallel, we've also been working on
>> developing an ongoing program.
>>
>>
>>
>> One aspect that we're working on is building an accessibility team.
>> As part of that, we're initially interested in a few things:
>>
>>
>>
>> - Do most companies have a full-time team?
>>
>> - How is the team organized?
>>
>> - How did other organizations get support from management for a team?
>>
>>
>>
>> Any other information on building an accessibility team would be
>> greatly appreciated. Our organization is in the transportation
>> industry with an eCommerce website and mobile app.
>>
>>
>>
>> Thanks in advance.
>>
>>
>>
>> Dennis Deacon
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Jennifer Sutton < = EMAIL ADDRESS REMOVED = >
>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Fri, 21 Aug 2015 17:25:15 -0700
>> Subject: [WebAIM] a few recent links related to CAPTCHA WebAIM list
>> members:
>>
>> Since CAPTCHAS are such a frequent topic on the list, I thought I'd
>> post two resources, below my name, that have been circulating on Twitter.
>>
>> Hope they help.
>>
>> Jennifer
>>
>>
>> 9 CAPTCHA Alternatives That Won’t Wreck Your UX
>> http://www.dtelepathy.com/blog/design/captcha-alternatives-better-ux
>>
>>
>>
>> Captcha Alternatives and thoughts - WCAG WG
>> https://www.w3.org/WAI/GL/wiki/Captcha_Alternatives_and_thoughts
>>
>> Looks like I may have a replacement for my usual post on this topic:
>> In Search Of The Perfect CAPTCHA Smashing Coding
>>
>> http://coding.smashingmagazine.com/2011/03/04/in-search-of-the-perfec
>> t-captcha/
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Chaals McCathie Nevile < = EMAIL ADDRESS REMOVED = >
>> To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >, lcmcevoy <
>> = EMAIL ADDRESS REMOVED = >
>> Cc:
>> Date: Sat, 22 Aug 2015 17:58:57 +0200
>> Subject: Re: [WebAIM] W3C-WAI Low Vision Accessibility Task Force -
>> Seeking Participation On Thu, 20 Aug 2015 05:03:52 +0200, lcmcevoy
>> < = EMAIL ADDRESS REMOVED = > wrote:
>>
>> So glad to hear about this. I’ve felt the needs of low vision users
>> have
>>> been overlooked. Thanks for this Jim.
>>>
>>
>> Indeed, and thank you for reaching out widely.
>>
>> Now to find network so I can join up, and time to do work.
>>
>> cheers
>>
>> Laurie
>>>
>>>
>>> On Aug 19, 2015, at 5:05 PM, Jim Allan < = EMAIL ADDRESS REMOVED = > wrote:
>>>
>>> The W3C Web Accessibility Initiative (WAI) has established a Low
>>> Vision
>>>> Accessibility Task Force to develop more specific guidance on low
>>>> vision accessibility related to content (WCAG 2.0) and browsers
>>>> (UAAG 2.0).[1]
>>>>
>>>>
>>>> The Low Vision Accessibility Task Force home page is:
>>>>
>>>> http://www.w3.org/WAI/GL/low-vision-a11y-tf/
>>>>
>>>>
>>>> The Low Vision Accessibility Task Force expects to:
>>>>
>>>> * Document requirements for low vision users;
>>>>
>>>> * Identify gaps in the above requirements between user needs and
>>>> how they are met by web sites that conform to WCAG 2.0;
>>>>
>>>> * Document sufficient and advisory techniques and failures for
>>>> WCAG
>>>> 2.0
>>>> to meet low vision user needs;
>>>>
>>>> * Define low vision use cases which user agents need to support;
>>>>
>>>> * Develop an extension to WCAG 2.0 to address low-vision user
>>>> needs effectively;
>>>>
>>>> * Develop support materials to explain the issues and
>>>> implementation of the above resources effectively.
>>>>
>>>>
>>>> The Task Force seeks to bring together individuals and
>>>> organizations to contribute to this W3C/WAI work.
>>>>
>>>>
>>>> We *invite you to contribute to the Low Vision Accessibility Task
>>>> Force*.
>>>>
>>>> * Active participation in the Task Force takes about 4 hours per
>>>> week, including teleconferences.
>>>>
>>>> * Participation is through either the WCAG Working Group or the
>>>> UAAG Working Group.
>>>>
>>>> * More about participation is at <
>>>> http://www.w3.org/WAI/GL/low-vision-a11y-tf/#participation>;
>>>>
>>>> If you cannot commit that much time, you can still review draft
>>>> documents.
>>>> To get announcements of drafts for review, see <
>>>> http://www.w3.org/WAI/about/announcements>;.
>>>>
>>>>
>>>> [1] WCAG & UAAG:
>>>>
>>>> * WCAG, the Web Content Accessibility Guidelines, is introduced at
>>>> < http://www.w3.org/WAI/intro/wcag>;.
>>>>
>>>> * UAAG, the User Agent Accessibility Guidelines for browsers and
>>>> other 'user agents', is introduced at <http://www.w3.org/WAI/intro/uaag>;.
>>>>
>>>> Please let us know if you have any questions.
>>>>
>>>>
>>>> Feel free to circulate this message to other lists; please avoid
>>>> cross-postings where possible.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Jim Allan, LVTF Facilitator, UAWG Chair Andrew Kirkpatrick LVTF
>>>> Facilitator, WCAG Co-Chair
>>>>
>>>> Joshue O Connor, WCAG WG Co-Chair
>>>>
>>>> Michael Cooper, WCAG WG Team Contact Jeanne Spellman, UAWG Team
>>>> Contact
>>>>
>>>> --
>>>> [image: http://www.tsbvi.edu] <http://www.tsbvi.edu>;Jim Allan,
>>>> Accessibility Coordinator Texas School for the Blind and Visually
>>>> Impaired
>>>> 1100 W. 45th St., Austin, Texas 78756
>>>> voice 512.206.9315 fax: 512.206.9264 http://www.tsbvi.edu/
>>>> "We shape our tools and thereafter our tools shape us." McLuhan,
>>>> 1964 >>>> >>>> archives at http://webaim.org/discussion/archives
>>>> >>>>
>>>
>>> >>> >>> archives at http://webaim.org/discussion/archives
>>> >>>
>>
>>
>> --
>> Charles McCathie Nevile - web standards - CTO Office, Yandex
>> = EMAIL ADDRESS REMOVED = - - - Find more at http://yandex.com
>>
>>
>> >> >> archives at http://webaim.org/discussion/archives
>> >>
>>
> > > archives at http://webaim.org/discussion/archives
> >


--
Work hard. Have fun. Make history.

From: _mallory
Date: Mon, Aug 24 2015 1:59PM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →

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

From: pratik roy
Date: Wed, Aug 26 2015 11:26AM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →

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

> Send WebAIM-Forum mailing list submissions to
> = EMAIL ADDRESS 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 ADDRESS REMOVED =
>
> You can reach the person managing the list at
> = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> To: = EMAIL ADDRESS REMOVED = , WebAIM Discussion List <
> = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> To: "WebAim Forum ( = EMAIL ADDRESS REMOVED = )" <
> = EMAIL ADDRESS 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 ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
> www.checkoutacollege.com<;http://www.checkoutacollege.com/>;
> www.sbctc.edu<;http://www.sbctc.edu/>;
>
>
>
>
> ---------- Forwarded message ----------
> From: "Léonie Watson" < = EMAIL ADDRESS REMOVED = >
> To: "'WebAIM Discussion List'" < = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> To: " = EMAIL ADDRESS REMOVED = " < = EMAIL ADDRESS REMOVED = >, WebAIM
> Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> To: "'WebAIM Discussion List'" < = EMAIL ADDRESS REMOVED = >, "Léonie
> Watson" < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS REMOVED = - - - Find more at http://yandex.com
>
>
>
> ---------- Forwarded message ----------
> From: Jon Metz < = EMAIL ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS REMOVED = >
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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.
>
>
>
> > > > >
>

From: _mallory
Date: Wed, Aug 26 2015 12:16PM
Subject: Re: Keyboard behavior with JAWS
← Previous message | Next message →

On Wed, Aug 26, 2015 at 10:56:41PM +0530, pratik roy wrote:
> Correct guess!
>
> Our developers are using <div> with tabindex="0" and role="button", so you
> can say these are fake buttons.

Okay, but so you're listening to both events then?

click, keyup? (I use either keyup or keydown, and avoid keypress
like the plague)

_mallory
>
> Thanks & Regards
> PRATIK ROY

> > ---------- Forwarded message ----------
> > From: _mallory < = EMAIL ADDRESS REMOVED = >
> > To: = EMAIL ADDRESS REMOVED = , WebAIM Discussion List <
> > = EMAIL ADDRESS 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

From: Bossley, Pete
Date: Wed, Aug 26 2015 2:47PM
Subject: Re: Keyboard behavior with JAWS
← Previous message | No next message

-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of pratik roy
Sent: Wednesday, August 26, 2015 1:27 PM
To: = EMAIL ADDRESS REMOVED =
Subject: Re: [WebAIM] Keyboard behavior with JAWS

Correct guess!

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

Can you explain why the use of a fake button? A real button would negate the need to manually trap for keyboard interaction...