12:28:27 RRSAgent has joined #eo 12:28:27 logging to http://www.w3.org/2010/09/24-eo-irc 12:28:56 kate has joined #eo 12:29:20 zakim, this will be eowg 12:29:20 ok, Andrew, I see WAI_EOWG()8:30AM already started 12:29:31 rrsagent, make logs public 12:29:38 Meeting: EOWG 12:29:42 +??P5 12:29:46 Chair: Shawn 12:30:00 +Shawn 12:30:03 zakim, who is here? 12:30:03 On the phone I see doyle, Sharron, ??P5, Shawn 12:30:04 On IRC I see kate, RRSAgent, Zakim, Sharron, Andrew, yeliz, shawn 12:30:08 shadi has joined #eo 12:30:23 zakim, call shadi-617 12:30:23 ok, shadi; the call is being made 12:30:25 +Shadi 12:30:42 zakim, mute me 12:30:42 Shadi should now be muted 12:31:13 zakim, call andrew-office 12:31:13 ok, Andrew; the call is being made 12:31:15 +Andrew 12:31:22 zakim, ??P5 is Kate 12:31:22 +Kate; got it 12:31:41 +Jennifer 12:33:00 zakim, who is here? 12:33:00 On the phone I see doyle, Sharron, Kate, Shawn, Shadi (muted), Andrew, Jennifer 12:33:02 On IRC I see shadi, kate, RRSAgent, Zakim, Sharron, Andrew, yeliz, shawn 12:33:03 +??P9 12:33:09 zakim, ??P9 is yeliz 12:33:09 +yeliz; got it 12:33:21 zakim, mute yeliz 12:33:21 yeliz should now be muted 12:34:20 ack me 12:34:33 zakim, mute me 12:34:33 Shadi should now be muted 12:34:50 +Ian 12:35:21 zakim, unmute yeliz 12:35:21 yeliz should no longer be muted 12:35:45 zakim, mute yeliz 12:35:45 yeliz should now be muted 12:37:06 topic: Developing Websites for Older People 12:37:44 60# unmute 12:38:31 scribe: Sharron 12:39:17 http://www.w3.org/WAI/older-users/developing#captcha 12:39:40 Shawn: Comments in the survey were mostly editorial, have been done except for the CAPTCHA techniques, which we will discuss 12:40:09 ack me 12:40:47 Shawn: Ian pointed out that having the callin option at the top of the list made him uncomfortable, and I agree. Rarely are they 24 hour staffed... 12:41:02 Jennifer: or staffed at all 12:41:33 Andrew: another comment was that people with multiple impairments can not use any of the alternatives 12:41:34 sylvie has joined #eo 12:41:42 +Sylvie 12:41:55 zakim, mute me 12:41:55 Shadi should now be muted 12:42:05 Shadi: and it is easier, in his opinion to use that option. It may work for large orgs, but in my opinion not for all organziations 12:42:45 zakim, mute sylvie 12:42:45 Sylvie should now be muted 12:42:46 Present: Doyle, Sharron, Kate, Shawn, Shadi, Andrew, Jennifer, Sylvie 12:43:02 Ian: This should not be a first solution. You should do everything possible to make your site accessible first before forcing people to seek a solution that is not Internet based. This is a last resort. 12:43:12 Shawn: Any other aspects to discuss? 12:43:24 Ian: would like to know the opinion of others 12:44:15 Doyle: I agree and would add that it is like providing text only rather than actually addressing the issues on your site. The possibility of getting in tyouch with a live person might be a nice thing, but should not be considered and accessibility option. 12:44:23 Sharron: I agree 12:45:06 I agree with Ian and Sharron 12:45:47 Shawn: You should absolutely do the other techniques. Since some people would be more comfortable picking up the phone. 12:46:11 ...so it is a good enhancement, no reason to exclude it, but offer it as just one option. 12:46:32 Andrew: I put it back in the middle, sort of burries it, demphasizes it. 12:46:34 I also like it's current location 12:46:44 Shawn: Yes I noticed and think that is a good solution. 12:46:46 sinarmaya has joined #eo 12:47:37 ...Next point is to review comments, thanks to everyone who replied in email. Any concerns with draft reply? 12:47:45 Jennifer: No concerns 12:47:52 Sharron: no concerns 12:48:05 :) 12:48:40 ack me 12:48:52 Jennifer: We have looked at two comments, in one of the drafts, Shadi's name was spelled wrong. You may want to check that. 12:48:56 zakim, mute me 12:48:56 Shadi should now be muted 12:49:30 ACTION: Andrew to check signature line for spelling 12:50:48 Shawn: Confirm the plan to publish. We wil post to the final URI and point to it. But will wait to announce it until after we refine and reintegrate expand/collapse function. 12:51:12 completed doc - http://www.w3.org/WAI/older-users/developing 12:51:40 ...high on our priority list is to address the problems we have had with it after 4 years. 12:52:13 ...remove the word DRAFT and put it where it will be. After we fix the expand/collapse, we will announce. How does that sound? 12:52:17 All: Fine 12:52:32 ack me 12:52:48 Topic: How People with Disabilities Use the Web 12:53:29 Shawn: Last week we addressed the comments related to sign language use. Shadi has now drafted proposed updates to those sections based on comments. Shadi? 12:54:09 http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/scenarios#onlinestudent 12:54:11 -> http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/scenarios#onlinestudent Scenario 3: Online student who is hard of hearing 12:54:12 Shadi: Comments are linked from the agenda. Debate within our group that relate to needs of deaf and hard of hearing community 12:55:10 zakim, who is making noise? 12:55:14 ...We have two scenarios relating to deafness, also number 8. But we will focus onScenario 3 - 12:55:22 shawn, listening for 11 seconds I heard sound from the following: Kate (8%) 12:56:05 ...one of the disconnects was that it failed to resonate with the public and caused some reactions from advocates. Has been toned down as a result. 12:58:00 Shadi: Removed: {Her preferred form of communication is sign language which she uses whenever she can.} Added:[She can hear some sounds but not enough to understand all spoken words.] 12:58:19 zakim, unmute sylvie 12:58:19 Sylvie should no longer be muted 12:58:19 Ok with me as well 12:58:21 Shawn: How does this cahnge work for everyone? 12:58:27 Doyle: OK 12:58:31 Jennifer: OK 12:59:03 Shawn: You will have more time to review 12:59:28 Sylvie: For me now it is no longer clear if the person is using sign language or not. 12:59:48 ...I would think "what does she need, really" 13:00:16 Shawn: I wonder if you just say "most speech" rather than some sounds 13:00:45 ...she is comfortable or her native language is sign language 13:01:38 Shawn: If sign language is in the scenario at all, it should be mentioned as her native language or her familiarity with it. 13:02:30 Shadi: There are many reasons to include a reference to sign language - it is something people really do use. Second mentioning it makes the association of accomodation in the real world and how it relates to online accomodation. 13:02:48 ...is anyone uncomfortable with keeping the reference to sign language. 13:02:53 All: No 13:03:19 q+ to mention written language 13:03:31 Shadi: OK that's good to know. Then we can reference her comfort with Sign and the fact that she has known it since use. 13:03:36 ack me 13:03:36 Andrew, you wanted to mention written language 13:03:42 ACTION: Shadi to extend sentence about Sign 13:04:19 Andrew: In conjunction with her familiarity with sign, make the distinction that the written language is not a problem for her. 13:04:29 action: shadi - scenario 3 - explain that Ms.Martinez knows and uses both written and sign language 13:04:45 Shawn: is fluent in both. Is a positive perspective. 13:05:28 action: shadi - scenario 3 - Ms.Martinez is fluent in both written language and sign language 13:05:39 -. http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/disabilities#deafness Deafness 13:05:53 s/-./->/ 13:06:19 zakim, mute me 13:06:19 Sylvie should now be muted 13:07:09 Shadi: Next bullet called Deafness. Will have an introductory paragraph that may remove some of the pointy-ness. Here tried to remove the prominence of the reference to written language. 13:07:41 ...Removed [For some people, sign language is the first language and they may or may not read a written language fluently, or speak clearly. They may therefore require simpler language that is supplemented by images, graphs, and other illustrations to make the written language more understandable.] 13:08:05 ...Added {Some may also rely on simpler language that is supplemented by images, graphs, and other illustrations to highlight the context. Some prefer sign language as an alternative to text or audio. However, not all people who are deaf know sign language.} 13:09:00 Shadi: What are you comments or thoughts about this? 13:09:47 Doyle: Seems OK. Last night I was speaking with a native Sign speaker. The Deaf culture doe not see itself as disabled. This captures that pretty good. 13:10:49 Andrew: Maybe a bit more of a qualifier here. Many deaf people read written language well, BUT sign is often the first language 13:11:00 Shadi: Need to be so defensive? 13:11:12 Andrew: don't know, raising it for consideration 13:11:19 Doyle: Doesn't hurt 13:11:31 Shadi: OK, other thoughts? 13:11:48 Shawn: Most people who are deaf are fluent in written language. Is that true? 13:11:55 Shadi: Not sure 13:12:14 Doyle: Many people become deaf over time, it could easily be true. 13:12:23 Shadi: Yes, numbers get tricky 13:13:00 ...could try something like hmmm, have to look for stats. 13:13:24 Shawn: Editor's discretion to see if it can be done smoothly? 13:13:30 [[While most people with deafness are fluent in written language, for some people sign language is their primary language.]] 13:14:57 -Ian 13:15:27 action: shadi - deafness - consider re-emphasizing the fluency in written language for most/many people who are deaf 13:16:21 Shadi: Move along to hard of hearing in next section. 13:17:01 -> http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/disabilities#hardofhearing hard of hearing 13:17:04 ...Removed: {To use the Web, people who are hard of hearing may rely on amplification of volume, transcripts, or captions for audio content. They may also rely on media players that display captions provided for audio content, on options to turn off any background audio, and on options to adjust the volume of the foreground audio. Some people who are heard of hearing may use sign language as the primary form of communication.} 13:17:26 ...Added: [To use the Web, people who are hard of hearing increase the volume to better hear audio content or use transcripts and captions to read the information. They rely on media players that display captions provided for audio content, provide options to turn off any background audio, and options to adjust the volume of the foreground audio. Some people who are heard of hearing use sign language as a form of communication.] 13:17:30 I am OK with this change 13:17:33 +Ian 13:18:18 Shadi: In barriers as well, the references to written language have been removed as well so that there re fewer of those. 13:18:22 ==== ROUGH IDEA for http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/disabilities#deafness: Many people who are deaf are fluent in written langauge and rely on transcripts or captions for audio content, and on media players that display the captions. Sign language is the first language of some people and some are not very fluent in written language and need simpler language that is supplemented by images, graphs, and other illustrations to make the written language 13:18:27 ...any comments here? 13:18:59 I suggest: ... Some people who are heard of hearing use sign language as their primary form of communication. 13:19:40 Shadi: Emmanuel advocating for reference to Sign 13:20:14 ...do you have more about your reasons/ 13:20:23 but not in the last paragraph :-) 13:20:38 my comment was about the previous paragraph 13:21:48 Shawn: Commenting on the change from "primary" to "a" form of communication 13:22:05 Shawn: I wondered too why you took that out. 13:22:45 Shadi: for some it is not primary, for some it is a known language but not fluent, and some don't know it all 13:22:52 because for they is not only a form or don't have the same value as the others forms 13:23:08 Shawn: Oh yes, we are in hard of hearing, not deafness. Then is it important to have it at all? 13:23:17 Yes, I agree, is not equal for all 13:23:56 Shadi: Yes, it depends on the level of hearing loss. It is true that sign language speakers are not only deaf people. It is fairly common for hard of hearing to use sign. Should mention 13:24:00 Shawn: why? 13:24:46 Yes, and in the example said that she are hard of hearing from the childhood, so probably the sign language is very important for she. 13:25:11 I think that this is an exterme example of hard of hearing ;-) 13:25:24 ...I ahve no idea where the differentiations are between hard of hearing and where it is that the lines of demarcation are made. So since we have just looked at deafness not sure why we need to reemphasize. 13:25:33 ...maybe include and make it shorter. 13:26:10 Shadi: The difference between visual and auditory disabilities are cultural. Other factors come in , not just the level of hearing. 13:27:19 cultural and legal. Can be different in each country. 13:28:03 http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/browsing#sign 13:28:06 Shadi: Let's quickly go through next two placeholder sections. Not much to review as yet. 13:28:39 [[the elderly mother of a freind of mine in Canada is effectively deaf and has always been, but didn't have the opportunity to learn sign language in rural Canad when she was achild - she is expert at lip reading]] 13:28:50 ...I updated what the section will contain. Will explain what sign language is, who uses it, who does not and the exisitance and limitations of Sign language avatars. 13:29:27 Shadi: Need anything else? 13:29:49 Shawn: Maybe that there are different sign languages just as there are different spoken language 13:30:02 Maybe that in some countries there are a standard about how make sign language videos for the web. As in Spain ;-) 13:30:21 Doyle: Yes and that syntactically Sign is quite distinct from written and spoken languages 13:30:32 action: shadi - sign language - mention that sign languages are different from country to country (ASL, BSL, ...); also that it is significantly different from written language (grammar) 13:30:43 Shadi: good, anything else? 13:31:08 [and that even in english speaking countries, the sign language is different between countries] 13:31:08 http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/browsing#captions 13:31:25 ...now to the 4th , captions and transcripts 13:32:10 Shadi: One of the issues is that Captions and Transcripts is the subject line, does not include CART becasue it is a method to provide captions. 13:32:24 Shawn: For live broadcasts, right? 13:32:32 Andrew: any live envet 13:32:53 ...as a technique for providing captions, it does not need to be in the heading 13:33:19 [ for editor - shadi: explanation of CART (that was vetted with this same commenter): http://www.w3.org/WAI/training/accessible.php#cart ] 13:33:35 zakim, mute me 13:33:35 Shadi should now be muted 13:33:38 Shadi: Disabilities and barriers page will be changed and we will talk more about it next week. 13:34:00 Shawn: Any other questions or comments about this? 13:34:10 ...Ok then next topic 13:34:29 Topic: Usability/Accessibility Document 13:35:18 Shawn: Shadi too a significant pass at how to approach and frame this topic. Still in rough draft stage. need your feedback, not at the wordsmithing area, but more general. Right approach? 13:35:35 s/too a/took a/ 13:35:56 :) 13:36:11 http://www.w3.org/WAI/EO/changelogs/cl-accessibility-n-usability#why 13:36:13 ...first section is Goals, Objectives 13:36:43 Andrew: reads four bullet points 13:37:40 Shawn: Overall comments about purpose and goals? Notice that primary audience includes policy people, researchers, students, etc 13:38:06 ...secondary audience is developers, etc. So keep in mind we are targeting a very different primary audience 13:39:35 ack me 13:40:18 zakim, mute me 13:40:18 Shadi should now be muted 13:41:04 ack me 13:41:12 Shawn: We are likely to spend most of the rest of this meeting on this document as I will be away next week. let's go through the scenarios. Shadi can you point our highlights and let's discuss? 13:42:57 Shadi: Scenario 1 is a situation that spawned this document. Researchers working with older people who make general recommendations that mix up accessibility and usability but fail to relate to exisitng standards. Results in fragmentation and researchers lack some web specific knowledge about accessibility support, relationships between user agents and web technologies, etc 13:43:50 ...results tend to be limited. Initially good work and observations but lack the cross references that would make it more useful an allow for the research to contribute. 13:43:59 zakim, mute me 13:43:59 Shadi should now be muted 13:44:04 Shawn: Comments? 13:44:59 Doyle: I would agree that it is important. The research does not include mush that has already been done. How to think about adancing the field. 13:45:43 ack me 13:45:51 s/adancing/advancing 13:46:00 Sharron: how get this information to people?! outreach 13:47:01 :) 13:47:38 zakim, mute me 13:47:38 Shadi should now be muted 13:47:42 ack me 13:47:46 Shadi: As we think about the target audience. Maybe to get to other researchers is through advocates, other researchers, etc. Is this our immediate target audience or our end user audience? 13:48:06 zakim, mute me 13:48:06 Shadi should now be muted 13:48:14 ...are we addressing it as speaking directly to the research community or by way of others. 13:48:24 I think both are important 13:49:02 Shawn: We have been focussing on finishing up the WAI-AGE documents but then will be refocusing EO priorities with this whole group of new resources. 13:49:47 ...Better Web Browsing, overlap with aging documents, How to report...etc. So outreach will come. 13:49:50 -Jennifer 13:50:02 ack me 13:52:08 Shadi: Let's look at scenario 2. A longer standing issue. Researchers in accessibility field tend to look at it through the lens of conformance. Excellent work by researchers, but the conclusions often fail to recognize aspects of usability. Auto-testing, sites that claim conformance demonstrate a gap in actual accessibility. 13:53:04 ...technically accessible because it conforms to WCAG (most research still is WCAG1) but not actually usable by people with disabilities. 13:53:48 ...need to use the framework of WCAG2 to examine the tension between technical accessiblity vs real accessibility 13:54:12 Doyle: Isn't it odd that these research projects occur in such isolation? 13:55:07 +Jennifer 13:57:18 ...this is an important topic and low hanging fruit. It is a next step for researchers to connect the work that exists. An easy and important step. 13:58:17 Shadi: There is also some sensitivity between research community and industry. Want to be positive about work that has been done and be encouraging about connecting these fields. 13:59:05 Shadi: Scenario 3 has an A & B part. Addresses the complexity of the standards documents 13:59:45 ...want to be candid about recognizing that but also suggest that people not jump right into standards with no background. 14:00:40 ...expalin that we are working on improving entries to the documents so that there are steps to take people into the technical documents. 14:00:55 Doyle: Where will this point to for the basic? 14:01:22 Shadi: Good question...probably to Involving Users, How People.., a few other resources 14:01:41 Shawn: Comments or questions? How does this seem to fit? 14:03:01 Doyle: not well 14:03:09 Sharron: I think it fits well. 14:04:04 Shawn: Anyone who has seen my talks, knows that I encourage people to look first at introductory documents. 14:04:23 ...but not sure it fits as a scenario. Not a primary theme. 14:04:59 I think that an introductory document don't feet the needs of a developer new in this field. Maybe the "Undersanding wcag 2.0 " can be more useful 14:05:07 Andrew: To address scenario 1 and scenario 2 we can encourage them to start with the right material. 14:05:42 Shawn: We need to define: Is this a step-by-step how to do things better? or is it a philisophical document? 14:05:59 and for the researchers, a document about how review accessibility. 14:06:29 Jeneifer: You are getting at the heart of the question. When I read this, it seemed very much like a philisophical document. I don't have a preference, but it is a decision that needs to be made. 14:06:55 Shadi: Just to mention that this document doesn't need to be related with conformance. 14:07:05 ...it is a provisional title. 14:07:06 http://www.w3.org/WAI/WAI-AGE/deliverables.html#overlap 14:07:30 I am sorry, I have to leave the call, have a good week-end, bye 14:07:35 Shadi: it is wide open. 14:07:42 -Sylvie 14:08:02 Shawn: Good point. Maybe one of the things we should do is play with totally different title and approach. 14:09:24 Shadi: 3B is more the developer perspective and may be out of sync with the rest. I am torn between the perspectives of Doyle and Sharron 14:10:08 [[Marying Accessibility and Usability]] 14:10:11 Shawn: it may be fun to brainstorm titles and approach. Marrying Accessibility and Usability...something that says we should look at these together 14:10:26 [[Understanding how Accessibility Fits with Blah]] 14:11:33 Shadi: Scenario 4 relates to widgits and being able to customize web sites to accomodate preferences. Such as the BBC site where customization is possible for many different user needs. 14:11:55 Jennifer: Is this where the understanding of user agents comes in? 14:12:03 Ian: A bit of a mine field there 14:12:18 Shadi: It is not related with the conformance, but the escneario 2 talks about the confusion created when a site says a level of compliance and the results of automatic review. Therefore, for these people is important to know the right conditions for review of accessibility. ;-) 14:12:49 Shadi: Yes, the perspectives range from users whould make those changes on their own end to saying users may not have the technical expertise to customize from thier end. 14:13:48 ...so what is realistic to expect from users? Good arguments can be made on both sides. What conslusions or recommendations do we make? 14:14:05 Ian: Will we address the accessibility of the widgit controls themselves? 14:14:47 Shadi: Have not gotten that far. have just tried to lay out messages that are of interest. 14:16:43 Ian: BBC provides good instructions of how to work the widgits. It comes at a cost. 14:16:55 Shadi: Does this topic fit? 14:17:48 Ian: It feels slightly different than other topics. We would need to give concrete recommendations rather than it being philisophical. 14:18:16 Shawn: How it fits and how we approch it will depend on how we define the document. 14:19:01 Shadi: Scenario 5 is quite interesting in the combiniation of the interests of both researchers and developers. 14:19:56 ...provision of very targeted content, such as e-learning environments. User groups really need different type of approach that entails preparing content differently. 14:20:29 ...discussion of the one-size-fits-all concept and the myth that WCAG is proscribing that. 14:21:58 ...in fact WCAG not only supports but actively requires adaptive methods of presentation. WCAG can actually help you address various needs. 14:22:30 Ian: Has a great deal of crossover in supporting mobile, etc. 14:22:48 Shadi: yes 14:23:21 action: shadi - usability/accessibility changelog - scenario 5 - add "devices" to title 14:23:30 Shawn: Questions and myths to consider have not changed, but please feel free to add to those. 14:23:40 http://www.w3.org/WAI/EO/changelogs/cl-accessibility-n-usability#who 14:23:57 ...if no additions right now, let's go back to the audience. 14:25:34 Shadi: If the primary audience includes researchers and technical policy developers - the question is, do we have the right messaging in the scenarios? 14:26:14 About the audience: is "researcher" the best term in english? Is not better: "analyst"? 14:26:53 ...I think the point of orienting researchers to accessibility, we should think about the best ways to do that. 14:27:37 Shawn: We are trying to reach xyz document but know they are unlikely to come here. So we will empower advocates to reach xyz audience. 14:27:47 ...is that the situation here? 14:28:14 ...will researchers come to this document or are we trying to reach those people through another audience? 14:28:53 Jennifer: I was stuck by the same point. if they are unaware of this as an area of study, how will we get them here? 14:29:59 Shawn: Maybe we need to think early on is what is the outreach strategy to get the messages out and then how will the document facilitate the outreach? 14:30:49 ...keep the discuaaion in mind. We will bring this back in two weeks. The first full week of Oct we will take up this discussion again. will look at the next draft at that time. 14:32:06 ...next week, will discuss "How People..." We are now bringing pieces of the documents in for final sign off. Want to relook at requirements of WAI-AGE document. Focusing on key messaging and tilte, Andrew has reformmatted. 14:32:40 ...may have addiitonal work on that next week. The bulk of what's there is ready for review. Skim and we will let you know if we update. 14:32:54 Jennifer: Can we footnote the statisitics? 14:33:00 -Ian 14:33:00 Andrew: yep, working on that. 14:33:34 -Jennifer 14:33:42 -Shawn 14:33:42 Shawn: Great, will post what's ready for review early next week. Bye for now. 14:33:44 -doyle 14:33:52 -yeliz 14:33:56 -Andrew 14:33:58 -Shadi 14:34:17 shadi has left #eo 14:34:19 rrsagent, draft minutes 14:34:19 I have made the request to generate http://www.w3.org/2010/09/24-eo-minutes.html Sharron 14:34:22 sinarmaya has left #eo 14:34:30 -Sharron 14:35:48 -Kate 14:35:48 WAI_EOWG()8:30AM has ended 14:35:50 Attendees were doyle, Sharron, Shawn, Shadi, Andrew, Kate, Jennifer, yeliz, Ian, Sylvie 14:45:18 yeliz has left #eo 15:17:02 Andrew has left #eo 15:52:55 Zakim has left #eo