You are here: Home › Accessibility statement
Accessibility statement
If you have something to say about the accessibility of this website, please contact us and let us know.
Site map
How you activate an access key depends on which browser and which operating system you're using. We presume that you, if you need access keys, already know how to activate them.
Images
Almost all images that convey information have a text equivalent and, if needed, also a separate description. The exceptions are images that we use for purely decorative purposes.
Colors
We don't convey any information through colour alone. However, we are aware that the contrast may be insufficient in some cases, but we hope it's not so bad that the text is completely illegible.
Tables
There aren't that many tables on this website, and those we have are used for tabular data, not for layout. We have marked up header cells and provided a summary for each table.
Design and layout
All design and layout is handled through style sheets, not tables. Browsers which don't support style sheets receive the same content, but without the design.
Scripts
All pages work even with browsers which don't support client-side scripting, or where this has been disabled. The existing scripts may provide some kind of added value, but they are in no way critical.
Plugins
Some pages make use of Flash technology. The existing Flash files, as the scripts, may provide some kind of added value, but they are in no way critical. To view the Flash files, you can install the free Macromedia Flash player.
We may link to Adobe PDF files for further information. To view these files you will need Adobe Acrobat Reader.
Miscellaneous
- The markup code marks up the different semantic components of a page. All pages validate in the W3C validator.
- The natural language is specified as either English, German, Dutch or French on each page. We have marked up any words or phrases in foreign languages.
- We serve pages in the language (English, German, Dutch or French) and with the content type HTML. We know we miss the point by making the page XHTML valid, but as User Agents evolve, this issue will be resolved.