Conversational Forms and Edge Delivery: What's Actually New in AEM Forms in 2026

Question

AEM Forms doesn't get as much Reddit airtime as Sites or Assets, but the 2026 release cycle has shipped some notable changes including a genuinely new interaction model. Here's what's actually landed, verified against current Adobe documentation.

1. Conversational Forms (Early Access) chat-style form completion

This is the most novel addition: a Conversational Forms component that can be dragged onto an AEM Sites page with no coding required. Instead of a traditional multi-field form layout, users answer questions one at a time in a chat-style interface closer to talking with a virtual assistant than filling out a form. It's currently Early Access, so treat it as something to pilot, not something to bet a production critical-path form on yet. Worth watching for use cases like lead qualification or intake forms where a conversational flow genuinely improves completion rates over a long static form.

2. Edge Delivery for Forms

Forms now has its own Edge Delivery approach authors can build forms using Excel or Google Sheets as the source, without deep platform training, and get near-perfect Google Lighthouse scores on the resulting live pages. This mirrors the broader AEM Edge Delivery Services direction (document-based authoring, performance-first delivery) but applied specifically to forms a meaningful option if your team already leans on EDS elsewhere and wants forms to follow the same authoring model.

3. Headless Adaptive Forms

Forms can now be created, published, and managed as headless assets accessible purely through APIs no traditional AEM UI dependency for the consuming application. This matters for teams building SPAs or mobile apps that need form logic (validation, conditional fields) without embedding the full AEM Forms rendering stack. Same trade-off as headless Sites content: more flexibility for custom front ends, less in-context authoring convenience.

4. Versioning finally comes to Forms Manager

Forms Manager now supports proper versioning for Adaptive Forms (both Core and Foundation Components), form fragments, themes, XDP templates, and binary assets. You can create versions, view full version history, and restore earlier states directly from the Forms & Documents console. If your team has been managing form versions manually (renaming files, keeping backup copies), this closes a real gap versus how Sites content has been versioned for years.

5. WCAG 2.2 accessibility improvements baked into Core Components

Adaptive Forms Core Components now generate WCAG 2.2-compliant semantic markup for checkbox groups, radio button groups, and the Panel component using proper <fieldset> and <legend> HTML to associate group labels with their options correctly for screen readers. This is a meaningful default-behavior improvement, not just an opt-in setting, so upgrading existing forms to the latest Core Components version may improve accessibility compliance without custom dev work.

6. Small but practical: multi-select dropdowns now render correctly in submission PDFs

A narrow but real fix multi-select dropdown selections are now properly reflected in the generated Submission PDF. Previously, this was a known gap where the PDF output didn't accurately capture what the user selected, which is a real problem for compliance/audit-sensitive form submissions.

Bottom line: the headline feature is Conversational Forms, but the more immediately useful changes for most teams are versioning support and the WCAG 2.2 accessibility defaults both close longstanding gaps rather than chase a new interaction trend. If you're evaluating whether to move existing forms to updated Core Components, the accessibility and PDF-rendering fixes alone are probably worth the upgrade.

Has anyone piloted Conversational Forms yet? Curious whether completion rates actually improved over a traditional layout, or if it just felt novel without moving the needle.

and HTML to associate group labels with their options correctly for screen readers. This is a meaningful default-behavior improvement, not just an opt-in setting, so upgrading existing forms to the latest Core Components version may improve accessibility compliance without custom dev work.6. Small but practical: multi-select dropdowns now render correctly in submission PDFsA narrow but real fix multi-select dropdown selections are now properly reflected in the generated Submission PDF. Previously, this was a known gap where the PDF output didn't accurately capture what the user selected, which is a real problem for compliance/audit-sensitive form submissions.Bottom line: the headline feature is Conversational Forms, but the more immediately useful changes for most teams are versioning support and the WCAG 2.2 accessibility defaults both close longstanding gaps rather than chase a new interaction trend. If you're evaluating whether to move existing forms to updated Core Components, the accessibility and PDF-rendering fixes alone are probably worth the upgrade.Has anyone piloted Conversational Forms yet? Curious whether completion rates actually improved over a traditional layout, or if it just felt novel without moving the needle.