Doug, I'm really concerned about your claims to understand accessibility and intentions to update the 2000 SVG guidelines.
please understand that my comments are intended to help understanding of SVG accessibility. inline comments: >>the logo will be distinctive, simple, and elegant. the image http://www.w3.org/Graphics/ ---------- is unlikely to be described in these terms simplicity is not necessarily an indication of humanity or homeliness, more usually evidence of reductionist belief systems frequently and no doubt mistakenly associated with those having pseudo-scientific tendencies :-) >>since this is intended for print and rasterization as well as SVG- format viewing, the logo will not have sound providing sound has nothing to do with whether the logo will be printed, obviously there is no expectation that the printed logo will sound. afaik providing sound for SVG1.2 has no known downside for other technologies. >>nor will there be interactivity nor focus Why not? if the logo is used as a link it should provide visual feedback when in focus, or at least the place it is embedded in should. This was the purpose of hover and border in html. >>The best way to achieve accessibility for a logo such as this is to have a text fallback, sorry this is just plain wrong, text is but one approach, which happens to suit a vocal and able minority. text is also an accessibility bonus. not as a fallback, but as a visible label. Very few people have access to a screen reader, let alone one that works with any sort of SVG, they tend to be very expensive. cheers Jonathan Chetwynd On 4 Sep 2006, at 22:24, Doug Schepers wrote: Hi- As Ronan points out, the logo is meant to be more of a symbol than an interactive document, and I can assure you that the logo will be distinctive, simple, and elegant. Since audio is only available in SVGT1.2+, and since this is intended for print and rasterization as well as SVG-format viewing, the logo will not have sound, nor will there be interactivity nor focus (or rather, the default initial focus will be on the root). The best way to achieve accessibility for a logo such as this is to have a text fallback, which has always been the plan. The <title> and <desc> of the final logo will contain the necessary textual information such that a screen-reader will be able to provide a voiced interpretation. This will be in a language-based <switch> to allow for many translations. I will note that this is innately much more accessible than a raster logo, which apart from its file name has no inherent text equivalent. Regards- -Doug Ronan Oger wrote: > Jonathan, > > Maybe you could propose some metadata, maybe 20-60 characters' worth? > > Other than that, I doubt we can have that much accesibility support given that > it has to be a lowest-common-denominator-svg logo, in other words it needs to > be static, all in the same unit set and work with svg1.0 and svgt1.1. > > But in the end, how exactly are we meant to implement this PR graphic? > > I guess the recommended practice will be to either add it as an image within > our svg at the end of the document, or as an inline group? > > As far as choice of graphics goes, the ones I have seen are generally quite > nice. I agree with you though that a simple, clean graphic is the best. > > Hopefully we won't end up with a flaming, pulsating, rotating SVG logo... ;-) > > Ronan > > On Sunday 03 September 2006 09:55, Jonathan Chetwynd wrote: > a> please could others express there thoughts regarding their >> preferences for a logo? >> >> as to my own, read on: >> >> Yesterday Stelt asked me on IRC if I was entering the SVG Logo Contest. >> >> I replied that I rather thought not as I liked the current W3C >> graphics logo >> ---------- >> >> as used here http://www.w3.org/Graphics/ >> >> which I find humane and homely unlike much technology which can be >> hard and cold. >> >> it was suggested that it wasn't interactive, and I agreed that >> cowboys.svg has much to commend it, though it isn't a logo. >> >> overnight it occurred to me that as a minimum I would naturally >> require a logo to be accessible. >> which might for instance mean that for me there - must - be some >> visual feedback to tell the user which element in the logo has focus, >> there should also be audio, keyboard tabbing, text equivalent and more. >> >> cheers >> >> Jonathan Chetwynd [Non-text portions of this message have been removed] ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
