WCAG 2.0 FORM FIELDS FOR GRAVITY FORMS
WCAG 2.0 form fields for Gravity Forms compatibility with REEID Translate
WCAG 2.0 form fields for Gravity Forms compatibility with REEID Translate is being reviewed using official plugin documentation. Wraps Gravity Forms radio, checkbox, and list (repeater) fields in a fieldset. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What WCAG 2.0 form fields for Gravity Forms does
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
WCAG 2.0 form fields for Gravity Forms is documented in the Forms category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How WCAG 2.0 form fields for Gravity Forms compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Wraps Gravity Forms radio, checkbox, and list (repeater) fields in a fieldset.
- Improves form validation by displaying an on-page message describing how many errors there were on the page, including a list of the form fields with errors and a link to each field.
- Adds aria-describedby attributes for date and website fields to provide clear instructions for required formats for screen reader users.
- Adds aria-describedby attributes for fields that have failed validation, using the default validation message (or a configured validation message) to provide screen reader users with the field error.
- Changes links in the form body (e.g., field descriptions or HTML fields) so they open in a new window and adds a title that reads 'this link will open in a new window' for screen reader users.
- Disables the Gravity Forms configured tabindex to stop users from tabbing between fields and on-page links.
TRANSLATION BOUNDARY
WCAG 2.0 form fields for Gravity Forms capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- No visitor-facing translation surface was established for this integration.
FREQUENTLY ASKED QUESTIONS
WCAG 2.0 form fields for Gravity Forms and REEID Translate FAQ.
What does WCAG 2.0 form fields for Gravity Forms do?
WCAG 2.0 form fields for Gravity Forms has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does WCAG 2.0 form fields for Gravity Forms have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from WCAG 2.0 form fields for Gravity Forms?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate WCAG 2.0 form fields for Gravity Forms in a multilingual WordPress workflow.
REEID documents WCAG 2.0 form fields for Gravity Forms functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.