I've been dabbling with search-engine-optimization lately so document metadata has been on my mind lately. That got me to thinking that identifying "document capabilities" could be made easy with better use of the metadata in the document.
We Built this City on <meta> Tags
Metadata is already used extensively in the <head> section of your HTML documents and have been fundamental in building the web. For example, the <meta> tag played a significant role in how search engines ranked your website stretching back to the pre-bubble days of the nascent Internet. Back in the day, I spent many hours trying to load up meta tags with relevant keywords for whomever's website I was working on.
Fifteen years later, and the <link> tag and the "rel" attribute are helping to make RSS and ATOM feeds easily discoverable (that's not to say it didn't appear until the 2000's it had actually been languishing within the HTML spec for years but was under-utilized in the mainstream web). Probably what really brought the presence of this metadata to the forefront was the conspicuous inclusion of the RSS logo in the address bar of popular browsers like Firefox and Internet Explorer. For example, you probably see the RSS logo in the address bar when visiting this site (hint, hint...).
But we want more, don't we?
Well, I do, or I wouldn't be writing this post! So where do we begin? What we're talking about really is metadata so its up to the <meta> tag to fill these shoes. The important part is to establish conventions and patterns to follow so Joe Google out there can parse your HTML documents to present the most useable/relevant pages to the user. Try this:
ADA Compliance and Search Engines
Example: <meta name="ADA" content="1" />
ADA-compliance has 3 levels, so it would be worthwhile to indicate more than just compliance, but also which level is attained and now visitors will be aware of what ADA compliant features they can access in a document. Those interested in providing accessible websites could determine their level of compliance using Bobby, and include their compliance level in the metadata.
Most special-capability browsers are playing a guessing-game with every web-page they display because all they can do is open the document, parse it and make the best use of the ADA features that are indicated in the markup.
But as many of us who've worked with <label> and <legend> know, most documents on the web are lacking even this simple and useful tags. So really the guessing-game just wastes the time and energy of a user who may require usability features to properly access a document but rarely finds websites that provide these basics.
If a browser could tell right away that the document is not going to meet the compliance needs of the browsee(?), it could notify the user that the document may not be accessible, or even better, kick in to a "smart-mode" browser that will try to re-process the HTML document into something that really is accessible.
Beyond visiting web pages first-hand, when HTML documents declare what level of compliance they intend to support in the <meta> tag, it would be possible for search engines to build indices of accessible documents, even partitioning the results based on the user's compliance needs! Hmmmm! That's good metadata!
For my Next Trick...
Yet there's plenty of other things we could support, it's metadata after all so it could be anything. For example, how handy would it be for Grandma to search only for documents that offer a large print version of their website's pages, or the author has prepared a printable version. The day is already upon us where we might prefer to know that a site is using AJAX/jQuery/Rails/Scriptaculous before we get there, so we don't have to watch our browser choke on the Javascript poundage, or your browser could reconfigure check available resources to warn you of potential trouble before you even click the link!
Really, we're only limited by our imagination... and the willingness of the search engines to use our metadata. But we could be making the web a much more useful place with a little forethought.
Tags: html, meta tags, ada, architecture