E-mail List Archives
Re: Custom tabs with a single tab panel: does it poseaccessibility issues?
From: Steve Green
Date: Aug 1, 2023 4:05AM
- Next message: Matson, Eric (ecmatson@uidaho.edu): "Re: WCAG 4.1.3 - Status Messages"
- Previous message: Jacob Kruger: "Creating collections of tab elements/controls that are then rendered correctly to assisstive technology?"
- Next message in Thread: tim.harshbarger@deque.com: "Re: Custom tabs with a single tab panel: does it poseaccessibility issues?"
- Previous message in Thread: Erick Wilder: "Custom tabs with a single tab panel: does it pose accessibility issues?"
- View all messages in this Thread
I have seen this coding method too, and it's horrible, stupid and unnecessary. I have no idea why they do stuff like this, other than to show off.
That said, it is probably WCAG conformant. It might fail SC 4.1.1 because there are tabs that don't have a corresponding tabpanel, but of course 4.1.1 will disappear from WCAG 2.2.
Adding and removing content from the DOM like this can cause corruption of a screen reader's virtual object model, and I have seen that many times. It usually manifests itself as a loss of focus position. However, although this is obviously an accessibility issue it's not a WCAG non-conformance. The behaviour may not even be consistent between machines or screen reader versions.
Steve Green
Managing Director
Test Partners Ltd
- Next message: Matson, Eric (ecmatson@uidaho.edu): "Re: WCAG 4.1.3 - Status Messages"
- Previous message: Jacob Kruger: "Creating collections of tab elements/controls that are then rendered correctly to assisstive technology?"
- Next message in Thread: tim.harshbarger@deque.com: "Re: Custom tabs with a single tab panel: does it poseaccessibility issues?"
- Previous message in Thread: Erick Wilder: "Custom tabs with a single tab panel: does it pose accessibility issues?"
- View all messages in this Thread