Hi, Jonathan- Jonathan Chetwynd wrote: > > I'm really concerned about your claims to understand accessibility > and intentions to update the 2000 SVG guidelines.
I never claimed to understand every issue involving accessibility, nor do I think you or any one person does either. This is why I will be working with Chaals and the WAI IG to try to reach the broadest possible set of accessibility needs. > >>the logo will be distinctive, simple, and elegant. > the image http://www.w3.org/Graphics/ > ---------- > > is unlikely to be described in these terms But my description does fit an ideal format for an iconic logo, which is meant to do 2 things: 1) serve as an indicator of necessary browser functionality; 2) help establish a "brand identity" for SVG. I'm sorry that this logo contest does not serve your agenda. May I suggest that you consider running a contest of your own, which emphasizes the qualities in SVG art that you are looking for? > >>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. Most people would find an audio component annoying, and would not use it on their site. If you want to submit a suitable sound clip, however, I will consider adding it to logo site as an optional addition. > >>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. It's extremely annoying that you clipped off the part of my reply that deals directly with your concern, then accused me of not addressing it: "(or rather, the default initial focus will be on the root)". I invite you to read the SVGT1.2 spec and disabuse yourself of the notion that there is no indicator of focus. [1] > >>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. This is too vague to supply any criteria for accessibility, beyond your vocal complaints. > 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. There will be a visible text component as well, which you would know if you read the svglogo.com Web site. However, because Firefox does not yet implement SVG Fonts, some of the "letters" may just be graphics... and that is what the text fallback is for. [1] http://www.w3.org/TR/SVGMobile12/interact.html#specifyingfocushighlight Regards- -Doug ----- 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/
