Quote:
Originally Posted by vermontcathy
What difference does it make what the back-end code looks like, as long as it looks good on the kindle?
|
Accessibility, for one thing.
Replacing elements that have semantic meaning (like H1 and EM) with generic elements (like DIV and SPAN) results in accessibility issues. Text-to-speech won't have the clues it needs to do the right thing.
Also, this is not about "looking good on a Kindle", as the EPUB isn't intended to be used on a Kindle...it's intended to be used on other devices. Because of that, it should maintain the proper elements.
Amazon doesn't seem to have a problem creating KF8 files that use appropriate HTML elements, so why should this EPUB output be any different?