Fixes delayed editor layout changes and off-center review checkmarks, improves early stylesheet loading, and preserves native editing and accessibility safeguards. Existing forms, entries and settings are retained. No database migration is required.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3753663,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3753663,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3753663,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3753663,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3753663,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"accessible-forms\/form":{"$schema":"https:\/\/schemas.wp.org\/trunk\/block.json","apiVersion":3,"name":"accessible-forms\/form","version":"1.4.1","title":"Accessible Form","category":"widgets","icon":"feedback","description":"Add a published contact form with accessible labels, validation, and a checked color theme.","keywords":["contact","enquiry","accessible"],"textdomain":"accessible-forms-by-accessible-org","attributes":{"formId":{"type":"number","default":0}},"supports":{"html":false,"customClassName":false,"align":["wide","full"]},"editorScript":"accessible-forms-block","editorStyle":"accessible-forms-block-editor","viewScript":"accessible-forms"}},"tagged_versions":["1.3.2","1.4.0","1.4.1"],"block_files":[],"assets_screenshots":{"screenshot-1.jpg":{"filename":"screenshot-1.jpg","revision":3753708,"resolution":"1","location":"assets","locale":"","width":1440,"height":1080},"screenshot-2.jpg":{"filename":"screenshot-2.jpg","revision":3753708,"resolution":"2","location":"assets","locale":"","width":1440,"height":1200},"screenshot-3.jpg":{"filename":"screenshot-3.jpg","revision":3753708,"resolution":"3","location":"assets","locale":"","width":1440,"height":1080},"screenshot-4.jpg":{"filename":"screenshot-4.jpg","revision":3753708,"resolution":"4","location":"assets","locale":"","width":1440,"height":1080},"screenshot-5.jpg":{"filename":"screenshot-5.jpg","revision":3753708,"resolution":"5","location":"assets","locale":"","width":1440,"height":1080},"screenshot-6.jpg":{"filename":"screenshot-6.jpg","revision":3753708,"resolution":"6","location":"assets","locale":"","width":1440,"height":1320},"screenshot-7.jpg":{"filename":"screenshot-7.jpg","revision":3753708,"resolution":"7","location":"assets","locale":"","width":1440,"height":1080},"screenshot-8.jpg":{"filename":"screenshot-8.jpg","revision":3753708,"resolution":"8","location":"assets","locale":"","width":1440,"height":1080}},"screenshots":{"1":"Build a form with clear field labels, keyboard reordering and the simplified editor navigation.","2":"Choose a contrast-checked theme and inspect the Normal, Focus and Error previews in Style.","3":"Configure Email & confirmation, insert an answer into the subject and preview a sample notification.","4":"Review the saved configuration, check for blocking problems and complete the required author review before publishing.","5":"Place a published form on a page or post, or use the block and shortcode instructions.","6":"Help visitors correct their answers with a linked error summary and clear field-level messages.","7":"Review Entries using readable status views, search and filters.","8":"Choose a named retention policy and review data-deletion settings under Privacy."}},"plugin_section":[],"plugin_tags":[1953,358,2253,601,1956],"plugin_category":[34,42],"plugin_contributors":[287421],"plugin_business_model":[],"class_list":["post-386209","plugin","type-plugin","status-publish","hentry","plugin_tags-accessibility","plugin_tags-contact-form","plugin_tags-form-builder","plugin_tags-forms","plugin_tags-wcag","plugin_category-accessibility","plugin_category-contact-forms","plugin_contributors-accessibledotorg","plugin_committers-accessibledotorg"],"banners":{"banner":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/banner-772x250.png?rev=3753663","banner_2x":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/banner-1544x500.png?rev=3753663","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/icon.svg?rev=3753663","icon":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/icon.svg?rev=3753663","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/screenshot-1.jpg?rev=3753708","caption":"Build a form with clear field labels, keyboard reordering and the simplified editor navigation."},{"src":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/screenshot-2.jpg?rev=3753708","caption":"Choose a contrast-checked theme and inspect the Normal, Focus and Error previews in Style."},{"src":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/screenshot-3.jpg?rev=3753708","caption":"Configure Email & confirmation, insert an answer into the subject and preview a sample notification."},{"src":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/screenshot-4.jpg?rev=3753708","caption":"Review the saved configuration, check for blocking problems and complete the required author review before publishing."},{"src":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/screenshot-5.jpg?rev=3753708","caption":"Place a published form on a page or post, or use the block and shortcode instructions."},{"src":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/screenshot-6.jpg?rev=3753708","caption":"Help visitors correct their answers with a linked error summary and clear field-level messages."},{"src":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/screenshot-7.jpg?rev=3753708","caption":"Review Entries using readable status views, search and filters."},{"src":"https:\/\/ps.w.org\/accessible-forms-by-accessible-org\/assets\/screenshot-8.jpg?rev=3753708","caption":"Choose a named retention policy and review data-deletion settings under Privacy."}],"raw_content":"\n
Accessible Forms helps you build contact forms that people can complete with a keyboard, a screen reader, magnification or a phone. Visible labels are required, choice fields use real groups, and validation lists every problem in a linked summary. Create as many forms as your site needs, each with its own fields, recipients and confirmation message.<\/p>\n\n
A honeypot, rate limits and link limits run on your own server. You can add self-hosted ALTCHA proof-of-work verification, which contacts no outside service.<\/p>\n\n
Forms include associated labels, optional help text, semantic choice groups, visible required indicators, keyboard focus styles and server-side validation. Repeated embeds use separate control IDs. Forms submit without JavaScript; JavaScript adds in-page submission without a reload.<\/p>\n\n
When you view a page with a form while logged in as someone who can edit it, a live check tests that page as your theme actually renders it (labels, focus, contrast, target size, covered controls, text spacing) and shows the results above the form, only to you. Results are listed under Tools \u2192 Health.<\/p>\n\n
These features support accessible form design. They do not guarantee WCAG conformance or legal compliance. Your theme, page structure, field wording and assistive technology all affect the final experience. Test the finished page with a keyboard and a screen reader. Automated checks do not replace a manual accessibility review.<\/p>\n\n
This plugin sends no analytics or telemetry. Entries store the submitted values, submission time, the page path (without query parameters), browser information, a salted IP hash, spam status and notification outcome. Each form can store less of this metadata. The live accessibility check runs only for logged-in editors and stores, on your site, the page path, the time and the problems it found; results expire after 30 days. See the FAQ for retention, exports and uninstall behavior.<\/p>\n\n
An optional paid add-on, Accessible Forms Pro, adds file uploads, conditional fields, steps, custom styling, more notification options and entry workflow tools. This plugin is complete without it, and accessibility and privacy features are never held back for Pro.<\/p>\n\n
All PHP, CSS and JavaScript is included in human-readable form in the plugin ZIP, and no build step is needed to modify the plugin. The bundled ALTCHA widget and library are unminified; THIRD-PARTY.txt links their original source and build instructions.<\/p>\n\n
ALTCHA browser widget 3.2.3 source and build instructions: https:\/\/github.com\/altcha-org\/altcha\/tree\/v3.2.3\nALTCHA PHP library 2.1.0 source: https:\/\/github.com\/altcha-org\/altcha-lib-php\/tree\/v2.1.0\nBoth are MIT licensed, with their license notices included in this plugin.<\/p>\n\n
This plugin does not connect to outside services.<\/p>\n\n
ALTCHA verification runs entirely on your site. The widget, translations, worker, challenge generation and verification are all served by your WordPress installation. There is no account, API key, tracking collector, verification cookie or call to an ALTCHA-hosted service.<\/p>\n\n\n
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.<\/p><\/dd>\n
Publish the form, then choose \u201cChoose where it appears\u201d in Review & publish, or \u201cPlace form\u201d in the forms list. Choose a content type, search for an item and choose its initial position. Open its editor, click \u201cInsert form\u201d, review the position and save. Existing content is preserved, and you can move the block between paragraphs using the normal WordPress block controls.<\/p>\n\n
\u201cCreate a new page or post instead\u201d 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.<\/p><\/dd>\n
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 \u201cRefresh forms\u201d after publishing a new form, or \u201cRefresh preview\u201d after publishing changed settings. Preview controls cannot send a submission.<\/p>\n\n
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.<\/p><\/dd>\n
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.<\/p><\/dd>\n
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.<\/p>\n\n
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.<\/p><\/dd>\n
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.<\/p><\/dd>\n
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.<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n
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.<\/p><\/dd>\n
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 \u2192 Health say which forms need fixing and what to fix.<\/p><\/dd>\n
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\".<\/p><\/dd>\n
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.<\/p><\/dd>\n
No. Notifications use your existing WordPress mail setup, including any SMTP plugin you already use. A successful test means the mail transport accepted the message; check the recipient's inbox to confirm delivery.<\/p><\/dd>\n
A submission is stored before a notification is attempted. If storage fails, the form shows an error and keeps the visitor's answers. If email fails, the stored entry records the failure and the notification is retried. An uncertain network response does not trigger an automatic second submission.<\/p><\/dd>\n
Each submission is stored first, then a background task sends its notification. Failed attempts retry; if the outcome is uncertain, the entry is flagged for review instead of being resent automatically. WordPress cron depends on site traffic or a server cron job. Settings include a staging test inbox that replaces the real recipients.<\/p><\/dd>\n
Administrators have full access. Editors can build forms but do not automatically see submissions: form editing, reading submissions, exporting, deleting and sending notifications are separate permissions.<\/p><\/dd>\n
WordPress moves it to Trash first. Its existing entries are retained and remain accessible in Entries. You can delete entries separately or let the retention policy remove them.<\/p><\/dd>\n
Completed entries and configuration are retained by default. Enable \u201cDelete all forms and entries when the plugin is deleted\u201d under Privacy to also remove forms, entries and settings. Deactivation keeps data.<\/p><\/dd>\n
Received submissions are kept for 365 days by default. Each form can use the site default, delete entries after a set period, or keep them until manually deleted. The form shows the current site default when it inherits that policy. A new submission keeps the retention policy in effect when it was received. Spam and Needs review entries have a separate 30-day limit. Activity records omit answers and credentials and expire after 90 days. Trash expires after 30 days or the earlier applicable limit. A daily WordPress cron job removes expired records.<\/p><\/dd>\n
WordPress privacy tools match entries by an exact submitted email address; forms without an email field need manual review. Erasure removes matching entries along with their notification payloads, private notes and any stored attachments. Suggested policy text is available in WordPress's privacy policy guide.<\/p><\/dd>\n
ALTCHA runs a proof-of-work check automatically when a visitor uses a form. Challenges are bound to the form and site, expire after 20 minutes, and can be accepted only once. If JavaScript is off or a token is missing, invalid, expired or reused, the message is held in Needs review without an email notification, so review that list regularly. The live site must use HTTPS (localhost also works for development). Proof of work raises the cost of automated abuse; it does not catch all spam or replace moderation.<\/p><\/dd>\n
No. Every feature included in this plugin is available without Pro, payment, a license key or an external account. This includes team roles, role permission controls and creating, editing or removing per-form submission access lists. Accessible Forms Pro is a separate, optional plugin distributed outside WordPress.org; its additional feature code is not included in this package.<\/p><\/dd>\n
The plugin preserves configuration supplied by an add-on so that an administrator can reactivate that add-on later without losing its settings. It does not provide the absent add-on's feature implementation. Existing submissions follow the configured privacy and retention policy. Submission access rules belong to Free and remain manageable and enforced regardless of whether an add-on is active.<\/p><\/dd>\n
No. They flag common wording and structure problems that make forms harder to complete. They cannot tell whether your questions make sense to your visitors, and they do not check your theme or page. Test the finished page with a keyboard and a screen reader.<\/p><\/dd>\n
It focuses on contact forms and enquiries. It does not process payments, reserve event inventory, or offer arbitrary custom CSS controls.<\/p><\/dd>\n
New submission, reply and resolution times are stored in UTC and shown in the current WordPress site time zone. Date filters use calendar days in that zone, including daylight-saving changes. Follow-up dates remain calendar dates. Exported event times include their UTC offset.<\/p>\n\n
Records from development builds may have dates without a known original time zone. They retain their original values and are labelled unconfirmed. Under Tools \u2192 Health, a settings administrator can confirm the original zone for all records or a selected form. Conversion runs in resumable batches and retains the original dates. Repeated daylight-saving hours stay unconfirmed unless an earlier or later occurrence is explicitly chosen. Invalid or nonexistent local times are never guessed. Unconfirmed dates are excluded from response-time statistics and creation-date-based cleanup; an existing UTC expiry or Trash deadline still applies.<\/p><\/dd>\n\n<\/dl>\n\n\n