Refactor options pages markup to follow WordPress standards

[claytoncollie]

This PR addresses #41 to fix the alignment and accessibility of checkbox and radio fields in the wp-admin settings pages. The markup has been updated to match WordPress Core patterns for form controls. This is a refactor, not a functionality change.

Changes made:

1. Checkbox fields (Gutenberg.php, PostPasswords.php):

   • Removed label_for argument from add_settings_field() since checkboxes shouldn't have the row label linked to them
   • Wrapped inputs in <label> elements with description text inside, matching Core's checkbox pattern

2. Radio fields (Passwords.php, Monitor.php):

   • Removed label_for argument from add_settings_field() for radio groups
   • Added <fieldset> wrapper with <legend class="screen-reader-text"> for accessibility
   • Each radio input is now wrapped in its corresponding <label> element

Benefits:

• Improved accessibility and keyboard usability
• Consistent markup with WordPress Core admin patterns
• Better screen reader support with proper fieldset/legend structure for radio groups

Closes #41

How to test the Change

1. Install the plugin on a local WordPress instance
2. Navigate to and verify the following settings pages:
   • Writing Settings (/wp-admin/options-writing.php):
     • "Use Classic Editor" checkbox - verify label is clickable
     • "Enable Password Protected Content" checkbox - verify label is clickable
   • General Settings (/wp-admin/options-general.php):
     • "Require Strong Passwords" radio buttons - verify Yes/No labels are clickable
     • "Enable Support Monitor" radio buttons - verify Yes/No labels are clickable
   • Network Settings (multisite only - /wp-admin/network/settings.php):
     • "Require Strong Passwords" radio buttons - verify proper fieldset structure
3. Save each setting multiple times to ensure functionality is preserved
4. Use a screen reader or browser accessibility tools to verify the fieldset/legend structure

Changelog Entry

Changed - Updated admin markup for checkbox and radio fields to match WordPress Core accessibility patterns

Credits

Props @claytoncollie

Checklist:

• I agree to follow this project's Code of Conduct.
• I have updated the documentation accordingly.
• I have added Critical Flows, Test Cases, and/or End-to-End Tests to cover my change.
• [] All new and existing tests pass.

[darylldoyle]

@claytoncollie thank you for putting this together! Can we also do this for Disable Comments and Allow Fueled SSO, please? They're left looking slightly odd without the style updates.

[claytoncollie]

@darylldoyle Refactored Comments and SSO on single and multisite

[darylldoyle]

Great work!