#42 Better support for Accessibility

[Mike Burns]

We'd like to see better support for Accessibility. For example, if you run WAVE (Web Accessibility Evaluation Tool / http://wave.webaim.org/) on FileLocker you receive various error/alert/etc. messages. They're sometimes simple errors like missing a <label> for a form <input>. If Penn State decides to implement FileLocker as a service we'd like to see Accessibility addressed and may be able to partner with you on this.

[Christopher Miller]

I ran the WAVE tool on Filelocker. Unfortunately, due to the current UI architecture (JAvascript actions tied specifically to DOM elements), getting Filelocker to pass would require a substantial UI rewrite. We're looking at eventually doing a full UI rewrite as Filelocker 3.0 with accessibility and internationalization built in from the beginning. We would be interested in partnering with Penn State on this.