Slashdot Mirror


Google Accessible Search Released

Philipp Lenssen writes "Google today released Accessible Search, a Google Labs product aiming to rank higher pages which are optimized for blind users. Google asks you to adhere to the W3C's Web Content Accessibility Guidelines if you want to make sure your pages are accessible (and thus, rank better on Google Accessible Search). I wrote a small tool to compare results of default and accessible results."

21 of 134 comments (clear)

  1. Accessible Content by Alexandra+Erenhart · · Score: 5, Insightful

    From the Accessible Search FAQ:

    How can sites make their content more accessible to the blind?

    Some of the basic recommendations on how to make a website more useable and accessible include keeping Web pages easy to read, avoiding visual clutter -- especially extraneous content -- and ensuring that the primary purpose of the Web page is immediately accessible with full keyboard navigation


    I wish more sites where like that. Do you want info? You get it right there, without all the mumbo-jumbo associated with most current websites.

    1. Re:Accessible Content by Igmuth · · Score: 3, Insightful
      Once I saw a site for local elections where there was a link to the part of the site for visually impaired people (large font page),
      Wait... are you saying that they had an entire seperate page that they made simply made the font larger? That is insane. The idea of accessible web pages is that if people need a larger font size, they should be able to select that larger font size in their viewer of choice, and it shouldn't break your page. (I.e. no images as text, etc)
    2. Re:Accessible Content by Ryan+Stortz · · Score: 3, Funny

      I tried searching for Porn and the 5th link down was to this article on the Register that claims Porn makes you blind. :(

      --
      Bugs are just features that have been fixed.
  2. Re:Hmm... by Shimdaddy · · Score: 5, Informative

    Blind people can use screen readers, but if you bury your content in flash or in images without alt text, it makes it very difficult (impossible really) for the screen reader to know what to say. Also, if you position everything in tables and it loads in a weird order but looks right when it hits the screen, it presents problems, since the reader won't know that the 5 rows down actually explains the 3 columns over.

    CSS can help with this, as it keeps the formatting away from the content, but you still have to keep your .html (or .php or whatever) source files nice, clean and logical. A simple test is, if you can read your source file easily (ie in notepad or vi or whatever) then you're probably ok.

  3. At some point it doesn't matter... by MudButt · · Score: 3, Interesting

    I somehow think that a search for "Adobe", "Photoshop", etc. will still give you adobe.com as the #1 result, despite its accessibility problems.

    1. Re:At some point it doesn't matter... by McGiraf · · Score: 5, Funny

      Photoshop, blind, hum ... well

  4. Re:Hmm... by statusbar · · Score: 4, Insightful

    There has been standards for blind web browsing for many years! The problem is that hardly anyone use them, even a lot of government web sites which by law must be accessible.

    The amazing thing is that google, by page-ranking these pages higher, I believe it will do more to improve web accessibility than any law or standards organisation could.

    --jeffk++

    --
    ipv6 is my vpn
  5. one of the best tool ever by mu22le · · Score: 5, Interesting

    I didn't get it initially but this is one of the best tool google ever gave us, most spam sites designer do not care for standards and are left out of the 'accessible' results. I think I'm going to switch to the new sevice soon.

  6. This could backfire by Animats · · Score: 3, Interesting

    With Google's "Accessable search", sites will be able to tell from their weblogs how many visitors are coming in via the "accessable search" route. So it will be possible to figure out the financial benefit of web accessability. If it turns out to be low, even for pages that Google thinks are "accessable", there's a business case for not bothering with "accessability".

  7. w00h00 - text-based search engine by guruevi · · Score: 3, Funny

    Finally I can start using Links2 or even Lynx to start browsing or any other curses based browser... mmm... gopher. Will work perfectly with my pine mail and telnet based IRC.

    I really commend google for providing us and maybe even forcing webdevelopers to use decent, W3C compatible standards. This means soon enough, we'll have websites that aren't IE compatible.

    --
    Custom electronics and digital signage for your business: www.evcircuits.com
  8. Google Accessible in not according to W3C standard by giriz · · Score: 4, Interesting
    --
    I don't want a signature.
  9. Re:Still missing the point. by laffer1 · · Score: 4, Interesting

    It depends. If you actually talk to a blind person, tables aren't as annoying as people using characters between links. For instance, doing navigation with a pipe (vertical bar) or some other character sounds strange to them. I worked for someone who was blind and owned their own business for a time. He said cnet was one of the most annoying web properties for him to use. At the time their navigation sounded terrible and was quite randomly placed. He also didn't like navigation at the top as much except on the first page. Worst of all, he hated hearing. about us vertical bar products veritcal bar etc...

    Oh and he used Internet explorer. His software tied in with that so it looked like an ie hit and even tried to load all the crap everyone else deals with in IE. He did IE on windows using a dell.

  10. Re:Still missing the point. by IdahoEv · · Score: 5, Insightful
    Indeed. Point 5 of the guidelines:
    Tables should be used to mark up truly tabular information ("data tables"). Content developers should avoid using them to lay out pages ("layout tables"). Tables for any use also present special problems to users of screen readers (refer to checkpoint 10.3).

    Even Google's ultra-simple front page violates this guideline, despite zero need to do so.

    Point 3 of the guidelines says this:
    Mark up documents with the proper structural elements. Control presentation with style sheets rather than with presentation elements and attributes.

    But if you dig into the source of google.com, you see cruft like this:
    <br><font size=-1><font color=red>New!</font>
    Google fails rather dramatically to implement any web standard, not even including a doctype. These problems aren't limited to their front page, either. news.google.com is just as bad or worse.

    This is really a shame. The content that google presents is lightweight and free of the layout challenges that can sometimes make web standards difficult to follow: Google should be the perfect test case for perfect standards and accessibility. Instead, it's a throwback to 1996 web design. That they're launching a tool to test accessibility to the blind is incredibly ironic.

    --
    I stole this sig from someone cleverer than me.
  11. Re:What? by illuminix · · Score: 4, Interesting

    My son is blind. He uses the web with a reader, and loves google. He searches for music, among other things. It's pretty amazing how effecient he is with it, given he can't see. Some sites work better than others. It is possible to optimize a site for the blind. You're ignorant.

    --
    http://cubemonkey.net/quotes -- fortune-mod quote generator
  12. Re:What? by Arker · · Score: 4, Insightful

    Optimizing websites for the blind is about as intelligent as optimizing music for the deaf...

    That's utter nonsense. First off, you think blind people can't process information? WTF?

    Second, it's not even about 'optimising for the blind' so much as simply 'using (rather than abusing) the web.' The web was designed from the start to deliver information in a neutral format so that the user-agent (browser) could then deliver that information appropriately. This may mean laying it out on a screen (of unknown dimensions and capability,) or it may mean speaking it aloud, or whatever. Proper web design is accessible to everyone. The errors that make sites inaccessible to the blind are the same errors that make them annoying and sometimes unusable to the rest of us as well.

    Keep in mind that you cannot dictate layout and use html properly and you'll have no problem. Ignore that fact and you shut out a lot of people, not just the blind.

    --
    =-=-=-=-=-=-=-=-=-=-=-=-=-=-
    Friends don't let friends enable ecmascript.
  13. Re:Hmm... by ajs · · Score: 4, Informative

    Flash's accessibility features are not terribly helpful. They don't adhere to any standards, and require you to run particular software (they rely on Microsoft Active Accessibility, for example) to be compatible with them.

    No, before you go around spouting "STFU" at other folks, make sure you're able to back up your claims. Just becuase a company says "our stuff has accessibility features" doesn't mean they DO, or that they are useful to people who would need them.

    PS: I just tried to find out more about their accessibility features, but they use Flash to explain that, and I don't have sound on this machine... kind of useless.

  14. For Thruly accessible webpages by guabah · · Score: 3, Interesting

    The w3c check is not an acurate measure on how thruly accessible the pages are

    I now this because I have friends who are blind and frecuently use screen reader applications

    If you really want to make sure your pages are accessible then download the trial version of Jaws for Windows wich is the defacto standard screen reader. This trial is limited to 40 minutes per session, but those 40 minutes should be enough to test your webpages.

    As mentioned in posts above, make sure the content can be reaced quickly by readers.

    1. Re:For Thruly accessible webpages by Bogtha · · Score: 4, Insightful

      The w3c check is not an acurate measure on how thruly accessible the pages are

      I now this because I have friends who are blind and frecuently use screen reader applications

      Yes and no. On the one hand, WCAG does have acknowledged shortcomings and it's certainly no guarantee. But aural browsers and screenreaders tend to be absolutely awful when it comes to supporting the markup that's intended to help them. They aren't designed to read accessible websites, they are designed to scrape as much meaning as they can out of inaccessible websites.

      So from a practical perspective, yes, you need to test in individual assistive user-agents if you want your website to be as usable as possible by disabled people. But when the markup is fine according to the W3C and assistive user-agents get it wrong, it's usually because the developers of the assistive user-agents haven't even heard of the W3C.

      --
      Bogtha Bogtha Bogtha
  15. Re:Hmm... by Dasaan · · Score: 3, Interesting

    Which raises an interesting point. What would happen if Google were to rank pages with valid html slightly higher that pages that don't validate properly?

    --
    XP is basicly 98 with a lot more extra features to hunt down and disable. --Dram
  16. Re:What? by Rifter13 · · Score: 3, Informative

    When I worked for Albertsons.com, we accidently created a site that worked well for the blind, and even received some recognition for it. After the initial release of the site, and finding out how some blind people were using it, we actually had a lady talk to our develoment staff about optimizing the site even further, which we did.

    It is a VERY good feeling to have, when someone that is in their 40s tell you how grateful they are for your service, since it is the first time in her life, she was able to actually shop for groceries. Adding alt text to images, that TELLS people what the image is, is a huge help. It is very simple things, that you do in HTML to make it possible. If you go in aiming to create well-formed HTML, you are about 80% there, by default.