- From: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>
- Date: Tue, 24 Aug 2010 14:11:35 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: Ian Hickson <ian@hixie.ch>, James Craig <jcraig@apple.com>, Jonas Sicking <jonas@sicking.cc>, Joshue O Connor <joshue.oconnor@cfit.ie>, HTML Accessibility Task Force <public-html-a11y@w3.org>, HTML WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>, Barry McMullin <barry.mcmullin@dcu.ie>, Laura Carlson <laura.lee.carlson@gmail.com>
On 24 Aug 2010, at 10:39, Julian Reschke wrote: > On 24.08.2010 02:31, Ian Hickson wrote: >> ... >> There was no way, prior to hidden="", to initially hide the application >> page (which is useless until the user is logged in). Authors used >> display:none to fake this, but that has poor accessibility results; for >> example, it means any user agent without CSS support would see the content >> that was intended to be hidden. >> ... > > So do you expect UAs to be released that do not support CSS but *do* support the new hidden attribute? If it gets standardized and UAs like Lynx continue to be developed, why wouldn't we expect this? Note the very same advantage applies to UAs that implement CSS but allow users to reject the author's CSS, a critical accessibility feature exposed by some popular browsers (e.g. Firefox and IE). -- Benjamin Hawkes-Lewis
Received on Tuesday, 24 August 2010 13:12:27 UTC