- From: Shane McCarron <ahby@aptest.com>
- Date: Mon, 25 Feb 2013 11:08:17 -0600
- To: Robin Berjon <robin@w3.org>
- Cc: Julian Reschke <julian.reschke@gmx.de>, Stéphane Corlosquet <scorlosquet@gmail.com>, "spec-prod@w3.org" <spec-prod@w3.org>
There are elements in HTML5 that are not present in earlier versions of HTML. To the extent those elements have semantics non-modern user agents will not be able to faithfully reproduce those semantics. The section element is a perfect example. IE6 will not know what to do with a section element. Screen readers will not know what to do with it. Textual document processors such as the Perl module HTML::Tree will also fail to properly interpret the element. Over time these sorts of things will hopefully become less important, but today they remain issues. On Mon, Feb 25, 2013 at 9:35 AM, Robin Berjon <robin@w3.org> wrote: > On 25/02/2013 16:29 , Julian Reschke wrote: >> >> On 2013-02-25 16:24, Shane McCarron wrote: >>> >>> On Mon, Feb 25, 2013 at 9:12 AM, Robin Berjon <robin@w3.org> wrote: >>>>> >>>>> I guess HTML4+RDFa might be. I will start lobbying for that now. >>>> >>>> >>>> I'll lobby for HTML5+RDFa, no point in downgrading perfectly fine >>>> markup! >>> >>> >>> The problem with it is that, while it may work in modern user agents, >>> it does not in legacy user agents. And it does not in screen readers. >>> And lots of other technology out there that we just don't encounter >>> every day. The constituency of the W3C is broader than people who run >>> the latest version of Chrome. >> >> >> It probably would be helpful if you gave a concrete example of a tool >> that won't be able to properly display the text. > > > Indeed, if this is true that's a serious bug in either HTML5, RDFa, or both. > Concerned spec writers need to know! > > > -- > Robin Berjon - http://berjon.com/ - @robinberjon -- Shane P. McCarron Managing Director, Applied Testing and Technology, Inc.
Received on Monday, 25 February 2013 17:08:46 UTC