I am working to make my team's Experience Builder apps as WCAG-compliant as possible. We make broad use of the accordion widget as it's excellent for visually grouping content, but its headers appear to be divs, not semantic headings (e.g., <h2>, <h3>, etc.). This can create a major challenge for users relying on assistive technology, who rely on content being organized by headings.
It would be fantastic if there was an option in the accordion widget's configuration to set the heading level (H2–H6) for headers. This would allow app authors to maintain proper semantic structure and improve compliance with WCAG guidelines.
