>>! In T303321#7880251, @bmartinezcalvo wrote:
>>>! In T303321#7879418, @Catrope wrote:
>>>>! In T303321#7823237, @egardner wrote:
>>> This particular issue has been addressed in the latest patch – tabs beyond the viewport should automatically scroll into view once they become active.
>>
>> Thanks, that helps. However, I still think the tabs scrolling UX is unclear. There are no scroll bars, there's no indication that you can scroll except for the gradient, and unless you're using a touch screen or track pad it's hard to discover how you can scroll.
>
> @Catrope I agree, for a more accessible tabs we should indicate the scroll with something more than the gradient, also not sure if all laptops or mouses could make the horizontal scroll without buttons. For this reason, I presented during the beginning of the task this other proposal where we combine both arrows and horizontal scroll. I think this would be the most accessible solution for any user and device.
>
> {F35068420}
>
>>>! In T303321#7781197, @bmartinezcalvo wrote:
>> What if we combine both (arrows and scroll)? With this solution our tabs component will be more accessible. We can build it adding Quiet Neutral buttons (icon only) as previous and next controls.
>>
>> {F35008590}
---
=== Figma
[[ https://www.figma.com/file/mn4bJHD74ks7DIcLlgLyFq/?node-id=1023%3A3889 | Figma spec sheet here ]]