There have been questions about how Episerver Forms is accessible for those with certain disabilities. More specifically, how does Episerver Forms conform to AA Web Content Accessibility Guidelines (WCAG) 2.0?
Episerver Forms, as of v4, does does not fully conform to AA guidelines. The add-on team is seeking to improve Forms on that front, but they offer some suggestions in the mean time.
This issue was raised in this forum thread: http://world.episerver.com/forum/developer-forum/Addons/Thread-Container/2017/1/episerver-forms---aa-compliance/
For now, add-on devs offer the following suggestion:
You can fully customize all view templates.
You don't need to customize the View Engine to point to your new templates.
- By default, no coding required, change in Forms.config file formElementViewsFolder="~/Views/Shared/ElementBlocks"
- You can implement new ICustomViewLocation to point to your (new, add up) location. Take a look at the OpenSource Samples project here.
Information about AA WCAG 2.0: https://www.w3.org/TR/WCAG20/
Please sign in to leave a comment.