- From: Leif H Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Tue, 18 Sep 2012 21:00:28 +0200
- To: mjs@apple.com
- Cc: silviapfeiffer1@gmail.com, joshue.oconnor@cfit.ie, john@foliot.ca, faulkner.steve@gmail.com, public-html-a11y@w3.org
Maciej Stachowiak > Sendt: 18/9/'12, 19:04 > On Sep 18, 2012, at 4:41 AM, Silvia Pfeiffer >> Would browser vendors resist such a paragraph and the implied >> implementation consequences? > > Whether or not vendors would agree with such a paragraph in the spec, > I'll leave that to vendor reps. But I think adding this text would not > make it any more likely that vendors would implement a UI to access > longdesc. Context menu is a long-known technique for longdesc support > which has clearly not caught on in mainstream UAs. The "turn the image > around" idea is handwavey to the point of uselessness. > > In addition to issues with these specific suggestions, keep in mind that > a previously raised concern with longdesc is that the corpus of available > longdesc content in the wild appears to have very high level of bad > content. While folks may disagree on the merits of this argument, it seems > unlikely that a clever UI idea would change anyone's mind about the wisdom > of exposing the existing longdesc corpus to users. > > So while I appreciate the constructive engagement, it seems unlikely to > be very persuasive to browser vendors. It does not seem to me that their > past key concerns were based on lack of UI ideas. So what are their concerns? Do they view fundamental thought is bad? Or do they view the HTML4 feature as not sufficiently specified, and thus that it has failed because authors did not know how it was supposed to function. (clearly there is evidence of that). I.e. the impact of lack of implementations, is important to the longdesc supporters. But not to the vendors? Leif
Received on Tuesday, 18 September 2012 19:01:30 UTC