- From: Daniel Montalvo <dmontalvo@w3.org>
- Date: Tue, 7 Dec 2021 16:54:04 +0100
- To: "'David Sloan'" <dsloan@tpgi.com>
- Cc: <wai-eo-editors@w3.org>
- Message-ID: <005f01d7eb82$aababe80$00303b80$@w3.org>
Thanks, That is a reasonable assumption. Those usability decisions have consequences on accessibility, as they affect specific groups of people with disabilities. Let's see what comes out from today's discussion. Best. -- Daniel Montalvo Accessibility Education and Training Specialist W3C/WAI From: David Sloan <dsloan@tpgi.com> Sent: Tuesday, December 7, 2021 4:48 PM To: Daniel Montalvo <dmontalvo@w3.org> Cc: wai-eo-editors@w3.org Subject: Re: No meeting tomorrow, please use time for designer modules survey Hi Daniel Sorry that I won’t be able to attend today’s TF meeting due to work pressures—I have meetings end-on today. But thanks for the feedback on my comments! Here are some responses: Module 1: I think “placement” would work as it implies a more deliberate selection of where something is put in a design, with “layout” a similar word to describe the spatial relationship of components of a design. Module 1: I acknowledge the points Carlos makes in his GH issue about whether “overuse” is a usability or accessibility issue. In this case we could argue that overuse adversely affects people with disabilities (cognitive overload from visual or auditory information, extra keyboard interactions required). Therefore I think it’s worth considering the impact of overuse on the user experience for people with disabilities, even if it’s not covered deeply. My point was more about the need to consider context when making a judgement on what is sufficient or too many, hence my edit suggestions. Hope this helps! Dave From: Daniel Montalvo <dmontalvo@w3.org <mailto:dmontalvo@w3.org> > Date: Tuesday, 7 December 2021 at 12:42 To: David Sloan <dsloan@tpgi.com <mailto:dsloan@tpgi.com> > Cc: wai-eo-editors@w3.org <mailto:wai-eo-editors@w3.org> <wai-eo-editors@w3.org <mailto:wai-eo-editors@w3.org> > Subject: RE: No meeting tomorrow, please use time for designer modules survey CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender. Hey Dave, Thanks for your valuable feedback. Please see my comments below as [Daniel]. --- # Module 1 In the introduction’s second bullet point, and the first Learning Outcome, what does “position” mean? The term is used in the introduction and LOs, and then only once more in the page. Is “position” a synonym for “layout”? Should it be “relative position”? Is it redundant? [Daniel] My intention was to refer to the place that interface components have, and on the impact misplacement has in user expectations. For example, navigation bars are generally placed to the left in desktop. In mobile you may expect a hamburger menu at the top left. We use "placement" in other modules. Would you be comfortable with placement? Topic: Flexible Layouts Use of “overuse/too many” is problematic as it implies an absolute condition, when overuse is contextual, and students need to be able to make a contextual assessment. Suggest the following edits: In the topic intro, second para: “Demonstrate approaches to providing an appropriate number and diversity of design elements use to avoid potential overload and distraction for some users.” In the topic LOs, second last bullet: “detect the potential overuse of design elements” [Daniel] Will discuss in today's TF as it may imply additional changes. There is currently an open issue for that by Carlos https://github.com/w3c/wai-curricula/issues/398 # Module 2 Typo in multiple places: should be “designer’s” not “designers’” [Daniel] That's corrected now. Topic: Tables First para starts “research strategies”. This could be interpreted as a noun phrase when it’s being intended as a verb. For clarity, suggest rephrasing as “Investigate strategies…” [Daniel] That's good suggestion. I will implement here and take a pass for additional occurrences of "research strategies". # Module 4 Topic: Gestures and Motion The introduction text: “Discuss gestures that require dragging and drawing specific paths on a touch screen. Explain that these are difficult (and sometimes impossible) to perform for some people.” seems quite limited. Suggest a reword: “Discuss gestures that require dragging and drawing specific paths on a touch screen. Explain the difficulties these may present some people with disabilities, and approaches to using complex gestures appropriately in interaction design.” [Daniel] That's done now. # Module 5 Topic: informative Images The two bulleted LOs for CAPTCHA (define alternatives to biometrics and CAPTCHA…, and explain the issues associated with…) seem to be the wrong way round in terms of importance/relevance. Indeed, the first one seems redundant—it’s not clear what the difference is between the two. I’d suggest removing the first or looking at rewording to make the two more distinct. [Daniel] That's good point. I have created issue <https://github.com/w3c/wai-curricula/issues/436> https://github.com/w3c/wai-curricula/issues/436 and will update when I have a proposal. General typo: use “humans” rather than “human beings” [Daniel] Done. # Module 6 Introduction text Include warnings of presence of flickering and flashing content, and pause/stop/hide functionality in the intro bullets? Topic: Movement and animation Include in LOs: “Detect content that may include flickering or flashing, and design ways to provide users with warnings of the presence of the flickering/flashing content before they encounter the content.” Teaching ideas: In the teaching idea on flickering/flashing content, there should be a warning that any activity involving showing students examples of flashing content may itself be harmful to some students, and needs to be provided to students only with prior warning. There should be a similar warning for the teaching idea of exposing students to animations. [Daniel] Will discuss ways to include such warnings in TF meeting today. Updates will be put on issue https://github.com/w3c/wai-curricula/issues/437 Best. -- David Sloan (he/him) Principal Accessibility Engineer Strategy and Research Lead TPG Interactive <https://www.tpgi.com/> www.tpgi.com A Vispero Company <https://vispero.com> https://vispero.com -- This message is intended to be confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, please delete this message from your system and notify us immediately. Any disclosure, copying, distribution or action taken or omitted to be taken by an unintended recipient in reliance on this message is prohibited and may be unlawful. From: Daniel Montalvo < <mailto:dmontalvo@w3.org> dmontalvo@w3.org> Date: Wednesday, 1 December 2021 at 10:21 To: David Sloan < <mailto:dsloan@tpgi.com> dsloan@tpgi.com> Subject: RE: No meeting tomorrow, please use time for designer modules survey CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender. That sounds good. Please copy <mailto:wai-eo-editors@w3.org> wai-eo-editors@w3.org in that mail. Thanks. Best. -- Daniel Montalvo Accessibility Education and Training Specialist W3C/WAI From: David Sloan < <mailto:dsloan@tpgi.com> dsloan@tpgi.com> Sent: Wednesday, December 1, 2021 10:08 AM To: Daniel Montalvo < <mailto:dmontalvo@w3.org> dmontalvo@w3.org> Subject: Re: No meeting tomorrow, please use time for designer modules survey Hi Daniel Thanks! I’ll do that now and send you my survey responses by email. Dave From: Daniel Montalvo < <mailto:dmontalvo@w3.org> dmontalvo@w3.org> Date: Wednesday, 1 December 2021 at 09:06 To: David Sloan < <mailto:dsloan@tpgi.com> dsloan@tpgi.com> Subject: RE: No meeting tomorrow, please use time for designer modules survey CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender. Hey Dave, There are eleven responses, but yours is as important as everybody else' 😊 If you do have the time this morning and you plan to do the survey, you can still provide your comments even if the survey is closed. I will process your comments and explain to the planning team this afternoon. Best. -- Daniel Montalvo Accessibility Education and Training Specialist W3C/WAI From: David Sloan < <mailto:dsloan@tpgi.com> dsloan@tpgi.com> Sent: Wednesday, December 1, 2021 10:02 AM To: Daniel Montalvo < <mailto:dmontalvo@w3.org> dmontalvo@w3.org> Subject: Re: No meeting tomorrow, please use time for designer modules survey Hi Daniel I planned to work on the survey this morning but realised it is now closed. I’m sorry I wasn’t able to get to it in time, but since you have 11 responses already I guess you have plenty of feedback. Dave From: Daniel Montalvo < <mailto:dmontalvo@w3.org> dmontalvo@w3.org> Date: Monday, 29 November 2021 at 12:05 To: <mailto:public-wai-curricula@w3.org> public-wai-curricula@w3.org < <mailto:public-wai-curricula@w3.org> public-wai-curricula@w3.org> Subject: No meeting tomorrow, please use time for designer modules survey CAUTION: This email originated outside Vispero. Do not click links, open attachments or forward unless you recognize the sender. Hey all, First, thanks to Carlos who has already completed the survey and provided very useful feedback. We will be discussing some issues he raised in the following meetings as I work through them. There will be no meeting tomorrow. Please use as much time as you can for the Designer Modules Thorough Review survey. <https://www.w3.org/2002/09/wbs/35532/curricula-designer-monkey-review/> https://www.w3.org/2002/09/wbs/35532/curricula-designer-monkey-review/ If you think you won’t be able to complete the survey by tomorrow, please reply to me with an estimate of when you would be able to review this resource so that I can propose next steps to the EOWG planning team. Thanks all for the time you commit to helping develop this resource. Best. Daniel Montalvo Accessibility Education and Training Specialist W3C/WAI -- Daniel Montalvo Accessibility Education and Training Specialist W3C/WAI
Attachments
- image/png attachment: image001.png
Received on Tuesday, 7 December 2021 15:54:10 UTC