/ Skip to main content / Skip to site menu / Shortcut keys /
www.jimfowler.us
jim at jimfowler dot us · 603 W 12th St · Juneau, Alaska 99801 · tel:+1-907-586-3279

Jim Fowler painting a landscape outdoors   Site Help


Purchases

If you would like to make a purchase, arrange a school visit, or have any other questions, please contact Jim Fowler. If you e-mailed but didn't receive a prompt reply, please call Jim at (907) 586-3279. Because of the plague of spam and automatic spam filtering, it is no longer possible to be certain that an e-mail to us, or our reply to you, will actually be delivered.

  Access keys (keyboard shortcuts)

This site provides numeric access keys allowing mouse free access to all the main areas of the site. Except as noted, the list follows UK Government recommendations:

  1. Home
  2. Skip to main content (not what's new)
  3. Site map
  4. Site search
  5. Skip to site menu (not FAQ)
  6. Site help
  7. Reserved (not complaints)
  8. Terms of Use
  9. Contact authors
  10. (Actually 0) access keys info

How to use the access keys in your browser

As of June 2007, the following information is believed to be accurate.

Site Navigation Aids

Our pages support the browser site navigation bar feature. This provide quick links to the home page, contents, and so forth. Netscape 6, Mozilla, and Seamonkey users can activate this by selecting the View menu, Show/Hide, Site Navigation Bar, Show Only As Needed (or Show Always). Users of Konqueror 3.3 or up can activate it by selecting the Tools menu, Document Relations, Configure, When necessary (or Always On). Users of Firefox may add the site navigation bar - addons.mozilla.org. Users of Internet Explorer 5 or up under Windows 98 or or up may add the LinkBar - www.draig.de. These take only a minute or two to obtain even on a dial-up connection.

Our pages also use structured headings, so users of screen readers can skip from heading to heading (for example, in JAWS, pressing ALT+INSERT+3).

Accessibility Statement

Our pages are intended to be widely accessible. You may note several buttons at the bottom of our pages. These claim that our pages meet certain requirements and also run tests that help us make sure our pages should be accessible:

  1. DC.Metadata. You may use this button to display citation information encoded in the page per Dublin Core - en.wikipedia.org recommendations. The button does not display the better known HTML meta description and keywords.
  2. W3C HTML 4.01 Check. This icon claims that the W3C HTML Validation Service - validator.w3.org found no hypertext markup language - en.wikipedia.org syntax errors in the page. Pressing it runs the test again. We use this test because avoiding HTML syntax errors greatly improves the chance that a page will be readable in all browsers.
  3. W3C CSS Check. This button claims that the W3C CSS Validation Service - jigsaw.w3.org found no Cascading Style Sheets - en.wikipedia.org syntax errors in the page. Pressing it runs the test again. We use this test because avoiding CSS syntax errors greatly improves the chance that a page will display as intended in most browsers.
  4. Checker A. This button claims that the Adaptive Technology Resource Center Checker - checker.atrc.utoronto.ca, a service of the University of Toronto, found no first order 'level A' accessibility errors in the page, and that the submitter reviewed the other identified checkpoints and concluded that the page met Web Content Accessibility Guidelines 1.0 Level A - www.w3.org. Pressing the button runs the test again. We use this test because it helps make it easier for everyone, including people with disabilities and search engine robots, to access the content of our pags.

It is hoped that these checks help make our pages widely accessible, easily indexed, and viewable in any browser - www.anybrowser.org.

Privacy Statement

We haven't yet developed a formal privacy policy for the website. However, unless you contact us by phone, postal mail, or e-mail, we don't collect any personally identifiable information. If you do contact us, we will only use your personal information, such as e-mail, to respond. We will not disclose your addresses to others, and we do not maintain a mailing list of our own.

There are web server logs, which will contain the IP address you had when you visited, certain computer information (such as your browser version), and the page(s) you viewed. However, if you are a dialup user, you generally would get a new IP address every time you dial in, and if you are a cable modem user, every time your modem is reset. We are also using a statistical counter of page view on the various pages. This service may also allow us to see search terms you entered to find our pages. But such information is not personally identifiable, is used only for statistical purposes, and short of a court order, it is never released.

Changing Mozilla's Access Key Prefix

For Mozilla based browsers including Firefox and Seamonkey, you can change the access key prefix. In Firefox 2+ and Seamonkey, the three key sequence with SHIFT may render numeric accesskeys nearly inaccessible, particularly to people with motor skill disabilities or cognitive decline. You can change the prefix to the traditional ALT key. Open the pseudo URL 'about:config', and enter the filter 'ui.key'. Change ui.key.generalAccessKey to 18 ALT. To reduce conflicts with menu access, you can also change ui.key.menuAccessKey to 27 ESCAPE. After restarting the browser, ESCAPE keys always get browser menus and ALT keys get web page accesskeys unless entered on the numeric keypad with NUMLOCK OFF, in which case they get special characters.

Why don't the access keys work?

You should check your system's documentation, because the information we have collected is neither authoritative nor complete. However, numeric access keys are known to be unsupported by IBM Home Page Reader and Windows Eyes and by older browsers. The minimum version required for accesskey support in several of the better known browsers is given below.

Some Additional Pages