JAWS Reading Commands. Training Archives. These training files are older DAISY and MP3 files. You may find them useful, so we have archived them here. For the most recent materials, please check the newest DAISY and MP3 materials on the Training Downloads page. JAWS Training Archives The following archives are training in MP3 or DAISY format for earlier versions of JAWS. NOTE: The Basic Training for JAWS beginning with JAWS version 13 and later is generic, and is not specific to any particular version of JAWS. The lessons teach concepts and as time goes on, both JAWS and Windows will change. Basic Training for JAWS Versions 12 and Earlier JAWS 12 Basic Training JAWS 11 Basic Training JAWS 10 and Prior Basic Training What's New in JAWS Prior Versions Surf's Up Prior Versions JAWS Help System JAWS Help System MP3 (11.6 MB) Getting Started with JAWS Excel with JAWS Excel Spreadsheets with JAWS MP3 (20.1 MB) Internet Explorer with JAWS - 8 Modules Speech and Sounds Manager with JAWS PAC Mate Training Archives PAC Mate BX 4.0 and 4.1 Audio Modules.
Using Forms with JAWS and MAGic. HTML forms allow you to access shopping carts, search engines, Web-based e-mail, bulletin boards, and so on. Forms include controls such as edit boxes, check boxes, radio buttons, combo boxes, and other controls similar to those used in dialog boxes. JAWS and MAGic take advantage of the features of HTML used to create forms and allow you to access all kinds of form controls. Moving Through Forms The following is a list of JAWS navigation quick key commands that allow you to move quickly from one control to another. When running JAWS alone, or both JAWS and MAGic together, all commands listed below work.
You can use the SHIFT key in combination with many of the keystrokes to move to the previous unit or element. NOTE: These commands do not work in forms mode. You can also display lists of specific types of form controls. To quickly locate a specific form control press INSERT+F5. MAGic Tip: You can also use INSERT+F5 with MAGic to list all form controls and their contents on a page. Introduction to Techniques for WCAG 2.0 | Techniques for WCAG 2.0. This document is part of a series of documents published by the W3C Web Accessibility Initiative (WAI) to support WCAG 2.0 [WCAG20]. It includes a variety of techniques which include specific authoring practices and examples for developing more accessible Web content. As well, it lists failures, which describe common mistakes that are considered failures of WCAG 2.0 Success Criteria. This is not an introductory document. It is a detailed technical description of techniques that can be used to address the requirements in WCAG 2.0.
In order to make the set of techniques maintained by the WCAG WG as comprehensive as possible, the WCAG WG encourages submission of new techniques so they can be considered for inclusion in this document. Sufficient and Advisory Techniques Rather than having technology specific techniques in WCAG 2.0, the guidelines and success criteria themselves have been written in a technology neutral fashion. Note that all techniques are informative. Technique Collections. The Roles Model | Accessible Rich Internet Applications (WAI-ARIA) 1.0. An element whose implicit native role semantics will not be mapped to the accessibility API. The intended use is when an element is used to change the look of the page but does not have all the functional, interactive, or structural relevance implied by the element type, or may be used to provide for an accessible fallback in older browsers that do not support WAI-ARIA. Example use cases: An element whose content is completely presentational (like a spacer image, decorative graphic, or clearing element);An image that is in a container with the img role and where the full text alternative is available and is marked up with aria-labelledby and (if needed) aria-describedby;An element used as an additional markup "hook" for CSS; orA layout table and/or any of its associated rows, cells, etc.
For example, according to an accessibility API, the following markup elements would appear to have identical role semantics (no role) and identical content. Human Ability and Accessibility Center | Developer guidelines | Software checklist. Understanding Accessibility If you are new to accessibility, review "Understanding accessibility" before completing the checklist or contacting the Human Ability and Accessibility Center for help. IBM software accessibility checklist Use this checklist for: Eclipse applications written using the Standard Widget Toolkit (SWT) controlsJava 2 or later applications written using Swing controls and componentsJava 1.1.x applications written using Abstract Window Toolkit (AWT) controls and componentsProducts with a command line or "green screen" interfaceThe output, as well as the user interface, of software toolsGeneral software products and applications that have a user interface Techniques pages, accessed via the link in each checkpoint, may contain more recent updates.
Related checklists: Use the IBM Web accessibility checklist for Web applications and for the product support Web site. References. Corner Article: Designing Accessible Plug-ins in Eclipse. Introduction A major goal of Eclipse 2.0 was to supply support for the use of Eclipse by people with disabilities. This article deals with the support provided in Eclipse for use of accessibility tools in the Microsoft® Windows , Linux GTK and Mac operating systems as well as general UI design tips for people who want to make accessible applications. It also covers the US Federal government section 508 accessibility regulations and the IBMTM accessibility checklist. Regulations and other Resources Much of the work in the industry in accessibility has been driven by the US Federal Government Section 508 Regulations. The Section 508 regulations are fairly general so IBM has provided a more detailed checklist for developers of accessible applications - see the IBM Accessibility Guidelines.
Types of Accessibility Support There are several types of disability that can be dealt with in an accessible application. Mobility enablement covers a wide range of issues. Figure 1. Colors and Images Fonts.