proposal for action-649 and action-651

close items related to 4.1.2 Name, Role, State, Value, Description:
leave SC and Intent as is because:
--if we genericize terms no one will know what we are talking about.
--we have added the descriptions of Name, Role, State, etc. in the
Intent, so the terms could be used with other technologies...
Name (component name)
Role (purpose, such as alert, button, checkbox, etc)
State (current status, such as busy, disabled, hidden, etc)
Value (information associated with the component such as, the data in
a text box, the position number of a slider, the date in a calendar
widget)
Description (user instructions about the component).

remove example 1 "A browser is developing a component..." it is
incomplete and need lots more work. Jeanne says it lame.

Jim
-- 
Jim Allan, Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964

Received on Tuesday, 31 July 2012 15:19:20 UTC