Thread Subject: Suggested update to 6.1.I so we can remove 6.1.B and 6.1.C (forms & scripting)

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: Peter Korn
Date: Wed, Jun 06 2007 1:10 PM

In the Web & Software subcommittee con-call today, we discussed removing
the forms and scripting provisions because they are covered by our other
provisions. In order to ensure that people reading the standard don't
inadvertently think that forms & script-generated pages aren't covered,
I suggest we simply note them in provision 6.1.I.

Therefore, I suggest the new 6.1.I be:

"For all user interface components, including form elements and those
generated by scripts, the name and role shall be programmatically
determinable, states, properties, and values that can be set by the user
shall be programmatically determinable and can be programmatically set,
and notification of changes to these items is available to user agents,
including assistive technologies. For example: 1. Frames shall be titled
with text that facilitates frame identification and navigation."

With this addition, we can then comfortably remove 6.1.B, which is:

"When electronic forms are used, the form shall allow people using
assistive technology to access the information, field elements, and
functionality required for completion and submission of the form,
including all directions and cues."

And we can further remove 6.1.C., which is:

"When pages utilize scripting languages to display content, or to create
interface elements, the information provided by the script shall be
identified with functional text that can be read by assistive technology."


Regards,

Peter Korn
Accessibility Architect,
Sun Microsystems, Inc.

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