javaserverfaces-spec-public
  1. javaserverfaces-spec-public
  2. JAVASERVERFACES_SPEC_PUBLIC-1159

Add support for WAI-ARIA aria-live property for portions of the page updated via <f:ajax>

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Ajax/JavaScript
    • Labels:
      None

      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

        Activity

        Hide
        Manfred Riem added a comment -

        Setting priority to Minor

        Show
        Manfred Riem added a comment - Setting priority to Minor
        Hide
        Ed Burns added a comment -

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

        Show
        Ed Burns added a comment - Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.
        Hide
        Ed Burns added a comment -

        I like this idea, targeting for 2.3.

        Show
        Ed Burns added a comment - I like this idea, targeting for 2.3.
        Hide
        kito75 added a comment -

        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.

        Show
        kito75 added a comment - 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.

          People

          • Assignee:
            Unassigned
            Reporter:
            kito75
          • Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated: