Thread Subject: 3-P User Interface Components
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: Andi Snow-Weaver
Date: Wed, Feb 06 2008 8:45 AM
- Return to this mailing list's archives
- View all messages in this thread
- Next message in thread: None
- Previous message in thread: None
- Messages sorted by: Author | Thread | Date
Based on feedback from Allen, we have discovered an error in the wording of
3-P User Interface Components. The current wording requires that states,
properties, and values be programmatically determinable only for user
interface components that can be set by the user. But this information is
also important for UI components that cannot be modified by the user. This
is not an intentional omission but rather an oversight.
I would therefore like to propose rewording the provision.
<current>
For all user interface components, including form elements and those
generated by scripts, the name and role must be programmatically
determinable. States, properties, and values that can be set by the user
must be programmatically determinable and can be programmatically set. Any
notification of changes to these items must be available to user agents,
including assistive technologies.
<current>
<proposed>
For all user interface components, including form elements and those
generated by scripts, the name, role, states, properties, and values must
be programmatically determinable. States, properties, and values that can
be set by the user can also be programmatically set. Any notification of
changes to these items must be available to user agents, including
assistive technologies.
</proposed>
Since this provision is harmonized with WCAG 2.0, we have also proposed the
same re-wording to the WCAG working group.
Andi
- Next message in Thread: None
- Previous message in Thread: None
WebAIM is an initiative of:
