by Adrian Gordon
5 (11 reviews)
WCAG 2.0 form fields for Gravity Forms
Modifies Gravity Forms form fields and improves validation so that forms meet WCAG 2.0 accessibility requirements.
Tested up to WP 5.1 (Current: 6.9)
vtrunk
Current Version vtrunk
Updated 6 years ago
Last Update on 24 Apr, 2019
Synced 14 hours ago
Last Synced on
Rank
#3,326
+1 this week
Active Installs
5K+
-6%
KW Avg Position
89.7
+0.4 better
Downloads
96.2K
+14 today
Support Resolved
0%
—
No change
Rating
100%
Review 5 out of 5
5
(11 reviews)
Next Milestone 6K
5K+
6K+
209
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 686 more installs to reach 6K+
Rank Changes
Current
#3,326
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
5.0
11 reviews
Overall
100%
5
11
(100%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 3 of 3| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| wcag | 30 | — | Tag | 15 hours ago |
| usability | 94 | — | Tag | 15 hours ago |
| gravity forms | 145 | — | Tag | 15 hours ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- trunk
- Last Updated
- Apr 24, 2019
- Requires WP
- 5.0+
- Tested Up To
- 5.1
- PHP Version
- N/A
- Author
- Adrian Gordon
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 5
- Reviews
- 11
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
WP Adminify – White Label WordPress, Admin Menu Editor, Login Customizer
7K+ installs
#2,736
Master Addons For Elementor - White Label, Free Widgets, Hover Effects, Conditions, & Animations
40K+ installs
#929
404 to 301 – Redirect, Log and Notify 404 Errors
100K+ installs
#336
Embed Plus for YouTube Gallery, Livestream and Lazy Loading with Facades
100K+ installs
#343
Auto Image Attributes From Filename With Bulk Updater (Add Alt Text, Image Title For Image SEO)
100K+ installs
#433
Frequently Asked Questions
Common questions about WCAG 2.0 form fields for Gravity Forms
If you're having troubles or even better know a solution, please leave a detailed message on the support tab.
I am aware of three issues that are yet to be resolved - duplicate ID's for checkbox lists, duplicate ID's for multi-page form wrappers (the hidden pages have the same ID), and duplicate ID's for the 'Save and continue later' link/button.
Opening links in new windows - isn't that bad practice?
Typically forcing links to open in a new window is bad practice, both from a usability and accessibility point of view. However when it comes to forms there is reason enough to do this - if the user clicks on the link they are taken away from the form - loosing any data they may have provided.
This plugin uses jQuery to modify the form once the browser has loaded it, any links in the form are changed to open in a new window (target='_blank'), then a title is added (or appended to the existing title) which reads 'this link will open in a new window'.
This is the H33: Supplementing link text with the title attribute technique.
I am aware of three issues that are yet to be resolved - duplicate ID's for checkbox lists, duplicate ID's for multi-page form wrappers (the hidden pages have the same ID), and duplicate ID's for the 'Save and continue later' link/button.
Opening links in new windows - isn't that bad practice?
Typically forcing links to open in a new window is bad practice, both from a usability and accessibility point of view. However when it comes to forms there is reason enough to do this - if the user clicks on the link they are taken away from the form - loosing any data they may have provided.
This plugin uses jQuery to modify the form once the browser has loaded it, any links in the form are changed to open in a new window (target='_blank'), then a title is added (or appended to the existing title) which reads 'this link will open in a new window'.
This is the H33: Supplementing link text with the title attribute technique.
I'm concerned it would have a negative consequence on SEO, because:
Search engines may down-rate your website, thinking you're attempting the black hat practice of stuffing a page with keywords that may not have any relevance to the content.
Search engines may index the links with the hidden text. For example, 'document title this link will open in a new window' instead of 'document title'.
I'm willing to be convinced otherwise. But my goal is to make a Gravity Form accessible for everyone - which needs to take into account how it affects search engines.
How is the plugin tested
The plugin is tested using screen-reader software JAWS and the latest version of Internet Explorer, Firefox and Chrome.
The plugin is developed using the latest version of Gravity Forms. The plugin may work in previous versions but could have mixed results. Only the latest version of Gravity Forms can be supported.
The aim of the plugin is to make forms created using Gravity Forms have valid HTML and comply with WCAG 2.0 - level AA.
Each change the plugin makes to a Gravity Form has been decided through research into best practice for usability and accessibility.
How do I disable the tabindex on the validation message
I DO NOT recommend removing the tabindex.
After considered research I am of the belief that tabindex with a value of =-1 is perfectly fine, and infact quite helpful in making critical messages such as a validation message appear immidately for screen reader users.
With that said, if you want to disable it you can add this code to your theme's functions.php file, below the starting <?php line.
add_action('itsg_gf_wcag_disable_tabindex', function () {
return true;
});
Search engines may down-rate your website, thinking you're attempting the black hat practice of stuffing a page with keywords that may not have any relevance to the content.
Search engines may index the links with the hidden text. For example, 'document title this link will open in a new window' instead of 'document title'.
I'm willing to be convinced otherwise. But my goal is to make a Gravity Form accessible for everyone - which needs to take into account how it affects search engines.
How is the plugin tested
The plugin is tested using screen-reader software JAWS and the latest version of Internet Explorer, Firefox and Chrome.
The plugin is developed using the latest version of Gravity Forms. The plugin may work in previous versions but could have mixed results. Only the latest version of Gravity Forms can be supported.
The aim of the plugin is to make forms created using Gravity Forms have valid HTML and comply with WCAG 2.0 - level AA.
Each change the plugin makes to a Gravity Form has been decided through research into best practice for usability and accessibility.
How do I disable the tabindex on the validation message
I DO NOT recommend removing the tabindex.
After considered research I am of the belief that tabindex with a value of =-1 is perfectly fine, and infact quite helpful in making critical messages such as a validation message appear immidately for screen reader users.
With that said, if you want to disable it you can add this code to your theme's functions.php file, below the starting <?php line.
add_action('itsg_gf_wcag_disable_tabindex', function () {
return true;
});