- From: <bugzilla@jessica.w3.org>
- Date: Sun, 03 Oct 2010 17:55:17 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10963
Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bhawkeslewis@googlemail.com
--- Comment #1 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2010-10-03 17:55:16 UTC ---
(In reply to comment #0)
> Tables are used extensively in most Widget libraries (like Dojo) for layout in
> order to get fidelity across browsers that authors cannot achieve through the
> use of CSS.
I'm not opposed to replacing the text "users of accessibility tools like screen
readers" with a rubric like "users of older accessibility tools that do not
support ARIA", but …
Can clients that do not support CSS present the users with the same content and
functionality? Can users still access all content and functionality when they
reject the author's styles in favour of their own preferences? Can users easily
reformat content that uses tables for layout with CSS or abstractions on top of
CSS, as required by WCAG2 1.3? I'm not convinced, but can you point to some
examples that demonstrate these properties?
If so, then it might be okay to allow tables to be used as layout aids *only*
when annotated with role="presentation".
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 3 October 2010 17:55:18 UTC