[CLOSED] Which accessibility standard supported by Ext.Net

  1. #1

    [CLOSED] Which accessibility standard supported by Ext.Net

    Hi:

    Generally, which accessibility standard supported by Ext.Net 1 and Ext.Net 2?
    Is there formal document describe that?
    This will decide whether the project will continue using Ext.Net framework.

    Thank you very much
    Last edited by Daniil; Jul 16, 2012 at 9:46 PM. Reason: [CLOSED]
  2. #2
    During the 2.x release cycle Section 508 and WAI-ARIA support should greatly improve. At the moment some of the foundation has been put in place, but there's still work to be done. It's a big a difficult job, but the plan is to at least provide 'Good' support.

    With a little work, developers can implement some functionality (ie, key nav) relatively easily. We have a plan to implement Focus Indicators, at least on Form Fields, but also hopefully all navigational elements.

    The "Access" Theme is an early step in Accessibility directly.

    Example

    <ext:ResourceManager runat="server" Theme="Access" />
    Summary:
    1. it's a huge priority
    2. there are people dedicated to implementing 508/ARIA support in ExtJS
    3. some support is already built-in
    4. other support can be configured "as needed" by the developer
    5. the "Access" theme is a concrete start
    6. enhanced support might be included with ExtJS 4.2, which should be included in Ext.NET 2.1 or 2.2.


    The following Sencha forum post provides some of these same points.

    http://www.sencha.com/forum/showthre...l=1#post839160

    Currently there's only a "partial" support for accessibility in ExtJS 4.1.0.
    If it's programmed with care:
    - with the use extra libraries like https://github.com/madrobby/keymaster (since the keyboard support in Ext is a PITA)
    - enhanced focus to see quickly where the keyboard navigation is heading
    - no pixel values (to allow easy scaling).


    Than it's possible to make an Ext application quite accessible for most groups (except the blind group - but that depends more on the type of app and the interactivity).


    It's allot of extra work to make an app accessible, but the other concurrent frameworks are quite behind ExtJS in this area.
    Hope this helps.
    Geoffrey McGill
    Founder

Similar Threads

  1. [CLOSED] accessibility for Ext.Net
    By leon_tang in forum 1.x Legacy Premium Help
    Replies: 5
    Last Post: Jul 17, 2012, 6:09 PM
  2. Ext.NET HTML compliant code (and accessibility)
    By Tallmaris in forum 1.x Help
    Replies: 5
    Last Post: Jul 31, 2011, 8:27 AM
  3. [CLOSED] Mulitple textbox in Standard prompt dialog
    By CarWise in forum 1.x Legacy Premium Help
    Replies: 3
    Last Post: Nov 25, 2010, 10:12 AM
  4. [CLOSED] Emulating a standard DropDownList
    By randy85253 in forum 1.x Legacy Premium Help
    Replies: 8
    Last Post: Dec 05, 2009, 7:53 PM
  5. [CLOSED] CheckboxSelectionModel Checkall as Standard
    By macap in forum 1.x Legacy Premium Help
    Replies: 11
    Last Post: Aug 05, 2009, 9:17 AM

Tags for this Thread

Posting Permissions