Accessibility Wishlist
From Dreamwidth Notes
Revision as of 01:37, 17 February 2009 by Jadelennox (Talk | contribs)
- Have a question/option at signup which can funnel people into an area that asks about accessibility needs and shows them what's available for different accessibility needs.
- For extra shininess, if somebody uses the audio version of the captcha select this option automatically.
- Clear and accessible instructions on signup page on what to do if you can't complete the captcha for journal creation.
- On all styles, have alt text for all images.
- Have a style which uses CSS to hide text alternatives for all icon links, so "select link by name" works for tools which can't use alt text for that.
- Maybe I'm being thick headed, but I don't understand this. Using CSS to hide text alternatives for what specific purpose? Maybe including an example here would help, because this sounds like something that needs to be addressed by the developer of the tools "which can't use alt text for that". Is this a common problem? I'm not a blind user. I'm just hoping to understand this problem better. --Textish 01:21, 17 February 2009 (UTC)
- (should we move this to the discussion page?) It's a keyboard control thing, not a blind accessibility thing. Actually, users with visual-impairment screen readers won't have an issue with this one, because those screen readers will correctly let you select alt text to go to image-only links. The problem is if you do your computer control entirely by the keyboard,and certain functionality is only accessible via image links, there needs to be a way to access the image links via the keyboard. Obviously, the correct way to do this is in the browser: Firefox does it right; Opera doesn't do it but has an open bug ticket; Internet Explorer doesn't do it and probably never will because Microsoft hates disabled people; I have no idea about Safari. But CSS-hidden textual links will allow keyboard access to those image-only controls on browsers which don't otherwise give access via alt text. This isn't necessary on all functions, but for one style which gets as much accessibility functionality as possible crammed in there it would be awfully nice.
- Maybe I'm being thick headed, but I don't understand this. Using CSS to hide text alternatives for what specific purpose? Maybe including an example here would help, because this sounds like something that needs to be addressed by the developer of the tools "which can't use alt text for that". Is this a common problem? I'm not a blind user. I'm just hoping to understand this problem better. --Textish 01:21, 17 February 2009 (UTC)
Jadelennox 01:37, 17 February 2009 (UTC)