W3C home > Mailing lists > Public > public-html@w3.org > September 2007

Re: @title's relation to accessibility

From: David Poehlman <poehlman1@comcast.net>
Date: Thu, 6 Sep 2007 14:48:23 -0400
Message-ID: <00df01c7f0b6$8117c040$0601a8c0@HANDS>
To: <public-html@w3.org>, <wai-xtech@w3.org>, "Sander Tekelenburg" <st@isoc.nl>

Thank you Sander.

----- Original Message ----- 
From: "Sander Tekelenburg" <st@isoc.nl>
To: <public-html@w3.org>; <wai-xtech@w3.org>
Sent: Thursday, September 06, 2007 8:37 AM
Subject: Re: @title's relation to accessibility



At 08:40 -0400 UTC, on 2007-09-05, David Poehlman wrote:

> What can the html wg do to make browsing on bad browsers better?

Nothing.

But we can try to define HTML5 such that it's likely that next versions of
that browser will be better. Meaning: make HTML5 such that it will actually
be implemented correctly by browser UAs.

> [...] Is there a way to help authors with this type of transform?

Unfortunately authors already apply every trick in the book to cicrumvent
known browser bugs. Thus hiding thise bugs from users, thus users not 
putting
pressure on the browser vendor to fix those bugs. (Well, this is my view. 
Not
everybody agrees :))

> Can code prevent uas from doing bad things?

Only in the sense that when as an author you know that a certain 
construction
triggers a certain browser bug, you can try to use an alternative
construction instead. But in practice that often leads to tricks that in 
turn
introduce other problems.


-- 
Sander Tekelenburg
The Web Repair Initiative: <http://webrepair.org/>
Received on Thursday, 6 September 2007 18:48:27 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:49 UTC