The WorldWide Web Consortium (W3C), in May 0f 1999, issued
Well, one purpose is to communicate your site content to blind search engine spiders, which can't hear auditory content either. If only we would pay attention to the W3C, the web would be fully accessible to all and completely search engine friendly. Hindsight and attention to historical web developments might serve to make us aware that SEO and accessibility are interwoven. Yes, SEO, as we'll discuss a bit more below. But first, let's look a bit closer at the W3C guidelines on accessibility. The idea is to allow those using assistive devices, or those with javascript disabled to navigate a web page easily and without the need of a mouse, using alternate methods to move through and activate links on the page. When using text only readers, web-enabled cell phones and other small screen devices it's not always possible to easily access and activate web page content.
Those guidelines recommend that web developers"Use features that enable activation of page elements via a variety of input devices."
There have been a few high-profile cases which should have served as wake-up calls for accessibility to online business."In 1999, the National Federation of the Blind (NFB) sued America Online, claiming it discriminated against the blind because its system is not accessible to them. The federation later dropped the lawsuit when AOL agreed to make its software compatible with devices designed for visually impaired users."
The above quote appeared in a
That CNet story was written after a law suit was filed against Southwest Airlines because the Southwest.com web site was not accessible to visually challenged web surfers using "screen reader" technology to browse the web. The story was titled "Disabilities Act Doesn't Cover Web"
OK, now lets jump forward another year to 2003, when attention was focused on Search Engine Optimization when Brandon Olejniczak wrote an article for Alistapart (ALA) titled "
There was still little attention paid to the connection between the two seemingly unrelated issues of accessiblity and SEO until Andy Hagans followed up with an article for ALA titled "
"I have been a search engine optimizer for several years, but only recently have become infatuated with web accessibility. After reading for weeks and painstakingly editing my personal website to comply with most W3C Web Content Accessibility Guidelines, I have come to a startling revelation: high accessibility overlaps heavily with effective white hat SEO."
Wait, an SEO "infatuated with accessibility" - they like each other and are now flirting! What a great couple they'd make! SEO's could approach their clients with the dual promise of improved search rankings AND keeping them out of court on accessibility issues. If a company loves that sexy search and cares little about accessibility, won't the idea of having search as a good friend make them at least accept the dull boyfriend, accessibility?
So in July of 2006, Google jumps into the web accessibility fray with "
Hmmmm. Remember my reference in the first sentence? WorldWide Web Consortium (W3C), in May 0f 1999, issued Web Content Accessibility Guidelines in which they recommend -
"Use features that enable activation of page elements via a variety of input devices."
AJAX, once again, requires use of a mouse, active javascript and visual cues not available to visually challenged visitors. Why do developers keep going there? I know, I know, because those sexy new tools are irresistible - but remember, SEO and accessibility are VERY good friends and miss SEO dislikes web tricks that insult or ignore the boyfriend, accessibility. Here we go again! Let's NOT have two separate sites - CSS and XHTML can accomplish the same things as AJAX and Flash (well at least similar things), remember SEO and accessibility REALLY like each other - don't separate them, bring them together.
Found an error or have a suggestion? Let us know and we'll review it.
Now let's hop forward to March of this year, where Rob Garner comments on the entire second site for search engines and screen-readers. If rich applications are a part of your future, get used to the idea of maintaining two sites."
Hold the presses, I have a great idea! Now that SEO and Accessibility have met, flirted and they clearly like each other, I propose that we get them married so that these issues stay forever together. I know it's not the norm for third parties to make marriage proposals (except in shotgun weddings), if the two are wed, won't that be enough to convince the web engineering teams AND corporate counsel that helping visually impaired web visitors (and avoiding lawsuits from NFB) WHILE ranking well in the search engines are very good business?
Pre-nuptials could be complex and it may be tough to get everyone to wrap their head around the concept of SEO married to accessibility, but it ultimately means increased web site visitors due to higher search rankings and less money lost fighting lawsuits over accessibility issues. More money, more visitors, less time in court - sounds like a marriage made in heaven.
Remember, search engine spiders are blind and can't hear. Design your pages for them and it resolves accessibility issues. SEO and accessibility are true soul-mates and should never be separated. The W3C neglected to introduce SEO to accessibility in 1999, but they did see the accessibility issues. Now that we realize search engine spiders demand accessibility and are responsible for increased search engine visibility (pun intended, sorry) let's not separate the two again. Profitability is related to accessibility, which is now married to SEO.
Suggest a Correction
No comments yet. Be the first to comment!