Comment #6 on issue 964 by philehol...@googlemail.com: check website
accessibility
http://code.google.com/p/lilypond/issues/detail?id=964
But the stylesheet still needs to be included in the HTML to make the
speech browser load it. It doesn't just look for one in the same directory
calle
Comment #5 on issue 964 by paconet@gmail.com: check website
accessibility
http://code.google.com/p/lilypond/issues/detail?id=964
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 sh
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
Comment #3 on issue 964 by paconet@gmail.com: check website
accessibility
http://code.google.com/p/lilypond/issues/detail?id=964
What direction should this progress towards? I thought the stylesheet just
had to be present.
___
bug-lilypond
Comment #2 on issue 964 by philehol...@googlemail.com: check website
accessibility
http://code.google.com/p/lilypond/issues/detail?id=964
A start was made on creating a text-to-speech stylesheet (called
text-to-speech.css) but this was never progressed. To keep the CSS
directory clean I'
Comment #1 on issue 964 by pnorcks: check website accessibility
http://code.google.com/p/lilypond/issues/detail?id=964
These are the authoritative references:
http://www.w3.org/TR/WCAG10/
http://www.w3.org/TR/WCAG20/
--
You received this message because you are listed in the owner
or CC fields
Status: Accepted
Owner:
Labels: Type-Other Priority-Postponed website Frog
New issue 964 by percival.music.ca: check website accessibility
http://code.google.com/p/lilypond/issues/detail?id=964
It would be nice if we complied with web accessibility standards -- do we
need to have descriptiv
