by ovann86 5 (11 reviews)

WCAG 2.0 form fields for Gravity Forms

Name: WCAG 2.0 form fields for Gravity Forms
Rating: 5.0 (11 reviews)
Author: ovann86

Modifies Gravity Forms form fields and improves validation so that forms meet WCAG 2.0 accessibility requirements.

WCAG 2.0 form fields for Gravity Forms ranks #3,560 among WordPress.org plugins with 4,000+ active installations, is #27 of 627 in the Accessibility category, a 5/5 rating from 11 reviews, and was last updated Apr 24, 2019. Data from WordPress.org, refreshed twice daily — see methodology.

Tested up to WP 5.1 (Current: 7.1.1)

vtrunk Current Version vtrunk

Updated 7 years ago Last Update on 24 Apr, 2019

Refreshed 7 hours ago Last Refreshed on

#27 of 627 in Accessibility Top 5% by installs Downloads +53.1% this week No update in over a year

View on WordPress.org

Rank

#3,560

-1 this week

Active Installs

4K+

-11.9%

KW Avg Position

N/A

— No change

Downloads

99K

+7 today

Support Resolved

— No change

Rating

100%

Review 5 out of 5

5 (11 reviews)

Next Milestone 5K

Total Progress 38.2%

4K+ 5K+

297

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

Upgrade to Pro

Need 618 more installs to reach 5K+

Rank Changes

Current #3,560

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

5.0

11 reviews

Overall 100%

11 (100%)

0 (0%)

Security History

Source: WPVulnerability

No known vulnerabilities on record for WCAG 2.0 form fields for Gravity Forms. Checked 6 days ago.

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: trunk
Last Updated: Apr 24, 2019
Requires WP: 5.0+
Tested Up To: 5.1
PHP Version: N/A
Author: ovann86

Support & Rating

Rating: ★ ★ ★ ★ ★ 5
Reviews: 11
Support Threads: 0
Resolved: 0%

Keywords

accessibility gravity forms usability wcag

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,759

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Embed Plus for YouTube Gallery, Livestream and Lazy Loading with Facades

100K+ installs

#357

404 to 301 – Redirect Manager, 301 Redirection, 404 Error Logs & 404 Monitoring

100K+ installs

#422

Auto Image Attributes From Filename With Bulk Updater (Add Alt Text, Image Title For Image SEO)

100K+ installs

#425

Accessibility by UserWay

Accessibility Widget by OneTap – Easy One-Click Accessibility Toolbar

50K+ installs

#693

Alt Text AI – Automatically generate image alt text for SEO and accessibility

20K+ installs

#1,191

View all Accessibility plugins

TL;DR

AI summary of the plugin's readme

This plugin is for Gravity Forms users who want their forms to meet WCAG 2.0 accessibility requirements. It modifies form fields and validation messages so screen reader users get clearer instructions, error descriptions, and proper field grouping.

Wraps radio/checkbox/list fields in fieldset
On-page validation error summary message
Links errors to form fields
aria-describedby for date and website fields
aria-describedby for validation errors
Disables configured tabindex
Opens body links in new window
Improved file upload field accessibility

Frequently Asked Questions

Common questions about WCAG 2.0 form fields for Gravity Forms

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.

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.

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; });