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:
- it's a huge priority
- there are people dedicated to implementing 508/ARIA support in ExtJS
- some support is already built-in
- other support can be configured "as needed" by the developer
- the "Access" theme is a concrete start
- 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.