16:35:46 RRSAgent has joined #eo 16:35:46 logging to http://www.w3.org/2009/11/02-eo-irc 16:58:06 shawn has changed the topic to: if you want us to join the teleconference bridge, type andrew and shadi to get their attention to call in 17:02:33 andrew has joined #eo 17:04:47 Jack has joined #eo 17:06:32 shadi has joined #eo 17:06:41 Sharron has joined #eo 17:08:15 suzette has joined #eo 17:08:23 hello 17:12:09 http://www.w3.org/WAI/EO/2009/11f2f 17:14:06 hbj has joined #eo 17:15:21 Shawn: Provides background and explains intent of the document, how it expands on involving users in evaluation to involving users with disabilities in the entire web development process. 17:16:17 3.1 Description of Services and Deliverables 17:16:17 Vendors must provide a narrative statement of work describing services, knowledge and relevant experience, and approach for providing deliverables outlined in section 2.0 above. Vendors must confirm that they will perform the accessibility testing and document their findings using the Massachusetts Technology Accessibility Validation and Reporting Instrument and the Accessibility Compliance Validation Summary Report template found on the “Forms and Terms” tab in 17:16:17 The Knowbility team, led by accessibility author and expert Sharron Rush, will take the following steps to meet the requirements of this project: 17:16:20 1. Discovery/Review: Sharron Rush will confer with the Stellar Corporation development team to understand all development tools, techniques and processes and to understand the various user tasks and outputs that the application is expected to provide. She will ask for any data sets that may be needed to implement effective auto-testing. This will ensure an appropriate and comprehensive testing environment. 17:16:24 2. Assignment of tasks: Once an understanding of tasks and technology is established, Ms. Rush will finalize the testing protocols according to the Massachusetts Technology Accessibility Validation and Reporting Instrument and the Accessibility Compliance Validation Summary Report template. She will assign specific assessment tasks to the team which, depending on the results of the discovery process, may include herself, Jim Thatcher and/or Derek Featherstone. 17:16:31 3. Reporting: Knowbility reports include screen by screen assessment, a pass/fail status for each of the Massachusetts ITD Enterprise Web Accessibility Standards, and recommendations for how to repair the application if it does not currently pass any specific one of the standards. Remediation recommendations are provided to the code level and can then be integrated into the application by the Stellar development team. In addition, the report will include resul 17:16:36 4. Delivery: Knowbility prefers to deliver the report in a Question and Answer type meeting. Our team will present our findings, identifying any common barriers that were found and offering remediation techniques. We will answer any questions you may have and work with your team toward full understanding and problem solving. 17:16:40 5. Retesting: If accessibility barriers are discovered and the Stellar team implements remediation techniques, Knowbility will re-test and confirm compliance at no additional charge. 17:17:22 http://www.w3.org/WAI/EO/Drafts/involving/ 17:17:49 Shawn: Look at overview and specifc wording issues, titles 17:24:27 Action: Including Users - fix title 17:27:37 Discussion of audience, is document broad enough to appeal to identified group? 17:30:24 Action: Including Users - take editorial pass at broadening language to inlcude developers of applications, browsers etc. Then another pass to ensure that it message was not diluted 17:31:05 ACTION: Including Users - take an edit pass to make sure it applies to tool developers, stds developers, etc. - then make sure it's not watered down or for the website developer. if leave -- probably then put something clear up fron that this applies to these otehrs 17:33:35 Suzette: introduces discussion of formative vs summative methods. 17:34:43 shadi: Efficieny, effective ness, motivation not say clearly "understanding" 17:35:39 Helle: various perspectives should be considered even before story boarding, in procurement process. 17:36:15 ...even part of setting up business case, compliance requirements 17:36:22 qustion: is this when to involve considerations for accessibility, or, including real, live users in the process 17:37:19 Shawn: Is document about including considerations or including real live users? 17:39:39 Andrew: Some consideration of the needs of PWD in general is needed before user testing will be effective. 17:41:27 Action: Including Users - Clarify in scope that focus is real live users but point to references that say more about geenral consideration of accessibility earlier. 17:42:37 zakim, dial ponderosa 17:42:37 sorry, shawn, I don't know what conference this is 17:42:44 zakim, this is eowg 17:42:44 shawn, I see WAI_EOWG(TPAC)10:00AM in the schedule but not yet started. Perhaps you mean "this will be eowg". 17:42:54 zakim, will be eowg 17:42:54 I don't understand 'will be eowg', shawn 17:42:59 zakim, this will be eowg 17:42:59 ok, shawn; I see WAI_EOWG(TPAC)10:00AM scheduled to start 163 minutes ago 17:43:06 zakim, dial ponderosa 17:43:06 ok, shawn; the call is being made 17:43:07 WAI_EOWG(TPAC)10:00AM has now started 17:43:08 +Ponderosa 17:43:38 -Ponderosa 17:43:40 WAI_EOWG(TPAC)10:00AM has ended 17:43:40 Attendees were Ponderosa 17:44:14 zakim, drop ponderosa 17:44:14 sorry, shadi, I don't know what conference this is 17:45:38 WAI_EOWG(TPAC)10:00AM has now started 17:45:45 +Shawn_Henry 17:45:48 -Shawn_Henry 17:45:49 WAI_EOWG(TPAC)10:00AM has ended 17:45:49 Attendees were Shawn_Henry 17:46:44 WAI_EOWG(TPAC)10:00AM has now started 17:46:50 +doyle 17:48:20 zakim, dial Ponderosa 17:48:20 ok, shawn; the call is being made 17:48:21 +Ponderosa 17:49:24 zakim, drop ponderosa 17:49:25 Ponderosa is being disconnected 17:49:25 -Ponderosa 17:49:41 zakim, call sierra 17:49:41 ok, shadi; the call is being made 17:49:43 +Sierra 17:50:22 zakim, drop sierra 17:50:22 Sierra is being disconnected 17:50:23 -Sierra 17:50:54 -doyle 17:50:56 WAI_EOWG(TPAC)10:00AM has ended 17:50:57 Attendees were doyle, Ponderosa, Sierra 17:53:16 WAI_EOWG(TPAC)10:00AM has now started 17:53:23 + +34.62.717.aaaa 17:56:03 +Sharron 17:56:06 - +34.62.717.aaaa 17:56:08 + +34.62.717.aaaa 17:59:29 -Sharron 17:59:56 - +34.62.717.aaaa 17:59:57 WAI_EOWG(TPAC)10:00AM has ended 17:59:58 Attendees were +34.62.717.aaaa, Sharron 18:00:41 Jennifer: Numbred defintitions could perhaps address the need for glossary defintitions to be different depending on audience. 18:04:48 Shadi: Could reduce definitions to one - user characteristics. 18:05:54 from users' perspective, better to have on this page? 18:08:51 Shadi: Can you find a generalized definition that will satisfy all situations? 18:09:35 idea: WAI glossary becomes the user friendly version, then points to def in WCAg or recent std 18:15:42 q+ already pointing to 18:20:28 more definitions exist in http://www.w3.org/WAI/EO/Drafts/PWD-Use-Web/2009/#tools 18:22:36 ack me 18:22:46 Shawn: Suggestion now on the table is to make the WAI glossary the user friendly version rather than the defintive formal version, then pull defintitions as needed into printed pages or onscreen display. 18:23:24 ...add adaptive strategies, web content, assistive technology, user characterisitics. 18:24:13 Shadi: Formal definition would be WCAG and WAI would link to that or other recent fromal definittions 18:25:55 action: authorized translation policy - look at not saying have to translation "WAI Glossary" first 18:27:58 action: shawn - when glossary done, look at changing pointers to definitions in Involving Users to the glossary 18:31:03 Shawn: Group ready for section by section review? When we come back from break, will do that. 18:43:11 WAI_EOWG(TPAC)10:00AM has now started 18:43:12 +Shawn_Henry 18:50:37 glaser has joined #eo 18:52:31 -Shawn_Henry 18:52:33 WAI_EOWG(TPAC)10:00AM has ended 18:52:33 Attendees were Shawn_Henry 18:52:54 zakim, call Ponderosa 18:52:54 ok, andrew; the call is being made 18:52:55 WAI_EOWG(TPAC)10:00AM has now started 18:52:56 +Ponderosa 18:53:33 zakim, drop Ponderosa 18:53:33 Ponderosa is being disconnected 18:53:35 WAI_EOWG(TPAC)10:00AM has ended 18:53:36 Attendees were Ponderosa 18:54:21 ted has joined #eo 18:54:58 WAI_EOWG(TPAC)10:00AM has now started 18:55:05 +Shawn_Henry 18:56:14 +Jack 18:56:41 +Ponderosa 18:56:51 -Shawn_Henry 18:58:30 worky 18:58:34 thanks Ted! 18:58:39 -Jack 18:58:43 ted has left #eo 18:59:09 +Jack 18:59:37 -Jack 19:01:42 jenoe has joined #eo 19:04:33 Action: Including Users - start with Paragraph 2 19:05:52 Action: Including users - consider following with a list of applications, browsers, software, etc 19:08:15 Action: Including Users - delelete negative conotation of "However, most developers..." 19:09:12 Suzette: Need somewhere to emphasize develop of relationships, etc 19:09:23 q+ to revisit accomodation 19:09:34 q+ to revisit ethics (in Involvoing users) 19:14:07 Action: remove (or change) example 2 in How Involving Users Early Helps 19:16:16 positive examples 19:17:09 case studies to support "involving Users Early hepls" 19:29:07 "How Involving Users Early Helps" - maybe

s for Helps Developers Makes More (Usable) Accessible for pwds 19:29:34 (efficiency, effectiveness, motivation triggers usability terminology - not good) 19:29:54 maybe heading or at least focus is UNDERSTANDING 19:35:49 Action: Change heading titles to something like "benefits to developers" and "Benefits to end users" 19:35:52 shadi has joined #eo 19:37:03 Action: Including Users - after rewrite, consider update to examples 19:38:36 Action: Including Users - consider benefits to owner as well as developer and user 19:39:29 Sharron has joined #eo 19:45:05 andrew 19:47:18 Action: Including Users - change "Combine Users with Standards" to some thing like "How this relates to standards" 19:47:55 s/Including Users - change "Combine Users with Standards" to some thing like "How this relates to standards"/Including Users - change "Combine Users with Standards" to some thing like "How this relates to standards" - maybe leave Combine , e.b., Combine User Involvement.../ 19:49:28 Sharron has joined #eo 19:52:29 achuter has joined #eo 19:55:31 we wave back 19:55:49 telecon is working. we'll be online for about 20 mins give ro take - the breaking for lucnh... 20:07:57 +cmsmcq 20:08:14 zakim. cmsmcq is michael 20:08:36 zakim, cmsmcq is michael 20:08:36 +michael; got it 20:12:13 zakim, mute me 20:12:13 sorry, jenoe, I do not know which phone connection belongs to you 20:12:43 zakim, mute Michael 20:12:43 michael should now be muted 20:17:44 -michael 20:17:50 WAI_EOWG(TPAC)10:00AM has ended 20:17:51 Attendees were Shawn_Henry, Jack, Ponderosa, michael 20:20:14 shawn has changed the topic to: Will resume teleconference around 1:00 US Pacific time 20:32:44 Sharron has joined #eo 20:52:44 Sharron has joined #eo 21:12:48 Sharron has joined #eo 21:18:48 WAI_EOWG(TPAC)10:00AM has now started 21:18:57 + +34.62.717.aaaa 21:19:47 - +34.62.717.aaaa 21:19:48 WAI_EOWG(TPAC)10:00AM has ended 21:19:48 Attendees were +34.62.717.aaaa 21:28:24 Sharron has joined #eo 21:31:03 shadi has joined #eo 21:32:07 shawn-lunch has joined #eo 21:33:52 zakim, dial Ponderosa 21:33:52 ok, shawn-lunch; the call is being made 21:33:53 WAI_EOWG(TPAC)10:00AM has now started 21:33:55 +Ponderosa 21:34:11 zakim, who is here? 21:34:11 On the phone I see Ponderosa 21:34:12 On IRC I see shawn-lunch, shadi, Sharron, jenoe, hbj, Jack, andrew, RRSAgent, Zakim 21:36:09 + +34.62.717.aaaa 21:36:11 -Ponderosa 21:36:12 +Ponderosa 21:36:46 zakim, aaaa is really William 21:36:46 +William; got it 21:38:08 suzette has joined #eo 21:38:59 +michael 21:39:58 we're here: http://www.w3.org/WAI/EO/Drafts/involving/#diverse 21:40:01 zakim, jenoe is really Michael 21:40:01 sorry, andrew, I do not recognize a party named 'jenoe' 21:40:59 zakim, mute michael 21:40:59 michael should now be muted 21:41:01 glaser has joined #eo 21:47:41 q+ to look at open issues list 21:50:28 zakim, umute me 21:50:28 I don't understand 'umute me', jenoe 21:50:38 zakim, umute michael 21:50:38 I don't understand 'umute michael', jenoe 21:50:49 zakim, unmute michael 21:50:49 michael should no longer be muted 21:52:27 zakim, mute michael 21:52:27 michael should now be muted 21:58:13 jennifer: also, don't want to make it look to hard, have to fgo the ir house etc. 21:58:43 Andrew: interacting with PWD and older people - their place may be better; AT setup; 2 older people might be better than one - maybe link to another resource where this info exists 21:58:46 q+ to say can we delete anything 22:00:45 goodnight michael - might se you tomorrow? 22:01:14 maybe in the early mornin 22:01:18 maybe in the early morning 22:01:58 -michael 22:03:31 Sharron has joined #eo 22:08:23 put things in one doc and popint to it in the other 22:10:19 ACTION: Involving Users - you can do a lot yourself, but sometimes you might need to bring in help 22:11:41 suzette has joined #eo 22:12:08 jenoe has left #eo 22:13:09 zakim, who is here? 22:13:09 On the phone I see Ponderosa, William 22:13:11 On IRC I see suzette, glaser, shawn, shadi, hbj, Jack, andrew, RRSAgent, Zakim 22:13:13 -William 22:13:14 zakim, drop william 22:13:14 sorry, shawn, I do not see a party named 'william' 22:16:13 hbj has joined #eo 22:16:36 ACTION: Involving Usres - moVe "analyzing Accessibility Issues" from one doc to to other (to eval one) 22:19:20 ack shawn 22:19:20 shawn, you wanted to look at open issues list and to say can we delete anything 22:20:32 accomodation - think have covered 22:21:39 Sharron has joined #eo 22:21:58 Sharron has left #eo 22:22:15 Sharron has joined #eo 22:22:59 ethics - e.g., can withdrawl 22:24:49 Action: Suzette to draft brief statement about ethics 22:25:25 Action: Involving Users - draft pointers for ethics 22:26:20 action: involving - andrew to research some pointers on ethics and working with users (to be used with Suzette's #17) 22:34:37 diverse abilities 22:35:45 special requirements 22:38:54 Action: Move to the front the fact that including people with disabilities (and older users) gets you usability for free. 22:47:18 rrsagent, this meeting spans midnight 22:48:24 http://www.w3.org/WAI/EO/Drafts/involving/new-users-eval 23:18:58 check for big things an dfix em first 23:20:59 action: Involving Users Eval - chagen "Preliminary Review" to more csual and include repair big, obvious things (also, refine what to have pwds focus on) 23:23:16 action: Involving Users Eval - change "Preliminary Review" section - maybe say someting about it helps to focus your efforts with users 23:23:58 planning 23:24:39 Sharron has joined #eo 23:36:38 glaser has joined #eo 23:38:16 andrew has joined #eo 23:57:37 shadi has joined #eo 00:00:12 Sharron has joined #eo 00:05:44 action: Involving Users Eval - check what would be involved in broadening it to tools, etc. - if not too much work [maybe as an adidional note] [and, look at how its done in compantion doc] 00:09:33 Action: Caution should be repeated in both documents. Harmonizes with "get usability for free" 00:13:26 Action: Involving Users Eval - look at putting together accessibility issues and drawing conclusions and separating out reporting. 00:14:11 Shadi: Not to draw hasty conclusions. 00:14:54 Shawn: caution against testing with one disability groups and extrapolating to all users with disabilities. 00:16:24 Sharron has joined #eo 00:17:12 Sharron has joined #eo 00:18:46 suzette: not to over extrapolate from the results in front of you 00:19:25 andrew: you have observations, not statistically significant tests 00:21:38 primary audience would take the results and enter it in the changelog 00:27:20 Action: Involving Users Eval - Move reporting within "prefessionals" section and perhaps editing. 00:28:11 rrsagent, make logs world 00:28:42 Shawn: Want to look at titles and references of both documents. 00:36:23 Suggestion 00:37:16 Suzette - Involving Users in Web Development - [Achieving] Better Easier Accessibility 00:37:49 Involving Users in Web Design and Development for Better Easier Accessibility 00:38:02 Involving Users in Web Design and Development for Better, Easier Accessibility 00:39:24 Involving Users in Web Accessibility Evaluation 00:40:58 Involving Users in Evaluating Web Accessibility 00:45:23 suzette: ... to improve accessibility 00:45:59 note - title - we really want to get reluctant readers to read this - thus "better & easier" 00:54:03 ACTION: Shawn & Andrew research other good references for Invovling Users 01:01:55 rrsagent, make minutes 01:01:55 I have made the request to generate http://www.w3.org/2009/11/02-eo-minutes.html andrew 01:15:51 NEW TOPIC "Improving Your Web Experience with Adaptive Strategies " 01:16:08 http://www.w3.org/WAI/EO/Drafts/adaptive/strategies.html 01:23:40 Andrew: seeing where to click, focus on pages 01:24:25 action: Enjoyable - mouse use - seeing where to click (ref back to enlarging links, form elements, etc) 01:24:54 "things your granny can do" versus things she'll need help with 01:25:22 Suzette: felt a need for a rating scale to indicate those things that users may be able to do for themselves and those things for which they are likely to need help. 01:27:07 Action: Andrew research effort on changing DPI setting 01:27:24 suzette: dpi settings can make a difference, in addition to screen resolution 01:31:18 manybe"descrease the resolution of your display" ->"descrease the resolution/dpi of your display 01:32:08 "change the resolution/dpi of your display" 01:32:41 action: shadi to check on wording for resoulution versus DPI settings 01:35:17 action: Enjoyable - capture that resoluton is affected by three changes under windows - resolution, DPI, accessibility 01:37:19 jack; tell them how to do the easy things 01:37:29 then point to the harder things 01:38:21 q+ to ask about including the common 01:41:38 http://accessibar.mozdev.org/ is tool bar to adjust colours , fonts etc 01:41:42 action: Enjoyable - introduction - some solutions/steps may need advanced techniques 01:42:00 jennifer: "hardware & software" works - "tool" not so much 01:45:00 action: Enjoyable - consider marking some techniues and/or refs as medium/advnaced level of difficulty 01:48:00 Sharron has left #eo 01:53:56 andrew: consider training as an option under 'explore your computer system' 02:05:00 disconnecting the lone participant, Ponderosa, in WAI_EOWG(TPAC)10:00AM 02:05:07 WAI_EOWG(TPAC)10:00AM has ended 02:05:12 Attendees were Ponderosa, +34.62.717.aaaa, William, michael 02:15:32 andrew has joined #eo 02:15:55 rrsagent, draft minutes 02:15:55 I have made the request to generate http://www.w3.org/2009/11/02-eo-minutes.html andrew