We reviewed and updated all outstanding Action Items. Sharron agreed to serve as EOWG representative on the Web History Community Group.
Most of the rest of the meeting time was spent in detailed review and editing of the Accessibility Basics pages of the EO wiki. Shawn thanked EO members for all contributing so usefully.
The group discussed the suite of support documents for Developing Accessibility Training. It was published in September 2010 as a draft. Members are asked to review and make recommendations for finalizing and officially publishing these documents in the Developing Training Notes wiki page.
Shawn reminded everyone to check their individual action items; work on "Actions for all EOWG" in the Announcements section of the EOWG home page; and update your Availability for Upcoming EOWG Teleconferences. We will miss at two meetings in July, so time can be spent on reviewing documents to be published.
The meeting wrapped up with a discussion of mainstream tech conferences and the value of participating in them to spread the word beyond our own community. Suzette also shared the announcement of an accessible apps competition with cash prizes.
<shawn> http://www.w3.org/WAI/EO/track/actions/open?sort=owner
Shawn: If everyone will just look at the dates and items listed and update them. If they are complete, change status to "Done" If not yet completed, change the date.
Sharron:Action items - set dates back to when you think you can get it done
Shawn and all:Walked through items of members in attendance and updated or completed.
<shawn> http://lists.w3.org/Archives/Public/w3c-wai-eo/2012AprJun/0031.html
Shawn: Quick tangent, we will look at a few things coming up that will maybe help more people become more aware of accessibility and the WAI-Engage. In the meantime, send a email to the list whenever you significant updates like these.
<shawn> Web History Community Group "gathers people interested in the history of the World Wide Web: how it was invented, what was out there that made it possible, and what happened in its early years. Our main goal is to collect and preserve valuable information (software, documents, testimonials) before it is lost." - http://www.w3.org/community/webhistory/
Shawn: Sharron, when I saw this I thought of you and what you had said the other day about the next generation of designers and developers may not understand the background of the web and how it as founded to connect people and ideas to each other. Many think of it as primarily a commercial medium. This project seems to want to capture that history. Would you want to participate?
... it is a Community Group and is starting slow. We just want to make sure that what comes out is inclusive of the history of accessibility as well.
Sharron: Sure, I can join as liaison
Shawn: Good, anyone else?
<scribe> ACTION: Sharron to join Community Group of Web History [recorded in http://www.w3.org/2012/06/08-eo-minutes.html#action01]
<trackbot> Created ACTION-166 - Join Community Group of Web History [on Sharron Rush - due 2012-06-15].
Denis: Does the WebEd wiki not cover this?
Shawn: No, WebEd is more of a training suite for development skills.
<shawn> version with notes: http://www.w3.org/WAI/EO/wiki/Basics_with_Notes
Shawn: If we make changes today, do so in the version with notes.
... thanks Vicki and Sylvie for reading, commenting and making such good notes.
... main changes are to the additions Suzette made. I tried moving them to the first section - The Web is for All People.
... look at the flow as well as the wording, please. How does it work?
<Vicki> works for me in that flow
Sharron+1
Denis: Some repetition?
Shawn: Is that a good thing to hammer it home, or should it be changed?
Suzette: Maybe if bulleted instead?
Denis: Yes
Andrew: I thought of that too
Shawn: It will be easier to read and will stand out more.
... (makes the change to wiki)
Denis: Better, but put the "prevent people" in lead-in so it need not be repeated
<Vicki> Yes
Shawn: But if skimming, will change the meaning. It is repetitive but may be good for emphasis.
Andrew: Yes, I agree to leave "prevent" in each of the bullets
Suzette: Not sure I like the phrase in each bullet, but I do like the bulleted presentation.
<Sylvie> OK with this change in bullets.
Shawn: Some other changes to the order, added "accessibility includes impairments related to aging"
Shawn: Next is "Web accessibility is essential for equal opportunity" which had been in Biz Case section. Thoughts on promotion of that section higher in the doc?
Suzette: Looks like a good place
Shawn: And I think it supports what we said we wanted to do with the entire page.
<Vicki> I like it
Shawn: next, let's consider the part within "Understand..." Look at sections that starts "People have a diverse range..."
Denis: Sentence may be too long, can we shorten it into parts?
Andrew: Yes, I think the sentence should be split. First part is about people and second part is about varience in ability.
Shawn: Go ahead and make the change Denis, and we can all look at it.
Denis: You mean now? In the wiki?
Shawn: Sure
Denis: I will do a placeholder and come back to tweek wording.
Shawn: Next issue under Accessibility Requirements...Andrew will you read it aloud?
Andrew: Reads "See Accessibility Principles to learn more about web accessibility requirements. This page has short paragraphs, lists, and descriptions that provide a better introduction to accessibility requirements than the formal standards/guidelines. It includes links to the standards so that you can get the definitive information when you want it."
... reads comments and response.
<shawn> {@@Suzette: this is the sort of sentence I was trying to avoid - it is descriptive but has no useful content (sorry!). The link points to some well written material on about 12 common accessibility issues. I would propose bringing a few sentences from there to here - readers can judge for themselves whether they might find it easier to read. I am happy to do that for next week if you set an Action
<shawn> on me}
<shawn> {@@ reply: Actually, we were trying on purpose for this one to more explicitly encourage people to follow this link. 11 May minutes say: How do we get people to follow this link? "Remember that the resources linked here are really really good. The idea is to make it very enticing to follow the link." suggestion: "Why not just say - we strongly encourage to review excellent resources for more
<shawn> background."}
Suzette: I will stick with my original comment and would like to see something more substantial here. At least a few tasty bits.
Shawn: (edits the wiki) refresh and see how we like the new information.
... does that help?
Suzette: Yes it probably does.
Denis: Would it not be more interesting to stick as much as possible to the short names under each one?
Shawn: The short handles really work better for those who already know about WCAG. Here, the main audience is expected to be people who are NOT familiar.
Denis: When looking at the short phrases, I see what you mean. Some of them do require more understanding of what is behind the phrases. Would need to know about WCAG already.
Shawn: So do we need to give them a clearer idea of what they will find when they follow the link?
Denis: Not sure it is that helpful as it is now, but is basically a good idea. I want the examples, but these may still be a bit too cryptic.
<scribe> ACTION: Denis will review examples for four principles and enlarge to help people understand the basic ideas that underline the priciples. [recorded in http://www.w3.org/2012/06/08-eo-minutes.html#action02]
<trackbot> Created ACTION-167 - Will review examples for four principles and enlarge to help people understand the basic ideas that underline the priciples. [on Denis Boudreau - due 2012-06-15].
Suzette: If you follow the links, there are good examples there, I just did not know which to choose.
... may be helpful Denis to review those.
Shawn: Yes, where it is possible, use the wording that we have already vetted.
... and so what do we think about the third section. Is it enough? Does it need more?
Andrew: Not sure that the part "This page has short paragraphs, lists, and descriptions that provide a better introduction to accessibility requirements than the formal standards/guidelines..." is relevant.
Vicki: Yes, it does not add
Denis: And if we can shorten, we should.
Shawn: OK, any objections to removing that?
<AndrewA> it's good :)
<suzette> much better thank you
Shawn: (edits wiki to remove) Next is "Components/Tools" consider the sentence..."help or hinder"
<shawn> These tools can help or hinder the creation of accessible content.
<shawn> These tools can help or hinder creating accessible content.
Sharron: Occasionally passive voice is OK, in this case it seems so.
Shawn: So leave "help or hinder?"
All: Yes (Denis makes edit)
Shawn: Edit to Biz Case, moved first section up to the "Equal Opptny" section. So now, it introduces older users, mobile as just two examples. First 3 paragraphs have changed. Please consider and comment.
<Vicki> +1
Denis: Yes it is fine.
... why is mobile put before older users?
... think people first would have older users come before mobile web.
Shawn: OK (makes switch)
Denis: Mobile is still something we don't have as good a grasp on. Finishing with that allows people to leave with something to think about.
Andrew: Another thought I had was that there is a growing number of people with disabilities using mobile technologies.
Shawn: That is something that WAI is working on and EO will help with the messaging on.
<AndrewA> http://www.w3.org/WAI/RD/2012/mobile/
Suzette: Do you have details?
<suzette> thank you Andrew
Shawn: Registration is expected to open on Monday so be ready to respond as soon as you get the message.
Denis: For consistency in Business Case, we have one paragraph for mobile web and one for older users. Paragraph structure should be consistently formatted.
Andrew: Sentence might say "for ALL these components..."
Denis: I am wondering why we say "people, content creators, and users" - why is it necessary to say people?
Denis: it doesn't really fit.
Shawn: You have 3 things - content, tools and people
Andrew: leave it as just people and expand in the paragraph.
Denis: I would prefer that.
Andrew: In heading, should we say web users?
<AndrewA> done
Shawn: Denis will look at examples in Principles section; Andrew will look at Tools section
... and Shawn will look at "from birth" wording.
Denis: I tried something if you want to look.
Andrew: Quite good, Denis.
Shawn: Anything else? Suzette?
<suzette> I'm attending Mobile Monday event June 11th - smart accessibility for mobile competition - see http://developer.vodafone.com/smartaccess2012/home/
<AndrewA> Can Suzette please report back to EO on "Mobile Monday" next week :)
Suzette: I am toying with idea in Componenets if it needs an opening sentence to set context.
Shawn: Can people make those edits today, so we have a clean version to consider next week, and get this wrapped up?
Denis: Yes
Andrew: OK
Suzette: Yes
Shawn: Then if each of you will plan on a careful read next week, we may be able to call it done.
... Shadi in order to call it done, we will need the revised heading. Can we bring to EO next week?
<shawn> ACTION: Shawn put on EOWG agenda for 15 June title of Tools|Techniques|Diversity in Web Use. [recorded in http://www.w3.org/2012/06/08-eo-minutes.html#action03]
<trackbot> Created ACTION-168 - Put on EOWG agenda for 15 June title of Tools|Techniques|Diversity in Web Use. [on Shawn Henry - due 2012-06-15].
Shawn: Good work, all. Suzette thanks for getting it started - everyone has contributed.
<shawn> http://www.w3.org/WAI/training/
Shawn: We put out draft in Sept 2010 but never announced it. Need to make sure 1. Comments are addressed 2. Expand / collapse function works, and 3. update links if needed
<shawn> ACTION: Andrew - Training resource suite - check survey issues addressed <https://www.w3.org/2002/09/wbs/35532/waitraining2b/results> - and links still updated [recorded in http://www.w3.org/2012/06/08-eo-minutes.html#action05]
<trackbot> Created ACTION-169 - - Training resource suite - check survey issues addressed <https://www.w3.org/2002/09/wbs/35532/waitraining2b/results> - and links still up to date [on Andrew Arch - due 2012-06-15].
Shawn: Would this be a good WAI-Engage project? As we review, we can document and change anything that really needs it. But if we have ideas and proposals for next version, could put on wai-engage?
<shadi> http://www.w3.org/WAI/EO/changelogs/cl-app-notes
Shawn: can also introduce topics that may not be appropriate for formal document but may be OK for development in WAI-Engage.
Shadi: And keep in mind the opportunity for putting into Application Notes
Shawn: Andrew if you can come back next week with status update and HTML files with changes. Then if everyone can have a look through and see what we may need to add either to this version or to creating more topics or expansion on WAI-Engage.
Denis: I would prefer to work on Preliminary Evaluation.
Shawn: EO will publish it, so will have to go through the review process to approve publication.
<shawn> ACTION: Sharron Review http://www.w3.org/WAI/training/ for what needs to be updated and how we might want to engage WAI_Engage for future work or related info [recorded in http://www.w3.org/2012/06/08-eo-minutes.html#action06]
<trackbot> Created ACTION-170 - Review http://www.w3.org/WAI/training/ for what needs to be updated and how we might want to engage WAI_Engage for future work or related info [on Sharron Rush - due 2012-06-15].
Shawn: Will meet just twice in July so you can spend the time in review and EO work.
Sharron:Big (D)esign conference was really productive in my opinion - interest has grown in accessibility in that communinity in 4 years of participating and this year I got to give a keynote. I approached it from the POV that accessiiblity is a design challenge.
<Vicki> way to go, sharon!
Sharron:Part of the reason for good reception, I think is that people are there because they want to be be good designers. Google provided and Knowbility adminstered scholarships so that people with disabilities were able to attend. Six people using assistive technologies like wheelchairs, screen readers, and captioning. In a group of 300 the inclusion of people with disabilities was noteable. Opening keynote gave me opportunity to follow up with people afterward. Later on a panel of "Future of Web Accessiiblity" included web professinals with disability. I was struck by the importance of being at mainstream tech conferences (instead of just talking with ourselves) - get the message out to the rest of the world
Shawn:Where else can we propose conferences like this and for people with disabilities to be giving talks?
Denis: Recently Chris Heilman gave talk with some accessibility issues integrated into the topics and we ended on a panel together. We discussed this very thing. We get bitter because we repeat the same things and they don't change.
... but we do not consider that we talk to the same people.
Denis: need to get the message to new audiences. even if we reach only a few in that setting, it expands beyond the community.
Shawn: A couple of things. I agree that it is important to look at other conferences. I spoke at Web Design World. In concurrent sessions with Accessibility as a topic, I could end up still talking to the choir.
... Sharron's point of trying to get plenary sessions early in the conference and being there afterward for follow up is key.
... even a few moments in an opening session will approve attendence at a session later on.
... ask for small amount of time in opening sessions.
<shawn> ACTION: Shawn & others look for other conferences that we want to actively target for short plenary [recorded in http://www.w3.org/2012/06/08-eo-minutes.html#action07]
<trackbot> Created ACTION-171 - & others look for other conferences that we want to actively target for short plenary [on Shawn Henry - due 2012-06-15].
Sharron:Also at disability conferences, that have not much on tech, e.g., independent living
<shawn> ACTION: Shawn & others look for disability-related conferences that don't focus on technology [recorded in http://www.w3.org/2012/06/08-eo-minutes.html#action08]
<trackbot> Created ACTION-172 - & others look for disability-related conferences that don't focus on technology [on Shawn Henry - due 2012-06-15].
Shawn: Common theme is to get beyond our own community.
<shawn> http://www.w3.org/community/wai-engage/wiki/Promoting_web_accessibility
<dboudreau> A great way to start looking for other conferences would be at www.lanyrd.com
Sharron: Don't we have a section on WAI-Engage on promoting web accessibility? Could it go there?
Denis: I see conferences there all the time and we could look for those close to where we each live, we could be progressively doing this.
... can sort by interest, geography, etc. Makes it convenient.
Shawn: Would be great to look ahead and talk to conference organizers before they have set keynotes.
... other outreach thoughts or observations?
Andrew: Suzette, can you tell more about Mobile Monday?
Suzette: This week is the launch event of a competition to create apps, attended by about 300.
... I am going to represent older users, and they will have people with dyslexia and other disabilities.
... The competition is to create accesible apps.
Shawn: WAI-IG list is to place notices of any accessibility related events or updates.
<AndrewA> http://developer.vodafone.com/smartaccess2012/home/
Suzette: They just launched it and four prize winners will receive $50K euros
... final presentation will be in Spain in October
Shawn: If it has just launched, you can still post to WAI-IG
<shawn> http://www.w3.org/WAI/IG/#mailinglist
Liam: We are seeing large retailers look at "responsive design" and I am being brought in because of my accessibility experience.
<shawn> +1 for responsive design and accessibility
Liam: wondering if it is worth having something about responsive design on WAI to loop people into accessibility through ARIA and HTML5.
<LiamClone> Mobile first design also
<AndrewA> CA govt will shortly be releasing updates to their common look and feel templates that incorporate responsive design nicely
Shawn: I have been dreaming of writing something up about it. Maybe a post for the W3C blog.
... other thoughts?
Andrew: Good idea.
... recently was privy to update of Common Look and Feel where they have incorporated responsive design into what they had previously done. Very nice.
Denis: We are having a code fest / hackathon to push the web experince tool kit for accessibility one step further.
<AndrewA> http://www.tbs-sct.gc.ca/ws-nw/wa-aw/wet-boew/index-eng.asp
Shawn: Let us know how that goes. Thanks for thoughts, discussion, ideas for reaching out. Great to see documents coming together, thanks for all you do. have a great weekend!