How to make the Form Primitive More Accessible During Server Processing

[kvnwolf]

Hello Radix Team!

I'm currently working with the Form primitive and I'm looking for guidance on enhancing its accessibility, especially when the form is being processed by the server.

1. Regarding aria-busy Attribute: Is it recommended to add the aria-busy attribute to the FormRoot component to indicate to users, especially those using screen readers, that the form is in the process of being submitted to the server?

2. disabled vs. aria-disabled Attributes: For the FormControl and FormSubmit components, should we prefer using disabled attribute or is it better to use aria-disabled? I'm particularly concerned about maintaining the best accessibility practices while the form is being processed.

3. Best Practices for Non-Field-Specific Form Errors: What are the best practices for handling errors that are not associated with a specific form field, especially in terms of accessibility? Should the FormRoot have aria-invalid and aria-describedby attributes to handle these kinds of errors?

Any guidance or insights on these topics would be greatly appreciated. Looking forward to making our forms more accessible and user-friendly.

Thank you!