- From: Michael Stenitzer <jenoe.stenitzer@gmail.com>
- Date: Fri, 28 Nov 2008 09:39:09 +0100
- To: "WAI Interest Group" <w3c-wai-ig@w3.org>
i'm sorry, but i have to disagree strongly. we are preparing accessible websites for people and not for standards. as long as there are ways to make a certain information accessible, usable and understandable with techniques that are supported by browsers and AT we should certainly choose those techniques. eg. the LONGDESC attribute does not help anybody (and i also see potential usability problems with this). therefore: don't use it but place a visible link for a detailed image description right after the image. concerning the AXIS attribute: there are other standard conformous ways and techniques to make a table accessible. use those. (BTW: usually the best one is to simplify a table structure as much as possible. this also helps without a screenreader. you might be surprised how difficult it is for many users to understand tables). just my 2 cents, michael On Thu, Nov 27, 2008 at 8:58 PM, Joachim Andersson <joachim.andersson@etu.se> wrote: > The usefulness is not really the issue. I understand that this might seem > strange, but developing according to W3C standards does not only concern the > time being, but the time to come. Hopefully Jaws and other tools used to > convey web based information will improve in upcoming versions, but at this > time they do not fully conform to W3C recommendations and specifications. > > Think of it this way. If web developers produce services according to W3C > specifications and recommendations, one day Jaws and other tools will render > web based content as it was meant to be rendered. That is when we get the > real use of it, and now is the time to develop this way, in order not to be > one step behind when Jaws reaches that goal. > > Best regards, > > Joachim Andersson > Web Accessibility Specialist > > 2008/11/27 Ramón Corominas <listas@ramoncorominas.com> >> >> Dear all: >> >> I've been reading a lot about the use of "axis" attribute to categorize >> and group cells, but I also have read that its support is almost inexistent. >> Does anyone know if this attribute is going to be supported in the near >> future? or perhaps in the distant future...? <wink> >> >> I've tested it with JAWS and nothing happens, so I'm confused about its >> real usefulness. >> >> Thanks in advance, >> Ramón. >> > > -- Michael Stenitzer | WIENFLUSS information.design.solutions
Received on Friday, 28 November 2008 08:39:45 UTC