W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > June 2007

UA bug on object

From: WCAG 2.0 Comment Form <nobody@w3.org>
Date: Mon, 25 Jun 2007 18:37:19 +0000 (GMT)
To: public-comments-wcag20@w3.org
Message-Id: <20070625183719.860EDBDAE@w3c4.w3.org>

Name: Aurélien Levy
Email: aurelien.levy@free.fr
Affiliation: tektonika
Document: UW
Item Number: Understanding Success Criterion 2.1.1
Part of Item: Techniques
Comment Type: technical
Summary of Issue: UA bug on object 
Comment (Including rationale for any proposed change):
I think the G21 technique is partially wrong because for most of the case it\'s an UA, plugin or  AT manufacturers problem not an author probem. 

For example, actually Firefox don\'t provide a way to navigate with keyboard trough a Flash object. the only way to achieve this is to click on it with the mouse and then click outside the flash to get the focus out. 

It\'s a Firefox bug not an author mistake, yes the author can hack this bug by providing a link before the flash and then use javascript and actionscript to move focus in and out of the flash element but what if javascript is turned off ?

Yes the users must not be trapped in the content, but for me it\'s just applicable in the case where the plugin or UA provide a way to access it (in and out) with the keyboard. So, it\'s more : don\'t break the UA or plugin feature to access plugin element otherwise the user can be trapped in the element. 

For exemple, at this time, for Flash element, it\'s equal to test that with IE the user can go trough the flash element without be trapped, with other browser i haven\'t to test it because they don\'t provide a way to trough the flash element with keyboard without the mouse (for Firefox, Safari and Opera at least)

Proposed Change:
Received on Monday, 25 June 2007 18:37:31 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:14:44 UTC