W3C

Results of Questionnaire WCAG Video Scripts: Batch 1 Thorough Review

The results of this questionnaire are available to anybody. In addition, answers are sent to the following email address: shadi+eosurvey@w3.org

This questionnaire was open from 2021-04-10 to 2021-04-30.

14 answers have been received.

Jump to results for question:

  1. Review level
  2. Draft Script 1.2.2 "Captions"
  3. Draft Script 2.2.5 "Re-authentication"
  4. Draft Script 2.3.3 "Animations from Interactions"
  5. Draft Script 2.4.7 "Focus Visible"
  6. Draft Script 1.3.1 "Info and Relationships"
  7. Draft Script 1.3.2 "Meaningful Sequence"
  8. Draft Script 1.3.3 "Sensory Characteristics"
  9. Draft Script 1.3.4 "Orientation"
  10. Draft Script 1.3.5 "Identify Input Purpose"
  11. Draft Script 1.3.6 "Identify Purpose"
  12. Other Comments

1. Review level

summary | by responder | by choice

Summary

ChoiceAll responders
Results
I reviewed it thoroughly. 11
I skimmed it. 2
I didn't get to it. (Abstain and accept the decision of the group.)

Skip to view by choice.

View by responder

Details

Responder Review levelComments
Laura Keen
  • I reviewed it thoroughly.
Kimberly Patch
  • I reviewed it thoroughly.
Justine Pascalides
Kris Anne Kinney
  • I reviewed it thoroughly.
Sylvie Duchateau
  • I reviewed it thoroughly.
Jade Matos Carew
  • I reviewed it thoroughly.
Vicki Menezes Miller
  • I reviewed it thoroughly.
Bruce Bailey
  • I skimmed it.
Lisa Seeman-Horwitz
  • I reviewed it thoroughly.
i read coga related ones well. less for the others..
Jennifer Delisi
Tzviya Siegman
  • I reviewed it thoroughly.
These look great.
Kevin White
  • I reviewed it thoroughly.
Brent Bakken
  • I reviewed it thoroughly.
Shawn Lawton Henry
  • I reviewed it thoroughly.
  • I skimmed it.
Some thoroughly. Some skimmed.

View by choice

ChoiceResponders
I reviewed it thoroughly.
  • Laura Keen
  • Kimberly Patch
  • Kris Anne Kinney
  • Sylvie Duchateau
  • Jade Matos Carew
  • Vicki Menezes Miller
  • Lisa Seeman-Horwitz
  • Tzviya Siegman
  • Kevin White
  • Brent Bakken
  • Shawn Lawton Henry
I skimmed it.
  • Bruce Bailey
  • Shawn Lawton Henry
I didn't get to it. (Abstain and accept the decision of the group.)

2. Draft Script 1.2.2 "Captions"

summary | by responder | by choice

Draft script for Success Criterion 1.2.2 "Captions"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 7
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 4
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
I abstain (not vote) and accept the decisions of the Working Group 1

Skip to view by choice.

View by responder

Details

Responder Draft Script 1.2.2 "Captions"Comments
Laura Keen
  • I approve this script as it currently is (no changes suggested)
Kimberly Patch
  • I approve this script as it currently is (no changes suggested)
Justine Pascalides
  • I approve this script as it currently is (no changes suggested)
Kris Anne Kinney
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
Something about the automated captions piece isn't sitting right with me. I agree we should mention that automated captions aren't always good, but in the last section should we mention that the university is working with a transcription company to create accurate captions for their videos?
Sylvie Duchateau
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
I have two questions:
1. In scene 5, the description says: "Martine clicks (staged) auto-caption button"
I am not sure to understand what "staged" means.
2. Final scene: I understand that the scene is the reverse of first scene, because Martine now watches an accessible video. In addition to seeing her smiling, is there a difference on the screen content she is seeing, to make it clear to the audience in what extend the video has changed and improved Martines experience?
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
Vicki Menezes Miller
  • I approve this script as it currently is (no changes suggested)
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz
  • I abstain (not vote) and accept the decisions of the Working Group
Jennifer Delisi
Tzviya Siegman
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
The only thing that jumped out is in 1.2.2. For those not familiar with the flaws of automated captioning, an example of what the problems are might help. One that happened to me recently, "new work" became "Newark". This might make the video longer than you intend though.
Kevin White
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
3: Would the hearing aid ever convey who is speaking?
5: Is the idea about the 'staged' button to make it clear that these are auto generated captions? I think YouTube just has a captions button and it might be auto or might be actual captions?
5: How will the garbled captions be clearly wrong? Without the audio it may not be clear that the captions are actually incorrect
6: Not sure what this scene is for... should they all have happy endings?
Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry “The captions also convey important audio information, such as clapping and who is speaking, which her hearing aid does not always convey.”
[med] clapping is often not important audio information for captions (and can often be seen) (and I would think is rare in college course videos)

“Most course videos have captions, which Martine uses to understand what is being said.”
[e] “understand”->”know” in : …Martine uses to know what is being said.

“which her hearing aid does not always convey.”
[?] would be good to check this way of describing it

“She can hear some sounds, but not enough to understand speech.”… “Unfortunately some videos do not have captions, making it difficult for Martine to follow the course.”
[med] If she can’t understand speech, and the material is spoken, then it seems “making it difficult for Martine to follow the course” -> “making it impossible for Martine to know what the instructor is saying.”

“Martine looks puzzled/upset.”
[low] <s>puzzled</s> frustrated, disappointed, angry, discouraged

“auto-caption button”
[i] Is there such a thing? I’ve seen a regular caption button that bring up language selection with “English (auto-generated)”

“garbled captions are displayed”
[fyi] to be realistic, they would be real words, just not necessarily make sense (and not sure that can come thought in a short video, because you would have to read the words to know they don’t make sense

“Also automatic captioning is often inaccurate. For example, it does not recognize some words and accents.”
[i] It’s more than that. Automatic captioning can be *wrong* and that can be significant in a course.
From https://www.w3.org/WAI/media/av/captions/#automatic-captions-are-not-sufficient : “… often the automatic caption text is wrong and does not match the spoken audio — sometimes in ways that change the meaning (or are embarrassing). For example, missing just one word such as “not” can make the captions contradict the actual audio content.”

“see frontal view of Martine’s face – she is happy/smiling”
[low] <s>happy/smiling</s> engaged, nodding in agreement, taking notes, looking interested

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Laura Keen
  • Kimberly Patch
  • Justine Pascalides
  • Jade Matos Carew
  • Vicki Menezes Miller
  • Bruce Bailey
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Kris Anne Kinney
  • Sylvie Duchateau
  • Tzviya Siegman
  • Kevin White
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
I abstain (not vote) and accept the decisions of the Working Group
  • Lisa Seeman-Horwitz

3. Draft Script 2.2.5 "Re-authentication"

summary | by responder | by choice

Draft script for Success Criterion 2.2.5 "Re-authentication"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 9
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 1
I approve this script only with the changes raised in GitHub or in the comments field below 1
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below 1
I abstain (not vote) and accept the decisions of the Working Group

Skip to view by choice.

View by responder

Details

Responder Draft Script 2.2.5 "Re-authentication"Comments
Laura Keen
  • I approve this script as it currently is (no changes suggested)
Kimberly Patch
  • I approve this script as it currently is (no changes suggested)
Justine Pascalides
  • I approve this script as it currently is (no changes suggested)
Kris Anne Kinney
  • I approve this script as it currently is (no changes suggested)
Sylvie Duchateau
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
Priority: Editor's discretion.
I would suggest to use positive form rather than negative. For example on scene 4:
Actual text: "Some websites and apps save the information he has entered before logging him out. When he logs back in, the information he previously typed has not been
lost."
Proposed change: "Some websites and apps save the information he has entered before logging him out. When he logs back in, the information he previously typed is still available" or something similar.
Rationale: it makes the information clearer and it is positive.
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
Vicki Menezes Miller
  • I approve this script as it currently is (no changes suggested)
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz
  • I approve this script only with the changes raised in GitHub or in the comments field below
I think more input is needed from COGA. He does not just take longer rembering. he needs to look up the information as he _can not _remember it accurately. he takes longer coping and transcribing. he makes mistakes, and more mistakes as it goes on and gets tiered. than the bloody thing times out... He could start again but there is no reason to think he will do any better, infact as he is now tiered and upset he will make more mistakes and take longer. he feels useless and helpless. he tries to look on the bright side of everything, and usually manages, but now he cries.
Jennifer Delisi
Tzviya Siegman
  • I approve this script as it currently is (no changes suggested)
Kevin White
  • I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
1: Why is Gopal looking puzzled and scratching his head? This seems stereotypical and doesn't really add anything more than that to the narrative
2: I think this is going to be tough - if it is just address information that Gopal is likely to have that on one note so what other information on the page would be lost.
3: This would be an extremely quick log out process - less than 10 seconds by the look of things. This might be a bit unrealistic and might benefit from a longer interruption. For example, interrupted by a phone call or the door bell - takes time to remember that he was in the middle of something - comes back to find it logged out. Or some such.
Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Laura Keen
  • Kimberly Patch
  • Justine Pascalides
  • Kris Anne Kinney
  • Jade Matos Carew
  • Vicki Menezes Miller
  • Bruce Bailey
  • Tzviya Siegman
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Sylvie Duchateau
I approve this script only with the changes raised in GitHub or in the comments field below
  • Lisa Seeman-Horwitz
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
  • Kevin White
I abstain (not vote) and accept the decisions of the Working Group

4. Draft Script 2.3.3 "Animations from Interactions"

summary | by responder | by choice

Draft script for Success Criterion 2.3.3 "Animations from Interactions"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 9
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 2
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below 1
I abstain (not vote) and accept the decisions of the Working Group

Skip to view by choice.

View by responder

Details

Responder Draft Script 2.3.3 "Animations from Interactions"Comments
Laura Keen
  • I approve this script as it currently is (no changes suggested)
Kimberly Patch
  • I approve this script as it currently is (no changes suggested)
Justine Pascalides
  • I approve this script as it currently is (no changes suggested)
Kris Anne Kinney
  • I approve this script as it currently is (no changes suggested)
Sylvie Duchateau
  • I approve this script as it currently is (no changes suggested)
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
Vicki Menezes Miller
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
Location: SC 2.3.3 - Scene 1
Priority: (e)
Current wording: Manti has a condition called vestibular disorder, which makes her nauseous and dizzy from certain types of animations.
Minor suggestion: Manti has a condition called vestibular disorder, which makes her nauseous and dizzy from viewing certain types of animations.
Rationale: I feel a verb is missing to more clearly describe what causes the nausea and dizziness.
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz
  • I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
this seems dangrouse. as he starts with the animation, and only after he has seen it can he switch it off.
Jennifer Delisi
Tzviya Siegman
  • I approve this script as it currently is (no changes suggested)
Kevin White
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
1: I don't know the answer to this, but would someone with vestibular disorder be using a mobile phone while walking around? Would that not cause a problem for them?
2: Not sure that 'swivelling' would be the best word to use - animated?
2: I have no idea what the visual is describing!... Oh, I think I get some of it. Might a warning be better at the start? It may be difficult to appreciate what the issue is without being able to see it in action.

Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry “Manti has a condition called vestibular disorder, which makes her nauseous and dizzy from certain types of animations.”
[med] -> “Manti has a vestibular disorder. Some types of animations make her very nauseous and dizzy.”
rationale: Simplify. Put the blame on the animations, not her.

“We see her moving her head away from the screen and turning the phone to avoid the animation.”
[low] show discomfort then look away from screen

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Laura Keen
  • Kimberly Patch
  • Justine Pascalides
  • Kris Anne Kinney
  • Sylvie Duchateau
  • Jade Matos Carew
  • Bruce Bailey
  • Tzviya Siegman
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Vicki Menezes Miller
  • Kevin White
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
  • Lisa Seeman-Horwitz
I abstain (not vote) and accept the decisions of the Working Group

5. Draft Script 2.4.7 "Focus Visible"

summary | by responder | by choice

Draft script for Success Criterion 2.4.7 "Focus Visible"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 6
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 3
I approve this script only with the changes raised in GitHub or in the comments field below 2
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below 1
I abstain (not vote) and accept the decisions of the Working Group 1

Skip to view by choice.

View by responder

Details

Responder Draft Script 2.4.7 "Focus Visible"Comments
Laura Keen
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
I'm not sure I like the phrase "Good websites" maybe 'Well-designed websites".
Kimberly Patch
  • I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
Location: 2.4.7
Priority: i
Suggested revision: I recommend using the same script but with a different type of user – someone who can't use the mouse, but who can hit keys without pain.
Rationale: As a journalist who has struggled with RSIs and trained others in the same boat this doesn't strike me as typical, advisable, sustainable or even very realistic. When hitting keys hurts and you're trying to limit typing a method that increases keystrokes – repeatedly hitting the tab to go through focus order – doesn't go well with the injury.
(If you did want to stay with Alex as the user a more realistic script would be for him to issue speech command that does not work as expected because the focus was not clear and is in a different place than he anticipated, then issuing the same command confidently and successfully because there's a good focus indicator that makes it clear where the focus is.)

Also here's a minor correction if you do stick with Alex.
Priority: e
Current Wording: flex wrists.
Suggested revision: stretch wrists
Rationale: more realistic for this type of injury
Justine Pascalides
  • I abstain (not vote) and accept the decisions of the Working Group
For this scenario, I would prefer to demonstrate the benefit of the focus indicator for someone with a cognitive disability who needs the visual cue to understand what field they are interacting with. The current scenario of someone with repetitive motion strain doesn't quite hit the mark, as one keystroke (while not ideal, he does have the ability to type) would let him know where he was on the page.
Kris Anne Kinney
  • I approve this script as it currently is (no changes suggested)
Sylvie Duchateau
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
Editor's discretion:
I don't know if we should comment on the column visual, but may be they should be similar.
In this video, when talking for the first time about the figure, his name is written: "Alex is ..."
In the other videos, the description says: "a man, or a woman".
Examples:
"Manti (young female) is using her mobile app"
"Gopal (older male)"
"Frontal view of Martine’s face moving around and away from her, to see her from behind sitting at a desk and working on a computer"
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
My official vote is for Team Ergonomic.
Vicki Menezes Miller
  • I approve this script as it currently is (no changes suggested)
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
can he guese what he is about to select and then go to the wrong page?
Jennifer Delisi
  • I approve this script only with the changes raised in GitHub or in the comments field below
[i] Some of the sentences are long, which makes them more complex for some listeners (and those reading the transcript).

Here is an example:
" Alex has been a reporter for many years and has developed a repetitive strain injury, which makes it painful to use a mouse and to type for extended periods of time."
Suggested rewrite: Alex has been a reporter for many years and has developed a repetitive strain injury. This makes it painful to use a mouse and to type for extended periods of time.

Another example:
"Good websites indicate the currently active links and controls, for example as a clearly visible rectangle around to highlight links and controls."
Suggested rewrite: Good websites show the currently active links and controls. This can be a clearly visible rectangle around an active link or control.

Tool that may be helpful when reviewing readability (though full disclosure this tool is not accessible for all): hemingwayapp.com

[i] For scene 4, it may be helpful for those not able to see the screen or those needing more information about the visuals to add something to the audio like:
As he presses the tab key, nothing changes on his screen to show him what has focus.

For both of these changes, I am recommending the scripts be reviewed with this in mind. I am not voting based on this exact wording.
Tzviya Siegman
  • I approve this script as it currently is (no changes suggested)
Kevin White
  • I approve this script only with the changes raised in GitHub or in the comments field below
1: I don't think that Alex is the best character to use for this. As noted, someone with RSI may be using speech control. Possibly someone with tremors who uses an adapted keyboard but not a mouse.
Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Kris Anne Kinney
  • Jade Matos Carew
  • Vicki Menezes Miller
  • Bruce Bailey
  • Tzviya Siegman
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Laura Keen
  • Sylvie Duchateau
  • Lisa Seeman-Horwitz
I approve this script only with the changes raised in GitHub or in the comments field below
  • Jennifer Delisi
  • Kevin White
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
  • Kimberly Patch
I abstain (not vote) and accept the decisions of the Working Group
  • Justine Pascalides

6. Draft Script 1.3.1 "Info and Relationships"

summary | by responder | by choice

Draft script for Success Criterion 1.3.1 "Info and Relationships"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 7
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 3
I approve this script only with the changes raised in GitHub or in the comments field below 1
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
I abstain (not vote) and accept the decisions of the Working Group 1

Skip to view by choice.

View by responder

Details

Responder Draft Script 1.3.1 "Info and Relationships"Comments
Laura Keen
  • I approve this script as it currently is (no changes suggested)
Kimberly Patch
  • I approve this script as it currently is (no changes suggested)
Justine Pascalides
Kris Anne Kinney
  • I approve this script as it currently is (no changes suggested)
Sylvie Duchateau
  • I approve this script only with the changes raised in GitHub or in the comments field below
I think something is missing here: good markup for headings, lists, tables, and so on, does not only help screen reader users to have the elements been announced, but also to navigate more easily to those elements or inside of those elements with the screen reader.
Suggestion: include not only that these elements are announced but that the user can more easily reach them and it enables her to move more quickly through the page.
Moreover, the second point regarding the mobile use of the site is not so clear to me, why is it important to a screen reader user?
"Fortunately the content management system used at her company generates good mark-up. In particular, for the many tables that Ilya needs to use. They are
coded so well that she can also use them with her tablet computer and mobile phone when she is traveling.
"
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
Vicki Menezes Miller
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
SC 1.3.1 - Scene 3
Priority: (e)
Current wording: When structures on a page are coded correctly, they are announced by the screen reader. For example, headings, lists, links, and table cells are properly announced. [We hear the screen reader announce a heading then a list under that heading]
Suggested revision: When a page is well structured and information is coded correctly, the screen reader can properly announce relevant information. For example, navigating from one section to another becomes quick and easy, a list of items becomes clear, a table can be understood. [We hear the screen reader announce a heading then a list under that heading]
Rationale: For clearer understanding that the page needs to be structured. coded correctly and this really benefits the user in order to navigate through a page.
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz
  • I abstain (not vote) and accept the decisions of the Working Group
Jennifer Delisi
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
[i] Some viewers of the videos will not be highly technical. They may be document authors - especially for this video. Because of this, I recommend removing in scene 5 the sentence "Fortunately the content management system used at her company generates good mark-up." It could be replaced by something with more common language like "Fortunately her company's payroll website uses the correct structures."
Tzviya Siegman
  • I approve this script as it currently is (no changes suggested)
Kevin White
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
5: Would be good to hear the table structure
5: Not sure the CMS is relevant?
Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry “She listens to a screen reader reading aloud what is on the screen instead.”
[med] delete “instead” (as that makes it seems like an exception to the common Braille reading

“Sometimes developers do not use the correct mark-up, and the structure becomes unclear.”
[med] -> “Sometimes developers do not use the correct mark-up, and the structure is not available to Ilya.”
rationale: “becomes” says that it was clear and it changes to unclear

“Fortunately the content management system used at her company generates good mark-up. In particular, for the many tables that Ilya needs to use. They are coded so well that she can also use them with her tablet computer and mobile phone when she is traveling.”
[low] Maybe too much storytelling here, too wordy?

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Laura Keen
  • Kimberly Patch
  • Kris Anne Kinney
  • Jade Matos Carew
  • Bruce Bailey
  • Tzviya Siegman
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Vicki Menezes Miller
  • Jennifer Delisi
  • Kevin White
I approve this script only with the changes raised in GitHub or in the comments field below
  • Sylvie Duchateau
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
I abstain (not vote) and accept the decisions of the Working Group
  • Lisa Seeman-Horwitz

7. Draft Script 1.3.2 "Meaningful Sequence"

summary | by responder | by choice

Draft script for Success Criterion 1.3.2 "Meaningful Sequence"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 9
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 1
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below 1
I abstain (not vote) and accept the decisions of the Working Group 1

Skip to view by choice.

View by responder

Details

Responder Draft Script 1.3.2 "Meaningful Sequence"Comments
Laura Keen
  • I approve this script as it currently is (no changes suggested)
Kimberly Patch
  • I approve this script as it currently is (no changes suggested)
Justine Pascalides
Kris Anne Kinney
  • I approve this script as it currently is (no changes suggested)
Sylvie Duchateau
  • I approve this script as it currently is (no changes suggested)
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
Vicki Menezes Miller
  • I approve this script as it currently is (no changes suggested)
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz
  • I abstain (not vote) and accept the decisions of the Working Group
Jennifer Delisi
  • I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
Apologies if I am misunderstanding. The 2 bullets in the notes section appear to contradict the text in scene 1. Is this about someone with aphasia, someone that has low vision and uses a screen reader, or someone with dyslexia? Or, does she have multiple disabilities? I cannot review the script before understanding the true scenario.
Tzviya Siegman
  • I approve this script as it currently is (no changes suggested)
Kevin White
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
1: If Preety uses text to speech books - why is she reading a printed book?
2: Are ebook readers a good technology to focus on? It may not resonate with people web community as not that aware of ePub?
3: A literature book is not likely to have sidebars
Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry “The text appears correctly but the reading software jumps around the [literature] page in a confusing order.”
[?] Is this realistic? Reading order can jump around on a page with different elements, but *literature* tends to have single block of text. ?

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Laura Keen
  • Kimberly Patch
  • Kris Anne Kinney
  • Sylvie Duchateau
  • Jade Matos Carew
  • Vicki Menezes Miller
  • Bruce Bailey
  • Tzviya Siegman
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Kevin White
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
  • Jennifer Delisi
I abstain (not vote) and accept the decisions of the Working Group
  • Lisa Seeman-Horwitz

8. Draft Script 1.3.3 "Sensory Characteristics"

summary | by responder | by choice

Draft script for Success Criterion 1.3.3 "Sensory Characteristics"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 6
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 4
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below 1
I abstain (not vote) and accept the decisions of the Working Group 1

Skip to view by choice.

View by responder

Details

Responder Draft Script 1.3.3 "Sensory Characteristics"Comments
Laura Keen
  • I approve this script as it currently is (no changes suggested)
Kimberly Patch
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
I'm assuming the button is going to stay colored and it's just the description that's changing, since the color helps other types of users
Justine Pascalides
Kris Anne Kinney
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
You mention color and sound as being an issue, but only address how to fix the "green button" for the color. Should we address the "speak after the beep" - how to make that more accessible?
Sylvie Duchateau
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
Priority editor's discretion.
Location: scene 3.
Actual text: "Sometimes instructions on websites say things like “press the button on the left” or “on the right”, which are confusing because they actually appear above
or below the text on her computer.
"
Proposed change: would it be useful to explain why they don't appear on the right or on the left but under or above on her screen?
Proposed change: Sometimes instructions on websites say things like “press the button on the left” or “on the right”, which are confusing because of her screen magnification, they actually appear above
or below the text on her computer.
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
Vicki Menezes Miller
  • I approve this script as it currently is (no changes suggested)
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz
  • I abstain (not vote) and accept the decisions of the Working Group
Jennifer Delisi
  • I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
[i] Scene 1 includes a lot of information. Recommend removing "magnifies the screen and" since magnifying content on the screen would (typically) also increase the text size. If there is a reason to note these separately, then this requires a separate sentence because that may not be apparent to all reviewing the video. From scene 2 it appears that increasing the size of the text is the focus of the topic, but if it is magnification, then this should be switched.

Further review of the audio content has it going through other types of issues. To help viewers connect this to the language of the success criteria, highly recommend using the exact language included in the SC. For example, using when appropriate the words shape, color, size, visual location, orientation, or sound. Scene 2, for example, could have the term visual location.

[i] Scene 4 may be confusing to some - wondering why this is different from 1.4.1.
Tzviya Siegman
  • I approve this script as it currently is (no changes suggested)
Kevin White
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
4: Where does it say Kaseem can't hear?
Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Laura Keen
  • Jade Matos Carew
  • Vicki Menezes Miller
  • Bruce Bailey
  • Tzviya Siegman
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Kimberly Patch
  • Kris Anne Kinney
  • Sylvie Duchateau
  • Kevin White
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
  • Jennifer Delisi
I abstain (not vote) and accept the decisions of the Working Group
  • Lisa Seeman-Horwitz

9. Draft Script 1.3.4 "Orientation"

summary | by responder | by choice

Draft script for Success Criterion 1.3.4 "Orientation"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 9
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 2
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
I abstain (not vote) and accept the decisions of the Working Group 1

Skip to view by choice.

View by responder

Details

Responder Draft Script 1.3.4 "Orientation"Comments
Laura Keen
  • I approve this script as it currently is (no changes suggested)
Kimberly Patch
  • I approve this script as it currently is (no changes suggested)
Justine Pascalides
Kris Anne Kinney
  • I approve this script as it currently is (no changes suggested)
Sylvie Duchateau
  • I approve this script as it currently is (no changes suggested)
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
Vicki Menezes Miller
  • I approve this script as it currently is (no changes suggested)
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz
  • I abstain (not vote) and accept the decisions of the Working Group
Jennifer Delisi
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
[e] Scene 2: I'm unclear why the individual in this script has both a stand and a mount. This communicates to me that someone else has moved his device for him, and attached it to both a stand (when at the table) and a mount on his wheelchair. For those less familiar with AT, it may be easier to have just one mounting method presented. This also will enable a more independent presentation of Jan, even with this type of physical disability. Many individuals have no ability at all to alter the orientation of their device. Demonstrating that some sites work well with a landscape orientation, but others do not, may help the learners better understand the concept.
Tzviya Siegman
  • I approve this script as it currently is (no changes suggested)
Kevin White
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
3: Is there something more essential than just comfort that could be used as an example of a problem with orientation?
5,6: Not sure why he is using another newspaper app if his favourite one works for him
Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry This seems a bit weak. Hopefully someone else provided suggestions.

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Laura Keen
  • Kimberly Patch
  • Kris Anne Kinney
  • Sylvie Duchateau
  • Jade Matos Carew
  • Vicki Menezes Miller
  • Bruce Bailey
  • Tzviya Siegman
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Jennifer Delisi
  • Kevin White
I approve this script only with the changes raised in GitHub or in the comments field below
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
I abstain (not vote) and accept the decisions of the Working Group
  • Lisa Seeman-Horwitz

10. Draft Script 1.3.5 "Identify Input Purpose"

summary | by responder | by choice

Draft script for Success Criterion 1.3.5 "Identify Input Purpose"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 9
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 1
I approve this script only with the changes raised in GitHub or in the comments field below 1
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below 1
I abstain (not vote) and accept the decisions of the Working Group

Skip to view by choice.

View by responder

Details

Responder Draft Script 1.3.5 "Identify Input Purpose"Comments
Laura Keen
  • I approve this script as it currently is (no changes suggested)
Kimberly Patch
  • I approve this script as it currently is (no changes suggested)
Justine Pascalides
Kris Anne Kinney
  • I approve this script as it currently is (no changes suggested)
Sylvie Duchateau
  • I approve this script as it currently is (no changes suggested)
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
Vicki Menezes Miller
  • I approve this script as it currently is (no changes suggested)
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz
  • I approve this script only with the changes raised in GitHub or in the comments field below
This is just not true for the conditions " It is not a memory issue, she just confused the numbers and letters when she was typing her username and password because they are not real words."
I dont realy like it peopcuse people think this is about students and it goes away as we "learn" as a dyslexic with a related memory issues, it isnt going away any time soon.
I would change it to trying to log on to the work network, and getting it wrong becuse you have a a low visual and auditory memory. ypu then get logged out becuse you try three times incorrectly. you then get sent to a support ine that yu can not operate becuse it has simmilar issues. you then miss your meetings. etc


again, i would send to coga.



Jennifer Delisi
  • I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
[i] I recommend that COGA members have an opportunity to review this script. I am really excited to see this type of issue brought forward, but feel it needs further review. For example, I have concerns about the use of the word "confused" in scene 2 and how this is presented. I recommend using phrasing more similar to what is in Content Usable, 6.7.2 Jonathan Scenario 2. This section of Content Usable focuses more on the time it takes to complete something without typos.
Tzviya Siegman
  • I approve this script as it currently is (no changes suggested)
Kevin White
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
4: If we don't show the code that much then I think this story is diluted.
5: Is there something about being able to trust that here information is entered correctly
Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Laura Keen
  • Kimberly Patch
  • Kris Anne Kinney
  • Sylvie Duchateau
  • Jade Matos Carew
  • Vicki Menezes Miller
  • Bruce Bailey
  • Tzviya Siegman
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Kevin White
I approve this script only with the changes raised in GitHub or in the comments field below
  • Lisa Seeman-Horwitz
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
  • Jennifer Delisi
I abstain (not vote) and accept the decisions of the Working Group

11. Draft Script 1.3.6 "Identify Purpose"

summary | by responder | by choice

Draft script for Success Criterion 1.3.6 "Identify Purpose"

For each of your comments, please clearly indicate:

  • Location: eg. "SC 1.2.2 - Scene 2"
  • Priority: eg. "[e]" for editorial or "[i]" for important
  • Current wording:
  • Suggested revision:
  • Rationale:

Summary

ChoiceAll responders
Results
I approve this script as it currently is (no changes suggested) 9
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion) 1
I approve this script only with the changes raised in GitHub or in the comments field below 1
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
I abstain (not vote) and accept the decisions of the Working Group

Skip to view by choice.

View by responder

Details

Responder Draft Script 1.3.6 "Identify Purpose"Comments
Laura Keen
  • I approve this script as it currently is (no changes suggested)
Kimberly Patch
  • I approve this script as it currently is (no changes suggested)
Justine Pascalides
Kris Anne Kinney
  • I approve this script as it currently is (no changes suggested)
Sylvie Duchateau
  • I approve this script as it currently is (no changes suggested)
Jade Matos Carew
  • I approve this script as it currently is (no changes suggested)
Vicki Menezes Miller
  • I approve this script as it currently is (no changes suggested)
Bruce Bailey
  • I approve this script as it currently is (no changes suggested)
Lisa Seeman-Horwitz Again with the students....these are a sterio type that are not in most peoples target audence.
How about Xeena has spent five years learning a symbol language. They know over 5000 symbols, and can now comunicate with these symbols.

Jennifer Delisi
  • I approve this script only with the changes raised in GitHub or in the comments field below
[e] If the text in the notes section is to be published, I recommend reviewing this text.
[i] It may be difficult for viewers to connect scene 4 with the rest of the information as it is quite different than the content coming before it. I recommend removing scene 4 because it does not describe the purpose listed in the notes section.
Tzviya Siegman
  • I approve this script as it currently is (no changes suggested)
Kevin White
  • I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
3: If we don't show the code that much then I think this story is diluted.
4: Reading view seems to be quite a common solution to this problem - is it something to flag if it is commonly solved in browsers now?
Brent Bakken
  • I approve this script as it currently is (no changes suggested)
Shawn Lawton Henry

View by choice

ChoiceResponders
I approve this script as it currently is (no changes suggested)
  • Laura Keen
  • Kimberly Patch
  • Kris Anne Kinney
  • Sylvie Duchateau
  • Jade Matos Carew
  • Vicki Menezes Miller
  • Bruce Bailey
  • Tzviya Siegman
  • Brent Bakken
I approve this script with minor suggestions; please consider my comments raised in GitHub or in the comments field below (for editors' discretion)
  • Kevin White
I approve this script only with the changes raised in GitHub or in the comments field below
  • Jennifer Delisi
I do not approve this script because of the comments raised in GitHub (OB) or in the comments field below
I abstain (not vote) and accept the decisions of the Working Group

12. Other Comments

Any other comments, thoughts, or suggestions?

Details

Responder Other Comments
Laura Keen
Kimberly Patch I think these are generally good and nicely narrowly focused
Justine Pascalides
Kris Anne Kinney Love these videos that show real-world scenarios to try to explain the SC to developers who may not understand what the need is. THANK YOU!
Sylvie Duchateau
Jade Matos Carew
Vicki Menezes Miller
Bruce Bailey Thanks for these, looks great!
Lisa Seeman-Horwitz Make sure someone with the disability (not just a aly) has reviewed each one
Jennifer Delisi Very exciting to see this type of work being done. Thank you for all the work that has gone into making the examples inclusive!
Tzviya Siegman These look great. Thank you!
Kevin White I think there is some inconsistency in the endings - don't know if it is a problem, but some end with happy fix, others end with happy bit but no fix mentioned.
Brent Bakken
Shawn Lawton Henry

More details on responses

  • Laura Keen: last responded on 12, April 2021 at 18:43 (UTC)
  • Kimberly Patch: last responded on 16, April 2021 at 18:14 (UTC)
  • Justine Pascalides: last responded on 20, April 2021 at 17:01 (UTC)
  • Kris Anne Kinney: last responded on 21, April 2021 at 16:50 (UTC)
  • Sylvie Duchateau: last responded on 22, April 2021 at 14:55 (UTC)
  • Jade Matos Carew: last responded on 22, April 2021 at 18:22 (UTC)
  • Vicki Menezes Miller: last responded on 23, April 2021 at 15:38 (UTC)
  • Bruce Bailey: last responded on 27, April 2021 at 15:21 (UTC)
  • Lisa Seeman-Horwitz: last responded on 27, April 2021 at 17:21 (UTC)
  • Jennifer Delisi: last responded on 27, April 2021 at 22:02 (UTC)
  • Tzviya Siegman: last responded on 28, April 2021 at 18:42 (UTC)
  • Kevin White: last responded on 29, April 2021 at 13:34 (UTC)
  • Brent Bakken: last responded on 29, April 2021 at 15:59 (UTC)
  • Shawn Lawton Henry: last responded on 1, May 2021 at 04:20 (UTC)

Compact view of the results / list of email addresses of the responders

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire