> -----Original Message----- > From: Ryan Nichols > Really a browser doesn't understand what any of the tags are. What you > see are only the browsers default behavior at rendering certain items > it's aware of in the DTD. This was all put in by whoever made the > browser, and is totally up to the browser. Default renderings are not > specified in W3C. This is the forward view of browser-to-document > relationships. All these default behaviors can be overridden by > supplying your own rendering rules (css).
You missed my point, but maybe it was just me being cryptic. I'm not talking about the *visual rendering* (default or otherwise, which yes of course can be changed to your heart's content via CSS). What I mean by *understand* is that certain elements trigger behaviours that go well beyond the mere visual aspects, and particularly in conjunction with assistive technology etc you need to stick to an established, agreed syntax. An example: let's say I dream up my own custom DTD which defines the elements ARTICLETITLE and ARTICLESTRAPLINE. I define some CSS to make them *visually* render like H1 and H2 would by default. Great, appearance wise it works as it should (in modern browsers anyway). However, if I'm using a screenreader on top of my OS, and - on a page using this custom DTD - I select the outline view (which lists the document structure by looking at the headings), I get back nothing because the browser and screenreader do not *understand* that ARTICLETITLE and ARTICLESTRAPLINE are structural elements that effectively denote headings for sections on the page. The same kind of thing would also apply, of course, to search engines: they would accept your custom elements (heck, they wouldn't care at all of course), but would treat them as they would any other plain text, not adding any extra weighting to anything because it's a title/heading/etc simply because they don't understand the custom elements defined in the DTD. *That's* what I'm going on about. Visually, yes...you can do whatever you want with your own elements. But for them to actually be useful, they need to stick to an agreed syntax whose rules (for all intents and purposes) have been hardcoded into a browser or user agent. Patrick ________________________________ Patrick H. Lauke Webmaster External Relations Division Faraday House University of Salford Greater Manchester M5 4WT Tel: +44 (0) 161 295 4779 e-mail: [EMAIL PROTECTED] webteam: [EMAIL PROTECTED] www.salford.ac.uk A GREATER MANCHESTER UNIVERSITY ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
