W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2016

RE: keyboard and IE 11

From: Bolena, Zachary <Zachary.Bolena@Schwab.com>
Date: Thu, 22 Sep 2016 12:34:43 +0000
To: "davebest@cogeco.ca" <davebest@cogeco.ca>, "'Roger Hudson'" <rhudson@usability.com.au>, "'WAI Interest Group'" <w3c-wai-ig@w3.org>
Message-ID: <62053ADD3023B54AADE56C4B4B327E27574A42D4@NEX3002CDC.us.global.schwab.com>
We use IE11 as a standard since our analytics reflect this being the most used browser by our audience.  So I am constantly working to make various custom controls work with IE11 along with other browsers.

In my experience Chrome or Firefox are more forgiving with code than IE. Especially with custom controls or controls created from frameworks like Angular or Bootstrap. There is no real answer when it comes to having a custom controls work in all browsers and with all screen readers. I always preach using a native control whenever possible. I will always test in various browsers and try to get a similar result.

Losing focus order can be a big issue when coding custom controls.  Especially if you come across a site out in the wild there can be all kinds of bad coding practices and where keeping a consistent focus order is not something the developers thought about within their code structure.


Thank you,
Zach Bolena


From: David Best [mailto:davebest@cogeco.ca]
Sent: Thursday, September 22, 2016 7:08 AM
To: 'Roger Hudson'; 'WAI Interest Group'
Subject: RE: keyboard and IE 11

Roger, it could be because there is a moving carousel on the page. Try turning off Page Updates in your screen reader user preferences.

From: Roger Hudson [mailto:rhudson@usability.com.au]
Sent: September 22, 2016 02:17 AM
To: 'WAI Interest Group'
Subject: keyboard and IE 11

Hi Group,

I can across an interesting issue today which I hope someone might be able to help with.

I was using a site containing an iframe with the keyboard and I.E. 11. I was able to enter the iframe and navigate the content of the iframe, but when I tabbed away from the last focusable item in the iframe focus appeared to go the next link down the page. However, the next tab returned focus to the first focusable item on the page (skip link at the top) so I was unable to tab beyond the iframe to the rest of the content on the page.

When I tried the page with Chrome or Firefox this problem didn't happen.

I also tried the page with NVDA, keyboard and IE 11 and the problem happened.

Is this a  known IE 11 bug? Or, can anyone offer any other suggestions?

Thanks,

Roger

Roger Hudson
Web Usability
Mobile: 0405 320 014
Phone: 02 9568 1535
Web: www.usability.com.au<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.usability.com.au&d=CwMFAg&c=Ezx-H5PgBrUMEEvxgJuTQRYrd-4D8l8I18qkZZzJQbo&r=gfIcoH9AOzWzA6hyAsR7zIoc3exAOSNc5ep43e0oO18&m=WvNM7F3ZkSMgLK3xb8u-w_IGi5C3FQ8RM_x4iVN4mRo&s=c5mHsydg4R6v7RkIl34h9iiVLqvdzau8Jsy2-vp46qs&e=>
Blog: www.dingoaccess.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.dingoaccess.com&d=CwMFAg&c=Ezx-H5PgBrUMEEvxgJuTQRYrd-4D8l8I18qkZZzJQbo&r=gfIcoH9AOzWzA6hyAsR7zIoc3exAOSNc5ep43e0oO18&m=WvNM7F3ZkSMgLK3xb8u-w_IGi5C3FQ8RM_x4iVN4mRo&s=undD5vB1IFi8q-hkNdEanR2u4vnEdt_7pPAifBaf5M8&e=>
Twitter: http://twitter.com/rogerhudson<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_rogerhudson&d=CwMFAg&c=Ezx-H5PgBrUMEEvxgJuTQRYrd-4D8l8I18qkZZzJQbo&r=gfIcoH9AOzWzA6hyAsR7zIoc3exAOSNc5ep43e0oO18&m=WvNM7F3ZkSMgLK3xb8u-w_IGi5C3FQ8RM_x4iVN4mRo&s=vnr46d6VPO8R33PT08rBgtL9b_0X6lFjf62asGI4-x4&e=>
Email: rhudson@usability.com.au<mailto:rhudson@usability.com.au>
Received on Thursday, 22 September 2016 12:36:30 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 22 September 2016 12:36:30 UTC