Accessibility Enhancements to Settings API
|Reported by:||taupecat||Owned by:||taupecat|
|Component:||Options, Meta APIs||Keywords:||has-patch settings-api|
I've only started working with the Settings API, but right off the bat I noticed two fairly major, but should be not too difficult to fix, accessibility issues.
1) The label/input field pairs are missing the HTML <label> tags that link the two.
Example: Field One <input id="field_one" name="field_one" type="text">
Should be rendered: <label for="field_one">Field One</label> <input id="field_one" name="field_one" type="text">
2) The settings pages themselves are laid out using a table. Tables should be reserved for tabular data, and not for page layout. CSS should be used for layout instead.
Thanks for your attention.
Change History (22)
comment:12 @nacin — 14 months ago
- Component changed from Accessibility to Administration
- Focuses accessibility added