W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2000

Re: How do I use CSS to fake a button?

From: Charles McCathieNevile <charles@w3.org>
Date: Mon, 24 Jul 2000 22:14:43 -0400 (EDT)
To: webmaster@dors.sailorsite.net
cc: Dave J Woolley <DJW@bts.co.uk>, w3c-wai-ig@w3.org
Message-ID: <Pine.LNX.4.20.0007242213540.13651-100000@tux.w3.org>
Well, it depends what the browser is - some are seriously broken to the point
of not being able to render accessible content. But in general I would say
that if the content is unreadable it is not accessible...


On Mon, 24 Jul 2000, Bruce Bailey wrote:

  Allow me to restate the question from a side conversation Dave and I have
  Can a page/site which is WCAG AAA compliant consider itself "accessible" even
  though the default rendering with a popular browser turns the intended content
  into useless hash?
  Dave J Woolley wrote:
  > > From: Bruce Bailey [SMTP:bbailey@clark.net]
  > >
  > >
  > > look at the source of http://www.dors.state.md.us/mrc/programs.html and
  > > http://www.dors.state.md.us/mrc/kiosk.css and tell me how I might get text
  >         [DJW:]
  >         This breaks quite badly on NS4.5.  Off list correspondence
  >         suggests that this was intended as a "best viewed on
  >         WebKiosk v.v" page, rather than a "best viewed on Any
  >         Browser"  <http://www.anybrowser.org/> one.
  >         The question was raised as to whether there was any duty
  >         on accessible content authors to author for anything other
  >         than fully compliant browsers.  (I believe that the lack of
  >         these means it is.)

Charles McCathieNevile    mailto:charles@w3.org    phone: +61 (0) 409 134 136
W3C Web Accessibility Initiative                      http://www.w3.org/WAI
Location: I-cubed, 110 Victoria Street, Carlton VIC 3053
Postal: GPO Box 2476V, Melbourne 3001,  Australia 
Received on Monday, 24 July 2000 22:14:46 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:35:57 UTC