Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Carousels) (Issue #1037)

flackr left a comment (w3ctag/design-reviews#1037)

> Re: the column scroll marker issue -- many accessible names are not counter-based, nor is composing a static string + counter a good practice for localization.

Agreed, on https://github.com/w3c/csswg-drafts/issues/12269#issuecomment-5640431614 I mentioned that this is an area where we could consider extension points to make localization easier.

>  I have not yet seen an example of how to give each column scroll marker a true custom accessible name.

Please help me understand your request. If the developer knows how many pages they want and how they want to split content regardless the user's display size, they can split them into individual elements and would not use column scroll markers. The use case for using column scroll markers is one where content is dynamically split into what fits in each page. What accessible names do frameworks or systems that split content into pages typically give to those pages? I'm not sure how an author would choose an exact label for each page if they don't know what will fit into it on the user's screen.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1037#issuecomment-5714114397
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1037/5714114397@github.com>