Easy Access

Our Statement of Accessibility

One of our goals with leihu.com was to make it as accessible as possible. We feel in many regards we’ve succeeded. We’ll discuss the technical aspects of our accessibility at the bottom of this page, but first we’d like to explain how to take advantage of some of the accessibility features.

! If you have suggestions or concerns about our accessibility, please contact us

Accessibility Features

Helpful navigation features for using leihu.com.

If you are using a current version screen reader you may use the following commands.

• Tap the ‘h’ key to move forward through headings.
• Hold the ‘shift’ key and tap the ‘h’ key to move backward through headings.
• Hold the ‘insert’ key and tap the ‘F6’ key to list all available headings.
• Tap the ‘tab’ key to move forward through hyper-links.
• Hold the ‘shift’ key and tap the ‘tab’ key to move backward through hyper-links.
• Hold the ‘insert’ key and tap the ‘F7’ key to list all available hyper-links.
• Tap the ‘enter’ key to follow high-lighted hyper-links.

! Brief overview of some common screen reader commands

With Firefox or MSIE you may use the following commands.

• Tap the ‘tab’ key to move forward through hyper-links.
• Hold the ‘shift’ key and tap the ‘tab’ key to move backward through hyper-links.
• Tap the ‘enter’ key to follow high-lighted hyper-links.

! More on Firefox accessibility or More on MSIE accessibility

Alternately if your using the Opera Browser you may use the following commands.

• Tap the ‘s’ key to move forward through headings and hyper-links.
• Tap the ‘w’ key to move backward through headings and hyper-links.
• Tap the ‘enter’ key to follow high-lighted hyper-links.

! More on Opera accessibility

Using comment or contact forms

You may use the following commands.

• Tap the ‘tab’ key to move forward through input fields.
• Hold the ‘shift’ key and tap the ‘tab’ key to move backward through input fields.
• Tap the ‘enter’ key while high-lighting the ‘submit button’ to submit the form.

Accessibility Failures

Even with our die-hard efforts to make this web-site 100% accessible, we’re not differently-abled and haven’t any access to screen readers, or the user experience that a differently-abled person may have. Therefore it’s impossible for us to make leihu.com 100% accessible for every possible situation or person. In certain situations and with certain disabilities I’m sure this site will fail miserably. If you happen to encounter such a situation, please contact us.

Accessibility Technical Discussion

In an attempt to make leihu.com as accessible as possible we’ve done the following;

• Used proper semantic structure for our xHTML markup.
• Applied a descriptive ‘alt’ attribute to all inline content images.
• Applied a descriptive ‘title’ attribute to all hyper-links, where able.
• Used minimal contextual images, in favor of readable text content.
• Used CSS for all presentation, leaving the xHTML free of presentational markup.
• Used tables for tabular data only.
• Used relative units of measurement for font sizing, to allow end-user sizing.
• Used labels, fieldsets and tab indexes on forms, where necessary.
• Used descriptive text for hyper-links for out of context understanding.
• Validated all xHTML and CSS, to increase proper semantic/presentational structure.
• Used Friendly URI structure, to increase URI readability and memorability

One common accessibility feature we actively chose not to support is “access-keys”.

Our reasoning is simple; between all the browsers and screen readers reserved “access-keys”, we're left with only two (2) available keys that will not interfere with a browser or screen reader ‘\’ (back slash) and ‘]’ (right square bracket).

We feel that overriding a access device’s reserved “access-keys” with our own is the opposite of being accessible, so we’ve chosen not to support “access-keys”. We sincerely apologize if this causes you any inconvenience.

! Disagree with our standing? contact us and sway our opinion.

---