- 🇺🇸United States smustgrave
Since there hasn't been a follow up to #36 in a year going to close for now.
But please if still a bug reopen, updating issue summary where needed.
Thanks!
Thanks to @merlinofchaos in #1963124-7: Resolve WCAG2 accessibility errors on main settings page → I learned that the #states mechanism uses CSS display:none; to hide content.
Unfortunately, this means that for screen reader users, nothing gets presented to the user. For a keyboard only user this isn't a problem because when they select a checkbox new ones appear, but screen reader users need to either have access to all of the checkboxes or be alerted that there is a change to the page.
I think the best approach is to simply mimic what we did with element-hidden & element-invisible and make a:
.js .js-hide {
display: none;
}
.js .js-invisible {
position: absolute !important;
clip: rect(1px, 1px, 1px, 1px);
overflow: hidden;
height: 1px;
width: 1px;
word-wrap: normal;
}I think that would address the problem, but it ties into core/misc/states.js
Any thoughts on this would be appreciated.
Closed: cannot reproduce
9.5
Last updated
The change/bugfix cannot be fully demonstrated by automated testing, and thus requires manual testing in a variety of environments.
It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Since there hasn't been a follow up to #36 in a year going to close for now.
But please if still a bug reopen, updating issue summary where needed.
Thanks!