Re: Issue 964 in lilypond: check website accessibility

[lilypond]

Comment #4 on issue 964 by percival.music.ca: check website accessibility
http://code.google.com/p/lilypond/issues/detail?id=964

"where should it go" - I don't know.  The style sheet wasn't used as an  
alternate style sheet in the html.  Do screen reader programs automatically  
look for a css file called "text-to-speech.css" and process that,  
regardless of what the HTML page says the style sheet is?  I suppose that's  
possible, although I consider it a bit unlikely.

What this issue needs, most of all, is somebody to care about  
accessibility.  Go read about the topic.  Submit patches to  
lilypond-texi2html.init or the itely files as necessary.  If it's useful,  
then do whatever modifications the text-to-speech.css needed, make sure  
it's used, etc etc.

I'll note that there's no need for a blind person to investigate this, of  
course.  I'm sure that there's open-source text-to-speech browsers  
available for linux (and thus under lilydev)... and this could be a really  
interesting project for anybody who was interested in web standards or  
accessibility or being nice.  Maybe good resume fodder?

ETA: 10-20 hours.  I'm guestimating that anybody looking into this should  
spend 5-10 hours reading about this topic in general, and then 5-10 hours  
producing doc build patches.  Maybe compile the website, put it somewhere  
special, and ask other people to review it using text-to-speech web  
browsers.