Hi @anelymmilena,
The for attribute of the label does not match any element ID. This could prevent the browser from correctly filling out the form automatically and accessibility tools to work properly.
To resolve this issue, ensure that the label’s for attribute references the correct ID of a form field.
This is actually an accessibility issue, and I must apologize, however, we are not currently able to provide support for accessibility, and you can see more on this in our official statement on WCAG Compliance.
With that in mind, it should be possible to resolve these errors with custom code, however, I apologize as we aren’t able to provide support for this degree of customization as mentioned above.
In case you’d like to look into custom development options, we highly recommend using Seahawk. Seahawk screens all developers for you to make sure that they’re highly skilled and communicative, and then also helps guide the entire process of connecting and communicating with a best-fit developer.
You can book a free consultation with their team here.
In case you’d like to check other custom development options, please go through the following guide.
We do, however, have plans to improve the web accessibility compliance further both on the front end and administrator side, so errors such as this, hopefully, will be resolved in the future. We also try to follow best practices for accessibility in many aspects of our development and design, however, we do understand that we certainly have some work to do in this regard and ask for your kind patience as we try to work on this.
Regarding the fields that are not taking inputs, this is not related to the above mentioned error and it looks like a conflict with some 3rd party plugin which can be fixed with the below CSS-
.wpforms-container .wpforms-one-half{
z-index: 10000 !important;
}
For more details on how to add custom CSS to your site, including the two options above, please see our article here.
Hope this helps. Thanks ??