AccessibilityOz



Web Accessibility Evaluation Tool

WAVE

Keyboard

By: AccessibilityOz

Date: October 2013

Contents

Web Accessibility Evaluation Tool WAVE Keyboard 1

Contents 2

Evaluating keyboard 3

Steps to take 3

Testing with WAVE 3

Checklists 5

Keyboard 5

Resources 7

WAVE 7

Further information 7

AccessibilityOz 7

Evaluating keyboard

Steps to take

NB: For the purpose of this document, the following information is based on using WAVE () by entering a page URL into the WAVE interface:

[pic]

1. The evaluated page will display with the WAVE summary and tool panel on the left, and page results (icons and text) on the right.

[pic]

2. Use the WAVE Details tab [pic] and review the page results for errors – for example, the yellow alert icon [pic] indicates a missing keyboard focus indicator.

a. Follow the Level A and Level AA checklists to identify any accessibility issues within the page table content.

NB: You may find it useful to create a separate list of URLs for each error type to help with implementation of a correction.

Testing with WAVE

WAVE does not have specific icons for all the checklist requirements; most require manual review with and without the tool.

Alerts

|Icon |Title |Description |Recommended Actions |

|[pic] |A positive tabindex |Tabindex values of 1 or greater |Consider restructuring the page so that tabindex |

| |value is present. |specify an explicit tab/navigation |is not needed. |

| | |order for page elements. Because it | |

| | |modifies the default tab order, cause | |

| | |confusion, and result in decreased | |

| | |keyboard accessibility, it should be | |

| | |avoided. | |

| |[pic] Any page that displays this icon fails KYB_A4ii |

|[pic] |An accesskey attribute |Accesskey provides a way to define |Remove the accesskey or be aware that the |

| |is present. |shortcut keys for web page elements. |accesskey may conflict with user shortcut keys. |

| | |Accesskeys often conflict with user or| |

| | |assistive technology shortcut keys and| |

| | |should be avoided or implemented with | |

| | |care. | |

| |[pic] Any page that displays this icon fails KYB_A5i |

|[pic] |Keyboard focus |While navigating through a page |Ensure that all links have a visible keyboard |

| |indicators are not |(typically using the Tab key), sighted|focus by navigating through the page using the Tab|

| |present. |keyboard users must be able to |key. Remove outline:0 or outline:none CSS styles |

| | |visually identify which element |from links, or provide some other non-color |

| | |currently has keyboard focus. |designator when the link receives keyboard focus |

| | | |(this can be done using a:focus CSS styles). |

| |[pic] Any page that displays this icon fails KYB_AA1 |

|[pic] |Redundant title text |Title attribute text is the same as |In most cases the title attribute can be removed, |

| | |text or alternative text. |otherwise modify it to provide advisory, but not |

| | | |redundant information. Note that the title text |

| | | |may or may not be read by a screen reader and is |

| | | |typically inaccessible to sighted keyboard users. |

| |Any page that displays this icon may fail KYB_A2ii, KYB_A2iii |

Checklists

Please note that using WAVE requires that each page must be checked individually.

Keyboard

Automated Checking

|Ref |Requirement |Yes |No |

|KYB_A4ii |Is the keyboard focus order meaningful - does the TAB order preserve meaning and | | |

| |operability (i.e. the TABINDEX attribute has not been used as this may interfere | | |

| |with built-in logical tab order)? | | |

|KYB_A5i |Are standard keyboard shortcuts operable (i.e. the ACCESSKEY attribute has not been | | |

| |used as this may interfere with the shortcuts of the browser, operating system, or | | |

| |assistive technology)? | | |

Manual checking (with the tool)

|Ref |Requirement |Yes |No |

|KYB_AA1 |Is there a highly visible keyboard focus indicator on all items (e.g. navigation, | | |

| |content, links, form elements, buttons or any other object control)? | | |

| |Note: Although this is a AA issue, its impact on users is very high and addressing | | |

| |it as if it were a Level A, high impact issue is recommended. | | |

| | | | |

| | | | |

|KYB_A4ii |Is the keyboard focus order meaningful - does the TAB order preserve meaning and | | |

| |operability (i.e. the TABINDEX attribute has not been used as this may interfere | | |

| |with built-in logical tab order)? | | |

|KYB_A5i |Are standard keyboard shortcuts operable (i.e. the ACCESSKEY attribute has not been | | |

| |used as this may interfere with the shortcuts of the browser, operating system, or | | |

| |assistive technology)? | | |

Manual review of the site

|Ref |Requirement |Yes |No |

|KYB_A1 |Is the site keyboard accessible (i.e. there are no keyboard traps within the | | |

| |navigation, content, links, form elements, buttons or any other object control | | |

| |within interactive or static content of the site)? | | |

|KYB_A2i |Is all content keyboard accessible (i.e. all interactive features and static content| | |

| |can be fully accessed and operated with the keyboard alone)? | | |

|KYB_A2ii |Is all content keyboard accessible (i.e. the TITLE attribute has not been used on | | |

| |links to present information not otherwise present on the page)? | | |

|KYB_A2iii |Is all content keyboard accessible (i.e. the TITLE attribute has not been used on | | |

| |images to present information not otherwise present on the page)? | | |

|KYB_A3 |Does the item presentation (e.g. navigation, content, links, form elements, buttons | | |

| |or any other object control) change on keyboard focus? | | |

|KYB_A4i |Does all content appear on keyboard focus (i.e. the appearance of content such as | | |

| |tool tips is consistent with its appearance on mouse over)? | | |

|KYB_A5ii |Are standard keyboard shortcuts operable (i.e. can the navigation be operated | | |

| |through standard keyboard means such as using the TAB key to move across the top | | |

| |menu and the up and down arrow keys to move up and down the navigation dropdown)? | | |

|KYB_A6 |Is all page content and instructional text device-independent (i.e. "click" alone is| | |

| |not used)? | | |

Resources

WAVE

WAVE



WAVE resources



WAVE Help



WAVE Toolbar



Further information

AccessibilityOz

Web: .au

Phone: 03 8677 0828

Email: enquiries@.au

Address: Level 9, 440 Collins Street, Melbourne 3000

-----------------------

AccessibilityOz

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download