Skip to content
This repository has been archived by the owner on Aug 19, 2024. It is now read-only.

Options for Moving, Flashing, or Blinking Content #27

Closed
shawna-slh opened this issue Nov 2, 2016 · 11 comments
Closed

Options for Moving, Flashing, or Blinking Content #27

shawna-slh opened this issue Nov 2, 2016 · 11 comments
Milestone

Comments

@shawna-slh
Copy link
Contributor

shawna-slh commented Nov 2, 2016

The new checks for Moving, Flashing, or Blinking Content that we have been working on (1, 23) have been integrated into a draft of the document so we can review them in context. Please skim the Easy Checks document overall to re-familiarize yourself with how the other topics and checks are presented.

Two options are presented, A & B below:

@shawna-slh
Copy link
Contributor Author

shawna-slh commented Nov 2, 2016

[medium-mild] Preference: Option B. One combined topic.

Rationale: I think reviewers will easily check all of these at the same time, rather than wanting to split it out into separate checks. Also, I think flashing is not a highly prevalent accessibility barrier that fully warrants it's own check. The topics are very related and the content that we have for each is very short (in comparison to the other topics) - and somewhat repetitive when split into two separate topics.

Update: After processing @susanatx 's comments below, I realize that the Moving topic really needs to include all movement, including blinking and flashing. So I now feel more strongly that it should be one topic combined.

@susanatx
Copy link

susanatx commented Nov 3, 2016

My initial thought is to separate them as I think it's important for people to know they are different types of content. But looking at the structure of the resource overall I don't think having them separate is a good fit.

Could we make it visually more clear that the "Moving" piece and "F/B" piece are separate? I know from experience this hard for some people to parse out the differences between the two so this is kind of a word soup that may not help.

@shawna-slh
Copy link
Contributor Author

shawna-slh commented Nov 3, 2016

@susanatx I updated it with subheadings. I thought it looked nice -- however, it looked like the first section was just moving, when in fact it also applies to flashing and blinking. Here is that iteration: https://rawgit.com/w3c/EasyChecks/7a396e9756575df043263d97ba56d8a29b9e89d8/index.html#moving

So after further consideration, I took out the headings and added flashing and blinking in the first two paragraphs, and "Additionally" before the last paragraph sentence.

I also bolded the key words in the checks.

OK?

@shawna-slh
Copy link
Contributor Author

Brent's comments from survey

Replace: Some people have trouble tracking moving objects.
Replace with: Some people have difficulty tracking moving objects.

Done.

Replace: Moving content includes "carousels" such as below, videos, ads, auto-updating stock tickers, and more. Users need to be able to control moving content, especially some people with attention deficit or visual processing disorders.
Replace with: Users need to be able to control moving content, especially some people with attention deficit or visual processing disorders. Moving content includes carousels (example below), videos, ads, auto-updating stock tickers, and more.

In many of the checks -- especially the first few, we first explain what it is, and then the accessibility issue. For this topic, I feel that it would be good to explain what is meant by moving content first -- so people can more quickly understand the breadth of that this topic cover and if it applies to their page.

I don't feel super strongly about that and if the group overall wants to switch the order of the sentences, I'd be OK with that.

@iamjolly
Copy link

iamjolly commented Nov 3, 2016

My preference is B. One combined topic. This information seems to be easy enough to parse together in a section rather than having separate sections or checks that testers may need to recall when testing.

@nitedog
Copy link

nitedog commented Nov 3, 2016

I also slightly favor one combined approach.

@susanatx
Copy link

susanatx commented Nov 3, 2016

This looks good @slhenry

@James-Green
Copy link

i also favor one combined approach

@dboudreau
Copy link

Also leaning towards a combined approach.

@vuxcaleb
Copy link
Contributor

vuxcaleb commented Nov 4, 2016

Resolution approved to combine.

@shawna-slh
Copy link
Contributor Author

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants