- From: Sam Ruby <rubys@intertwingly.net>
- Date: Tue, 09 Oct 2012 15:03:01 -0400
- To: Paul Cotton <Paul.Cotton@microsoft.com>
- CC: Edward O'Connor <eoconnor@apple.com>, "public-html-a11y@w3.org" <public-html-a11y@w3.org>, Richard Schwerdtfeger <schwer@us.ibm.com>
On 10/09/2012 02:43 PM, Paul Cotton wrote: > Ted > > Richard’s email below asks for an additional change related ISSUE-204. > Can you reply and or let us know if you are planning to make the > suggested change? This is not related to issue 204, and Richard has now opened a separate bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=19405 > /paulc > > Paul Cotton, Microsoft Canada > 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 > Tel: (425) 705-9596 Fax: (425) 936-7329 - Sam Ruby > *From:*Richard Schwerdtfeger [mailto:schwer@us.ibm.com] > *Sent:* Wednesday, October 03, 2012 6:05 PM > *To:* Edward O'Connor > *Cc:* public-html-a11y@w3.org > *Subject:* Re: Review of Section 7.1 by ARIA working group in PF > > > Rich Schwerdtfeger > > "Edward O'Connor" <eoconnor@apple.com <mailto:eoconnor@apple.com>> wrote > on 10/02/2012 07:03:48 PM: > >> From: "Edward O'Connor" <eoconnor@apple.com <mailto:eoconnor@apple.com>> >> To:public-html-a11y@w3.org <mailto:public-html-a11y@w3.org>, >> Date: 10/02/2012 07:04 PM >> Subject: Re: Review of Section 7.1 by ARIA working group in PF >> >> Hi Rich, >> >> You wrote: >> >> > 1. We read this text and we don't believe this text was agreed upon by >> > anyone and we have doubts this is enforceable[…] >> >> This text predates the ISSUE-204 discussion; in fact, it's been in the >> spec since March 2010: >> >>http://html5.org/r/4846 >> >> > From an accessibility perspective it does not really hurt us[…] >> >> OK. Given that, can you live with that paragraph it currently stands? If >> not, would it help if the example were changed from screen readers to, >> say, printers? >> > yes, if you were to change this to printers that would be excellent! > >> > 2. […] I don't have an issue with it[…] >> >> OK. >> >> > 4. This text refers to content being active but what is not clear is >> > whether "active" hidden text would appear in the tab order. We don't >> > believe that is the case but it needs to be stated somewhere. >> >> OK. Do you have suggested text to make that clear? > > Yes. I would suggest changing the following text: > > "Elements in a section hidden by the hidden > <http://dev.w3.org/html5/spec/editing.html#the-hidden-attribute> attribute > are still active, e.g. scripts and form controls in such sections still > execute and submit respectively. Only their presentation to the user > changes." > > To: > Elements in a section hidden by the hidden > <http://dev.w3.org/html5/spec/editing.html#the-hidden-attribute> attribute > are still active, e.g. scripts and form controls in such sections still > execute and submit respectively. Only their presentation to the user > changes. Although active, content hidden by the hidden > <http://dev.w3.org/html5/spec/editing.html#the-hidden-attribute> attribute is > not focusable and does not participate in sequential focus navigation. > > >> > For example, what happens when you have <div tabindex="0" hidden>. >> > Does the div appear in the tab order? >> >> Did you try that in browsers? What happened? >> > > Yes, I tried it using Firefox and Chrome and both skipped the hidden > div. Safari (Version 6.0.1 (7536.26.14)) on Mac OSX did not allow me to > tab to any of the active elements whether they were visible or hidden. I > am not sure why. hidden does not appear to work in IE9.0.8. Perhaps > there is a mode I need to select. > > /(See attached file: hiddenactive.html)/ >> >> Thanks, >> Ted >> >
Received on Tuesday, 9 October 2012 19:03:32 UTC