12:26:20 RRSAgent has joined #eo 12:26:20 logging to http://www.w3.org/2014/09/12-eo-irc 12:26:22 RRSAgent, make logs world 12:26:22 Zakim has joined #eo 12:26:24 Zakim, this will be 3694 12:26:24 ok, trackbot; I see WAI_EOWG()8:30AM scheduled to start in 4 minutes 12:26:25 Meeting: Education and Outreach Working Group Teleconference 12:26:25 Date: 12 September 2014 12:26:30 Chair: Shawn 12:26:37 Scribe: Sharron 12:27:10 zakim, call shadi-617 12:27:10 ok, shadi; the call is being made 12:27:11 WAI_EOWG()8:30AM has now started 12:27:12 +Shadi 12:27:27 Wilco has joined #eo 12:28:29 metzessive has joined #eo 12:28:41 AnnaBelle has joined #eo 12:28:42 yatil has joined #eo 12:28:54 + +1.615.417.aaaa 12:29:10 zakim, call EricE-Skype 12:29:10 ok, yatil; the call is being made 12:29:12 +EricE 12:29:13 +Shawn 12:29:28 zakim, nick yatil is EricE 12:29:28 ok, yatil, I now associate you with EricE 12:29:31 zakim, mute me 12:29:31 EricE should now be muted 12:29:34 + +1.512.731.aabb 12:29:44 +??P3 12:29:53 zakim, ??P3 is me 12:29:53 +kevin; got it 12:29:55 + +1.202.276.aacc 12:30:03 zakim, aaaa is me 12:30:03 +AnnaBelle; got it 12:30:16 zakim, aacc is Jon 12:30:16 +Jon; got it 12:30:23 \me Yeah. Will miss you guys! 12:30:55 + +1.562.256.aadd 12:31:16 paulschantz has joined #eo 12:31:44 zakim, who is on the phone? 12:31:44 On the phone I see Shadi, AnnaBelle, Shawn, EricE (muted), +1.512.731.aabb, kevin, Jon, +1.562.256.aadd 12:32:02 zakim, aadd is Wayne 12:32:02 +Wayne; got it 12:32:13 +[IPcaller] 12:32:30 zakim, aabb is Jan 12:32:30 +Jan; got it 12:32:47 Zakim, [IPcaller] is Sharron 12:32:47 +Sharron; got it 12:33:06 zakim, mute me 12:33:06 Sharron should now be muted 12:33:23 Wayne has joined #eo 12:33:32 +PaulSchantz 12:33:53 Topic: Implementing Web Accessibility 12:34:35 Shawn: This is ready for complete and thorough review. Use GitHub if you re comformatble with that. or email or wiki. 12:34:50 ...anyone have discussion of that? 12:35:28 Kevin: Very open for any comments, suggestions, etc 12:35:40 Shawn: So everyone add to to-do 12:35:52 Topic: WCAG-EM Report Tool 12:36:36 Shadi: We got just a couple of comments, thanks to those of you who got people to use it, we got quite a few comments. Most are not yet implemented 12:36:44 zakim, unmute me 12:36:44 Sharron should no longer be muted 12:37:19 zakim, mute me 12:37:19 kevin should now be muted 12:37:58 Shadi: I have tried to make clear those items that have been discussed and that are scheduled for implementation. We need to discuss three comments. Link from agenda to the wiki to find those comments 12:38:17 ...let's look at second comment, 12:38:21 zakim, mute me 12:38:21 Sharron should now be muted 12:38:51 +[IPcaller] 12:39:12 zakim, IPcaller is Wilco 12:39:12 +Wilco; got it 12:39:26 borders & shading https://www.w3.org/WAI/EO/wiki/WCAG-EM_Report_Tool_Comments#borders 12:39:30 http://w3c.github.io/wcag-em-report-tool/dist/#/audit/scope 12:39:49 Jan has joined #eo 12:41:09 Shadi: OK Let's look at first comment, "borders and shading." If you look at the input area, Wilco has done one round of emphasis so now we should consider if this is good. 12:42:04 Shawn: The areas look kind of 3-D. I am used to the background with shading but the field itself being entirely white. 12:42:17 ...the gradient gives it a look of a button. 12:43:07 Kevin: None of the visual aspects of this has come up in my testing with others. In fact I got very good feedback on the overall look. 12:43:57 Shadi: Typically the editable aspect would be white to indicate that it can be filled 12:44:24 Wayne: I don't think it is the color, but the gradient 12:44:32 s/Kevin/Paul 12:44:57 Shawn: You could have a darker border with the text box area being white 12:45:46 Shadi: The text area is so large that we wanted to indicate that focus is within the text box regardless of zoom 12:46:10 ...are you then suggesting making borders larger and darker. Wilco? 12:46:21 Wilco: I don't see any problem. 12:47:07 Paul: I have a question about when focus comes into the filed, could the border not change color 12:47:24 Shadi: It is the way it works now with this one. 12:47:32 Wayne: I like how it is now 12:47:53 Paul: I do too, but the color change in the border can be more obvious 12:48:44 Wilco: Changing the background color will have an impact on more than this aspect. 12:49:40 Paul: The light background color was requested for an app we built at CSUN as an alternative to plain white which is too bright for some visual disabilites 12:50:09 ...it is a subtle change but makes a great deal of difference 12:50:33 http://www.w3.org/WAI/tutorials/ 12:51:05 Sorry Sharron. I just saw this. It was me. 12:51:52 q+ to say browser color setting 12:52:54 Shadi: The very faint horizontal border will suffer the most. If we can change that would it wok to make the background darker? 12:53:33 ...one thing I notice on the tutorials is this very thin and unobtrusive red line at the top. Might that be useful? 12:53:57 Shawn: The report tool has no W3C logo so branding? 12:54:01 q+ 12:54:05 ack me 12:54:05 shawn, you wanted to say browser color setting 12:54:06 Shadi: It has W3C colors 12:55:07 Shawn:I was checking to see if this would accept my own application of color, not found it yet, but wanted to agree with Paul's comment about bright white 12:55:15 Paul's example http://lists.w3.org/Archives/Public/w3c-wai-eo/2014JulSep/0067.html 12:56:03 AnnaBelle: We need to make note of the fact that we don't have clear connection to W3C. I had mentioned it before but wanted to reintroduce the fact. 12:57:04 Zakim, mute me 12:57:04 sorry, metzessive, I do not know which phone connection belongs to you 12:57:13 metzessive is Jon 12:57:18 Shadi: I am hearing that there is a preference for a slightly shaded page background. That will allow us to have the input field become white and could darken and strengthen the borders. Will come back to the gradient question. 12:57:33 It's a subtle change, but it really makes a big difference (our app had a white background at first). 12:57:38 zakim, Jon is metzessive 12:57:38 +metzessive; got it 12:57:43 zakim, mute me 12:57:43 metzessive should now be muted 12:57:49 +1 12:57:54 ...will add slightly darker background, field inputs white, stronger borders if needed. 12:58:18 ...and about gradients, Wilco do you want to keep them? 12:58:29 Wilco: Yes I really really like them. 12:59:06 Shadi: Shawn, will this address yourconcern even if we keep the gradient? 12:59:24 Shawn: Yes I beleive with those other additions it should be OK 13:00:06 Shadi: Great, we will try that and is there anything else on this? 13:00:08 floating save https://www.w3.org/WAI/EO/wiki/WCAG-EM_Report_Tool_Comments#floatingsave 13:00:48 Shadi: Next question is about the fact that the "Save" button is at the very top. 13:02:08 ...as you make your way through the application, you must scroll back up to the nav bar to Save as you collect data. A suggestion has been to have a floating "Save" 13:02:24 Entire menu 13:02:32 +1 13:02:41 Jon: Or float the entire menu 13:03:04 +1 to perhaps, maybe it being a good idea 13:03:05 +1 from me, and the people who tested 13:03:19 Shadi: That would have the beenfit of having key reources handy 13:03:56 good point, wayne 13:04:12 ...so that no matter where you are in the process the top nav will be at teh top of your screen 13:04:17 when you say "floated" you actually mean "fixed" right? 13:04:28 Wayn: Big problem for magnifcation 13:04:48 Wilco: We can set it only for certain size screen - we can address that 13:04:50 q+ 13:04:53 q- a 13:05:03 s/Wayn/Wayne 13:05:35 What about a visibility when the focus shifts back up on the page? Like what happens in Android UI? 13:05:59 q+ to ask about top menu items on first page 13:06:09 Shadi: The entire code of this is online and they are using a branch of this tool in Wilco's organization. So we know it is possible to configure the Auto-save 13:06:26 Wilco: and it is already in there ifyou know how to use it 13:07:36 Wayne: At 200% the top bar takes up about you are losing a lot of screen space 13:07:52 zakim, unmute me 13:07:52 Sharron should no longer be muted 13:08:44 Wayne: about 1/6 of the screen and since we only have 50 words on a screen that is huge 13:08:55 zakim, mute me 13:08:55 Sharron should now be muted 13:09:26 Zakim, unmute me 13:09:26 metzessive should no longer be muted 13:09:32 wayne are you using text only or page zoom? 13:09:49 +1 to talk about menu bar 13:10:00 oops q+ 13:10:03 Wayne: So we need to really think about how to float and where the break points will be 13:10:06 q+ 13:10:21 q- 13:10:27 ack m 13:12:17 Jon: When you say floating, do you mean fixed on the top? Is it possible to note when zoom is activated and get rid of icons etc to alleviate the situation? One observation that was made is the length of time it takes to use the tool. The fixed nav would be a good mediation of that. 13:12:20 I will do screen shots. 13:12:22 zakim, unmute me 13:12:22 Sharron should no longer be muted 13:13:27 Jon: See the Android UI as you shift focus down, the navigation disappears, but if you move focus up, the nav becomes visible to the user 13:14:11 Shadi: I understand but I dislike that function personally. Never know when/how it shows and can be confusing 13:14:17 zakim, mute me 13:14:17 Sharron should now be muted 13:14:40 q+ to mention close & open nav at top? 13:14:52 Jon: I will send some links for possible solutions 13:15:25 Shadi: We are running to the end of Wilco's time so we need to determine what is absolutely needed in this version. 13:15:30 ack me 13:15:30 shawn, you wanted to mention close & open nav at top? 13:15:48 http://stackoverflow.com/questions/1713771/how-to-detect-page-zoom-level-in-all-modern-browsers 13:16:11 Shawn: Brainstorm - if we have it always visible, could it inlcude a collapse option? 13:16:38 Shadi: Good idea but new feature...Wilcon what is the effort? 13:17:12 s/Wilcon/Wilco 13:17:39 Wilco: I am experimenting with the idea of float, need to consider screen height but if we inlcude a collapse that may not be an issue 13:18:15 Shadi: So to minimize the function, there are icons needed, placement questions, etc so I am sensing that this may be considerably more work. 13:18:28 Wilco: Yes it will take considerable work 13:19:14 Shadi: Several applications do contain this sort of thing but it is something that needs thinking, planning, testing 13:19:57 ...we are likely to have a Control+S for some browsers but what if we don't have the fixed nav here? 13:20:15 Shawn: I am afraid it is significant 13:20:21 zakim, unmute me 13:20:21 Sharron should no longer be muted 13:20:24 I agree with Shawn 13:20:30 yes 13:20:38 i am 13:21:07 how quickly are you iterating? I ask only half in jest 13:21:39 q+ 13:22:25 Jon: When you first see the page, you see the Save or hear it only once with a screen reader. Many of these testing will be doen in between other projects and people don't like to spend more time than they must. Having the save more available by far outweighs the investment 13:22:26 ack p 13:22:34 zakim, mute me 13:22:34 Sharron should now be muted 13:23:01 Paul: I would not want to hold up the release but could it come a few weeks down the road? 13:23:51 Shadi: No we have no resources for further iteration, we need to get as far down the road as we can. We are past the time of funding for this but are stretching Wilco's time to make this one the best possible 13:24:07 Paul: It is in GitHub, we could fork it 13:24:53 Wayne: Why not have a save button by each input like on the wiki 13:25:10 Shawn: Maybe on every Guideline level? 13:25:23 Shadi: Will people think that is a localized save? 13:25:30 Shawn:Possibly 13:26:23 Wayne: Vertical scrolling is not as significant as horizontal scrolling but nevertheless is significant in terms of time 13:26:56 subtopic: Results for the entire sample 13:27:57 Shadi: Staying on Step 4, the Audit the Sample, it is supposed to be flexible. Some will evaluate page by page, some will provide reports only on the sample level, not detail on every page. This is meant to support all approaches. 13:29:43 Zakim, mute me 13:29:43 metzessive should now be muted 13:30:04 ...if you want to evaluate on a page-by-page level, the labeling may not be as clear. There is a need to make it clear that the tool will only report what you put in, that there are functions hidden throughout the tool, and that results are customizable. 13:31:33 Shawn: Making sure that people will understand that they may just make a determination for all of the sample, but some will be judging page by page. The result is reported for the full sample and later after having looked at all of them, would make the determination for the whole sample. 13:33:06 Shadi: Step 4 is the most complex because it has so many various ways it might be used. When you are first here...there is SC to evaluate, there are Principles, Guidelines and expandble functions. At the SClevel, the expand is a button on the left hand side 13:33:22 ...is that clear? 13:34:13 ...if you go to Step 3 and add a couple of pages, then go to Step 4 and will ahve pages loaded 13:35:03 ...I worry that "Show Results for Individual Pages" may not be clear and you must know that before you choose that option you are expected to choose those individual pages 13:35:22 zakim, unmute me 13:35:22 Sharron should no longer be muted 13:36:09 zakim, mute me 13:36:09 Sharron should now be muted 13:36:28 Sharron: I agree that the instruction must be made more clear 13:36:47 q+ to suggest higlighting 13:36:48 Shawn: Show Results for Selected Pages? 13:37:07 ack me 13:37:08 ack k 13:37:09 kevin, you wanted to suggest higlighting 13:37:33 q+ 13:38:17 zakim, mute me 13:38:17 kevin should now be muted 13:38:25 Kevin: That button only becomes useful and purposeful when you have selected something, maybe disble the button until you have chosen individual pages to look at 13:38:34 ack w 13:39:09 Wilco: perhaps it wuld be clearer if we make the "Select Sample" to "Choose or Create" sample. 13:40:20 Shadi: Independently of that. Say we had a better name for that... 13:40:44 Shawn: What about Kevin's idea of only making it visible when pages are slected 13:41:32 Shadi: If the button is not visible how would you find that function, how would you know you could display info for slected pages? 13:42:02 Shawn: We may need to have hep text...one or two lines that tell you what you can do here. 13:42:05 q+ to talk about tutorial 13:42:10 s/hep/help 13:42:57 Wayne: Every other control is more of a combo box, why not align with other controls? 13:43:48 ...Just because there are only two selections is this not the same function and could you not make it more of a toggle? 13:44:46 Shadi: Wilco can tell me if there is an option to do something like "Show All" 13:45:13 ack me 13:45:14 kevin, you wanted to talk about tutorial 13:45:16 Wayne: To specify only certain pages in this presentation of it, is confusing 13:46:19 Kevin: Having an intro/help text is often done with a popup mini-tutorial that gives you an overview of the function that is available 13:46:51 zakim, mute me 13:46:51 kevin should now be muted 13:48:06 Shadi: These have been good ideas, thanks for sharing your thoughts, Wilco and I will take this back and see what we can and cannot do. 13:48:59 ...there were a few submitted comments that did not entirely make sense to me and I will follow up off line 13:49:25 Wayne: I am sending more screen shots. I think it is remarkable that this application is fully operable and 400% 13:49:36 s/and/at 13:50:29 Shadi: Anything else on this age? 13:50:34 s/age/page 13:50:36 My testers really REALLY liked exporting the document 13:51:04 Zakim, unmute me 13:51:04 metzessive should no longer be muted 13:51:04 Shawn: Jon, can you summarize and submit your results with your testers? 13:52:23 Jon: I have a very small sample, but they think the ability to export was extremely helpful. Not much detailed feedback but the length of time to do the testing was more than expected. 13:53:04 zakim, who is noisey? 13:53:04 I don't understand your question, shawn. 13:53:11 zakim, who is making noise? 13:53:12 Zakim, mute me 13:53:12 metzessive should now be muted 13:53:18 Shadi: We have hopes that in future we will be able to add automated test results and have it integrated into the final report 13:53:23 shawn, listening for 11 seconds I heard sound from the following: Shawn (12%), Shadi (66%) 13:53:31 Topic: Tutorials 13:53:58 -Wilco 13:54:22 http://www.w3.org/WAI/tutorials/tables/ 13:54:36 Shawn: We had a comment come in about the text alternatives on the Tables Concept page. I think it is too much to read the email, but Eric will walk us through what is the issue 13:54:38 ack me 13:56:58 Eric: The comment was that the small table images have incorrect alt text. For example, the basic tables icon says "Typically you have one row or column..." Some have no alt text because the text that follows is sufficient to describe. The comment was that the approach is inconsistant 13:58:17 Shawn: If you don't understand the issue, notice that the table image in the first one, Basic Tables is rendered as follows: 13:59:32 Eric: The image is not visually where it is in the code. So the alt text in the first one specifies more about the basic tables. It is not only describing the image but is trying to communicate the same info in the flow of how a screen reader would read it. 13:59:43 zakim, unmute me 13:59:43 Sharron should no longer be muted 14:00:15 zakim, mute me? 14:00:15 sorry, Sharron, I do not know which phone connection belongs to me? 14:00:23 zakim, mute me 14:00:23 Sharron should now be muted 14:00:31 ack me 14:00:43 Sharron: What is the exact objection? 14:01:00 q+ to comment on the comment 14:01:13 ack me 14:01:14 kevin, you wanted to comment on the comment 14:01:17 Eric: That the alt text does not completely describe the image and the inconsistancy of sometimes using empty alt when the inline text is deemed to be sufficient 14:01:58 zakim, mute me 14:01:58 kevin should now be muted 14:02:01 +1 for Kevin's comment 14:02:15 Kevin: I read the comment. It is not clear why the objection exists. It comes across that it is technically incorrect but it does not make clear what problem it might cause an actual user. 14:02:50 The alternative text is "equally" effective 14:02:54 http://lists.w3.org/Archives/Public/wai-eo-editors/2014Sep/0006.html 14:03:08 Shawn: Let's try to figure this out so it does not go for another week. Please take a reading break so we can figure this out. 14:07:32 q+ 14:07:52 ack me 14:08:03 Shawn: There is a technical objection that the presentation does not exactly match how we decribe an approach in the images tutorial. However, there does not seem to be an example of a user who would miss information. That makes it difficult to know how to address the comment. 14:08:21 -Jan 14:08:29 q+ 14:08:30 Is there a TL;DR version? 14:08:46 Shadi: This may be an objection to a percieved bias that WAI optimizes for screen reader users. 14:09:00 I have to get on another call - have a great weekend everyone. 14:09:23 ack me 14:09:24 q+ 14:09:31 zakim, unmute me 14:09:31 metzessive should no longer be muted 14:09:42 q+ 14:09:48 ack j 14:09:58 ack me 14:10:02 ack metz 14:10:05 Shawn: However the main reason for having the icons was for users with low vision and/or dyslexia and that use case would not be dependent on the text alternative in any case. 14:10:44 Jon: Is the complaint that we have alt text on images that should not have alt text? 14:11:01 q+ to highlight iconic use of icons 14:12:24 Shawn: No I think the complaint is of the fact that the alt text does not precisely describe the iamge but rather is meant to facilitate general understanding of the intent of the image and is further meant to fit into the flow of the accompanying paragraph. 14:14:59 Jon: We (people with cognitive disabilities that affect the ability to process information simultaneously) may be looking at images on the screen, I expect the alt text to describe the image, not to provide context. I think visually. When I talk, I translate your words into pictures, and my pictures into text. 14:15:08 Shawn: So you look at alt text for images? 14:15:16 q+ 14:15:51 ack sh 14:15:53 ack me 14:15:57 Jon: Yes, all the time. Sometimes as a translation device to help me understand the realtion to your words and my images. It can clarify a bit more about what you are talking about. 14:16:50 Shadi: OK the first alt text will read "Typically will have one header..." 14:17:58 ...so is this a case of reverse information for those who do not use screen readers? Are users of alt text getting more information that those who only see the icon. It may be seen as a decorative image by sighted users. 14:18:15 ack e 14:18:15 EricE, you wanted to highlight iconic use of icons 14:18:56 Eric: The thing with the images is that there use iconic and therefore we may not need to provide as much informaiton as we do. 14:19:05 Shawn: So what is the proposed change? 14:19:28 I do not see a clear request for change in Olaf's email 14:19:30 Eric: The text is also iconic, it presents what was my intention of choosing that icon. 14:19:59 Shadi: If that was the intent, it should be the same to all 14:20:10 Shawn: Info in alt text is more than what is in image 14:20:21 ack w 14:20:33 Eric: Alt text tells me the same as what is in the image from my POV 14:21:36 s/me the same as/the same basic information as/ 14:22:40 Wayne: If I cannot percieve an icon, the alternative text that I want usually is what is the function of the icon, a plain description of the visuals is often insufficient. Second is that whatever you decide is the purpose of an iconic image, it may not be meeting the task. 14:23:06 i believe that we should use alt text to explain what the image is. 14:23:53 q+ 14:23:54 Shawn: Where is everyone else on this issue? 14:24:01 +1 metzessive 14:24:31 ...Eric do you understand why there may be an ojection? 14:24:36 Eric: Yes 14:24:42 -1 that these are decorative. 14:24:49 s/ojection/objection 14:25:17 Shadi: So my opinion is that the icon information is provided inline and that the image should have empty alt 14:25:22 +1 14:25:42 zakim, unmute me 14:25:42 Sharron should no longer be muted 14:26:01 zakim, mute me 14:26:01 Sharron should now be muted 14:26:17 ack me 14:26:50 Kevin: I am not quite sure that providing empty alt text meets the need described by Jon 14:27:01 Shawn: So what is your counterproposal? 14:27:16 q+ 14:27:37 q- 14:28:25 q+ 14:28:31 Jon: They are not decorative. 1st is to explain what's going on in the grey vs white boxes. You want to explain what is going on there. If we did not need to talk about it it would be decorative. 14:29:23 Shawn: The words that accompany the icons, the paragraph text is what would be a description of the boxes, would it be repeated? 14:30:20 Jon: I don't think it is wrong to repeat text as alt and as text. When I look at alt text I want a quick overview of what is going on. 14:30:25 q? 14:30:31 Shawn: Can anyone stay on the call over time? 14:30:38 ack p 14:30:57 Shawn: For those that have to leave, review Forms Tutorial 14:31:00 -AnnaBelle 14:31:35 Paul: In the context of this page, they are largely decorative and should probably just say "icon representing..." 14:31:40 ack w 14:32:05 Wayne: I misunderstood Jon, I change my vote and I like Jon's idea - a lot 14:32:31 Shawn: So you are in favor of getting the redundant information 14:32:47 Wayne: Not redundant so much as repeated 14:32:47 -PaulSchantz 14:33:06 Sharron: I am not in favor of repeating the same alt text as the onscreen text 14:33:21 zakim, who is on the phone? 14:33:21 On the phone I see Shadi, Shawn, EricE, kevin, metzessive, Wayne, Sharron (muted) 14:33:23 zakim, unmute me 14:33:24 Sharron should no longer be muted 14:34:37 Sure. It could also be "an example of a basic table", but it could be better IMO if it clarified what was happening. 14:34:39 zakim, mute me 14:34:39 Sharron should now be muted 14:36:17 What about "example of basic table with a row of headers"? Short, to the point? 14:36:45 http://www.w3.org/WAI/tutorials/images/decorative/#decorative-image-as-part-of-a-text-link 14:38:25 Shadi: Some have empty alt when the information onscreen is sufficient. We can move the rest into the parapgraph. The question really is whether the icons are illustrative or merely decorative. The reason the comment said it was contradictory is that we are not consistent with each other, we don't describe what they look like, what is the meaning of the white vs shading aspects of the icon. So 14:38:25 there was never an intent for this to be an informative image 14:39:23 Eric: Empty alt would be my preference and putting any additional info in the paragraph 14:40:20 Shawn: What are your thoughts about empty alt being the solution overall? 14:41:33 Jon: Well, you do not have to use the very same text as in the paragraph. Could use: "example of basic table with a row of headers"? and such as a short, to the point explanation of what the icon is meant to illustrate 14:41:56 Sharron: +1 I am OK with this 14:42:23 zakim, unmute me 14:42:23 Sharron should no longer be muted 14:42:48 Wayne: Table for a week 14:43:04 Sharron: For what purpose? 14:44:16 Shawn: It is a challenge at this point we do not have a solution that will be accepted as the clear right answer for everyone. 14:45:03 zakim, who is on the phone? 14:45:03 On the phone I see Shadi, Shawn, EricE, kevin, metzessive, Wayne, Sharron 14:46:45 Wayne: In this instance, both needs can be met. Jon and I will exchange emails. Our goal will be to find the alt text that can fill the needs and not contradict the intent of the tutorial. 14:47:13 agreed with being short and succinct 14:47:31 Shawn: To meet our expectations the alt will have to be very very short and succinct 14:48:14 Shadi: Send it to the list as soon as you have suggestions so others can weigh in 14:49:03 Shawn: For next week what is our action 14:49:40 Sharron: Leave as is until we have a solution 14:51:37 Shawn: We look forward to input and will continue to brainstorm. 14:52:12 -Shadi 14:52:17 -kevin 14:52:23 ...Shadi, Eric can you send the email for the Forms review and the type of review? Thanks all, until next week. 14:52:43 trackbot, end meeting 14:52:43 Zakim, list attendees 14:52:43 As of this point the attendees have been Shadi, +1.615.417.aaaa, EricE, Shawn, +1.512.731.aabb, kevin, +1.202.276.aacc, AnnaBelle, +1.562.256.aadd, Wayne, Jan, Sharron, 14:52:46 ... PaulSchantz, Wilco, metzessive 14:52:51 RRSAgent, please draft minutes 14:52:51 I have made the request to generate http://www.w3.org/2014/09/12-eo-minutes.html trackbot 14:52:52 RRSAgent, bye 14:52:52 I see no action items 15:01:54 RRSAgent has joined #eo 15:01:54