- From: Jennifer Chadwick <jcha@siteimprove.com>
- Date: Thu, 15 Aug 2019 18:27:03 +0000
- To: Shawn Henry <shawn@w3.org>, Daniel Montalvo Charameli <dmontalvo@w3.org>, "shadi+EOsurvey@w3.org" <shadi+EOsurvey@w3.org>, wai-eo-editors <wai-eo-editors@w3.org>
Hi Shawn and Daniel, thanks for walking and talking this through. 😊 Shawn raised a good point how the scope, here in this context, is about what web accessibility encompasses, and as Daniel pointed out, opposed to or separate from other disciplines in technology. I think my mind immediately went to the scope of projects - meaning, how much of the current design, content writing, development and QA testing work does this thing called "web accessibility" touch? Meaning, how much extra work will there be? Is it really necessary? Etc. I have dealt with these questions when training or assisting teams implement a culture or process for accessibility in large organizations. Shawn's suggestion of "Definition and scope of what web accessibility covers" is really clear but I understand could be awkward as a title. I would also like to keep 'scope' rather than change to 'range of web accessibility'. I will be on the call tomorrow and look forward to speaking about this in more depth! Jenn Jennifer Chadwick, CPACC, CUA Lead Accessibility Strategist and Product Expert, North America 110 Yonge Street, Suite 700 | Toronto, Ontario M5C 1T4 Direct +1 647 952 0364 | jcha@siteimprove.com Click here to opt out of receiving emails. Cliquez ici pour vous désabonner/désinscrire. -----Original Message----- From: Shawn Henry <shawn@w3.org> Sent: Thursday, August 15, 2019 1:01 PM To: Daniel Montalvo Charameli <dmontalvo@w3.org>; Jennifer Chadwick <jcha@siteimprove.com>; shadi+EOsurvey@w3.org; wai-eo-editors <wai-eo-editors@w3.org> Subject: "scope" - Re: [wbs] response to 'WAI-Curricula: Thorough Review for units 1 and 2' Just chiming in with my perspective. :) I just re-read the Teaching Ideas in that section. To me "Scope" is a good word to cover all of that. /me checks definitions of "scope" * the extent of the area or subject matter that something deals with ... and sees there's lots about "scope" in terms of project management -- and this heading is *not* using scope in that sense -- it's not "scope of work..." it's "Scope of [what] Web Accessibility [encompasses]" brainstorming ideas... maybe "Range of Web Accessibility" ... that doesn't seem as good as "Scope" to me. > "Accessibility in context" I'd mildly prefer *not* to use that phrase other than for this meaning: https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2FWAI%2Ffundamentals%2Faccessibility-intro%2F%23context&data=02%7C01%7Cjcha%40siteimprove.com%7Cab84614732854b7bcae808d721a23273%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C1%7C0%7C637014852831887174&sdata=vgVQGbrWUNVVbvZKaniavskiU42JUR28b1d9uoTvvbo%3D&reserved=0 > Could the word "scope" be clarified I tried ideas for clarifying it in: "Introduce the definition and scope of web accessibility." with something like: "Introduce the definition and scope of web accessibility, that is, the range of what is covered by "web accessibility". or "Introduce the definition and scope of what web accessibility covers." "Introduce the definition and scope of what web accessibility addresses." but those are awkward or don't work grammatically. --- Jenn, > Could the word "scope" be clarified for those who are new to this and are responsible for defining and managing the scope within projects? I assume it isthe scope of work - around implementing digital accessibility? Firstly there is the definition of what accessibility is, and then the scope of work, technology, budget, or experience around accessibility is defined as well? As I understand it, that is not the way this is using "scope". So maybe it's OK as it? Or you have other ideas for making it clearer? Anyway hope above helps y'all with ideas. :-) Best, ~Shawn On 8/15/2019 11:01 AM, Daniel Montalvo Charameli wrote: > Hi Jenn: > > > Thanks for your feedback. > > > I have some followups for you. > > > Could the word "scope" be clarified for those who are new to this and are responsible for defining and managing the scope within projects? I assume it isthe scope of work - around implementing digital accessibility? Firstly there is the definition of what accessibility is, and then the scope of work, technology, budget, or experience around accessibility is defined as well? > > In this topic, the scope would be what accessibility comprises, what it is, and what the boundaries would be with respect to other disciplines such as usability and inclusion. This word might be misunderstood. Maybe "Accessibility in context" or something like this could help clarify? > > > ----------- > > > It might make sense to break this topic out into two separate topics: Components of Web Accessibility and Web Accessibility and Assistive Technologies, firstly the components of web accessibility (browsers, authoring tools and how these are compatible with assistive technologies) and secondly, maybe an exploration of each assistive technology as it relates to the needs of different abilities and the barriers caused when a web page is not made compatible. > > The latter would then speak to the learning outcomes listed below: "Learners should be able to demonstrate what they have learned from exploring assistive tools and adaptive strategies, such as explaining different settings they found in their web browser" and "Note: Emphasize how accessibility is about enhancing the ability of people to use technology." > > > I tried to approach these ideas in the previous topic, Diverse > Abilities, Tools, and Barriers. I know it is a huge topic in itself > but we tried not to emphasize in any singular topic excessively. that > is, I tried having separate topics for features and barriers, I also > tried to have a topic for the types of disabilities... and these > approaches led to a pretty medical picture, which we are trying to > avoid. We could discuss about this on the phone if you feel strongly > about it, anyway > > > Best. > > > Daniel. > > > On 8/13/2019 5:54 PM, Jennifer Chadwick via WBS Mailer wrote: >> The following answers have been successfully submitted to 'WAI-Curricula: >> Thorough Review for units 1 and 2' (Education and Outreach Working >> Group) for Jennifer Chadwick. >> >>> --------------------------------- >>> Overview >>> >>> ---- >>> Please read the complete drafts for Unit 1 and Unit 2. These are now >>> ready for thorough review. >>> Background: — To prepare for this questionnaire, you might want to >>> have a look at the following: >>> * The WAI-Curricula Requirements Analysis page >>> * July 12th minutes on WAI-Curricula Thorough review! — Review >>> everything at all levels, including copy-editing. This is the "last >>> call" before publication. >>> Feel free to comment in the below edit boxes or to open a New GitHub >>> Issue >>> >>> Note: The review versions linked above will not change during the >>> review period. Daniel will address some issues as they come in, so >>> the live draft might change during this review period. You might >>> want to check GitHub issues and the live updates before doing your >>> review: Live draft - Unit 1 and Live draft - Unit 2. >>> >> Comments: >> Unit 1: >> >> Should the second title be "Competencies"? >> >> Under Instructors, it seems obvious but could be stated that people >> with disabilities also regularly work as instructors and teachers, >> and to encourage people to hire instructor talent from within these >> communities (if that makes sense). However, having lived experience >> in one area doesn't make you an expert on other disabilities. I may >> be overly sensitive to the term "bring in" but it sounds a bit like >> show and tell and prefer the term "Invite". >> >> Under Topics to Teach could the word "scope" be clarified; I assume >> it is the scope of work - around implementing digital accessibility? >> Firstly there is the definition of what accessibility is, and then >> the scope of work, technology, budget, or experience around >> accessibility is defined as well? >> >> It may be too early in the learning process, but also as a learning >> outcome it would be nice for learners to understand how each person >> currently contributing to technology, to web content and those that >> define the user experience - UX and graphic designers, developers, >> content writers, quality assurance and regression testers - plays a >> role and contributes to web accessibility. >> >>> --------------------------------- >>> Review level and timing >>> >>> ---- >>> Please indicate below the level of consideration you were able to >>> provide for this review. If you were unable to get to it and would >>> like more time, please indicate that as well. Thanks! >>> >>> >> * (x) I read the material carefully . >> * ( ) I skimmed the material >> >> * ( ) I need more time and have put a date below when I can get to it. >> * ( ) I am not going to be able to review this material and will >> defer to the decisions of the group. >> >> >> >>> --------------------------------- >>> Unit 1: What is Web Accessibility >>> >>> ---- >>> Focus on unit 1 What is Web Accessibility: >>> * Do you agree with the introduction, learning outcomes, and >>> competences? >>> * Do you think Learning Outcomes and Ideas for Assessment are >>> coherent and feasible? >>> * Do you agree with the wording, tone, and approach? >>> * Do you have other thoughts, suggestions, or comments? >>> Please feel free to comment in the below text box or open a >>> dedicated GitHub Issue for Unit 1 >>> >> Comments: >> Should the second title be "Competencies"? >> >> Under Instructors, it seems obvious but could be stated that people >> with disabilities also regularly work as instructors and teachers, >> and to encourage people to hire instructor talent from within these >> communities (if that makes sense). However, having lived experience >> in one area doesn't make you an expert on other disabilities. I may >> be overly sensitive to the term "bring in" but it sounds a bit like >> show and tell and prefer the term "Invite". >> >> >>> --------------------------------- >>> Topic: Stories of people with Disabilities >>> >>> ---- >>> Focus on topic Stories of People with Disabilities: >>> * Do you agree with the introduction and learning outcomes? >>> * Do you think Learning Outcomes, Teaching Ideas, and Homework >>> Ideas are aligned? >>> * Do you think Teaching Ideas and Homework Ideas cover well the >>> scope of this topic? >>> * Do you agree with the wording, tone, and approach? >>> * Do you have further ideas or suggestions? >>> Please feel free to comment in the below text box or open a >>> dedicated GitHub Issue for Topic Stories of People with Disabilities >>> >> Comments: >> It may be too early in the learning process, but also as a learning >> outcome it would be nice for learners to understand how each person >> currently contributing to technology, to web content and those that >> define the user experience - UX and graphic designers, developers, >> content writers, quality assurance and regression testers - plays a >> role and contributes to web accessibility. >> >>> --------------------------------- >>> Topic: Scope of Web Accessibility >>> >>> ---- >>> Focus on topic Scope of Web Accessibility: >>> * Do you agree with the introduction and learning outcomes? >>> * Do you think Learning Outcomes, Teaching Ideas, and Homework >>> Ideas are aligned? >>> * Do you think Teaching Ideas and Homework Ideas cover well the >>> scope of this topic? >>> * Do you agree with the wording, tone, and approach? >>> * Do you have further ideas or suggestions? >>> Please feel free to comment in the below text box or open a >>> dedicated GitHub Issue for Topic Scope of Web Accessibility >>> >>> >> Comments: >> Could the word "scope" be clarified for those who are new to this and >> are responsible for defining and managing the scope within projects? >> I assume it is the scope of work - around implementing digital accessibility? >> Firstly there is the definition of what accessibility is, and then >> the scope of work, technology, budget, or experience around >> accessibility is defined as well? >> >> >> >> >>> --------------------------------- >>> Unit 2: People and Digital Technology >>> >>> ---- >>> Focus on unit 2 People and Digital Technology: >>> * Do you agree with the introduction, learning outcomes, and >>> competences? >>> * Do you think Learning Outcomes and Ideas for Assessment are >>> coherent and feasible? >>> * Do you agree with the wording, tone, and approach? >>> * Do you have other thoughts, suggestions, or comments? >>> Please feel free to comment in the below text box or open a >>> dedicated >>> >> Comments: >> The terms "web accessibility" and "digital technology" are being used >> interchangeably. I understand that web a11y is part of digital >> technology and also that digital technology also includes software that is used in >> conjunction with the web, websites and mobile application. In the >> learning outcomes, could this be addressed? "Learners should be able to: >> >>> --------------------------------- >>> Topic: Diverse Abilities, Tools, and Strategies >>> >>> ---- >>> Focus on topic Diverse Abilities, Tools, and Strategies: >>> * Do you agree with the introduction and learning outcomes? >>> * Do you think Learning Outcomes, Teaching Ideas, and Homework >>> Ideas are aligned? >>> * Do you think Teaching Ideas and Homework Ideas cover well the >>> scope of this topic? >>> * Do you agree with the wording, tone, and approach? >>> * Do you have further ideas or suggestions? >>> Please feel free to comment in the below text box or open a >>> dedicated GitHub Issue for Topic Diverse Abilities, Tools, and >>> Barriers >>> >>> >> Comments: >> >> >>> --------------------------------- >>> Topic: Components of Web Accessibility >>> >>> ---- >>> Focus on topic Components of Web Accessibility: >>> * Do you agree with the introduction and learning outcomes? >>> * Do you think Learning Outcomes, Teaching Ideas, and Homework >>> Ideas are aligned? >>> * Do you think Teaching Ideas and Homework Ideas cover well the >>> scope of this topic? >>> * Do you agree with the wording, tone, and approach? >>> * Do you have further ideas or suggestions? >>> Please feel free to comment in the below text box or open a >>> dedicated GitHub Issue for Topic Components of Web Accessibility >>> >> Comments: >> It might make sense to break this topic out into two separate topics: >> Components of Web Accessibility and Web Accessibility and Assistive >> Technologies, firstly the components of web accessibility (browsers, >> authoring tools and how these are compatible with assistive >> technologies) and secondly, maybe an exploration of each assistive >> technology as it relates to the needs of different abilities and the >> barriers caused when a web page is not made compatible. >> >> The latter would then speak to the learning outcomes listed below: >> "Learners should be able to demonstrate what they have learned from >> exploring assistive tools and adaptive strategies, such as explaining >> different settings they found in their web browser" and "Note: >> Emphasize how accessibility is about enhancing the ability of people >> to use technology." >> >> For me, the connection to people - i.e. that digital or web >> accessibility is all about ensuring a person's user experience is >> included, is not problematic technically or otherwise and is designed >> for, within scope of every project, new build, release and ongoing >> design and development of a website, i.e. is included and valid as >> any design that is currently approved - is the most important takeway for me in this section. >> >> Accessibility is not accommodation, or we should be moving away from >> accommodating on top of an existing design. Inclusive design is a >> singular design wherever possible that works for the majority of >> people, and tweaks and accommodations can be added. The norm is inclusive design. >> >> >>> --------------------------------- >>> Any other Thoughts/suggestions? >>> >>> ---- >>> Any other thoughts or suggestions? >>> >>> >> Comments: >> These are excellent sections and currently I rely on the existing >> resources that are linked here (How people with disabilities use the web). >> >>> These answers were last modified on 13 August 2019 at 15:53:55 U.T.C. >>> by Jennifer Chadwick >>> >> Answers to this questionnaire can be set and changed at >> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.w3.org%2F2002%2F09%2Fwbs%2F35532%2Funit12cr%2F&data=02%7C01%7Cjcha%40siteimprove.com%7Cab84614732854b7bcae808d721a23273%7Cad30e5bc301d40dba10a0e8d40abe0f9%7C1%7C0%7C637014852831887174&sdata=%2Fd5gsNoSQB4wHmdRqZu4ErT10yxDvgaKRMr7ez52%2BOw%3D&reserved=0 until 2019-08-13. >> >> Regards, >> >> The Automatic WBS Mailer >>
Received on Thursday, 15 August 2019 18:27:30 UTC