Radiobutton


type: widget

release: TBD

status: in development - GitHub branch: formcontrols

documentation: N/A

demo: N/A

 

TODOs

 


 

1 - Description:

 

This is a custom radiobutton for situations where a standard OS radiobutton does not fit the visual design system. Ideally, these should employ progressive enhancement and be created and works as a proxy to a standard radiobutton. All standard radiobutton behavior and accessibility features should be included in this widget. If we replace a standard widget, it should never lose features.

 

See also http://forum.jquery.com/topic/jquery-ui-checkbox-radio-button#14737000002542704


 

2 - Visual Design:

 

 


 

 

3 - Functional Specifications/Requirements:

 

(Detailed descrition of how the script will be structured: defaults, options, architecture, extensibility, etc.)

 


 

4 - Markup & Style:

 

     4.1 Initial markup examples

 

     (Pre-enhanced HTML markup structure that will be transformed into the final widget. There may be multiple possible HTML markup options per widget: for example, for a slider, radiobuttons, inputs or selects could all be used. )

 

     4.2 Recommended transformed HTML markup

 

     (The HTML markup structure and classes that will be used by the scripts in the enhanced version) 

 

     4.3 Accessibility recommendation

 

    (Detailed recommendations for ARIA, HTML markup, CSS and javascript that will contribute to universal access and full section 508 accessibility for screen readers, mobile devices and any other devices) 

 

     4.4 CSS & Theme

 

    (Description of the CSS classes to be used for all states, how custom theming and Themeroller support will work.) 

 


 

5 - Latest version of plugin:

 

(Link to the latest version in the jQuery UI trunk here)

 


 

6 - Open issues being discussed

 

(Use this area to place things that we're hashing out like featuresand options we're not sure we should include, questions about how this fits into UI and relates to other widgets and utilities, known problems, whether features should be broken across multiple releases, etc.)