View Single Post
Old 05-02-2019, 05:04 PM   #20
elibrarian
Imperfect Perfectionist
elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.elibrarian ought to be getting tired of karma fortunes by now.
 
elibrarian's Avatar
 
Posts: 679
Karma: 863576
Join Date: Dec 2011
Location: Ølstykke, Denmark
Device: none
I've no intention of starting a long and esoteric discussion, but reading the latest posts here I can't help thinking, that we're inventing obstacles where none are to be found.

I can't find anywhere any indication whatsoever that it should be "bad" to style <Hx>-elements with css or having to hide them. But I can find tons of examples of what to do with them in css …

And I know, that an empty Hx tag would be real bad for search engine optimization, if it occured on a "real" webpage. In an epub, it will pass epubcheck, but ACE will generate an error "Element does not have text that is visible to screen readers …"

Just my 2 ¢ thoughts …

Regards,

Kim
Kim
elibrarian is offline   Reply With Quote