
package com.smartgwt.client.docs;

/**
 * <h3>Accessibility / Section 508 compliance</h3>
 * Smart GWT is a fully accessible technology which fulfills the Section 508 requirements of
 *  U.S. government law and similar international standards.  Specificallly:
 *  <ul>
 *  <li> components are fully keyboard navigable and the browser's native focus indicator reveals
 *  keyboard focus to the user
 *  <li> components are themable/brandable, allowing a variety of high contrast and limited color
 *  range look and feel options to compensate for visual acuity disabilities
 * <li> the WAI-ARIA standard is supported for adding semantic markup to components to identify
 * them to
 *  screen readers such as NVDA or JAWS.
 *  </ul>
 *  <P>
 *  <b>WAI-ARIA support</b>
 *  <P>
 * ARIA is a standard from the WAI (Web Accessibility Institute) that allows modern Ajax
 * applications to
 * add semantic markup to the HTML used to create modern Ajax interfaces to enable screen reader
 * support.
 * This semantic markup allows a screen reader to identify the function and state of complex
 * components
 * such as load-on-demand lists and trees even though they are composed of simple elements such a
 * &lt;div&gt;s.  
 *  <P>
 *  Note that ARIA support is the correct way to evaluate the accessibility of a web
 * <i>application</i>.  Standards which apply to a web <i>site</i>, such as ensuring that all
 * interactive
 * elements are composed of native HTML anchor (&lt;a&gt;) or &lt;form&gt; controls, cannot and
 * should
 * not be applied to a web <i>application</i>.  A web application's accessibility must be
 * evaluated in
 *  terms of its ARIA support.
 *  <P>
 * By default, Smart GWT components will write out limited ARIA markup sufficient to navigate
 * basic
 *  menus and buttons.  Full screen reader mode is not enabled by default because it has a small
 * performance impact and subtly changes the management of keyboard focus in a way that may be
 * less
 *  intuitive when primarily navigating an application with the mouse.
 *  <P>
 * The limited ARIA support which is enabled by default is intended to allow a screen reader user
 * to
 * navigate to a menu to enable full screen reader support.  This is analogous to a partially
 * visually
 * impaired user ariving at a site with normal theming and needing to switch to a high-contrast
 * skin.
 *  <P>
 *  To enable full screenReader mode, call 
 *   SC.setScreenReaderMode() before any
 * Smart GWT components are created or drawn.  This implies that if an end user dynamically
 * enables
 * full screen reader support, the application page must be reloaded, as an any existing
 * components will
 *  not have full ARIA markup.
 *  <P>
 * For an overview of ARIA, see <a href='http://www.w3.org/WAI/intro/aria.php'
 * target='_blank'>http://www.w3.org/WAI/intro/aria.php</a>.
 *  <P>
 *  To completely disable ARIA markup, call
 *  
 *   SC.setScreenReaderMode(false) before any components are drawn.
 *  <P>
 *  <b>Recommended Screen Reader Configuration</b>
 *  <P>
 * The recommended configuration for screen reader use is the most recent available release of
 * Firefox
 *  and either the JAWS or NVDA screen reader.
 *  <P>
 * While WAI-ARIA markup is provided for other browsers, support for WAI-ARIA itself is known to
 * be
 *  limited in current release versions of IE and other browsers supported by Smart GWT.
 *  <P>
 *  <b>Application-level concerns</b>
 *  <P>
 * While Smart GWT enables accessible web applications to be created, it is always possible for an
 * application to violate accessibility standards.  The following is a brief and not exhaustive
 * list of
 *  concerns for application authors:
 *  <ul>
 *  <li> for any operation that can be triggered via drag and drop, you should offer an equivalent
 * keyboard-only means of performing the same operation.  For common grid to grid drags, this is
 * easily
 * accomplished using {@link com.smartgwt.client.widgets.grid.ListGrid#transferSelectedData
 * ListGrid.transferSelectedData()}.
 *  <li> if you use a component in a way that is not typical, such as using an ImgButton as a
 * non-interactive stateful display, set its {@link com.smartgwt.client.widgets.Canvas#getAriaRole
 * Canvas.ariaRole} appropriately.  For a list of ARIA
 * roles, see <a href='http://www.w3.org/WAI/PF/aria/roles#role_definitions'
 * target='_blank'>http://www.w3.org/WAI/PF/aria/roles#role_definitions</a>.
 *  Note that in most cases you will not need to modify the default ariaRole written out by
 *  the Smart GWT framework with screenReader mode enabled.
 * <li> for plain HTML content that is incorporated into an Ajax interface (such as an embedded
 * help
 * system), embed the HTML into an {@link com.smartgwt.client.widgets.HTMLFlow} (whose default
 * ARIA role is "article") and ensure the
 * HTML itself is accessible (for example, has "alt" attributes on all images which are
 * semantically
 *  meaningful)
 *  <li> in addition to setting explicit ARIA roles per canvas, Smart GWT also allows 
 *  developers to specify values for explicit 
 *  
 *  {@link com.smartgwt.client.widgets.Canvas#setAriaState ARIA states}
 * (see <a href='http://www.w3.org/TR/wai-aria/states_and_properties'
 * target='_blank'>http://www.w3.org/TR/wai-aria/states_and_properties</a>) to be written
 *  out with the HTML for a component. <br>
 *  Note that, as with ariaRoles, in most cases the
 *  framework automatically writes out any appropriate aria state information based
 *  on the component being generated - you'd only make use of this property if
 *  using components in some custom way. 
 *  To provide a concrete example: a developer might implement a logical nested
 *  "menu" built from a set of Button instances. In that case, some button might have
 *  ariaRole set to <code>"menuitem"</code> and (if it launches a sub-menu),
 * also the <a href='http://www.w3.org/TR/wai-aria/states_and_properties#aria-haspopup'
 * target='_blank'>"haspopup"</a>
 *  aria state. The code for this would be something like:
 *  
 *  
 *  <pre>
 *   myButton.setAriaRole("menuitem");
 *   myButton.setAriaState("haspopup", true);
 *  </pre>
 *  
 *  </ul>
 *  <p>
 *  <b>Known Screen Reader bugs / quirks</b>
 *  <p>
 *  JAWS: By default, JAWS treats a web page as a web document - text interspersed with graphics,
 *  links, etc. - and not as an application consisting of form controls, interactive buttons,
 * lists, and so on. To enable application mode in JAWS, it is necessary to add
 * <code>role="application"</code>
 *  to the &lt;body&gt; tag. See
 * <a href='http://www.freedomscientific.com/Support/TechnicalSupport/Bulletin/1404'
 * target='_blank'>Freedom Scientific Bulletin 1404 - In ARIA&#44; what is the difference in how
 * JAWS treats role="application" and role="document"?</a>
 * @see com.smartgwt.client.util.isc#setScreenReaderMode
 * @see com.smartgwt.client.widgets.Canvas#setAriaState
 * @see com.smartgwt.client.widgets.grid.ListGrid#getCellRole
 * @see com.smartgwt.client.widgets.grid.ListGrid#getCellAriaState
 * @see com.smartgwt.client.widgets.grid.ListGrid#getRowRole
 * @see com.smartgwt.client.widgets.grid.ListGrid#getRowAriaState
 * @see com.smartgwt.client.widgets.grid.ListGrid#getHeaderButtonAriaState
 * @see com.smartgwt.client.widgets.Canvas#getAriaRole
 * @see com.smartgwt.client.widgets.Canvas#getAriaState
 * @see com.smartgwt.client.widgets.form.fields.FormItem#getAriaRole
 * @see com.smartgwt.client.widgets.form.fields.FormItem#getAriaState
 * @see com.smartgwt.client.widgets.grid.ListGrid#getAriaRole
 * @see com.smartgwt.client.widgets.Img#getAltText
 * @see com.smartgwt.client.widgets.grid.ListGrid#getCanTabToHeader
 * @see com.smartgwt.client.widgets.grid.ListGrid#getCanTabToSorter
 * @see com.smartgwt.client.widgets.grid.ListGrid#getScreenReaderCellSeparator
 * @see com.smartgwt.client.widgets.grid.ListGrid#getScreenReaderRowSeparator
 * @see com.smartgwt.client.widgets.grid.ListGrid#getScreenReaderIncludeFieldTitles
 * @see com.smartgwt.client.widgets.grid.ListGrid#getScreenReaderWriteRowLabelledBy
 */
public interface Accessibility {
}
