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

Leverage selectItem.getDescription() to generate "title" attribute

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Minor Minor
    • Resolution: Unresolved
    • Affects Version/s: 1.1
    • Fix Version/s: None
    • Component/s: Components/Renderers
    • Labels:
      None
    • Environment:

      Operating System: All
      Platform: Sun

    • Issuezilla Id:
      137
    • Status Whiteboard:
      Hide

      cat2 renderkitdoc size_small importance_medium

      Show
      cat2 renderkitdoc size_small importance_medium

      Description

      Whenever we render a SelectItem, we could use the getDescription( ) method to
      render a "title" html attribute for additional 508 compliance.

      Ed

        Activity

        Hide
        Ed Burns added a comment -

        >>>>> On Thu, 19 Jan 2006 13:42:59 +0100, Jean-Baptiste BUGEAUD said:

        bjb> Dear JSR abd EG Members,
        bjb> On §4.2.2.1 of JSF1.2 PFD describing the properties of SelectItem, it is
        bjb> written :

        bjb> « description / RW / String / A description of this selection item, for
        bjb> use in development tools. »

        This is a good idea but because it would have a big change on the
        renderers I'm deferring it to the next release.

        bjb> IMHO, a description for a specific item is important data that should be
        bjb> represented to user screen in order to enhance the page accessibility.

        bjb> As an example, (X)HTML got an attribute on most tags that is title, and
        bjb> this description for HTML rendering should ge there if defined. This is
        bjb> the same exact behaviour the disabled property is disabling the
        bjb> selection in HTML using the disabled attribute.

        bjb> So the sentence in the spec should be something like :
        bjb> « A description of this selection item, that can be rendered to the user »

        bjb> Such a description attribute should be IMHO present to most tag so that
        bjb> the same accessibility level can be provided to the page using dynamic
        bjb> content.
        bjb> See WAI for more elements on accessibility : http://www.w3.org/WAI/

        bjb> Regards,
        bjb> Jean-Baptiste BUGEAUD

        Show
        Ed Burns added a comment - >>>>> On Thu, 19 Jan 2006 13:42:59 +0100, Jean-Baptiste BUGEAUD said: bjb> Dear JSR abd EG Members, bjb> On §4.2.2.1 of JSF1.2 PFD describing the properties of SelectItem, it is bjb> written : bjb> « description / RW / String / A description of this selection item, for bjb> use in development tools. » This is a good idea but because it would have a big change on the renderers I'm deferring it to the next release. bjb> IMHO, a description for a specific item is important data that should be bjb> represented to user screen in order to enhance the page accessibility. bjb> As an example, (X)HTML got an attribute on most tags that is title, and bjb> this description for HTML rendering should ge there if defined. This is bjb> the same exact behaviour the disabled property is disabling the bjb> selection in HTML using the disabled attribute. bjb> So the sentence in the spec should be something like : bjb> « A description of this selection item, that can be rendered to the user » bjb> Such a description attribute should be IMHO present to most tag so that bjb> the same accessibility level can be provided to the page using dynamic bjb> content. bjb> See WAI for more elements on accessibility : http://www.w3.org/WAI/ bjb> Regards, bjb> Jean-Baptiste BUGEAUD
        Hide
        Ed Burns added a comment -

        2.1

        Show
        Ed Burns added a comment - 2.1
        Hide
        Ed Burns added a comment -

        Prepare to delete "spec" subcomponent.

        Show
        Ed Burns added a comment - Prepare to delete "spec" subcomponent.
        Hide
        Ed Burns added a comment -

        Move these to unscheduled because we need to target them correctly. 2.next isn't
        specific enough.

        Show
        Ed Burns added a comment - Move these to unscheduled because we need to target them correctly. 2.next isn't specific enough.
        Hide
        rogerk added a comment -

        cat2

        Show
        rogerk added a comment - cat2
        Hide
        Ed Burns added a comment -

        renderkitdoc

        Show
        Ed Burns added a comment - renderkitdoc
        Hide
        Ed Burns added a comment -

        These are targeted at 2.1.

        Show
        Ed Burns added a comment - These are targeted at 2.1.
        Hide
        Ed Burns added a comment -

        triage

        Show
        Ed Burns added a comment - triage
        Hide
        Ed Burns added a comment -

        rogerk

        Show
        Ed Burns added a comment - rogerk
        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage
        Hide
        rogerk added a comment -

        triage

        Show
        rogerk added a comment - triage
        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
        Manfred Riem added a comment -

        Setting priority to Minor

        Show
        Manfred Riem added a comment - Setting priority to Minor

          People

          • Assignee:
            Unassigned
            Reporter:
            Ed Burns
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: