Accessibility Statement

This website is mostly compliant to all accessibility standards. It was designed to be read by everyone. However, even if some accessibility features are available, the site is optimized for modern browsers, especially browsers based on GRE (Mozilla, Firefox, Camino, etc.).

Access Keys

Use with the Alt key in Windows, or Control in Mac OS, in combination with these keys. If you use Internet Explorer, you may have to do the key combination, and then press Enter. Otherwise, i.e. in FireFox and Safari, you only need to do the combination.

Numeric access keys

• ALT + 1 → Home
• ALT + 2 → Archives
• ALT + 3 → Work
• ALT + 4 → Contact
• ALT + 5 → About

Alpha access keys

• ALT + S → Skip to page content
• ALT + N → Skip to navigation

Titled Links

Most of the links in the pages have a title. When you put your mouse over the link, a tooltip will show you where the link will bring you, or a brief description of itself. Also, some of the italic quotes of the site have a title, which will explain to you why they are in italic.

Navigation Aids

This site is using <link>'s tags. If you are using a modern browser supporting those aids, such as Mozilla or the LinkToolbar extension for Firefox, you can use them to easily jump from a month to the next one, get on the previous level in the site, or checking the latest weblog entry posted. In Mozilla, go in View > Show/Hide > Site Navigation Bar > Show Always or Show Only As Needed to show the bar.

Valid Code

All the pages are written in valid XHTML 1.0 and presented with a valid CSS-based layout. Using these standards make sure that the website is functionnal in all modern browsers, those that are supporting the W3C standards.

Semantic Markup

This website's code use a clean and semantic markup. Especially when we talk about heading tags. The title is using h1 tag, subtitles are using h2 tags. It's not very easy to notice, since most people enable CSS to view the pages.

But if you disable CSS (eg. with the blank button in the sidebar or with Web Developper Toolbar in Firefox), you'll notice that the “raw” layout is nicer & cleaner with this markup.

Accessibility references

• W3 accessibility guidelines, which explains the reasons behind each guideline.
• W3 accessibility techniques, which explains how to implement each guideline.
• W3 accessibility checklist, a busy developer's guide to accessibility.
• U.S. Federal Government Section 508 accessibility guidelines.

Books to read on Accessibility

• Dive Into Accessibility, by Mark Pilgrim shows you how to make your site more accessible in a month, providing you a different tip each day of the month. I've used some of his accessibility techniques and recommandations. Cost: Free (0 USD$).