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 ARIA attributes, passthrough attributes can be used.
This task requires an analysis of the input controls to determine which ones need changes, but generally speaking any UI component that maps to a native HTML widget should support aria-invald and aria-rquired attributes, and possibly aria-readonly. For a full list of support states and properties, see: http://www.w3.org/TR/wai-aria/states_and_properties#state_prop_def.
Original thread: http://java.net/projects/javaserverfaces-spec-public/lists/jsr344-experts/archive/2013-03/message/124