My apologies, Justin was mistaken as to our roadmap, or may not have realized that all of the highlighted issues were part of ADA compliance.
Our goal for the project is to be AA compliant by the end of 2017 in time for the new federal regulations next January. We are open to and accepting all input and assistance in this task, though we have not yet started on it specifically (we are still researching and preparing to consult with experts on the subject, as we are certainly not currently experts on accessibility and need help outside of our team.)
I apologize for the confusion. Accessibility is definitely important to our team, and we fully admit we’ve dropped the ball by not getting started sooner.
I have managed to overcome a couple of these limitations by way of jQuery as a “client side” solution. But, in addition to not being able to customize the error messages, I am also unable to affect the secondary pages of the multipart forms. And, bc the forms print as a JS and not inline HTML, the “blur” scripts tend to wipe out some of the changes I have made .. specifically to the event tracking for the submit button.
As I mentioned earlier, we will need to move on from Ninja Forms for this client and future .org projects (we have several more on the horizon). This means that we will likely be using custom developed forms until these ADA compliant features are implemented by NF as we cannot risk our clients getting audited at any time and failing due to technologies we introduce them to and deploy.
However, I am glad to hear that Ninja Forms is at least taking its lack of ADA compliance seriously. And thank you for your response.
-
This reply was modified 2 years, 5 months ago by
vtadmin33313.
If you are interested in helping us with this process, please feel free to create issues or even submit any code you might have that resolves the issue to our GitHub at https://github.com/wpninjas/ninja-forms/
We would absolutely love your feedback as we move forward on ADA compliance.
I have not actually dug through the code base of your plugin to search for an answer. Time restrictions have limited my ability to only perform the actions I have for the client side jQuery “solution”. If I can get caught up on some of my projects, I would be more than happy to take a look to see if I can contribute. Or perhaps another developer within my shop *might* be able to take some time to review.