icepicksu

Again, the checkbox itself can be operated, but the labels are incorrect and confusing. They should also be fixed per my last comment.

CSS display:none will certainly hide from screen readers, so yes that change now makes them fully operable. The remaining issue is the labels, which now read to a screen reader as “DisabledEnabled” or “NoYes”. They are already programmatically associated with the actual option (e.g. Debug Mode), so I don’t think these are necessary. Optionally you could keep just the affirmative label to reflect the checked state.

You can contact your hosting provider to check if there is a running process and kill it.

Right, but that doesn’t address the fact that the plugin let me create that runaway fictitious process when it shouldn’t have.

No, it may seem so but is not. The role defines a WAI-ARIA landmark to screen readers for quicker jumps around a page. Note the attribute can also take on the “search” landmark to distinguish it from a generic form, and does not necessarily need to be within the <form> tag but could also be put in the surrounding <div> tag. All Contact Form 7 forms should have role=”form” built-in to be WAI-ARIA compliant, and you might also consider building in support for the aria-label or aria-labelledby attributes for situations where there are multiple forms on a single page since screen readers will announce this to distinguish them.

See https://www.w3.org/WAI/GL/wiki/Using_ARIA_landmarks_to_identify_regions_of_a_page for reference.