Our objective is to create a format that is sufficiently stable that it won't need a fallback solution.
SVG is incredibly consistant from machine to machine, much more so than HTML. Can you give me an example of a case where fallback would be necessary (leaving aside questions of accessibility)?
Semantic markup is an issue for search engines, but we are building websites for people to read.
Visitors to a website never see the tags. They have no idea if something is <h1> or <div> or <strong>.
Are you suggesting that semantic markup is important for people, or for Google? Is this purely an accessibility issue (I don't mean to diminish the importance, it's just a question)?
Our plan is to automatically create parallel content for accessibility requirements, including semantic information. Sort of like the <noscript> tag, an imaginary <nosvg> tag.
If you feel like I am missing the point of semantic markup, I would love to know why, (or you can just post a link).
The reason to use semantic markup is precisely because you don’t know what you want to do with the data after the fact. If you, for instance, make all quotes italic, and also emphasize words using italic, how would you later find all the quotes (maybe to verify their authenticity or create source links)? You can’t, since you have hidden the semantic meaning (emphasis or quote) behind a visual style (italic). Non-semantic markup loses information which you originally had when creating the document, and you might need that information later.
Of course, semantic markup is also turning out to be very important for accessibility reasons, since the things people are really needing from a document is its semantic content, and its visual style can be discarded if necessary.
> Our plan is to automatically create parallel content for accessibility requirements
I don’t know. “Separate but equal” seldom works out well.
Our objective is to create a format that is sufficiently stable that it won't need a fallback solution.
SVG is incredibly consistant from machine to machine, much more so than HTML. Can you give me an example of a case where fallback would be necessary (leaving aside questions of accessibility)?
Semantic markup is an issue for search engines, but we are building websites for people to read.
Visitors to a website never see the tags. They have no idea if something is <h1> or <div> or <strong>.
Are you suggesting that semantic markup is important for people, or for Google? Is this purely an accessibility issue (I don't mean to diminish the importance, it's just a question)?
Our plan is to automatically create parallel content for accessibility requirements, including semantic information. Sort of like the <noscript> tag, an imaginary <nosvg> tag.
If you feel like I am missing the point of semantic markup, I would love to know why, (or you can just post a link).