First, thank you for maintaining this plugin! It’s been really useful for our organization.

I wanted to flag an accessibility issue. When adding fields like First Name or Last Name, the given code doesn’t include for attributes on labels or corresponding id attributes on inputs. This means screen readers can’t programmatically associate labels with their fields.

I saw in the Oct 2024 release notes that label associations were addressed for some fields, which is great! But it looks like manually added fields still generate markup like this:

<label>First Name</label>
<input type="text" name="FNAME">

Rather than the accessible pattern:

<label for="firstName">First Name</label>
<input type="text" name="FNAME" id="firstName">

I know we can edit fields manually to add these attributes, but I’d love to see accessible markup as the default. Many site builders may not realize the attributes are missing, and with upcoming accessibility compliance deadlines for public institutions, having accessible defaults would help a lot of organizations avoid issues down the road.

Would you consider adding automatic for/id generation for custom fields in a future update? Happy to provide more info if helpful.