Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scope of carousel example #2700

Open
Ignacio-de-Loyola opened this issue May 12, 2023 · 1 comment
Open

Scope of carousel example #2700

Ignacio-de-Loyola opened this issue May 12, 2023 · 1 comment
Labels
Feedback Issue raised by or for collecting input from people outside APG task force Pattern Page Related to a page documenting a Pattern question Issue asking a question

Comments

@Ignacio-de-Loyola
Copy link

Ignacio-de-Loyola commented May 12, 2023

Describe your concern

According to ARIA APG's documentation for Carousel, "Typically, one slide is displayed at a time, and users can activate a next or previous slide control that hides the current slide and "rotates" the next or previous slide into view." It is stated. What I'm curious about is whether Carousel, where multiple slides are displayed, should be connected to the entire container of slides by inserting the aria-controls property to the previous/next buttons in the same way.

[Example Case]
image

Link to the version of the specification or documentation you were looking at at.

Carousel

@jnurthen jnurthen transferred this issue from w3c/aria May 12, 2023
@css-meeting-bot
Copy link
Member

The ARIA Authoring Practices (APG) Task Force just discussed Scope of carousel example.

The full IRC log of that discussion <jugglinmike> subtopic: Scope of carousel example
<jugglinmike> github: https://github.com//issues/2700
<jugglinmike> jongund: I think we had another discussion about this. The slider seems to be more like a scroll feature. On the WebAIM discussion list, they were talking about course selection
<jugglinmike> jongund: They were calling that a slider and wondering where the focus should go
<jugglinmike> jongund: It seems like this is similar; when you have more than one thing showing at a time
<jugglinmike> Matt_King: We call those "h-scrolls" as short for "horizontal scrolls", and they are a lot like a carousel, except that they don't automatically rotate
<jugglinmike> jongund: Maybe we need a horizontal scroll example
<jugglinmike> Matt_King: When they say the entire container, maybe they mean the visible set
<jugglinmike> Matt_King: It doesn't seem like this specific example fits our carousel pattern very well
<jugglinmike> Matt_King: I don't know how common this pattern is and if it's something that we should be focusing on, but if someone wants to take it on...
<jugglinmike> jongund: I think it's pretty common. It also came up on the webaim list
<jugglinmike> Matt_King: I would love to have a soft of incubator practice for new things like this. Something to promote a wider variety of input
<jugglinmike> Matt_King: I think it's pretty clear, though, that the carousel pattern isn't going to solve this problem as it is
<jugglinmike> Zakim, end the meeting

@mcking65 mcking65 added question Issue asking a question Feedback Issue raised by or for collecting input from people outside APG task force Pattern Page Related to a page documenting a Pattern labels Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feedback Issue raised by or for collecting input from people outside APG task force Pattern Page Related to a page documenting a Pattern question Issue asking a question
Projects
None yet
Development

No branches or pull requests

3 participants