Accessibility wishlist suggestions

[cesy]

I was just looking at the Accessibility Wishlist on the wiki, and noticed several good ideas.

"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."
How would this be done? What should the question be, and should it just take them to a FAQ, or something else? I'll write this up for dw_suggestions once we've got a clearer idea.

"On all styles, have alt text for all images."
Do we have any styles that don't at the moment?

"Make sure all forms on the site follow accessibility guidelines for screenreaders."
Do we have bugs open for all of these, or are there more bugs we need to open?

For the documentation wishlist on the second half of the wiki page, has this been brought to the attention of the docs team at any point?

Comments

[jeshyr]

I don't think the docs team have been told about the documentation wishlist, no.

The other questions, I'm unsure. I'm pretty sure all the system styles (celerity, tropo, etc.) have proper ALT tagging but the official journal styles may not if they add their own images - somebody needs to ask the styles team about that.

Forms, no idea.

The funnel at signup was my idea, and I was thinking of something fancier than a FAQ really. Too tired to type it up tonight, ask me again in a day or two?

r

[jadelennox]

1. we started talking about some of the documentation/FAQ-type questions in a recent post in this community, but didn't get very far. I'm not sure what the question should be, but I think it should point to a page of documentation that covers some of that stuff that I linked in the wiki (note that not all of the suggestions people made have been incorporated into that list yet). And no, it has not been brought to the attention of the documentation team at any point. I'm not sure what I was waiting for.

2. For the most part, no, although I still have a couple of open bug fixing some of the alt text issues.

3.The primary open bug for this issue at the moment is the wai-ari a bug, but that doesn't cover general forms best practices. I'm not sure if there is a bug for that one; if there is, it should be in their tagged accessibility. The first part of such a bug would be writing out a specification for what that would mean, and probably putting it up here for debate, because one thing I'm learning from the webaim mailing list is that there is controversy about what best practices for forms really means.