W3C

Site Navigation

Nearby

Results of Questionnaire User Stories - WAI Starfish review for updates to How People with Disabilities use the Web

The results of this questionnaire are available to anybody.

This questionnaire was open from 2021-07-15 to 2021-08-09.

8 answers have been received.

Jump to results for question:

  1. Introduction and Purpose
  2. Review level
  3. User: Alex
  4. User: Blair
  5. User: Ilya
  6. User: Lee
  7. User: Luis
  8. User: Martine
  9. User: Noor
  10. User: Preety
  11. User: Yun
  12. Additional comments
  13. Done?

1. Introduction and Purpose

The following survey has the purpose of gathering input on current progress for updates to the existing resource of User Stories within How People with Disabilities Use the Web.

We seek broad input from EOWG and COGA TF participants and others who may have interest.

This is a Starfish review meaning that we are looking for anything we may have missed about the description of the user and/or any barriers they may encounter that are not included. There is no need at this time for wordsmithing or copy edits.

Several user scenarios are being redeveloped and we expect it will take you several hours to give appropriate consideration to the work that has been done. Given the amount of material and the importance of the work, it is organized so that you can review one or two and save your work to come back as time allows. Thank you for your thoughtful responses:

To get a sense of the goals, you may wish to review the Requirements for the Update Project. Once you are confident about the update goals, please review the profiles of the specific users. These will further developed for eventual publication and your comments will help us flesh them out. As you review them, please think about:

  • Are all relevant aspects accurately described - is anything missing?
  • Is there anything in the descriptions that should not be there?
  • Have all potential barriers to efficient use been captured and described?
  • Try to catch all significant issues in this review. (if you bring up large issues later, they could cause delays, now is the time for them)
  • Have we identified all the barriers that might be encountered by each user?

Please comment in the comment boxes or open a GitHub issue

Details

Responder
Denis Boudreau
Jade Matos Carew
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau
Michele Williams
Laura Keen
Daniel Montalvo Great work. I am so excited to see this resource updated.

Please see my issues
https://github.com/w3c/wai-people-use-web/issues/created_by/daniel-montalvo

Not stuck in any of these, but I do think they do deserve further thought.

2. Review level

What level of review did you do?

Summary

ChoiceAll responders
Results
I thoroughly reviewed the materials. 5
I skimmed them. 1
I need more time and will review by the date provided below.
I didn't get to it and will not in the near future. I abstain from providing comment on this resource. 1

(1 response didn't contain an answer to this question)

Details

Responder Review level
Denis Boudreau I didn't get to it and will not in the near future. I abstain from providing comment on this resource.
Jade Matos Carew My review was half way between a thorough review and a skim.
I'm also completing this on the hottest day of the year so far, apologies if what I'm trying to say doesn't make much sense!
Kimberly Patch I thoroughly reviewed the materials. I thoroughly reviewed the user I have direct experience with (Alex0.
Rain Breaw Michaels I thoroughly reviewed the materials. From Lisa and Rain's discussion of these stories:

We don’t feel comfortable asking the larger COGA Task Force to review any further at this time. Much of the framing of cognitive differences and disabilities in the current user stories may be upsetting to COGA TF participants, as they are largely stereotypical and not representative of the lived experience of our actual participants. Lisa and Rain did a thorough review of the stories, and our feedback is documented in this google doc: https://docs.google.com/document/d/1K87FbKnCj67DcCjnvbf0oheMRTRypdFinIVDtF-xr8I/edit#

We would be happy to set up a time to talk with the EOWG, and answer questions and concerns.

Thank you for giving us this opportunity. We look forward to what these become!
Sylvie Duchateau I skimmed them.
Michele Williams I thoroughly reviewed the materials.
Laura Keen I thoroughly reviewed the materials.
Daniel Montalvo I thoroughly reviewed the materials.

3. User: Alex

When considering the description of Alex and potential design barriers:

  • Is the user description accurate - is anything missing?
  • Is there anything in there that should not be in there?
  • Are all likely barriers included - is anything significant missing? (The barriers are not intended to be an exhaustive list. We are looking to have 4-6 ish barriers that cause significant problems for each user.)
  • Do you agree with the overall presentation structure?

You can comment below or leave a GitHub Issue about Alex

Details

Responder Comments
Denis Boudreau
Jade Matos Carew 'He uses an ergonomic keyboard to navigate around web pages...'. I think this should be a seperate sentence, otherwise it might give the impression that it's the ergonomic bit of the keyboard which is helping him navigate.
Another language point (sorry) I think the paragraphs in the main section could do with a bit of re-ordering to make it more readable. So one paragraph for keyboard, the other for voice control. I actually prefer the 4 bullet points in the original version, I think it makes it clearer.
Kimberly Patch I've used speech Input and mixed input for the past 20-odd years due to Repetitive Stress Injuries (RSIs), and this persona doesn't strike me as a typical, successful, or useful example to others who are battling RSI's. I think it's important to Illustrate personas who are using assistive technologies well and sustainably. Hitting a key repeatedly is something that generally exacerbates RSIs, and generally makes folks who have RSIs cringe. All the barriers for this persona are keyboard-only barriers. I'd choose a persona with a disability that better matches keyboard-only use to illustrate these barriers. A more typical RSI persona (who avoids hitting keys repeatedly to avoid reinjury) could illustrate more typical barriers for that injury.
Rain Breaw Michaels
Sylvie Duchateau 1. In the description of Alex's assistive technology:
"The software allows him to select and ‘click’ on links with his voice"
May be it could be more accurate to write that he can click using his voice, because voice alone cannot click?
2. Editor's discretion: identify in the page structure what is the barrier, what is the problem and what works well. If I understand correctly, all is for now in a bulleted list, without identifiying which text depends from each encountered barrier.

Solution : make separated lists for each problem. Make sublist for each item that illustrates each barrier. Or use numbered list for each barrier adn bulleted sublist to explain each barrier, problem and what works well.
Michele Williams Looks pretty complete to me (with one caveat below). It was a little surprising to see "text alternatives" listed under the Related Principles but looks like that includes labels on form fields. I assume then you mean that's important for voice recognition (since it technically wouldn't impact keyboard or mouse users). If so, I'm good with all that.

My caveat is there's a device called a "roller mouse" that one research participant with carpal tunnel syndrome told me really helped her and completely eliminated the need for using the keyboard. This doesn't mean that's the case for everyone but something to consider is maybe updating the disability or mentioning this kind of tech just to ensure we're up-to-date with our info, not coming across as exaggerating the guidelines' applicability, or making people sound more helpless than they are for the sake of empathy/pity, etc.
Laura Keen I don't have any comments or input.
Daniel Montalvo

4. User: Blair

When considering the description of Blair and potential design barriers:

  • Is the user description accurate - is anything missing?
  • Is there anything in there that should not be in there?
  • Are all likely barriers included - is anything significant missing? (The barriers are not intended to be an exhaustive list. We are looking to have 4-6 ish barriers that cause significant problems for each user.)
  • Do you agree with the overall presentation structure?

You can comment below or leave a GitHub Issue about Blair

Details

Responder Comments
Denis Boudreau
Jade Matos Carew (I'll comment on this when it's ready)
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau What about adding that he prefers communicate in writing things rather using a phone to talk to somebody because direct relationship with somebody may be more difficult for him?
Michele Williams Not my area of expertise, though the descriptions sound more like Intellectual Disability than Autism. One direction this may go is to promote a practice I've seen people like Lainey Feingold do which is to summarize an article in plain language prominently at the top of the page: https://www.lflegal.com/2021/06/dominos-june-2021/
This could tie with reading level, which is a controversial guideline from the chatter I've seen but could get copy writers to feel more included in understanding the guidelines and how they apply to their work.

Overall not sure what's important to pull out here -- the representation of Autism, calling out a certain guideline, or acknowledging a certain barrier. If that's made more clear I'm happy to do some digging though I'm sure the COGA group will have the most input.
Laura Keen I don't have any comments or input.
Daniel Montalvo

5. User: Ilya

When considering the description of Ilya and potential design barriers:

  • Is the user description accurate - is anything missing?
  • Is there anything in there that should not be in there?
  • Are all likely barriers included - is anything significant missing? (The barriers are not intended to be an exhaustive list. We are looking to have 4-6 ish barriers that cause significant problems for each user.)
  • Do you agree with the overall presentation structure?

You can comment below or leave a GitHub Issue about Ilya

Details

Responder Comments
Denis Boudreau
Jade Matos Carew I think an additional paragraph about mobile phone use would be helpful here, it's in the original more and would fit with the intended aim of improving mobile web accessibility in the re-draft. It's also in the quote at the beginning but then isn't explored much further in the rest of the section.
Would a pop up window barrier be useful here? Especially when they're problematic to close in mobile devices.
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau 1. May be explain why she does not read Braille? Why many blind people don't?

2. In "assistive technologies and adaptative strategies, I am not convinced that skip links should be kept. As I found that screen readers do not handle this very well, the anchor does not always work properly. Mabe prefer using quick navigation keys around headings, lists, landmarks.

3. In barriers, "Good use of headings", this is not a barier but an imrovement. Rather say: bad use of headings, or web pages without headings?

4. Same for other barriers: clear error messages, consistent layout, is not a barrier but an advantage.
Michele Williams Currently the "day in the life" description for Ilya doesn't really provide any insights - it doesn't match the barriers and related principles and doesn't really describe what she's doing with her screen reader. I think people have trouble understanding that (1) it's reading code and not the design, (2) people are navigating by skipping around based on the markup, and (3) they can't confirm anything outside of what they hear (that is, really remind people blind people can't see, it's hard to drive that point home). It would be good if the scenarios walked through that a bit more and explained why her online cloud services do work (e.g., marked up correctly, has table headings, etc.) and then keep the part about her colleagues not doing their part with alt text.
I don't think keyboard traps are necessary here because it already feels long, but I do like the CAPTCHA although I suspect people will wonder if "reCAPTCHA" covers this concern. Not sure if we're including the last pieces about knitting just to help dispel blindness myths but I think it may open up more questions than it answers with maybe something like "People often wonder how she can do these things but there's adaptations for everything and she learned these in her blindness training."
One sentence says, "Both devices have built in screen readers and other tools, like zoom, that can really help her." Does Ilya have usable vision? If not, why would zoom be important? If so, that's not made clear in the description. Also, keep in mind that people may mistake this for Zoom video conferencing so may need to say "magnification". :-)
Laura Keen I don't have any comments or input. This description of Ilya and her potential barriers is well written and robust. I like the quote at the beginning as it gives you a clue as to what Ilya's story might be.
Daniel Montalvo

6. User: Lee

When considering the description of Lee and potential design barriers:

  • Is the user description accurate - is anything missing?
  • Is there anything in there that should not be in there?
  • Are all likely barriers included - is anything significant missing? (The barriers are not intended to be an exhaustive list. We are looking to have 4-6 ish barriers that cause significant problems for each user.)
  • Do you agree with the overall presentation structure?

You can comment below or leave a GitHub Issue about Lee

Details

Responder Comments
Denis Boudreau
Jade Matos Carew 'Sometimes there can be problems with the way these sites use color to differentiate between teams, player positions..', I think the problem here needs to be identified (is it to do with adequate contrast/settings? This is mentioned in the original.)
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau Ok for this page except following sentence in barriers, I don't understand:
"Works well: Enemies are also marked with a symbol/use a red triangle so I can easily identify them." What is meant with enemies here?
Michele Williams Is there opportunity to provide pictures for some of these? Does that broaden the scope too much? It's just so much more impactful to see what red/green color blindness looks like (and a few others could use some graphics too). Overall, I like the direction of this and bringing in the Fantasy Football example.
Laura Keen I don't have anything to add/remove.

Question: We're using 2 different spellings of the word "color" [colour]. I'm guessing that's intentional. Is it really necessary?

Daniel Montalvo

7. User: Luis

When considering the description of Luis and potential design barriers:

  • Is the user description accurate - is anything missing?
  • Is there anything in there that should not be in there?
  • Are all likely barriers included - is anything significant missing? (The barriers are not intended to be an exhaustive list. We are looking to have 4-6 ish barriers that cause significant problems for each user.)
  • Do you agree with the overall presentation structure?

You can comment below or leave a GitHub Issue about Luis

Details

Responder Comments
Denis Boudreau
Jade Matos Carew My hesitation here is that in the original the situation with the online shopping website was positive, here the difficulty buying tickets is quite negative, which is a shame.
In the 'job' paragraph, it appears to be talking about language, so it might be good to move the parts over about his own language use (word prediction/choices) instead of/in addition to the navigation part (which could be made into a separate paragraph and expanded on.)
I think the addition of the two sentences at the end about online shopping are not needed unless they're going to be part of a larger paragraph about shopping, they don't add much to the description in their current form. That paragraph could focus on the accessibility functions of his mobile phone instead.
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau 1. An explanation is missing why following is confusing for Luis: "Especially confusing is when he clicks on a link and ends up in a PDF file."

2. After the sentence: "Luis is keen to get a job but worries that the jargon will make this initially difficulty.", some parts are positives, what helps him, and other are negatives, what does not help him. May be only write what is a plus, because you have:
- Plain language = plus;
- Abbreviations and acronyms are minus, slowing him down. May be say: not using acronyms is helpful because other wise it slows him down. Or change the connecction word between the sentence before and this one that says: "also".
- Headings is a plus again, but is linked to the sentence before with also.

Suggestion: write first what helps him and then what is disturbing.

3. At last, same issue as in the other descriptions about the title of the barrier which is sometimes a helpful thing: for example Breadcrumb trail, sometimes a real barrier.
Michele Williams This feels a little "kitchen sink" in that it seems to have a lot of guidelines packed in. Perhaps some of this can go into the "Blair" persona? I think it either needs to focus on ordering basketball tickets or using simplified/focused mobile apps for shopping, but not both. I'm also not sure what this was trying to get at: "Especially confusing is when he clicks on a link and ends up in a PDF file."
Laura Keen I have nothing to add/remove.
Daniel Montalvo

8. User: Martine

When considering the description of Martine and potential design barriers:

  • Is the user description accurate - is anything missing?
  • Is there anything in there that should not be in there?
  • Are all likely barriers included - is anything significant missing? (The barriers are not intended to be an exhaustive list. We are looking to have 4-6 ish barriers that cause significant problems for each user.)
  • Do you agree with the overall presentation structure?

You can comment below or leave a GitHub Issue about Martine

Details

Responder Comments
Denis Boudreau
Jade Matos Carew The sign language element is confusing here, suggestion: I'm a native sign language user. Most people don’t realise that sign language is a completely different language. I can read text in English but it is hard as I am always translating from my first language, which is sign language.'

'While she can hear some sounds, she does not hear enough to understand speech.' this part is in the quote, it should be moved to the main body.

Merge paragraphs one and two. I'd separate out the sentence with SL interpreters and CART, e.g. The university where Martine studies provides sign language interpreters for some live lectures and tutorials. When this is not possible, CART is provided...

Should the inaccuracy of automated captioning be a barrier here?

I really like this profile btw.
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau Everything sounds good, barriers are clear.

One suggestion: "Provide audio alternatives such as sign language, captions or transcript."
For her, sign language may help, but not necessarily for others who do not understand sign language. So if you write "or", people may think that audio alternatives may be enough when they provide sign language.
Proposed change: Provide audio alternatives such as sign language, captions and transcript.
Michele Williams Not sure what this means in her quote: "I can read text but it is hard as I am always translating from my native language." -- Is this persona a non-native speaker of her current country? That's not reflected in the rest of the text. I might stay away from that and stick to "auto-craptions" and lack of captions.

I think the examples here could speak a bit more to the current states of captions such as "open captions" on social media videos and how they're useful though sometimes the color contrast makes them hard to see.

For "Inaccurate captions" maybe this comes from auto-captions or caption interpreters who don't type technical terms accurately? Overall not sure we should point out barriers unless it's clear how someone can fix it and currently I'm not sure what this barrier is trying to say or what I could do to avoid it.

"Design of captions" says, "When watching movies online, the captions often appear on top of the video." Is this true in other countries because I've not seen a U.S.-based player do this. Instead maybe this can be replaced with open captions or that people need to be careful about where they place important visual information on the screen to ensure captions don't cover the content.

"No alternative for audio" isn't clear to me and not really realistic (e.g., TV news programs don't generally have ASL interpreters or transcripts). Maybe this is saying that live captions are hard to follow on the TV so online news is more helpful??

Overall it says that Martine doesn't understand sign language so doesn't seem like this should be one of the related principles. However, I think the tone of the final version needs to be careful not to dismiss the value of sign language for others either; this is currently coming across as if sign language isn't needed as everyone can read text like captions.
Laura Keen I don't have anything to add/remove.

Note [3rd paragraph last sentence]:
"Auto-captioning can be useful for her bit it can also cause her problems if it’s available but incorrect." "bit" should be but
Daniel Montalvo

9. User: Noor

When considering the description of Noor and potential design barriers:

  • Is the user description accurate - is anything missing?
  • Is there anything in there that should not be in there?
  • Are all likely barriers included - is anything significant missing? (The barriers are not intended to be an exhaustive list. We are looking to have 4-6 ish barriers that cause significant problems for each user.)
  • Do you agree with the overall presentation structure?

You can comment below or leave a GitHub Issue about Noor

Details

Responder Comments
Denis Boudreau
Jade Matos Carew I like this profile, but I think it's really heavy on the impact of her blindness rather than incorporating a little more about deafness as well? Maybe it doesn't need it.
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau I'm afraid this can be confusing for people when the text says she is blind but can read enlarged text and Braille. I know many people who still can see a bit and don't want to learn Braille. May be provide more explanations about what legally blind means, may not mean the same in the different countries. I think we could use "partially sighted people" for those who still can see a bit.
Michele Williams If this is going to have a quote about watching videos, we may want to explain how that works a bit more since deaf-blindness is hard for some people (me included) to fully understand/appreciate. It also doesn't quite match the examples in the "day in the life" portion so seems disconnected.

Overall, it's a bit hard to understand how, if she's recently legally blind, she learned to use Braille (or, rather, what prompted using Braille and taking the significant time out to learn it?). If Noor has usable vision, how does Braille help (e.g., gives eyes a rest, faster?). For now it seems like she might use a large monitor or screen (e.g., to see videos) so not reconciling how Braille devices fit in.

"She communicates using sign language and a portable electronic Braille device" seems one-sided. If she's communicating with a fellow deaf person, can she see their signs? How do non-disabled people communicate with her in-person?

Since you mention making captions larger, should this communicate the need for players to recognize .vtt caption files and allow adjusting caption sizes? (Not super explicitly but more like how you have other things like "it helps when video players let her adjust caption size".)

"She has had problems in the past being able to submit coursework because the form buttons weren’t recognised by here device." - This is makes it seem like a Braille device is doing something significantly different and needs specialized code rather than simply displaying and following along with a screen reader (and standardized code). I would reword and/or explain this here so people don't get the wrong impression. It's also helpful to understand there are all-in-one Braille devices with calendars, etc., but I'm not sure people will know what to do with that information about compatibility with just the W3C resources currently listed.

Seems "Reflow" should be one of the Barriers.
Laura Keen I don't have anything to add/remove.
Daniel Montalvo

10. User: Preety

When considering the description of Preety and potential design barriers:

  • Is the user description accurate - is anything missing?
  • Is there anything in there that should not be in there?
  • Are all likely barriers included - is anything significant missing? (The barriers are not intended to be an exhaustive list. We are looking to have 4-6 ish barriers that cause significant problems for each user.)
  • Do you agree with the overall presentation structure?

You can comment below or leave a GitHub Issue about Preety

Details

Responder Comments
Denis Boudreau
Jade Matos Carew I think the original proflie for Preety was more coherent in that the focus was on one context, school. With the new profile, it seems to jump around a little. Perhaps a rework of the paragraph structure would help this so that each paragraph has a clear focus, e.g. in paragraph 3, separate out 'Preety is a fan of old science fiction...'
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau One of the barrier is not a problem but something helpful: spelling suggestions is not a barrier.
Michele Williams "My screen reader helps me focus on what I am reading." - I would say "text-to-speech software"; people often think (1) screen readers are the only AT and (2) people are firing up screen readers for TTS type assistance when really screen readers are giving a lot more information and overriding interaction patterns in ways that are too overwhelming for the average sighted user.

I had this question on another survey but do people still use "sitemaps"? Would be curious to see some testimonials of that.

Right now this feels heavy on the ADHD and TTS, and not so full on the Dyslexia and spelling help. However, I presume that would get more filled out in the next phases of writing.

I noticed captions are listed under AT and that may be a good point to call out in the top paragraph as well - that captions help concentration along with TTS for reading.

When Shell Little explains how debilitating moving advertisements are, it really hit home for me. Perhaps this can be an even stronger point - that it can ruin someone's ability to complete their entire next set of activities. Not saying we have to get overly or overtly dramatic, but I think some messages that people think they know (like how distracting ads are likely bad) can be more brought home.

Laura Keen See GitHub issue: [Preety] #122
Daniel Montalvo

11. User: Yun

When considering the description of Yun and potential design barriers:

  • Is the user description accurate - is anything missing?
  • Is there anything in there that should not be in there?
  • Are all likely barriers included - is anything significant missing? (The barriers are not intended to be an exhaustive list. We are looking to have 4-6 ish barriers that cause significant problems for each user.)
  • Do you agree with the overall presentation structure?

You can comment below or leave a GitHub Issue about Yun

Details

Responder Comments
Denis Boudreau
Jade Matos Carew I think there's a bit of superfluous info in the first paragraph, and perhaps the tone is a bit negative (in comparison to the old version which was more neutral?) e.g. the final straw.
Would something to do with error correction be a useful barrier to include here?
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau IN assistive technologies, I wonder if this could be an idea to add skip links.
The barriers are clear.
No other comments.
Michele Williams I feel like Yun would make a great use case for mobile via tablet interaction. I could see that when he transitioned to retirement someone bought him a tablet (like I did for my mom) and it could help his short term memory loss in that he just needs to tap the familiar icons on the desktop, they set text size as large in the operating system so no need to constantly zoom, and it's easy to maintain his blog from the app when it hooks up his Bluetooth keyboard to it. His hand tremor is less a problem with his touchscreen mobile device placed on the table than using a mouse on desktop and allows him to be anywhere in the house to engage with it. There's less logins to remember because everything was a one-time set-up in each app. He can also more easily use video calling with his family which he really enjoys. I'm not sure what the barrier would be but I think we've mentioned CAPTCHA a little too much in the other scenarios. Maybe it helps to have labels along with the icons on the home screen of his tablet in case the logo icon designs change, or having to go to the internet where reflow doesn't work.
Laura Keen Quote:

"I love all this new technology. It is great to "be" see my grandchildren. It takes me a bit to find all the controls and sometimes they are a bit of the small side, but I get there in the end"

delete "be" and add a period after "end."
Daniel Montalvo

12. Additional comments

Use the space below to include any additional observations or concerns you would like to see addressed at this stage. Thank you! This is an improtant, widely used resource, we appreciate your help in making it comprehensive and relevant.

Details

Responder Additional Comments
Denis Boudreau
Jade Matos Carew Sorry if anything I've written there isn't clear, pleae just give me a shout if you want me to clarify anything
Kimberly Patch
Rain Breaw Michaels
Sylvie Duchateau May be not enough about people with motor difficulties, such as people who cannot use their hands at all and use eyesticks or other pointing devices.

Otherwise, good resource!
Michele Williams I love the redesign of the landing page - much clearer and more inviting and enticing.

I worry that each persona is still a lot of text at the top so maybe that'll get flushed out over time, but I can definitely see this being useful for trainers to repurpose and for people really looking to understand the diversity of disability to be able to gleam from. Great job team!
Laura Keen The user stories are well written and provide a wide variety of barriers and solutions for accessibility.
Daniel Montalvo

13. Done?

Summary

ChoiceAll responders
Results
I have done some review, and will do more before the survey closes.
I'm done with my review. 5

(3 responses didn't contain an answer to this question)

Details

Responder Done?Comments
Denis Boudreau
Jade Matos Carew
Kimberly Patch
Rain Breaw Michaels I'm done with my review.
Sylvie Duchateau I'm done with my review.
Michele Williams I'm done with my review.
Laura Keen I'm done with my review.
Daniel Montalvo I'm done with my review.

More details on responses

  • Denis Boudreau: last responded on 20, July 2021 at 01:52 (UTC)
  • Jade Matos Carew: last responded on 21, July 2021 at 15:47 (UTC)
  • Kimberly Patch: last responded on 24, July 2021 at 12:02 (UTC)
  • Rain Breaw Michaels: last responded on 26, July 2021 at 17:14 (UTC)
  • Sylvie Duchateau: last responded on 30, July 2021 at 14:37 (UTC)
  • Michele Williams: last responded on 31, July 2021 at 15:55 (UTC)
  • Laura Keen: last responded on 3, August 2021 at 12:35 (UTC)
  • Daniel Montalvo: last responded on 9, August 2021 at 16:15 (UTC)

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

WBS home / Questionnaires / WG questionnaires / Answer this questionnaire

Report issues on GitHub project w3c/wbs-design or by mail to sysreq.