To sitemap or not to sitemap.

A while ago, I noticed that the World Wide Web Consortium does not only offer Web Content Accessibility Guidelines – it also offers these nice logos for the three different levels of conformance. After reading the guidelines it seemed to me that the only criterion that the post-graduate college’s page (which I designed) does not completely comply with is checkpoint 13.3, because it doesn’t offer a sitemap or table of contents. Since I have this weird urge to get the best W3C accessibility badge available I started to read a bit about sitemap design. I quickly realized that there is not nearly as much literature on this topic to be found as I would have thought. So I read what I found and started to think, draw a few basic designs, and hack some CSS code to display the stuff in a map-ish way without relying on a static picture or tables. After investing quite a bit of time into the whole issue, I realized that it just doesn’t make sense to produce a sitemap for a site that does not have any real complexity. The few sections that are available can be navigated to on every page via the navigation bar, and the if there are further links in the respective section they are all available from that page. Looking at these facts, I decided that the site does fully comply to section 13 as it is, because navigating this site would only be made more complex if I add a mostly redundant sitemap or table of contents. *eyes WAI AAA badge eagerly*


Leave a Reply