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

Content Module 1 - Distraction values and examples need to be updated #170

Open
snidersd opened this issue Nov 30, 2020 · 4 comments
Open
Assignees
Labels
1) content module tag-tracker Group bringing to attention of the TAG, or tracked by the TAG but not needing response.

Comments

@snidersd
Copy link
Member

snidersd commented Nov 30, 2020

This issue relates to tag issue 476 discussionsContent Module 1 Distraction value of sensory and the overlap with prefer-reduced-motion.

Note: tag issue 476 discussionsContent Module 1 has been closed Jan. 2021 by TAG.

@snidersd snidersd added 1) content module tag-tracker Group bringing to attention of the TAG, or tracked by the TAG but not needing response. labels Nov 30, 2020
@lseeman lseeman assigned lseeman and unassigned lseeman May 24, 2021
@snidersd snidersd self-assigned this May 24, 2021
@snidersd
Copy link
Member Author

After reviewing the Editor's Draft of Content Module 1 and nothing has been added related to reduced-motion.

@johnfoliot johnfoliot self-assigned this Jul 26, 2021
@johnfoliot
Copy link
Contributor

Will revisit this, but note at this time that prefers-reduced-motion is applied at the document or site level, whereas our solution is intended to be applied at the element level.
Will look to write up some text that points this out for the TF to review.

@johnfoliot
Copy link
Contributor

Overcome by time: Tag Issue #476 has been closed

@snidersd
Copy link
Member Author

snidersd commented Aug 1, 2022

Reopening this issue based on our 01 Aug 2022 weekly meeting. Also note Content Module 1 symbol values for distraction has updated the examples to show audio, widgets, and animated advertising before the issue was closed, but the group decided not to add the new values.

We need to have a working example of multiple elements on the page (stock-ticker, timer, and an ad) to show that with distraction="sensory" you can stop one or two at the element level, and it is not possible media queries because it is at the page level, not element level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1) content module tag-tracker Group bringing to attention of the TAG, or tracked by the TAG but not needing response.
Projects
None yet
Development

No branches or pull requests

3 participants