accessibility statement

RWDI Anemos is committed to providing a web site that is accessible to everyone. The site has been tested with automated tools and is highly accessible; however, we have yet to have true user feedback. Please let us know if you have any accessibility feedback regarding this web site.

accessibility projects

Table less layout

We are using a table layout to ensure the footer is at the base of the view port or the base of the page, which ever is lowest. We have yet to find a simple workable table less layout. 'Simple' because most workable options require hacks, which limits web site development and adds to accessibility considerations.

The current design of our web site has a very minimal table layout. In comparison to other web sites committed to accessibility, our table layout is less intrusive.

In June 2005, we found a simple CSS layout, however, it provided inconsistent results, thus we are still using the current layout.

resizable text

We are using a fixed text size as we have yet to solve cross-browser inconsistencies. We will move to resizable text. If this is of interest to you, try Firefox, Opera or other browsers that allow a user to resize text.

site map

A site map is considered desirable, therefore, we aim to build a site map. To minimize inconsistencies, we are investigating an automatic site map builder.

keyboard shortcuts

We are unsure wether defining keyboard shortcuts conflicts with established browser shortcuts. At this time, it is understood that Alt+# are generally open for use so we have defined the following, based on popular usage:

Access key 1 - Home page
Access key 9 - Feedback / Contact us
Access key 0 - Accessibility statement

If you are an accessibility user, we welcome your guidance. Please send your keyboard shortcut feedback my way.

Adjacent links

Accessibility checkpoint 10.5 (priority 3) suggests "...include non-link, printable characters (surrounded by spaces) between adjacent links."

Currently, screen readers would read our 'standard links' as "Link Careers Link News Link Search Link Contact Us". With a vertical bar (a common printable character), it will read as "Link Careers vertical bar Link News vertical bar Link Search vertical bar Link Contact Us". It seems that the printable character is excess since the word 'link' is sufficient. Interestingly, without the printable character, it would be simpler and thus achieve checkpoint 14.1 ("Use the clearest and simplest language appropriate for a site's content" | priority 1). Please provide your adjacent link feedback to help the enlightenment process.