Lock Fonts in eReaders

[ownedbycats]

Originally Posted by JSWolf

And if an image is used instead of text, it will not be a pleasant reading experience.

Inaccessible to those using screenreaders (or possibly dyslexic-friendly fonts) too.

[JSWolf]

@Ken_Moorhead I have to say that your testing is not working well. You also need to test with various eInk Readers such as Kobo & Kindle. They can perform differently then you think. The programs are not the same.

As for using h1-h4 in the main text, don't. h1-h4 are for headers. Regular text in the main text should be using <p> with or without classes.

As for colors, don't. They don't work well with eInk screens that don't support color.

[theducks]

Originally Posted by ownedbycats

Inaccessible to those using screenreaders (or possibly dyslexic-friendly fonts) too.

Screen readers use ALT tags. The coder should indicate the words shown on the image (and not just 'Image').

[Ken_Moorhead]

@Quoth - Thank you. Everything you said is what I pretty much suspected. Especially the part about <p> and classes.

@Ned - Understood and I can see that. For what it's worth, I've abandoned the idea.

[Quoth]

Originally Posted by JSWolf

As for colors, don't. They don't work well with eInk screens that don't support color.

Very often they won't give expected contrast on the few niche color eink that do exist. The color eink is really for comics. Terrible for coloured text.
Also colour may have unexpected consequences in "Dark Mode" which different phones and tablets may do differently, or may be kludged by an App.

[Quoth]

Originally Posted by Ned

I must admit I'm not keen on the author/publisher telling me what font to use - I prefer my own, and will edit any 'enforced' font rather than read in it.

Yes, unlike paper the advantage of ebooks is changing things done by publishers that you don't like. The ebook should be tested with generic defaults (without embedded enabled) and embedded fonts treated as a suggestion.