Asolis Accessibility:

Accessibility Navigation:

This is the Navigation for the Accessibility page, to come back here press alt+1 on PCs and ctrl+1 on Macs. You may also scroll (of course) or just click the link at the end of each article.

• Accessibility Navigation—1
• Web Content Accessibility Guidelines 1.0―2
• Site Signature—3
• Web Standards—4
• Compatibility with Mobile Devices—5

Web Content Accessibility Guidelines 1.0:

The Asolis website conforms to the Triple-A Web Content Accessibility Guidelines 1.0 of the W3C. The Asolis website currently has two warnings when validated for WCAG accessibility. The lack of tabindex attributes for all <a> tags and the lack of accesskey attributes for all <a> tags. Although I try to make the website as accessible as possible, I don't have time to add those attributes to every <a> tag and worry about if it will work currently (meaning I don't have time to make sure every single attribute is different for every hyperlink I make). Now on to how to use these Accesskeys.

To use the accesskeys on PCs press alt+accesskey and on Macs press ctrl+accesskey. All items on the nav bar have accesskey and tabindex attributes and the letters to their left show which accesskey is used to move to that page.

Site Signature

You may be wondering what a site signature is, as it isn't very common to find on a website. Well Phoenity uses a site signature (see top-right hand corner of their page) and that's what inspired me to add a site signature when releasing the new Asolis layout, Asolis 1.0.

Now on to what the site signature actually is. Since Phoenity has already compiled some good links on the subject, I'll just point you to them.

• CSS signatures
• User stylesheets for specific sites
• Body IDs
• Fun with body IDs

Web Standards:

This website conforms to the W3C standards, but some browsers aren't very standards compliant, notably Microsoft's Internet Explorer, which still lacks support for the XHTML MIME type (application/xhtml+xml) in IE 7.0. Although I try to make the site as accessible as I can, users of browsers that don't have much standards support should switch to browsers such as Firefox or Opera.

Compatibility with Mobile Devices

The website can be viewed by most mobile devices (I had to give up some of my valid code to do that though), but I'm not entirely sure how easy it is to navigate the website using them yet. The accesskeys should help, but I'll try to make the website more accessible to these devices in the future once I learn more. Sorry for any inconvenience, but if you have any suggestions you can always contact me!