Re:How to create content that works well with screen readers
by sedachv on Sunday April 09, 2017 @04:54PM
(#14074307)
Until version 12, the Opera web browser had a menu with a big list of CSS override styles that worked like Firefox's Reader View. Some were for page development/debugging, some emulated small screen devices, and a lot were there to improve readability. I have good vision and used the Opera CSS overrides and still use Firefox Reader View frequently because many web pages are poorly accessible even for people without disabilities. When Opera went to the WebKit rendering engine the CSS overrides were removed. I still miss them.
Re:How to create content that works well with screen readers
by houst0n_ on Saturday April 08, 2017 @09:23PM
(#14069979)
I can't remember the last time firefox 'reader view' didn't work for me.
Do you really need to go down those roads this often(serious)?
I'm really not trying to call you on anything; but would you mind sharing some example links where it don't work so we can fix it?
I can't find a single example which doesn't work currently. Things have really improved recently.
What I routinely can't or maybe just won't read on ff reader view thigh are forums/hn comments.
Re:How to create content that works well with screen readers
by greenyoda on Saturday April 08, 2017 @09:56PM
(#14070051)
You might like the "Dark Background and Light Text" add-on for Firefox:
https://addons.mozilla.org/en-US/firefox/addon/dark-backgrou...
Unlike Reader View, it lets you pick any combination of colors that you like.
Re:How to create content that works well with screen readers
by mwcampbell on Sunday April 09, 2017 @12:57PM
(#14073179)
As someone with low vision myself, I appreciate your point. However, have you considered just using a screen reader to read any significant amount of prose? That's what I've done for the past 12 years or so. I still use my eyes when reading and writing code, though.
Having done this for countless times, I started thinking as to why I need to do this (obviously given my condition). Why do I have to write a user CSS? Because like Firefox's Reader View, computers could do heuristics at best and when they fail a human has to tell computers which part of a page is text. Why does someone have to figure it out? Because HTML does not contain that information (except for pages that adapt HTML5 semantic tags).
I wish HTML were a bit more restrictive and a page couldn't be designed arbitrarily. For example, if the "Hyper Text" were a lightweight markup language like Markdown or reStructuredText rather than HTML, my life would have been much easier. Some people might say it would be too restrictive. But I have to point out that the standard way of transmitting text, which is by encoding a character to a code point with some character set, is already restrictive when compared with handwriting. We abandoned the freedom to draw characters arbitrarily for communicating machine- (and thereby visually-impaired-) friendly. Because we use character codes to transfer text, we can use any font we like almost everywhere with little effort. I just want the same thing to have happened in the Web.