ks accessibility target & testing responsibilities

7/27/2019 KS Accessibility Target & Testing Responsibilities

1/30

WCAG

#

WCAG

Level Check PDT

QA

Integratio

VISUAL

Ensure that ALL CAPS is not used for long sections of text # x

1.4.4 AA

Set page to 200% zoom and make sure all elements are intact and

usable without any additional horizontal scrolling# x

2.4.4 A

Does all link text make sense on its own, and imply where it will

take the user? x

Are text blocks shorter than 80 characters per line? x

2.4.7 AA

Is it visually apparent which page element has the current

keyboard focus? x x

Make sure there is some visual cue as to where the focus is at any

given moment x

3.3.2 A

Form elements that require a specific format, value, or length are

appropriately explained through help text or form field layout. x x

Are there sufficient instructions and cues in context to help in form

completion and submission? xAre all fields that should be required indicated as such? x

1.3.3 A

Redundant coding - meaning isn't conveyed solely by one type of

sensory characteristic, such as visual (color, size, shape, location,

orientation) - meaning can be programmatically determined x

1.4.1 A

Color: is not the only visual means of conveying info, including

prompting a response, action, or distinguishing a visual element x

1.4.3 AA

Contrast ratio of at least 4.5:1 except for large scale text (3:1), No

minimum ratio for logotypes or things that are decorative (inactive

UI) x x

1.4.5 AA

Text used instead of images of text except for customizable

images (by user) and essential images (logotype) x

2.4.2 A Web pages have titles that describe topic or purpose x x

2.4.6 AA Headings and labels describe topic or purpose x

2.4.5 AA

More than 1 way to locate a web page within a set of pages, except

where the page is the result of, or step in, a process x

3.3.1 A

If an input error is detected, the item that is in error is identified and

the error is described to the user in text x

3.3.3 AA

If error is automatically detected & suggestions for correction are

known, then suggestions are provided to the user (unless it would

jeopardize security or purpose of the content). x

3.3.4 AA

For web pages that cause legal commitments or financial

transactions, that modify or delete user-controllable data in data

storage systems, or that submit user test responses, at least 1 of

following is true: 1-is reversible, 2-data is checked for errors &

user is provided opportunity to correct, 3-mechanism is available to

review, confirm & correct before finalizing submission x

MANUAL


2/30

2.1.1 A

Manually check to ensure all user-manipulable aspects can be

accessed without a mouse, using keyboard only.

x x

2.1.2 A

No keyboard trap: user focus can be moved to and away from a

component of the page x x

Make sure there are no focus stops to elements that can not be

found on the screen x x

1.3.2 A Is the tabbing order the same as the visual order? x

2.4.3 A

Does the order make sense for the task the user is expected to

perform? x

Does the spacebar activate the following controls when they have

input focus: checkboxes, radio buttons? x

3.2.1 A

Focus: when any component receives focus, it does not initiate a

change of context x x

3.2.2 A

Input: changing the setting of any user interface component

doesn't automatically change the context unless the settings

change process advises the user of the behavior before invoking

the component x

3.2.3 AA

Navigation mechanisms that are repeated on multiple web pages

are in the same consistent order unless a change is initiated by the

end user

3.2.4 AA

Components that have same functionality within set of web pages

are identified consistently x

4.1.1 A

Parsing: in content implemented using markup languages,

elements have complete start and end tags, elements are nested

according to their specifications, elements do not contain duplicate

attributes, & IDs are unique (except where specs allow thesefeatures) x

4.1.2 A

Name, role, value: for all UI components, the name & role can be

programmatically determined; states, properties & values set by

the user can be programmatically set; and notification of changes

to these items is available to user agents, including assistive

technologies.

SCREEN READER

n/a

Use a screen reader with the page open to ensure that the page

can be read/spoken by the screenreader

n/a

The navigation order of links, form elements, etc. is logical and

intuitive.

n/a

Does the order make sense for the task the user is expected to

perform?

1.3.2 A Is the reading order correct?

1.3.2 A Is the reading order the same as the visual order?

1.3.1

Is the page broken into appropriate groups of content? Is this

reflected in the hierarchy of headers (whether off-screen or on-

screen)? x x

n/a Are all items visually presented as headers also coded as such? x


3/30

1.1.1A

Is there appropriate alt text for images and unlabeled buttons (i.e.

icon-only buttons)? x x

n/a

Any fields that are part of a field group, each input has its own off-

screen label. x x

2.4.1 A

Provide a way to bypass blocks of content that are repeated on

multiple pages

3.3.1 A

If an input error is detected, the item that is in error is identified and

the error is described to the user in text

4.1.2 A

Name, role, value: for all UI components, the name & role can be

programmatically determined; states, properties & values set by

the user can be programmatically set; and notification of changes

to these items is available to user agents, including assistive

technologies.


4/30

QA System

Level UX Core Notes

Link purpose (in context): the purpose of each

link can be determined from the link text alone

or from the link text together with its

programmatically-determined link context

Labels or instructions are provided when

content requires user input

Not likely to be in build unless UXD suppliesimage. Can be checked by seeing if part of

word can be selected using cursor. If not, it's an

image of text rather than rendered text.

Also noted in Screen Reader section.

This is primarily about providing explicit and

meaningful error messaging:

http://www.w3.org/TR/UNDERSTANDING-

WCAG20/minimize-error-suggestions.html

The KRAD framework provides both client-side

and server-side error validation, which meets

this critierium (#2).


5/30

Can all links, controls, and buttons be activated

with the enter key?

Does the spacebar activate the following

controls when they have input focus:

checkboxes, radio buttons?

Does the escape key close dialogs?

x x

@UX: What do we do about context switchers,

which are placed above the breadcrumbs on

some pages?

x x

This calls for general UI consistency:

http://www.w3.org/TR/UNDERSTANDING-

WCAG20/consistent-behavior-consistent-

functionality.html. Adherence to UIM will allow

PDTs to meet this critieria.

x @UX: Is this done using code checkers?

x

@UX: Is this what ARIA covers? And is this

done using code checkers?

Also noted in Screen Reader section.

x

x

x

x

x

x


6/30

x

x

x

A "Skip to main content" link should be included

as part of the applicaition boilerplate

x

x


7/30


8/30


9/30


10/30


11/30


12/30

NA at this time (assuming

no audio)1.4.2

Required (AA) 1.4.3

Required (AA) 1.4.4

Required (AA) 1.4.5

No 1.4.6

NA at this time 1.4.7

Consider 1.4.8

Consider 1.4.9

KEYBOARD

ACCESSIBLE2.1

Required (A) 2.1.1

Required (A) 2.1.2

Consider

2.1.3

TIMING-SENSITIVE

ASPECTS - Review

assumption of none in

KRAD UI at this time

2.2



Keyboard Accessible:

Enough time: provide users enoug


13/30

NA at this time

2.2.3

NA at this time2.2.4

Consider requiring this

one! (AAA)2.2.5

FLASHING ASPECTS:

Review assumption of

none in KRAD UI at this

time

2.3


NA at this time

2.3.2

NAVIGATION 2.4

Required (A) 2.4.1Required (A) 2.4.2

Required (A) 2.4.3

Required (A) 2.4.4

Required (AA) 2.4.5

Required (AA) 2.4.6

Required (AA) 2.4.7


one! (AAA) 2.4.8


one! (AAA)

2.4.9


one! (AAA) 2.4.10

READABLE 3.1

3.1.1



one! (AAA)3.1.3


one! (AAA) 3.1.4

Readable: content is readable & un

Seizures: Do not design content in

Navigable: Provide ways to help us


14/30

No

3.1.5


one! (AAA)

3.1.6

PREDICTABLE 3.2

Required (A) 3.2.1

Required (A) 3.2.2

Required (AA) 3.2.3

Required (AA) 3.2.4


one! (AAA)3.2.5

HELP & ERROR

HANDLING3.3

Required (A) 3.3.1

Required (A) 3.3.2

Required (AA) 3.3.3

Required (AA) 3.3.4


one! (AAA) 3.3.5


one! (AAA)

3.3.6

COMPATIBLE 4.1

Predictable: web pages appear & o

Help users avoid and correct mista

Compatible: maximize compatibili


15/30

Required (A) 4.1.1

Required (A)4.1.2


16/30

uickref/Overview.php

LEVEL A - Priority 1 (25 criteria)

All non-text content that is presented to user has a text

alternative. See WCAG link above for details on exceptions.

Alternative provided for pre-recorded Audio-only and Video-only

Captions provided for pre-recorded audio in synchronized media

(except where media is alternative for displayed text)

Alternative provided for synchronized media (e.g., audio

description of video segments except where video is alternative

for displayed text)

(Level AA)

(Level AA)

(Level AAA)

(Level AAA)

(Level AAA)

(Level AAA)

Info & relationships: info, structure & relationships can be

programmatically determined or are available in text

Meaningful sequence: a correct reading sequence can be

programmatically determined

Sensory characteristics: redundant coding - meaning isn't

conveyed solely by one type of sensory characteristic, such as

visual (size, shape, location, orientation) or sound - meaning can

be programmatically determined

Color: is not the only visual means of conveying info, including

prompting a response, action, or distinguishing a visual element

sers to see & hear content including separating foreground

atives for any non-text content.

ives for:

d in different ways without losing info or structure


17/30

Audio control: a mechanism must be available to pause or stop

audio content, or to control the volume independently from the

overall system volume

(Level AA)

(Level AA)

(Level AA)

(Level AAA)

(Level AAA)

(Level AAA)

(Level AAA)

All functionality & info is operable through a keyboard interface

w/o requiring specific timings for individual keystroke (see

WCAG link above for exceptions)

No keyboard trap: user focus can be moved to and away from a

component of the page

(Level AAA)

Timing adjustable: time limit can be turned off, adjusted or

extended by user (see WCAG link above for exceptions)

User can pause, stop, or hide any moving, blinking, scrolling, or

auto-updating info

time to read and use content


18/30

(Level AAA)

(Level AAA)

(Level AAA)

Do not include anything that flashes more than 3 times in a

second, that violates general flash and red flash levels (affected

by frequency, luminance, area, & color).

(Level AAA)

Provide a way to bypass blocks of content that are repeated on

multiple pagesWeb pages have titles that describe topic or purpose

When sequential navigation sequences affect meaning or

operation, focusable components receive focus in an order that

preserves meaning & operability

Link purpose (in context): the purpose of each link can be

determined from the link text alone or from the link text together

with its programmatically-determined link context

(Level AA)

(Level AA)

(Level AA)

(Level AAA)

(Level AAA)

(Level AAA)

the default human language of each web page can be

programmatically-determined

(Level AA)

(Level AAA)

(Level AAA)

derstandable

way that is known to cause seizures

ers navigate, find content, and determine where they are


19/30

(Level AAA)

(Level AAA)

Focus: when any component receives focus, it does not initiate a

change of context

Input: changing the setting of any user interface component

doesn't automatically change the context unless the settings

change process advises the user of the behavior before invoking

the component

(Level AA)

(Level AA)

(Level AAA)

If an input error is detected, the item that is in error is identified

and the error is described to the user in text

Labels or instructions are provided when content requires user

input

(Level AA)

(Level AA)

(Level AAA)

(Level AAA)

perate in predictable ways

es

y with current & future user agents, including assistive techn


20/30

Parsing: in content implemented using markup languages,

elements have complete start and end tags, elements are

nested according to their specifications, elements do not contain

duplicate attributes, & IDs are unique (except where specs allow

these features)

Name, role, value: for all UI components, the name & role can

be programmatically determined; states, properties & values set

by the user can be programmatically set; and notification of

changes to these items is available to user agents, including

assistive technologies.


21/30

LEVEL AA - Priority 2 (13 criteria)

(See level A)

(See level A)

(See level A)

(See level A)

Captions provided for all live audio (A=for all pre-recorded audio,

AA=also for all live audio)

Audio descriptions provided for all pre-recorded video segments

(synchronized with other sound in the video, unless the existing

audio explains all w/o needing the visual)

(Level AAA)

(Level AAA)

(Level AAA)

(Level AAA)

(See level A)

(See level A)

(See level A)

(See level A)

rom background

Conformance Level/Priority Descriptions


22/30

(See level A)

Contrast ratio of at least 4.5:1 except for large scale text (3:1),

No minimum ratio for logotypes or things that are decorative

(inactive UI)

Text can be resized up to 200% without assistive technologies

(except for captions & images of text)

Text used instead of images of text except for customizable

images (by user) and essential images (logotype)

(Level AAA)

(Level AAA)

(Level AAA)

(Level AAA)

(See level A)

(See level A)

(Level AAA)

(See level A)

(See level A)


23/30

(Level AAA)

(Level AAA)

(Level AAA)

(See level A)

(Level AAA)

(See level A)(See level A)

(See level A)

(See level A)

More than 1 way to locate a web page within a set of pages,

except where the page is the result of, or step in, a process

Headings and labels describe topic or purpose

Any keyboard operable UI has mode of operation where

keyboard focus indicator is visible

(Level AAA)

(Level AAA)

(Level AAA)

(See level A)

Multiple languages: for docs with multiple language (passages or

words) the language can be identified by assistive technologies

(so are pronounced appropriately)

(Level AAA)

(Level AAA)


24/30

(Level AAA)

(Level AAA)

(See level A)

(See level A)

Navigation mechanisms that are repeated on multiple web pages

are in the same consistent order unless a change is initiated by

the end user

Components that have same functionality within set of webpages are identified consistently (includes alt text on )

(Level AAA)

(See level A)

(See level A)

If error is automatically detected & suggestions for correction are

known, then suggestions are provided to the user (unless itwould jeopardize security or purpose of the content).

For web pages that cause legal commitments or financial

transactions, that modify or delete user-controllable data in data

storage systems, or that submit user test responses, at least 1 of

following is true: 1-is reversible, 2-data is checked for errors &

user is provided opportunity to correct, 3-mechanism is available

to review, confirm & correct before finalizing submission

(Level AAA)

(Level AAA)

ologies


25/30

(See level A)

(See level A)


26/30

LEVEL AAA - Priority 3 (23 criteria)

(See level A)

(See level A)

(See level A)

(See level A)

(See level AA)

(See level AA)

Sign language interpretation is provided for all prerecorded

audio content in synchronized media.

Where pauses in foreground audio are insufficient to allow

audio descriptions to convey the sense of the video, extended

audio description is provided for all prerecorded video content

in synchronized media.An alternative for time-based media is provided for all

prerecorded synchronized media and for all prerecorded video-

only media.

An alternative for time-based media that presents equivalent

information for live audio-only content is provided

(See level A)

(See level A)

(See level A)

(See level A)


27/30

(See level A)

(See level AA)

(See level AA)

(See level AA)

Contrast ratio of at least 7:1 except for large-scale text (4.5:1),

No minimum ratio for logotypes or things that are decorative

(inactive UI).

Low or no background audio: For prerecorded audio-only that

(1) contains primarily speech in the foreground, (2) is not an

audio CAPTCHA or audio logo, and (3) is not vocalization

intended to be primarily musical expression such as singing or

rapping, at least one of the following is true: the audio doesn't

have background sounds, or the background sounds can be

turned off, or the background sounds area at least 20 decibels

lower than the foreground speech content (4 times quieter).

Visual presentation of blocks of text: foreground and

background colors can be selected by user, width is no more

than 80 characters or glyphs, text is not justified to both right

and left margins, line spacing (leading) is at least 1.5 within

paragraphs & 1.5 times larger than that between paragraphs,

text can be resized without assistive technology up to 200

percent in a way that doesn't require user to scroll horizontally

to read a line of text on a full-screen window.

Images of text: only used for pure decoration, essential

images - inlcudes logotypes. (Same as1.4.5 except noexceptions via user-customization are allowed.)

(See level A)

(See level A)

All functionality of the content is operable through a keyboard

interface without requiring specific timings for individual

keystrokes. Same as 2.1.1 except no exceptions are allowed.

(See level A)

(See level A)


28/30

Timing is not an essential part of the event or activity presented

by the content, except for non-interactive synchronized media

and real-time events.

Interruptions can be postponed or suppressed by the user,

except interruptions involving an emergency.

When an authenticated session expires, the user can continue

the activity without loss of data after re-authenticating.

(See level A)

Web pages do not contain anything that flashes more than

three times in any one second period, over any area of the

screen (regardless of general and red flash levels).

(See level A)(See level A)

(See level A)

(See level A)

(See level AA)

(See level AA)

(See level AA)

Information about the user's location within a set of Web pages

is available.

Link purpose (link only): A mechanism is available to allow the

purpose of each link to be identified from link text alone, except

where the purpose of the link would be ambiguous to users in

general.

Section headings are used to organize the content (within

writing, 4.1.2 covers this within UI components).

(See level A)

(See level AA)

Unusual words: A mechanism is available for identifying

specific definitions of words or phrases used in an unusual or

restricted way, including idioms and jargon.

Abbreviations: A mechanism for identifying the expanded form

or meaning of abbreviations is available


29/30

Reading level: When text requires reading ability more

advanced than the lower secondary education level after

removal of proper names and titles, supplemental content, or a

version that does not require reading ability more advanced

than the lower secondary education level, is available.

Pronunciation: A mechanism is available for identifying specific

pronunciation of words where meaning of the words, in context,

is ambiguous without knowing the pronunciation.

(See level A)

(See level A)

(See level AA)

(See level AA)

Change on request: Changes of context are initiated only by

user request or a mechanism is available to turn off such

changes

(See level A)

(See level A)

(See level AA)

(See level AA)

Help: Context-sensitive help is available.

Error prevention: For Web pages that require the user to

submit information, at least one of the following is true:

submissions are reversible, or data is checked and user is

provided opportunity to correct them, or a mechanism is

available for reviewing, confirming and correcting info before

finalizing submission


30/30

(See level A)

(See level A)

ks accessibility target & testing responsibilities

Documents