On 3/25/13 5:53 PM, Kito Mann wrote:
> Hello everyone,
>
> There are a couple of ARIA attributes that may not be easily handled
> via pass-through attributes, and I'm thinking they should probably be
> added to all of the standard form controls: aria-required [1] and
> aria-invalid [2].
Shouldn't the standard renderers simply render these attributes
automatically without requiring the page author to specify any
passthrough attributes?
>
> I'm beginning to think an assessment of the standard controls for ARIA
> would be helpful...
Yep. In cases where ARIA attributes have a reasonable mapping to
existing component-level properties (eg. aria-required can be mapped to
<h:inputText>'s required attribute, aria-invalid can be mapped to the
EditableValueHolder's valid state), we should enhance the standard
Renderers to automatically render the ARIA attributes.
For other cases, seems like passthrough attributes are the way to go.
Andy
>
> I recognize we can't do this for 2.2, but is this something we can do
> in a maintenance release, or no?
>
> [1] http://www.w3.org/TR/wai-aria/states_and_properties#aria-required
> [2] http://www.w3.org/TR/wai-aria/states_and_properties#aria-invalid
> ___
>
> Kito D. Mann | @kito99 | Author, JSF in Action
> Virtua, Inc. | http://www.virtua.com | JSF/Java EE training and consulting
> http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info |
> @jsfcentral
> +1 203-998-0403
>
> * Listen to the Enterprise Java Newscast:
> _http://blogs.jsfcentral.com/JSFNewscast/
> _
> * JSFCentral Interviews Podcast:
> http://www.jsfcentral.com/resources/jsfcentralpodcasts/
> * Sign up for the JSFCentral
> Newsletter: http://oi.vresp.com/?fid=ac048d0e17