AccessibilityOz



Bureau of Meteorology

Manager Factsheet

Keyboard

By: AccessibilityOz

Date: October 2013

Contents

Bureau of Meteorology Manager Factsheet Keyboard 0

Contents 1

Overview 2

Keyboard accessibility principles 2

Impact on users 3

Manager Checklist – Keyboard 5

Level A 5

The Web Content Accessibility Guidelines 2.0 7

WCAG 2.0 Accessibility Guidelines 7

Using automated testing tools 7

Introduction 7

Recommended tools 7

Testing keyboard with the Web Developer Toolbar 8

Testing keyboard with WAVE 8

Testing keyboard with OzART 8

Resources 10

Accessibility 10

Tools 10

Further Information 11

AccessibilityOz 11

Overview

Keyboard accessibility principles

Website accessibility via the keyboard is one of the most important aspects of disability access. Keyboard accessibility is important to people with the following disabilities:

▪ Blindness;

▪ Low vision;

▪ Motor impairments; and

▪ Cognitive impairments.

It is commonly known that websites are often accessed using the mouse. However, for many users, the use of the keyboard can increase their ability to navigate and access the content and functionality of a web page effectively. Some users will rely on their keyboard exclusively. Individual use and combinations of keys such as the ‘TAB’, ‘Ctrl’, ‘Shift’, ‘Enter’ and arrow keys are used, sometimes in conjunction with the use of other assistive technologies such as screen readers.

Areas of importance for keyboard access are also covered specifically in the relevant category factsheets:

▪ Navigation

Use of main and sub navigation with and without the use of JavaScript.

▪ Content

Accessing links and moving around the page, avoiding reference to device-dependent handlers within page content or feature instructions.

▪ Coding

Controlling moving or scrolling content.

▪ Forms

Entering, validating and submitting information.

▪ Interactive site features

Using Interactive maps and Image maps; Slideshows; Image galleries; Virtual tours; Magazines; Calendars; Flash or JavaScript features and Java applets; Audio/Video and any other interactive object.

Accessibility principles specific to the use of the keyboard include, but are not limited to:

▪ Avoid keyboard traps

o When a keyboard user encounters a keyboard trap and is therefore unable to exit a site feature or content area they are effectively stuck and must close the browser window and start again. If all content, controls and interactive elements cannot be accessed and/or operated via the keyboard, users that rely on the keyboard alone will be unable to navigate or understand the site.

▪ Ensure that all content can be accessed with the keyboard alone

o Do not prevent keyboard users from accessing any website content or functionality.

o Ensure that standard keyboard shortcuts are operable and that the navigation can be accessed through standard means.

o Avoid referring to device-dependent handlers (e.g. “click”) within page content or instructional text.

▪ Keyboard focus indicator is highly visible and clear

o Do not remove visible keyboard focus indicators on any items i.e. links, navigation, form fields, buttons or any other object control.

▪ Ensure that all information is available via the keyboard

o Avoid the use of the TITLE attribute on links and images as this information cannot be accessed by the keyboard.

o Ensure that all content appears on keyboard focus in a way which is consistent with content appearing on mouse over e.g. tool tips.

▪ Item presentation changes on keyboard focus

o Item presentation should change when keyboard focus is received in the same way as when a mouse hovers over the content.

Impact on users

The following is an overview of common keyboard accessibility errors and the impact on users with a disability.

• Avoid keyboard traps

When a keyboard user encounters a keyboard trap they are unable to exit a site feature or content area and are effectively stuck and must close the browser window and start again.

• Ensure that all content can be accessed with the keyboard alone

Content, controls and interactive elements that cannot be accessed and/or operated via the keyboard will not be available to keyboard users.

▪ Keyboard focus indicator is highly visible and clear

Without a highly visible keyboard focus indicator on all items such as links, navigations, form fields, buttons or any other object control, the keyboard user is unable to perceive where they are on the page content, or within the interactive site feature, and take their desired action.

▪ Ensure that all information is available via the keyboard

When the TITLE attribute is used on links and images to present information not otherwise available on the web page the keyboard user is not able to access this content.

▪ Item presentation changes on keyboard focus

A change in item presentation, in the same manner as when the mouse hovers over the item, aids navigation around the site, location of desired information and activation of required functionality.

Manager Checklist – Keyboard

The following checklist is intended to guide managers on the review of keyboard accessibility. It should be used during the review phase to ensure compliance of the site.

Areas of importance to be reviewed for keyboard access are also covered specifically in the relevant category factsheet:

▪ Navigation; Content; Coding; Forms and Interactive site features (e.g. Interactive Maps, Slideshow, Image Gallery etc).

Level A

|Ref |Requirement |Pass |Fail |

|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_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_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_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)? | | |

|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)? | | |

The Web Content Accessibility Guidelines 2.0

WCAG 2.0 Accessibility Guidelines

The Web Content Accessibility Guidelines relevant to keyboard accessibility include:-

|Guideline |Description |

|2.1 |Keyboard Accessible: Make all functionality available from a keyboard. |

|2.4 |Navigable: Provide ways to help users navigate, find content, and determine where they are. |

Copyright © W3C 11 December 2008 World Wide Web Consortium [Status: Recommendation]

The relevant success criterion, appropriate techniques and common failures are detailed in the website developer factsheet.

Using automated testing tools

Introduction

Automated testing tools are useful in assisting content managers and web developers with the identification of accessibility issues and errors of a website.

These tools are able to perform ‘machine-operable’ testing only, and should be used as a companion alongside human site review and testing.

The following testing tool information is provided as a guide only and is not an exhaustive list.

Recommended tools

The following testing tools are recommended as the most suitable, based on volume of pages being tested:

|Tool |Volume of pages |Type of tool |

|Web Developer Toolbar |Single pages. |Free browser extension for Firefox or Chrome. |

|WAVE |Single pages or small section of |Free online tool – can be used online or download the |

| |pages. |toolbar. |

|OzART |Large section of pages or entire |Online reporting tool – produces error category specific |

| |website. |reports, reduces time spent manually inspecting single web |

| | |pages. |

NB: In some instances only one tool may be suitable regardless of the volume of pages to be tested. In addition, if no tool is suitable a manual site review will be required.

Testing keyboard with the Web Developer Toolbar

The following KYB references are requirements from the Checklist.

|Automatic |Manual required |Not assessed |

|KYB_A4ii |KYB_A2ii |KYB_AA1 |

|KYB_A5i |KYB_A2iii |KYB_A1 |

| | |KYB_A2i |

| | |KYB_A3 |

| | |KYB_A4i |

| | |KYB_A5ii |

| | |KYB_A6 |

Testing keyboard with WAVE

The following KYB references are requirements from the Checklist.

|Automatic |Manual required |Not assessed |

|KYB_A4ii |KYB_AA1 |KYB_A1 |

|KYB_A5i | |KYB_A2i |

| | |KYB_A2ii |

| | |KYB_A2iii |

| | |KYB_A3 |

| | |KYB_A4i |

| | |KYB_A5ii |

| | |KYB_A6 |

Testing keyboard with OzART

The following KYB references are requirements from the Checklist.

|Automatic |Manual required |Not assessed |

|KYB_A4ii |KYB_A2ii |*KYB_A1 |

|KYB_A5i |KYB_A2iii |*KYB_A2i |

| |KYB_A6 |*KYB_A3 |

| | |*KYB_A4i |

| | |*KYB_A5ii |

| | |*KYB_AA1 |

* OzART does provides the location of site features that require manual testing

Resources

Accessibility

Disability Discrimination Act 1992



A brief guide to the Disability Discrimination Act

(by the Australian Human Rights Commission)



World Wide Web Access: Disability Discrimination Act Advisory Notes

(by the Australian Human Rights Commission)



WCAG2 (W3C Web Content Accessibility Guidelines, Version 2.0)



Web Accessibility National Transition Strategy



Tools

Web Developer Toolbar



WAVE page by page accessibility tool



OzART reporting tool

.au

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