Thread Subject: SSA Comments on recommended 1194.21 provisions

Note

This archival content is maintained by WebAIM and NCDAE on behalf of TEITAC and the U.S. Access Board . Additional details on the updates to section 508 and section 255 can be found at the Access Board web site.

From: Baker, Robert C.
Date: Thu, Jun 07 2007 2:50 PM

Initial comments from the SSA Accessibility Staff on the recommended
1194.21 provisions shared at the last TEITAC meeting.


1194.21a (minor edit for clarity)
All functionality of the user interface is operable through a keyboard
interface. Specific timings for individual keystrokes cannot be
required, except where the underlying function requires input that
depends on the path of the user's movement and not just the endpoints.


1194.21 (c)
Consider specifying an acceptable contrast ratio and set a minimal pixel
size for the border to improve testability.


1194.21 (d)
How would an application vendor handle coding for multiple platforms?

Consider exposing page name and page section (heading tag and associate
different sections of a page)

Consider exposing field association directions and cues


1194.21 (g)
Consider deleting "when the availability of those selections are
developed and documented according to industry standards" . We don't
see the need for qualifying it-that confuses it. The systems colors and
fonts should always be an option, and they should always be user
selectable.


1194.21 (h)
Consider adding "Information provided in the animation should be
included (alt text, long description, or on screen)"

Consider deleting the specific reference to equivalent facilitation
here. Equivalent facilitation should not be encouraged as a way of
meeting a standard explicitly in the standard itself.


1194.21 (j)
Consider specifying "n"


1194.21 (l)
Consider specifying what is needed for access to directions and cues -
these have not been raised as a concern. Should this be an expansion of
other requirements - such as 1194.21(d), rather than making it specific
to electronic forms here?


New provisions:
Consider adding a provision for logical tabbing order. SSA runs across
many applications that do not provide a logical tabbing order, creating
situations where we could have "30 keystrokes to one mouse click".

Consider adding a provision for minimal size for clickable elements
including clickable text. (low vision users)

Thanks,
Robert

WebAIM is an initiative of:
Center for Persons with Disabilities (CPD) Utah State University