[wp-trac] [WordPress Trac] #31354: Compound settings confusing with screen readers (checkboxes)
WordPress Trac
noreply at wordpress.org
Mon Feb 23 15:51:53 UTC 2015
#31354: Compound settings confusing with screen readers (checkboxes)
-------------------------------------+------------------------------
Reporter: Cheffheid | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Administration | Version: 4.1
Severity: normal | Resolution:
Keywords: has-patch needs-testing | Focuses: accessibility
-------------------------------------+------------------------------
Comment (by afercia):
I'm not sure playing with JavaScript can really help here, I'd say it
would be a possible enhancement to evaluate after the main issue is
solved. IMHO the first thing to do here should be using proper labels that
make sense also when read out of context and probably restructure a bit
the form. Just use Plain Old Semantic HTML (POSH), nothing fancy, consider
HTML give us fieldset and legend elements for free and use them when
appropriate.
About the first example:
[[Image(http://i.imgur.com/0r0lDSn.png)]]
- the checkbox is meant to enable/disable the setting, it's a general
"switch" and this should be clear even when the label is read out of
context
- the other two, are sort of "sub settings", it should be clear they're
discarded if the main checkbox is not checked
What I would suggest:
{{{
fieldset
legend: Comments pagination
checkbox + label: Break comments into pages
label + input field: Top level comments per page
label + select: Comments page to display by default: last
page|first page
(added) label + select: Comments to display at the top of each page: older
comments|newer comments
}}}
Consider this other example:
[[Image(https://cldup.com/doimEsOQKY.png)]]
Here, the labels are:
> "Automatically close comments on articles older than"
> "days"
The first one doesn't tell me it's an on/off switch, but says something
about "older than". Confusing. The second one says just "days", I don't
have a clue what it refers to, when read out of context. This second
example is a bit more difficult to handle, still thinking about a proper
solution :)
I understand this would require some minor UI changes, so it needs UI
feedback and I'm pretty confident we could find a good balance between
functionality and visual. Any thougths more than welcome.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/31354#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list