37

As a blind user of both Stack Overflow and Server Fault I was wondering if any thought has been given to making the sites more accessible? Most things work well enough such as asking and answering questions, but some things are not accessible such as upvoting comments. It would also be nice if there were headings or another quick way to jump from answer to answer.

  • 1
    Also see meta.stackexchange.com/questions/20108/… for a similar question. – Aaron Sep 23 '10 at 19:11
  • 1
    My answer there also includes a bookmarklet that sort of fixes the problem, though it's a very bad way to fix it. The only way to really fix it is to have the SO folks update their code. – Aaron Sep 23 '10 at 19:12
5

It's extremely difficult for us to judge a site's accessibility. I'd say the thing to do is to outline the problems you've observed in good detail, and post each one as a separate question on Meta Stack Exchange.

  • 1
    diveintoaccessibility.org – John Topley Jul 14 '09 at 14:34
  • 7
    I'm making use of something better than a book: an actual person who knows the shortcomings of SO's accessibility. It's like the difference between using a browser compatibility chart and firing up Opera. – Hilarious Comedy Pesto Jul 14 '09 at 14:37
  • Of course, but there are still a set of principles that you can follow as a starting point. – John Topley Jul 14 '09 at 14:42
  • 1
    @JohnTopley The site Dive Into Accessibility no longer exists; the domain has been for sale for some time now. – user800 Sep 25 '16 at 15:49
3

Good point. Too often we forget about the visually-impaired. I spent a couple months working on revamping a client's website after spending 10 or so minutes on the phone with a man who uses jaws to surf the web.

1

I was just wondering about this as I was trying to manipulate parts of SO pages in conkeror and having some troubles due to the markup that is used in places, particularly in comments. I installed a screen reader, but must confess I don't know anything about them so I couldn't really judge how well it worked. The general idea of making things more usable in a screen reader seems fairly straight forward however. As John Topley pointed out, Dive into Accessibility is a pretty quick read that points out easy ways to improve in this area, such as adding summaries to tables.

0

Only a "read out loudly" feature would not be sufficient (though it is necessary one).

To make the site friendly to blinds / people with severe visual impairment / deaf-blinds peoples; it needs something more.

You'll need also a

  • sound indicator, when the mouse pointer enters at a definite field / icon / button. In cases of toolbar, icons, buttons, hyperlinks you need to read-out loud the name of button.

  • accessibility to all sorts of Braille touch-monitor and braille printers

  • accessibility to a vibrator, in cases of a phone/ any other gadget provide a vibration system. It would work similar as sound-indicators of icons, buttons and borders.

  • audio guide for all help articles, notifications, warnings etc.

  • tutorial links about Braille, especially for guides/ companions/ parents/ teachers of the blind or deaf-blind person.

  • Also for normal monitor, each paragraph (English) along with a Braille transcript (printable in normal printer) especially for guides/ assistants/ parents/ teachers of the blind person, to assist better.

Those who do not want these features; would be able to turn off or on it.

Agree; the responsibility is not much of SE-network; but the responsibilities go more to the browser and system-softwares publishers and hardware manufacturers to make the entire Earth more disabled friendly; but SE developers may keep a concern to design the site with additional supports and increased hardware access capability.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .