Please enter the URL that you'd like to shorten or click here to shorten current:
Type: Page by page
Access: Downloadable toolbar for use with Internet Explorer
Company: Vision Australia
The Web Accessibility Toolbar is a downloadable toolbar for use with the browser Internet Explorer or Opera. It functions as a page-by-page accessibility evaluator, and can test many of the W3C Web Content Accessibility Guidelines in addition to other features such as changing screen resolution. Errors are highlighted within the page itself.
The Web Accessibility Toolbar should only be used when you are testing a small number of pages. You will need to run tests on each page manually. Initially you will need to download the toolbar prior to any testing.
Downloading the Web Accessibility Toolbar is straightforward. You will need the following system requirements:
You can also download the Internet Explorer Web Accessibility Toolbar in a variety of languages:
Open Internet Explorer and select the "View" menu. Select the "Toolbars" option and then the "Accessibility Toolbar" option. The toolbar will appear under the address bar and any other toolbars you may have installed.
There are twelve menu items, each containing a number of tests. These twelve menu items are:
To run a test, select a particular menu, for example "Images" and then select the particular test you want to run, for example "Toggle Image/Alt".
The selected test will be run on the page itself. For instance the "Toggle Image/Alt" test will replace all images with their ALT attribute, for example:
For more information on all the functions of the Web Accessibility Toolbar, see Toolbar functions page. The following table lists some recommended tests for particular W3C Web Content Accessibility Guidelines checkpoints.
|Level A Checkpoint||Menu||Test|
|1.1: testing ALT attributes of an image||Images||Toggle Image/Alt|
|1.1: identify any frames||Structure||Frame Borders|
|1.1: identify any downloadable files||Doc Info||List Downloadable Files|
|1.1: identify any multimedia files||Doc Info||Identify Multimedia Files|
|2.1: testing whether information has been provided without relying solely on colour||Images||Greyscale|
|4.1: determine whether the changes in the language have been identified||Doc Info||Show Lang Attributes|
|5.1: test whether table headers have been used||Structure||
Show Table Headers, Simple Data Table, Complex Data Table
|6.1: testing the site works with style sheets disabled||CSS||Disable CSS|
|6.3: test whether the site can be used with Java, Flash and iframes disabled||Tools, Simulations||Disable Plugins|
|6.3: identify any scripts||Doc Info||Identify Scripts|
|7.1: test that the screen does not flicker||Images||GIF Flicker Test|
|9.1: testing whether image maps are client-side or server-side||Images||Show Image Maps|
|12.1: test whether a frame has a title||Structure||Frame Name / Title|
|Level AA Checkpoint||Menu||Test|
|2.2: testing whether colour contrast is sufficient||Images||JuicyStudio, Vischeck|
|3.2: validating the HTML||Validate, W3C HTML Validator||Validate HTML|
|3.2: validating the CSS||Validate, W3C CSS Validator||Validate CSS|
|3.3: testing whether style sheets have been used for layout and presentation||CSS||
Show Applied Styles, Show Style Sheet(s)
|3.4: determine whether relative units have been used for style sheet property values||CSS||Show Style Sheet(s)|
|3.5: determine whether headings have been used and whether they have been nested||Structure||Headings, Heading structure|
|3.6: determine whether list markup has been used||Structure||List items|
|3.7: determine whether quotes have been marked up with Q and BLOCKQUOTE||Structure||Blockquote & Q|
|6.4: test whether device-dependent event handlers have been used||Structure||
|11.2: identify any deprecated HTML elements||Source||Deprecated HTML|
|12.3: determine whether FIELDSET has been used to break up a form||Structure||Fieldset / Labels|
|12.4: determine whether field labels have been explicitly associated with fields||Structure||Fieldset / Labels|
|13.1: test whether links have clearly identified targets||Doc Info||List Links|
|13.2: determine whether metadata has been included||Doc Info||Metadata Information|
|Level AAA Checkpoint||Menu||Test|
|4.2: test whether acronym and abbreviation markup has been used||Structure||Acronyms/ Abbreviations|
|9.4: identify the tab order of the page||Structure||Show Tab Order|
|9.5: identify whether access keys (keyboard shortcuts) have been used||Structure||Access keys|
|10.3: test whether a table can be used if it is linearised||Structure||Linearise (Remove Tables)|
The following are failures from random sites.
Test: Toggle Image/Alt
According to this error, the images on the right are missing ALT attributes. If any of the images in the page are missing ALT attributes then a dialog box also pops up and identifies the number of images missing ALT attributes.
Test: Fieldset / Labels
According to this error, the Search field does not have a field label. If there are no labels, fieldsets of legend elements in the page are missing ALT attributes then a dialog box also pops up.
Test: Event Handlers
This image has an onmouseover. On testing the site this onmouseover changes the colour of the "Personal" section and creates a flyout menu. This menu cannot be activated via the keyboard and is therefore inaccessible.
Test: Complex data table
According to the above test, the table includes a SUMMARY tag ("Schedule of events"), all table headers are marked up properly (eg. the code for cell Wed 15 Day 0 is "id=day20060315") and all data cells reference appropriate headers (eg. the headers referenced by the first data cell are "openingceremony" and "day20060315").
According to the above test, all headings are marked up appropriately. Using the ‘Heading Structure’ test you can determine whether headings have been nested properly.
Enter your email address to subscribe or unsubscribe from the eGov What's New mailing list.
Please enter email address of the person you wish to send this page to.