Repository navigation
Testing criteria for custom scrollbars (WCAG 1.4.11 & 2.5.8) #5140
|
I am writing to inquire about the exact criteria regarding whether browser scrollbars are subject to accessibility testing. As I understand per WCAG guidelines, default browser scrollbars are considered User Agent components and are therefore generally exempt from accessibility evaluation. However, when the scrollbar is customized by the author using CSS (e.g., through the scrollbar-color and scrollbar-width properties), I am wondering if it then becomes subject to SC 1.4.11 Non-text Contrast and SC 2.5.8 Target Size (Minimum), as it functions as a customized UI component. Reference: CSS Scrollbars Module Level 1 My specific questions are:
Any clarification on this matter would be greatly appreciated and very helpful for practical accessibility improvements. |
Replies: 3 comments
|
I have found a relevant clause in the WCAG 2.2 specification regarding Target Size (Minimum). According to the User Agent Control section in Understanding Success Criterion 2.5.8: Target Size (Minimum): "This Success Criterion does not apply to size and spacing of target(s) that are controlled by the user agent." The specification also mentions: I would love to hear the community's or the working group's thoughts on whether this interpretation is correct, and if there are any official guidelines or ongoing discussions regarding this specific scenario. |
|
I have always included custom scrollbars in my testing. Some websites may support alternative means of scrolling, but that is a secondary consideration.
FWIW, I hate custom scrollbars so much that I use the Stylus browser extension to revert to the native scrollbars on some websites.
|
|
yes, custom scrollbars need to be evaluated like any other author-created content. no, there's no specific callout in all the relevant SCs/understanding documents for this, as the spec can't cover every possible "thing" that an author does. |
yes, custom scrollbars need to be evaluated like any other author-created content. no, there's no specific callout in all the relevant SCs/understanding documents for this, as the spec can't cover every possible "thing" that an author does.