Room for Improvement
Join LibraryThing to post.
This topic is currently marked as "dormant"—the last message is more than 90 days old. You can revive it by posting a reply.
The early stages of exploring any innovative environment with a screen reader can have a pretty steep learning curve. At first it's hard to know what is a true access problem, and what is simply a new (but totally usable) interface. As I become more familiar with lt, I'm getting better at understanding where the accessibility problems truly lie. Now I'm ready to start cataloging the problems, but I want to do it in as productive a way as possible. What's the best place and form for such a list:
* A new topic here in this group?
* An entry in wikithing?
Is there a start on such a list somewhere that I can review to avoid duplication? I couldn't find any entries related to accessibility in wikithing.
Section 508 Amendment to the Rehabilitation Act of 1973
Some reading material. Might not affect LT. Don't know if a membership by a Federal entity constitutes a contract. I'M NO LAWYER
Yes. Thanks for that. I'm not a lawyer either, but I'm not really getting at legality.. I'm more interested in real-world accessibility where there are specific features of lt that don't work with sr's due to lack of labels/alts, or because you just plain can't find them. As above, I'd like to log them somewhere and I'm hoping more experienced lt users can steer me in the right direction as to what would be most constructive and in keeping with existing practices here. Do you have any thoughts on this? Thanks!
Personally, I think a page about known accessibility problems in the Wikithing would be great since more people can work on them together and things can be 'crossed off' as the site improves.
It would be great to have Tim's input though. Have you thought about sending him a message?
I agree with you that a page in the wikithing would be a great idea. Tim reads this Topic -- or at least he used to -- so he will probably pop in if he still has time to follow these things.
too bad the code isn't open source, and that we could work on the accessibility problems ourselves and propose fixes to LT that way.
(These days, my biggest accessibility problem with the site is the fact that the ui keeps changing, so all the macros I have written to navigate around the book pages keep breaking, and I don't know where anything is. Which is only a little bit more difficult than it would be if I didn't have accessibility issues, I suppose, because I still wouldn't know where anything is.)
I do read this.
I've got to go in five minutes, so I'm not going to get into this too deeply. But I want to do what I can in the "order of pain." I know that being fully accessible is not going to happen any time soon. The best standards of accessibility take time and effort, and I have to pick my battles. We're stretched very thin as it is.
Would it help if there was a Wikithing page that listed accessibility problems, categorized by severity? That way it would be easier to spend your precious time on the stuff that will make the most impact.
Perhaps the wikithing could even include some 'suggested solutions' to make it even simpler to implement. I'm sure there are some quick fixes that will emerge that way. Some other stuff will be harder to fix but lets take it one step at a time.
I think it would. In general, I find bug lists a drain on my time, but this is a specific domain, and one I don't know well enough.
We can start it conversationally, of course.
Hi, all, nice to meet you. OK. I'm happy to start posting content if someone else will tell me where to put it on wikithing. Thanks for the constructive and rapid resolution.
It looks like jadelennox has started posting accessibility problems in a talk topic. Should I jump in on that, or will someone tell me where I should start logging my suggestions in wikithing. I'd really rather do it in a wiki form so that it's easier to organize and edit. I'm just a little tentative about deciding on its proper location because I know avid wikiers are quite particular about where things go, and I don't want my message to be damned due to its misplacement in the medium.
This topic is not marked as primarily about any work, author or other topic.