Jul 05, 2015, 5:35 PM
Ext.net 3.1 Ext JS 5.1 Accessibility ext-aria
looking at the Sencha documentation is says in ext js 5+ the ext-aria package is a separate cmd package
"As of Ext JS 6+, ARIA functionality integrates directly into the component life-cycle. This means you won’t need a special “aria†package to get correct ARIA behavior. Applications will now support screen readers (like JAWS) without the need for special inclusion.
However, in Ext JS 5, the “ext-aria†package is a separate Cmd package that provides support for ARIA States and Properties. The ‘ext-aria’ package should be included in the Sencha Cmd generated app.json file’s requires block like any other package."
Looks like ext.net 3.1 comes with ext js 5.1. I was able to export the ext-aria package using the Sencha Cmd tool but I don't know how I would get it linked into ext.net? We need as much 508 support as we can get. This is the link I was reading: https://docs.sencha.com/extjs/5.1/co...ssibility.html
any help greatly appreciated!
thanks!
"As of Ext JS 6+, ARIA functionality integrates directly into the component life-cycle. This means you won’t need a special “aria†package to get correct ARIA behavior. Applications will now support screen readers (like JAWS) without the need for special inclusion.
However, in Ext JS 5, the “ext-aria†package is a separate Cmd package that provides support for ARIA States and Properties. The ‘ext-aria’ package should be included in the Sencha Cmd generated app.json file’s requires block like any other package."
Looks like ext.net 3.1 comes with ext js 5.1. I was able to export the ext-aria package using the Sencha Cmd tool but I don't know how I would get it linked into ext.net? We need as much 508 support as we can get. This is the link I was reading: https://docs.sencha.com/extjs/5.1/co...ssibility.html
any help greatly appreciated!
thanks!