Appian Community and Appian Academy are being upgraded. From July 24–August 3, the Appian Community will be in read-only mode. During this time, the site will be read-only and user registration will be disabled. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
Hi team,
I have a question regarding accessibility and semantic markup compliance.
In several interfaces, users can enter information or interact with components such as radio buttons and dropdowns. For accessibility reasons, these interactive elements are required to be contained within a <form> element.
<form>
Is there a way to achieve this without using a Form Layout?Currently, the top-level structure of the interface is built using a Header Layout, and I’d prefer not to refactor the entire layout if possible.
Has anyone encountered a similar requirement or found a clean approach to handling this?
Thanks in advance.
Discussion posts and replies are publicly visible
No — interactive components like radio buttons, dropdowns, text fields, etc. do not need to be wrapped in a formLayout() purely for accessibility or semantic markup compliance in Appian.In Appian SAIL, formLayout() is not required to generate an HTML <form> tag for accessibility purposes. Appian handles accessibility and ARIA semantics internally.
Thanks Aditya!