Accessibility, UI theming and integration with non-react web application

[umairahmad14]

Hi,

I'm seeking answers to the following questions. I'd appreciate any information you can provide.

1. Has Smart Forms been assessed against WCAG 2.1 AA or WCAG 2.2 AA? Is there an accessibility conformance report (VPAT/ACR), or are there known accessibility limitations?
2. Can Smart Forms be fully themed to match an existing government design system? Are there examples of organisations replacing the default Material UI styling with their own branding and css theme?
3. Which browsers are officially supported? Has Smart Forms been tested with the browser support matrix typically required for Australian Government web applications?
4. Have there been any performance benchmarks for large questionnaires? Are there known performance limitations?
5. Does Smart Forms support custom validation rules in addition to standard FHIR validation? Can custom business rules be plugged in without modifying the library?
6. Does Smart Forms assume a particular FHIR server, or can it work with any REST endpoint that provides Questionnaire and accepts QuestionnaireResponse?
7. Are there any recommended security practices for deploying Smart Forms in production (e.g. CSP compatibility, sanitisation of expressions, XSS considerations)?
8. Can custom question types or widgets be added without forking the project? Example Date of Birth picker.
9. Is Smart Forms actively maintained? How frequently are releases made, and how are breaking changes communicated?
10. We are evaluating Smart Forms for integration into the Australian My Health Record National Consumer Portal. Has Smart Forms been integrated into an existing non-React enterprise application (such as AEM or another CMS, Java, HTML5, CSS3, Ajax) while preserving the host application's branding, accessibility, and navigation? If so, are there any recommended architecture patterns or example implementations?
11. What is the roadmap for FHIR R5 support?

Highest Regards,
Umair Ahmad.