| The following are relevant areas in which the Wisconsin Section pages do
not meet the requirements and suggestions made by the Bobby
accessibility compliance software. The areas all concern
Priority 2 and Priority 3 Web Content Accessibility Guidelines. The other
issues raised by Bobby do not apply to these web pages. Notes: these pages were generated with Microsoft Frontpage
2002. Compliance is determined partially automatically and
partially by self-assessment. If you find an obstacle on this site,
please contact us so we can fix it!
Priority 2 Requirement
Relative Size and Position--Microsoft Frontpage 2002 defines absolute font sizes, such as
"1" and "2". Web Content Accessibility
Guidelines require relative font sizes, such as "+1" and
"-1". The reason for this is so that the visitor can
control the font size with his or her own browser. People with
visual impairments can then set the type on the page to a larger size,
enabling them to read the site. It makes the site more accessible.
This font behavior in Frontpage 2002 cannot be modified by the web page
designer.
Priority 2 Check
Avoid Use of Obsolete Language Features if Possible--the "font" tag,
automatically generated by Frontpage. This blanket requirement
helps ensure that all browsers can interpret the pages.
Priority 3 Requirements
Provide a Summary for Tables--The layout of these pages
is handled with tables. Microsoft Frontpage does not provide the
option to define a "summary" in the Table Properties tab.
This item is analogous to the "alt" feature for pictures.
Summaries can be defined by hand by editing the HTML, and this has been
done for this site. The text reads, "Table for formatting
only". Frontpage generates additional table code,
however, which cannot be edited.
The reason why a summary is requested is that some people use a browser
that reads the page aloud. Tables are read line for line.
Without a visual cue and without summary information, a table read line
for line can be confusing.
Separate Adjacent Links with More than Whitespace--this
error refers to the horizontal and navigational bars at the top and left
sides of the page. Without the graphics, the links look like one
long multi-worded link. These bars are automatically generated by
Frontpage. A partial workaround is provided in the form of a link
("skip navigation bars") to bypass the navigational bars. The bypass
link appears before both the graphical bars at the top and left and the
text bars at the bottom of the page. A visitor who uses the tab key
to advance through the links on a page can use these links to skip to the
main text of the page. (a Section 508 requirement)
Note that the text navigational links in the page footer are separated
by square brackets, [ ], in addition to whitespace.
Note: cascading style sheets have been implemented
for this web site to work around a bug in Frontpage 2002. This site
uses a theme, and in Frontpage 2002, themes use graphical elements for,
among other things, bullets. All graphical elements should have
alternate text strings associated with them (ALT), including
bullets. Frontpage 2002 neither allows ALT strings to be set nor
allows ordinary bullets to be set in the theme. The cascading style
sheets allow for ordinary bullets to be set. The page appears to
load first the ordinary bullet and then the graphical one. The Bobby
site does not generate an error when this technique is applied, but it is
possible that this workaround does not completely address the problem.
|