1jadelennox
I'm always vaguely say "oh dear! Librarything is less accessible than it can be!" without ever listing specific bugs. I like the suggestion of setting up a wikithing, but I don't want to do that in the wrong place, so for now, I just want to track some accessibility problems, and I will do it here in talk.
These are features I can't access at all in my screen reader (Dragon NaturallySpeaking) except by doing the extremely painstaking mouse movement commands:
* choosing the number of stars with which to rank a book. (Until recently, this didn't work in the library list, but worked in the edit details page because it was a drop-down. Now the edit details pages using the same JavaScript as the library list, and I can't set star rankings anymore.)
* Applying the "favorite" star to a talk topic
* Save any changes in the latest revision of the edit worked and edit book pages. There is something going on with the "save" and "cancel" buttons: they are not normal selectable links, and they seem to require a mouse click. I haven't looked at the code yet but I assume there is some JavaScript happening here.
* change from the book details to the work details tab, and vice versa. Again, these aren't normal selectable links. JavaScript again, I assume.
There's nothing inherent in JavaScript or AJAX that prevents you from doing these same features while still allowing accessibility.
(To be fair, I should point out one thing which has been fixed -- choosing an alternate cover for a book, either Amazon provided or member uploaded, used to be inaccessible, and now that's accessible. Thanks!)
These are features I can't access at all in my screen reader (Dragon NaturallySpeaking) except by doing the extremely painstaking mouse movement commands:
* choosing the number of stars with which to rank a book. (Until recently, this didn't work in the library list, but worked in the edit details page because it was a drop-down. Now the edit details pages using the same JavaScript as the library list, and I can't set star rankings anymore.)
* Applying the "favorite" star to a talk topic
* Save any changes in the latest revision of the edit worked and edit book pages. There is something going on with the "save" and "cancel" buttons: they are not normal selectable links, and they seem to require a mouse click. I haven't looked at the code yet but I assume there is some JavaScript happening here.
* change from the book details to the work details tab, and vice versa. Again, these aren't normal selectable links. JavaScript again, I assume.
There's nothing inherent in JavaScript or AJAX that prevents you from doing these same features while still allowing accessibility.
(To be fair, I should point out one thing which has been fixed -- choosing an alternate cover for a book, either Amazon provided or member uploaded, used to be inaccessible, and now that's accessible. Thanks!)
2Polyphemus
@jadelennox
Call me rash, but in the absence of guidance I went ahead and started accessibility as a WikiThing page. Please check it out and let me know if you think it suits our needs. Other than assigning a priority your observations in the previous post could almost be pasted directly into my proposed format.
I'm not a wikier really, so I'm sure things could be organized better. Please feel free to suggest or make any structural improvements.
Call me rash, but in the absence of guidance I went ahead and started accessibility as a WikiThing page. Please check it out and let me know if you think it suits our needs. Other than assigning a priority your observations in the previous post could almost be pasted directly into my proposed format.
I'm not a wikier really, so I'm sure things could be organized better. Please feel free to suggest or make any structural improvements.
3Polyphemus
@jadelennox
I've added all of your observations from message 1 into the accessibility page of wikithing
http://www.librarything.com/wiki/index.php/Accessibility
I've edited and summarized in spots, so please correct me if I've over-stepped. Also, please look at my priority guesses for your reported problems and adjust them to match your true level of concern. Thanks so much for your collaboration
I've added all of your observations from message 1 into the accessibility page of wikithing
http://www.librarything.com/wiki/index.php/Accessibility
I've edited and summarized in spots, so please correct me if I've over-stepped. Also, please look at my priority guesses for your reported problems and adjust them to match your true level of concern. Thanks so much for your collaboration
4jadelennox
@Polyphemus
I never said, but thank you so much for doing this. I will modify in wikithing -- the recent UI changes have made some things better and some things worse, as could be expected.
I never said, but thank you so much for doing this. I will modify in wikithing -- the recent UI changes have made some things better and some things worse, as could be expected.
5FLCC-library
Hello, I'm trying to find a way my library can continue using the library thing widgets within springshare's libguides. They are currently not compliant with the web accessibility update and require alt text be added to the cover images. I have been unable to find anything or anyway of accomplishing this. Looking for any advice.
