Please note that "screen readers" and "readers without JavaScript" aren't in any way the same thing -- modern screen readers hook into "real browsers" like IE, Safari, Chrome, and Firefox and JavaScript runs just great in them.
Serious accessibility concerns should really be referred to someone who's an expert... do we have anybody on staff or volunteer who has real, direct, current experience with vision-impaired users and their needs?
-- brion
On Wed, Apr 24, 2013 at 11:51 AM, Pau Giner pginer@wikimedia.org wrote:
Also, did you think of the accessibility issues in your solution?
First, I want to clarify that the prototype was made just to communicate the idea in terms of interaction. The The implementation is just a quick hack to simulate this interaction.
For a production implementation I can image the whole list of languages to be sent to the client, and then, the list being shortened by Javascript. For those users without Javascript (from screen-readers, to Search engine crawlers) the same list of links they receive now will be available for them.
In any case, developers could provide even better strategies to solve that. As an interaction designer I just wanted to share the idea to collect possible concerns with the interaction proposed, to be fixed in next iterations of the designs before development effort is made.
On Sat, Apr 20, 2013 at 2:04 AM, Mathieu Stumpf < psychoslave@culture-libre.org> wrote:
Also, did you think of the accessibility issues in your solution? Here I especialy think of people with view disabilities, for who js often mean no way to get the content, while a long list of hyperlinks is manageable.