Bobby 5.0 from Watchfire.

Bobby, from Watchfire, http://www.watchfire.com, is the best known accessibility checker
because it has been around for the longest time. Bobby was first released by CAST, the Center for Applied Special Technology, http://www.cast.org/, as
a free downloadable tool in September, 1996. Bobby was acquired by Watchfire in 2002 where they produced Version 5.0 in
2003 with improved spidering and reporting. My understanding is that the testing algorithms for the previous version,
Bobby Worldwide (Version 4.0), are the same.

Choose the tests to be used – Bobby

To choose tests in Bobby 5.0 we need to create a project and associate the choice of tests with that project. So once
Bobby is started, open the Project Properties dialog ( Tools
| Project Properties ). For now, choose a name for the project,
say STEP Tests, and go to Accessibility from the left hand menu
of the project Properties dialog shown in Figure 13-1.

Figure 13-1. Choose guideline sets in Bobby 5.0

The Guideline selection section of this properties dialog allows the choice of Section 508 Standards or the Web Content
Accessibility Guidelines, with A, AA, or AAA compliance just like the choices for most of the tools. Also like WebXM, there
is no way to say Section 508 and Priority 1 and 2 WCAG. So instead, we will create a custom set of guidelines that combines
the two.

Note the checkbox, to collect code. If you want the code fragments included in the reports, you need to check this box.

The Configure Custom Guidelines dialog (using the Configure button from the Properties Dialog) is shown in Figure 13-2.

Figure 13-2. Test selection with Bobby

This Bobby interface includes all the relevant information for each test. The Type column indicates whether or not the
test raises an error or a warning. For each test, the corresponding WCAG checkpoint and priority is listed. If relevant,
the paragraph of the Section 508 standards appears there too.

So using this interface, if you want all WCAG priority 1 and 2 sure fire tests (no warnings), restrict the Type column
to Errors and the WCAG Priority column to 1 and 2, using the pull down menus shown in Figure 13-2. Then activate the Select
All in View button—and each of the check boxes will get checked. Well that should work. It doesn’t. What happens
as a result of the sequence just described is that all P1 and P2 tests are checked, including the warnings. You have to
go back and sort through and uncheck the warnings you don’t want.

Analyze the files – Bobby

The Project Properties dialog also contains the place where you set up Bobby to analyze the site. The screen shot in
Figure 13-3 shows the What to Scan portion of the Properties dialog.