denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise
Was thinking about the alt text for user icon heads and how we could change them to be better and more natural for screenreaders. I've opened bug 2037; the first comment says:

The userhead icon alt is [info - user] and the community is [info - community].
Change to [user profile] and [community profile] for more natural flow in
text-to-speech.

I'm trying to check that this is a change that would be useful. A friend of mine who uses a screenreader says that "user profile" and "community profile" would be the best mix of clarity and brevity and that the best thing to do is to make the first word the key word. But I wanted to post here to make sure that I haven't overlooked anything.

Thoughts?
[personal profile] rho
Hello wonderful accessibility team!

We're in the process of designing an entirely new FAQ system at the moment, and one of the things that I'm keen to do is make sure that we have accessibility considerations built in from the start. Unfortunately, I'm not at all knowledgeable when it comes to accessibility, so I don't know what we need to be looking at. If you could go take a look at this entry from [site community profile] dw_docs where I have a first draft version of the specifications for the new system up, I'd appreciate it. I need to know:

1. What of the current spec will be bad for accessibility.
2. What of the current spec have I managed to get right, accessibility-wise.
3. What have I just not thought of at all that needs to be added in.

Thanks!
jadelennox: Oracle with a headset: Heroes Use Headsets (gimp: heroes use headsets)
[personal profile] jadelennox
I've made a modified version of the account creation page in order to address bug 1016. I've tested it with JAWS 10 and nVDA, but I know my experience testing as a sighted user is imperfect and doesn't really produce the experience of knowledgeable full-time screen reader users.

I'd love to get several testers trying out this page, with only a multitude of testers with a variety of tools. Because the new page uses WAI-ARIA accessibility encoding, it will have extra features that are only available to people using the newest tools(for example JAWS 10). However, it should still be reporting accurate errors for people using screen readers that don't have WAI-ARIA functionality.

If you are a screen reader user, I would love it if you test that page. Try a bunch of things. Try to create accounts both correctly and incorrectly. Try to create accounts with bad passwords or usernames you've already used. Let me what works and what doesn't!

(You should know something I discovered to much frustration during testing: if you test to make sure that it insists you be over 13 based on your birthday, and then you try again with a much older birthday, the system has a timeout to make sure that you aren't just gaming the system and changing the year of your birth.)

Let me know how the tests go, and tell me what screen reader/operating system/browser combination you are using.

Thank you so much!
jeshyr: Standrd glyphs representing disability, blindness, interpreters and information. (Disability)
[personal profile] jeshyr
I'd like to put together a list of all the stuff in Dreamwidth that's aimed at making us more accessible - so everything from "We have a diversity statement" to "Alt text for user icons" to "comment threads easier to navigate because of semantic HTML" to (eventually) "guides available to teach users to use browser accessibility functions themselves".

I don't think there's a list in one place of all the improvements that have been made which relate in some way to accessibility for any group.

Ones I can think of:

- Alt text for user icons
- Diversity Statement (which goes with "our volunteers care about accessibility")
- "Other" option in gender field
- Layout of HTML in comment threads is semantic now, which makes them easier to navigate with a screen reader and some other accessibility software..
- We've made the format=light and style=mine options more widely known and easier to use by putting them on the navbar.
- Readers have more control over their viewing experience - eg if they don't want the navbar then they can turn it off globally.

What other improvements have people noticed in accessibility while reading and using Dreamwidth?

Ricky
Page generated Mar. 23rd, 2017 04:11 pm
Powered by Dreamwidth Studios