WebAIM - Web Accessibility In Mind

E-mail List Archives

Keyboard behavior with JAWS

for

From: pratik roy
Date: Aug 24, 2015 4:04AM

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 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. 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 REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Cc:
> Date: Fri, 21 Aug 2015 18:33:47 +0000
> Subject: Re: [WebAIM] WCAG Extensions
> -----Original Message-----
> From: _mallory [mailto: <EMAIL 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 REMOVED> >
> To: "'WebAIM Discussion List'" < <EMAIL 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 REMOVED> >
> To: " <EMAIL REMOVED> " < <EMAIL 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 REMOVED> ]
> Sent: Thursday, August 20, 2015 4:54 PM
> To: <EMAIL 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 REMOVED> >
> To: WebAIM Discussion List < <EMAIL 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 REMOVED> >
> To: WebAIM Discussion List < <EMAIL REMOVED> >, lcmcevoy <
> <EMAIL 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 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 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 REMOVED> - - - Find more at http://yandex.com
>
>
> > > > >
>