Edit ISSUE-331: Discuss UA requirement of syncing DOM attributes that refer to the same accessibility state or property (e.g. HTML 5 @required and @aria-required)

Nickname:

Title:

State:

Product:

Raised By:

Description:
Discuss UA requirement (recommendation?) of syncing DOM attributes that refer to the same accessibility state or property (e.g. HTML 5 @required and @aria-required). Although I think it's probably the right way to go, DOM purists are gonna have a problem with this, and it will make more work for browser vendors, so we should definitely defer this discussion for ARIA 1.0. This would be similar to the way browsers manage other states like HTMLCheckboxElement.checked, where it can either be changed via the property or the attribute. When one is changed, the other is synced. If an element's 'required' property was changed, then that change should be reflected in the DOM by any attributes that refer to the property, including both @required and @aria-required. For example, on the following HTML 5 element: <input> 1. Author changes DOM attribute via el.setAttribute('aria-required', 'true'); 2. UA changes element's 'required' property to reflect the explicit DOM attr change. 3. UA changes the other DOM attr (@required) to reflect the implicit property change. Final result would be this DOM element: <input required aria-required="true">

Add notes (no markup allowed, URIs get automatically hyperlinked):

No related emails.

No User notes.

Accessible Rich Internet Applications Working Group Issue Tracking

Edit ISSUE-331: Discuss UA requirement of syncing DOM attributes that refer to the same accessibility state or property (e.g. HTML 5 @required and @aria-required)