Priority 2 Accessibility
This page does not meet the requirements for Bobby AA Approved status.
Below is a list of 3 Priority 2 accessibility error(s) found:
- Use relative
sizing and positioning (% values) rather than absolute (pixels).
(7 instances)
Lines 132, 135, 144, 154, 187, 188, 211
- Use a public
text identifier in a DOCTYPE statement. (1 instance)
Line 1
- Make sure event
handlers do not require use of a mouse. (7 instances)
Lines 134, 230, 231, 232, 233, 234, 235
Priority 2 User Checks
User checks are triggered by something specific on the page; however,
you need to determine whether they apply. Bobby AA Approval requires that
none of them apply to your page. Please review these 9 item(s):
- Check that the
foreground and background colors contrast sufficiently with each
other. (15 instances)
Lines 130, 134, 135, 138, 141,
144, 145, 148, 154, 187, 188, 211
- If objects use
event handlers, make sure they do not require use of a
mouse.
- Avoid use of
obsolete language features if possible. (2 instances)
Lines 154, 192
- Use style sheets
to control layout and presentation wherever possible.
- Is the user
made aware that there will be pop-up windows or changes in the active
window? (18 instances)
Lines 134, 149, 150, 151, 222,
223, 225, 226, 227, 228, 229, 230, 231, 232, 233, 234, 235
- Make sure that
all elements that have their own interface are operable without a
mouse. (1 instance)
Line 192
- If this gif
image is animated, make sure it does not contain fast or distracting
motion. (8 instances)
Lines 134, 135, 138, 141, 145,
148, 187, 211
- If scripts
create pop-up windows or change the active window, make sure that the
user is aware this is happening. (4 instances)
Lines
8, 29, 36, 155
- Mark up any
quotations with the Q and BLOCKQUOTE elements.
The following 7 item(s) are not triggered by any specific
feature on your page, but are still important for accessibility and are
required for Bobby AA Approved status.
- Make sure that
all link phrases make sense when read out of context.
- Group related
elements when possible.
- Make sure your
document validates to formal published grammars.
- Is there a site
map or table of contents, a description of the general layout of the
site, the access features used, and how to use them?
- Is there a
clear, consistent navigation structure?
- Use the latest
technology specification available whenever possible.
- Where it's
possible to mark up content (for example mathematical equations) instead
of using images, use a markup language (such as
MathML).
|