[JAVASERVERFACES_SPEC_PUBLIC-1159] Add support for WAI-ARIA aria-live property for portions of the page updated via <f:ajax> Created: 28/Jan/13  Updated: 01/Aug/14

Status: Open
Project: javaserverfaces-spec-public
Component/s: Ajax/JavaScript
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Minor
Reporter: kito75 Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Tags: accessibility

 Description   

Currently, JSF doesn't have any explicit support for WAI-ARIA (http://www.w3.org/WAI/intro/aria.php), except for the role attribute. <f:ajax> should be updated to use the aria-live attribute at the very least.

See EG thread here: http://java.net/projects/javaserverfaces-spec-public/lists/jsr344-experts/archive/2013-01/message/5



 Comments   
Comment by kito75 [ 01/Mar/13 ]

After looking at this in more detail, there are several attributes that one may need to apply to the element that's being updated by an Ajax:

  • role
  • aria-live
  • aria-busy
  • aria-atomic
  • aria-relevant

(See http://www.w3.org/TR/wai-aria-practices/#LiveRegions)

Only the page author (and possibly the component being re-rendered) know which attributes should be set, and what the values should be. Since the regions are denoted with these attributes up-front, perhaps there's not much for <f:ajax> to do after all, because the page author can either use pass-through attributes or HTML5-friendly markup to specify these attributes on the component that needs to be updated.

Comment by Ed Burns [ 27/Mar/13 ]

I like this idea, targeting for 2.3.

Comment by Ed Burns [ 01/Aug/14 ]

Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

Comment by Manfred Riem [ 01/Aug/14 ]

Setting priority to Minor

Generated at Sat Apr 25 02:11:38 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.