Hi Joe,
I haven’t needed to use a public repository before, so not sure if I did it right.
https://github.com/ovann86/gravity-forms-wcag-20-form-fields
Any contribution is more than welcome as long as it’s moving towards the objective of better accessibility, specifically focusing on the WCAG 2.0 specification.
At the moment I can’t help but feel the plugin is thrown together, so if you think anything can be done better please do what you can.
Thanks.
Adrian
Thanks! I’ll have some contributions soon.
Hi, many thanks for this plugin. I’d started to cobble together my own filters for making Gravity Forms more accessible, but this covers more than I’ve done.
I’d love to contribute, there’s already a few issues I’ve found. However, the version on GitHub isn’t the latest.
I know it’s a pain versioning in two different places, and I’ve not got round to automating anything between GitHub and wordpress.org. However, I’ve found it fine to base the very latest code on GitHub, then tag releases there when I copy code over to SVN for release on wordpress.org. Could you do something like that? I’m a bit wary of working on the GitHub version and then discovering replication of or clashes with code that’s actually already there, but on SVN.
Hi Steve,
Sorry for the delay in responding.
Contribution is more than welcome!
I wrote this plugin to support a project I was working on, so I can say as a fact that I’ve only looked at the standard fields that my project was using. I did read somewhere not to bother using the grouped fields like ‘address’ because they’re an accessibility nightmare – maybe something worth adding to the to do list if it is issue.
There’s two other bugs reported, I’ll let you know once I’ve sorted those out and update the copy on GitHub. (I’m almost certain the copy on GitHub is out of date.)
PS: I’m glad I’m not the only one that sees versioning on GitHub as a pain – it means I end up with a version on my development environment, the wordpress SVN and GitHub – argghh !
