Hi Andreas,
Indeed, if SBG is tagged correctly, it is easy for adaptive technology to be able to read it. Tagging involves using the title attribute to label elements. See http://www.viewplustech.com for examples of accessible SVG.
Pranav -----Original Message----- From: Andreas Neumann [mailto:a.neumann@...2251...] Sent: Friday, May 31, 2013 12:22 PM To: inkscape-user@lists.sourceforge.net Subject: Re: [Inkscape-user] svg for web pages.
Hi,
I wouldn't recommend doing an SVG only website.
But the accessibility of SVG is way better than the one from Flash. The one is a binary, frame based format, the other is text-based markup that humans, machines, search engines and screen readers can read. I have seen screen readers for the blind where Apache Batik was used to make SVG charts and maps accessible to the blind and visually impaired by providing tactile and acoustic feedback.
True - SVG screenreaders are not yet embedded in browsers by default, but if more people would use SVG on the web, it would encourage browser developers to improve the accessibility of SVG documents. Technically (from a format point of view) there are no accessibility problems with SVG - but implementation wise and maybe also from author guidelines things could be improved.
I would use SVG along with HTML, each for its strength. Interactive graphics, apps, charts and maps with SVG, documents with lots of text and navigation with HTML, backgrounds, gradients and decorations (e.g. for bullet lists) can be done in SVG in modern browsers.
Andreas
On Fri, 31 May 2013 08:20:11 +0200, Maarten van der Velde wrote:
An all-SVG site: well, If only for the 'sake of argument' and 'proof of concept'... yeah, why not? Good idea!
But I still don't understand the original question. What do you mean with " I am wondering about the use of a site map." → How to build a sitemap in SVG? Or, what should be the navigation-structure of the site be?
Or: what CMS supports all-SVG websites :)
?
On Fri, May 31, 2013 at 2:39 AM, Steve Litt wrote:
On Thu, 30 May 2013 17:50:10 -0400
john Culleton wrote:
On Thu, 30 May 2013 17:11:48 -0400 Steve Litt wrote:
On Thu, 30 May 2013 08:37:51 -0400 john Culleton wrote:
I am planning to convert one of my web sites to all-svg. I am wondering about the use of a site map. Is it the same as for
an
html site (with different names of course)?
John, are you saying there will be no HTML on your website,
only
SVG?
Why?
SteveT
Perhaps because it can be done. I built a subdomain and put just
an
index.svg file on it and it worked. Now I am not religous about
this.
If there is a good reason for using html wrapped around an svg
entity
I may do that. Can you think of a good reason?
My main reason is that HTML is good at its job...
- Separates meaning from style (via CSS etc)
- Very easy to hand code in an editor
- Worldwide standard
Against that backdrop, what would be the compelling reason to have a website *exclusively* built with SVG? Obviously SVG is good for the images, and for links in the images if that can be done, and video, etc, but I'm not sure why one would forgo the ease and adaptability of HTML.
By the way, I'm starting to use SVG images on my websites. Often direct from Inkscape, with the Inkscape metadata still in them. They render well with all my browsers (but I don't use IE). See this:
http://www.troubleshooters.com/bookstore/larrymap/larrymaps.htm [4]
Thanks,
SteveT
Steve Litt * http://www.troubleshooters.com/ [5] Troubleshooting Training * Human Performance
Get 100% visibility into Java/.NET code with AppDynamics Lite It's a free troubleshooting tool designed for production Get down to code-level detail for bottlenecks, with
Links:
[1] mailto:John@...1668... [2] mailto:slitt@...2357... [3] mailto:John@...1668... [4] http://www.troubleshooters.com/bookstore/larrymap/larrymaps.htm [5] http://www.troubleshooters.com/ [6] http://p.sf.net/sfu/appdyn_d2d_ap2 [7] mailto:Inkscape-user@lists.sourceforge.net [8] https://lists.sourceforge.net/lists/listinfo/inkscape-user [9] mailto:slitt@...2357...