by accessibledotorg 0 (0 reviews)

Accessible Forms by Accessible.org

Name: Accessible Forms by Accessible.org
Author: accessibledotorg

In development – beta phase. Not recommended for use. Do not install. Will be ready November 1.

Accessible Forms by Accessible.org ranks #72,089 among WordPress.org plugins with 0+ active installations, is #496 of 765 in the Accessibility category, and was last updated Oct 29, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.5.5 Current Version v1.5.5

Updated 4 days ago Last Update on 29 Oct, 2026

Refreshed 2 days ago Last Refreshed on

#496 of 765 in Accessibility Actively maintained

View on WordPress.org

Rank

#72,089

— No change

Active Installs

— No change

KW Avg Position

N/A

— No change

Downloads

349

+29 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 10

Total Progress 0%

0+ 10+

44,521

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 10 more installs to reach 10+

Rank Changes

Current #72,089

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

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

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

Start Tracking Free

Plugin Details

Version: 1.5.5
Last Updated: Oct 29, 2026
Requires WP: 6.4+
Tested Up To: 7.1.4
PHP Version: 8.1 or higher
Author: accessibledotorg

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

accessibility contact form form builder forms 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,757

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

#360

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

100K+ installs

#428

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

100K+ installs

#429

Accessibility by UserWay

80K+ installs

#509

Accessibility Widget by OneTap – Easy One-Click Accessibility Toolbar

AccessiYes Accessibility Widget for ADA, EAA & WCAG Readiness

20K+ installs

#1,116

View all Accessibility plugins

Frequently Asked Questions

Common questions about Accessible Forms by Accessible.org

Yes. Each form has its own fields, theme, recipients, subject, button text and confirmation message. Duplicate a form to start from an existing design. The copy is a draft; entries stay with the original form.

Publish the form, then choose “Choose where it appears” in Review & publish, or “Place form” in the forms list. Choose a content type, search for an item and choose its initial position. Open its editor, click “Insert form”, review the position and save. Existing content is preserved, and you can move the block between paragraphs using the normal WordPress block controls. “Create a new page or post instead” starts a draft of the selected content type with the form already included. Sites using the Classic Editor receive a shortcode. Your role's editing, creation and template restrictions still apply. Public custom post types must support the WordPress content editor to appear in this picker.

Yes. Insert the Accessible Form block in a page, post, supported custom content type or template and search for a published form by name. Move the block where you want it. The block previews the published form. Use “Refresh forms” after publishing a new form, or “Refresh preview” after publishing changed settings. Preview controls cannot send a submission. The block offers wide and full-width alignment when the theme supports them. To place a form in a sidebar, use a block-based widget area or a shortcode-capable widget.

In Email & confirmation, expand Use a thank-you page. Search by name or load more pages, then choose one under After submission. Only published pages without passwords are offered. If a chosen page later becomes unavailable or password-protected, visitors receive the inline confirmation instead.

Choose one of the four built-in themes in the Style step. Each passes the plugin's contrast checks: at least 4.5:1 for text and button labels, and 3:1 for button and field boundaries. Focus indicators, checkbox marks, validation feedback and confirmation text use the same checked palette. Your own colors, text size, spacing and layout are available with Accessible Forms Pro, under the same checks. These checks cover the plugin's own color surfaces. A site theme, custom CSS or browser autofill styling can affect the completed page, so inspect it after embedding the form.

Yes. Email, telephone and URL fields receive the relevant browser hints automatically. Recognizable name, company, job title and address labels receive suitable hints too. Advanced options let you choose a specific purpose. To turn autofill off for a question that looks like the visitor's own details, confirm that it asks about someone else, such as a friend's email.

Yes. Save a draft at any setup step. Changes to a published form remain separate until you choose Publish changes. Review & publish previews your current edits; the block and public page use the published version. If your edits break an accessibility rule, they are still saved, and the editor lists what to fix each time you open it. They cannot be published until the problems are fixed, and visitors keep seeing the last version that passed. You can also discard them. The editor points out most problems as you type. Before each publication, review the questions and instructions and confirm the required author review in Review & publish. Changes clear that confirmation. Server checks still run without JavaScript, and first publication through Quick Edit or bulk actions requires the form editor's review. Passing checks is not an accessibility certification. Open keyboard test preview creates a private, working copy of current edits for 30 minutes. Test questions, errors and confirmation with sample answers. It creates no entries or notifications and uploads no files. Without JavaScript file selection is disabled. Test current edits with your site theme lets you choose an editable page for a private snapshot, replacing an existing embed or appending to normal page content without changing the page or live form. Spam verification, save/resume, actual attachments and delivery need a normal staging test. Accessibility test record saves the tested draft and your reported browser, assistive technology, page and results. Leave unperformed tests as Not tested. Ten recent reports are retained and relevant changes mark them out of date. Recording works without JavaScript and does not publish or certify the form. Covering checks examine all active plugin controls and repeat for states you reach; large or interrupted checks remain incomplete.

When an update makes the checks stricter, a published form that no longer passes stays online, so the pages that use it keep working. The forms list, the editor and Tools → Health say which forms need fixing and what to fix.

Labels keep a field's purpose visible while typing and connect the control with its accessible name. Placeholders cannot replace them in this editor. Labels, choices, the heading and the button text must be written in words, not only symbols or emoji, because screen readers announce them as names. Two questions can share a label only under different section headings, and the heading then becomes part of each question's name, such as "Billing address Street".

The public form submits and shows validation feedback without JavaScript. Cached embeds may request one additional review before sending; an uncached form link is also available. If ALTCHA verification is enabled, messages without a token go to Needs review without email notifications. Adding and rearranging fields in the admin editor requires JavaScript.