- From: Justin James <j_james@mindspring.com>
- Date: Tue, 28 Oct 2008 08:09:19 -0400
- To: "'David Poehlman'" <david.poehlman@handsontechnologeyes.com>, "'Schnabel, Stefan'" <stefan.schnabel@sap.com>, "'Laura Carlson'" <laura.lee.carlson@gmail.com>, "'HTML WG'" <public-html@w3.org>, "'Steve Faulkner'" <faulkner.steve@gmail.com>, "'W3C WAI-XTECH'" <wai-xtech@w3.org>, 'aurélien levy' <aurelien.levy@free.fr>
Agreed. Most of the griping I hear from authors about one browser or another not being "HTML compliant" comes from the assumption that the HTML spec defines rendering, simply because a few web browsers render something one way, and the other browsers render it differently. The reality is, the HTML spec does not define UA behavior, and for good reason: HTML doesn't know what the UA's capabilities are, nor does it care, or even matter. J.Ja > -----Original Message----- > From: public-html-request@w3.org [mailto:public-html-request@w3.org] On > Behalf Of David Poehlman > Sent: Tuesday, October 28, 2008 6:56 AM > To: Schnabel, Stefan; Laura Carlson; HTML WG; Steve Faulkner; W3C WAI- > XTECH; aurélien levy > Subject: Re: [LIKELY JUNK]Re: title/alt attribut keyboard accessibility > > > I'm not getting the distinction here. What is the speciality of title > that > it should be singled out in this way and Why should it be done here > rather > than in aria or uaag? What is important is that anything done be > device > agnostic and device type agnostic as well otherwise, we need a fallback > cascade which might be difficult to speck. > > > ----- Original Message ----- > From: "Schnabel, Stefan" <stefan.schnabel@sap.com> > To: "Laura Carlson" <laura.lee.carlson@gmail.com>; "HTML WG" > <public-html@w3.org>; "Steve Faulkner" <faulkner.steve@gmail.com>; "W3C > WAI-XTECH" <wai-xtech@w3.org>; "aurélien levy" <aurelien.levy@free.fr> > Sent: Tuesday, October 28, 2008 3:55 AM > Subject: RE: [LIKELY JUNK]Re: title/alt attribut keyboard accessibility > > > We need a UA-specific hotkey for displaying the content of the title > attribute > in the same separate (yellow) popup window as for the mouseover > operation. > > HTML5 spec definitely should be more precise + complete here. > > In Lynx the "title" content could be displayed e.g. in Lynx status area > on > request. > > - Stefan > > -----Original Message----- > From: wai-xtech-request@w3.org [mailto:wai-xtech-request@w3.org] On > Behalf > Of Laura Carlson > Sent: Dienstag, 28. Oktober 2008 00:39 > To: HTML WG; Steve Faulkner; W3C WAI-XTECH; aurélien levy > Subject: [LIKELY JUNK]Re: title/alt attribut keyboard accessibility > > Steve Faulkner <faulkner.steve@gmail.com>, W3C WAI-XTECH <wai- > xtech@w3.org> > > Aurélien Levy wrote [1]: > > >> Is it possible to have something in the spec to say that the way of > >> rendering the content of the title/alt attribut must be non specific > to > >> a certain type of pointing device or is it to the UAAG spec to say > >> something like that ? > > Ian Hickson wrote [2]: > > > Right now HTML5 doesn't say that user agents should do anything with > this > > information. The non-normative rendering section will probably > suggest > > current behaviour but hasn't been written yet. (Volunteer editors > welcome; > > see the e-mail from earlier today.) > > Related: Steve Faulkner's June 6, 2008 bug report "User Agent display > of title attribute content not defined": > http://www.w3.org/Bugs/Public/show_bug.cgi?id=5807 > > Best Regards, > Laura > > [1] > http://lists.w3.org/Archives/Public/public- > html/2008Oct/thread.html#msg131 > [2] > http://lists.w3.org/Archives/Public/public- > html/2008Oct/thread.html#msg134 > > -- > Laura L. Carlson
Received on Tuesday, 28 October 2008 12:10:13 UTC