UI Accessibility Checker Web Plug-in
Contents
Warning - TableShouldHaveHeader
Error - TableShouldNotHaveHeader
Error - TableShouldNotHaveName
Error - HeaderAndTitleShouldMatch
Error - ControlShouldHaveValue
Warning - ElementHasEmptyStringAsName
Error - RepeatLinkNameWithDifferentValue
Error - AccNameContainsInvalidString
Warning - AccNameShouldNotContainRole
Error - MemberNotImplememented
This error indicates that the document does not contain an h1.
This warning indicates that a table, if it is a data table, should use < th> tags instead of < td> in the first row.
Note: This is an issue for people who rely on a screen-reader because they will be unable to determine which column a particular table cell belongs to when navigating though the table cells.
Possible causes for this warning:
1. The table has more than one row but has at least one 'td' instead of 'th' in the first row.
This warning indicates that a table appears to be a layout table, and therefore should use not < th> tags in the first row.
Note: This is an issue for people who rely on a screen-reader because the table will be interpreted as a data table.
Possible causes for this warning:
1. The table has only one row and has at least one 'th' in the first row.
This warning indicates that a table, if it is a data table, should have a caption.
Note: This is an issue for people who rely on a screen-reader because the screen reader uses the caption to identify a table to the user. Without a caption, the screen-reader cannot identify the table.
Possible causes for this warning:
1. The table has more than one row and has no caption.
This warning indicates that a table appears to be a layout table, and therefore should not have a caption.
Note: This is an issue for people who rely on a screen-reader because the table will be interpreted as a data table.
Possible causes for this warning:
1. The table has only one row, but also has a caption.
This warning indicates that the frame tag is missing the recommended title attribute.
Note: Even though AccChecker is not checking for it, the title attribute in the frame tag should match the title tag in the file being included in the frame.
Possible causes for this error:
1. Frame tag has no title attribute.
This warning indicates that the document's title and the first < h1> content don't match.
Possible causes for this error:
1. < title> content is not equal to first < h1> content.
This warning indicates there should be more headers in the document, due to the amount of content in it.
Note: The number of characters per header set is currently fixed to 800.
Possible causes for this error:
1. There are more than x characters per header on the page.
This error indicates that an element is reporting an invalid Active Accessibility role. For example, the get_accRole method used to retrieve the Active Accessibility role of an element returns an integer value that does not map to a valid object role constant (such as ROLE_SYSTEM_LISTITEM).
Note: This is an issue for people who rely on a screen-reader and keyboard for navigation because elements may be incorrectly identified to the user.
Possible causes for this error:
1. The element, or its parent, has an Active Accessibility role set inappropriately.
Related Resources
This error indicates that an element does not supply an expected value based on the element’s assigned Active Accessibility role. This implies that the element does not have the get_accValue method implemented. The following Active Accessibility roles should all supply a value:
· ROLE_SYSTEM_COMBOBOX
· ROLE_SYSTEM_SLIDER
· ROLE_SYSTEM_LINK
· ROLE_SYSTEM_TEXT
· ROLE_SYSTEM_SPINBUTTON
· ROLE_SYSTEM_SCROLLBAR
· ROLE_SYSTEM_PROGRESSBAR
· ROLE_SYSTEM_OUTLINEITEM
· ROLE_SYSTEM_IPADDRESS
Note: This is an issue for people who rely on a screen-reader and keyboard for navigation because an element that has an intrinsic value must be able to report that value to a user.
Possible causes for this error:
1. The element, or its parent, has an Active Accessibility role set inappropriately.
Related Resources
This error indicates that an element does not have a name. For example, an image that is missing an alt tag.
Note: This is an issue for people who rely on a screen-reader and keyboard for navigation because the screen reader might incorrectly identify an element to the user. An image that serves a strictly decorative purpose shouldn't have a name. Use alt="" as the alt text.
Possible causes for this warning:
1. An image doesn't have an alt tag.
2. A link does not contain text or an element with a name.
3. The document doesn't have a title.
4. A button doesn't have a name.
This error indicates that an element should have a label to provide its name, but doesn't have one.
Note: This is an issue for people who rely on a screen-reader and keyboard for navigation because the screen reader might incorrectly identify an element to the user.
Possible causes for this warning:
1. Radio button doesn't have a label.
2. Check button doesn't have a label.
3. Text field or similar doesn't have a name.
This warning indicates the element has "" as a name.
Note: This is not an issue, as long as the element serves only decorative purposes, as the screen reader user will be unaware of the existence of this element.
Possible causes for this warning:
1. An image has alt="".
2. Element has name set to empty string.
This error indicates that multiple links have the same name, but they link to different destinations.
Note: This is an issue for people who rely on a screen-reader. Because the screen reader communicates the links to the user only by reading the names, theuser will assume that the links are the same.
Possible causes for this warning:
1. At least two links have same name, but different href values. The name of the link is determined from the text within the link. If there is no text, the link gets its name from the element name within it.
· This error indicates that the name of an element contains too many characters. For example, the get_accName method used to retrieve the Active Accessibility name of an element returns a string greater than the limit of 32000 characters.
Note: This is an issue for people who rely on a screen-reader and keyboard for navigation because an element may have an unpronounceable, non-intuitive name.
Possible causes for this error:
1. The element, or its parent, has an incorrectly assigned name or label.
· This error indicates that the name of an element contains invalid characters (these characters are replaced by AccChecker). For example, the get_accName method used to retrieve the Active Accessibility name of an element returns a string that contains tab, newline, or ampersand characters.
Note: This is an issue for people who rely on a screen-reader and keyboard for navigation because an element may have an unpronounceable, non-intuitive name.
Possible causes for this error:
1. The element, or its parent , has an incorrectly assigned name or label.
· This error indicates that the name of an element incorporates its Active Accessibility role. For example, the get_accName method used to retrieve the Active Accessibility name of an element returns “ROLE_SYSTEM_SCROLLBAR_*”.
Note: This is an issue for people who rely on a screen-reader and keyboard for navigation because an element may have an unpronounceable, non-intuitive name.
Possible causes for this error:
1. The element, or its parent, has an incorrectly assigned name or label.
2. The element, or its parent, has a default name that has not been revised to a friendly name. For example, button1.
This error specifies that an exception unrelated to the verifications has been raised by AccChecker.
To report issues such as this, see the AccChecker 'About' dialog for contact information.
This error specifies that a method call has failed unexpectedly.