Accessibility

y 

n/a 

n 

Recommended 

_ 

_ 

_ 

id: 

All application functions are accessible from the keyboard. 

Recommended 

_ 

_ 

_ 

ie: 

Colors should not be hard coded. 

Recommended 

_ 

_ 

_ 

if: 

Graphic attributes, such as line, border, and shadow, should not be hard coded. 

Recommended 

_ 

_ 

_ 

ig: 

Font sizes and styles should not be hard coded. 

Recommended 

_ 

_ 

_ 

ih: 

All application code uses descriptive names for widgets. Such descriptive names for widgets using graphics instead of text (for example, palette items and icons) allow screen reading software to provide descriptive information to blind users. 

Recommended 

_ 

_ 

_ 

ii: 

Interactions do not depend upon the assumption that a user will hear an audible notification. 

Recommended 

_ 

_ 

_ 

ij: 

Where appropriate, users can choose to receive cues as audio or visual information. 

Recommended 

_ 

_ 

_ 

ik: 

The application does not overuse or rely exclusively on audible information. 

Recommended 

_ 

_ 

_ 

il: 

Users can choose to configure the frequency and volume of audible cues. 

Recommended 

_ 

_ 

_ 

im: 

Tear-off menus and user configurable menus for key application features may be provided for users with language and cognitive disabilities. 

Recommended 

_ 

_ 

_ 

in: 

Application keymappings do not conflict with existing system-level key mappings reserved for access features in the X Windows server as shown in Table 10-6.

Five consecutive clicks of Shift key 

On/Off for StickyKeys 

Shift key held down 8 seconds 

On/Off for SlowKeys and RepeatKeys 

Six consecutive clicks of Control key 

On/Off for screen reader numeric keypad functions. 

Six consecutive clicks of Alt key 

Reserved for future access use