The main goal of this meeting is to get input from those who will not be at the face-to-face next week.
<trackbot> Date: 26 October 2012
<scribe> Scribe: Sharron
<Wayne> All the monkies in the zoo give their best regards to you, good morning.
<shawn> http://docs.webplatform.org/wiki/Main_Page
<shawn> encouraging and monitoring accessibility info
Shawn: The issue is to encourage and monitor accessibility issue within this work.
Suzette: I discovered that someone had changed something in our materials. I have changed it back and wondered what was the protocol about that.
Shawn: Thanks for doing that. I
need to find out why I did not get notification since I am set
for a watch on those pages.
... so that is one thing, how to manage changes that others
make.
... but the broader issue is to go through and encourage people
to contribute, especially to contribute accessibility
considerations on other pages.
... so in general techniques for images, for example, add how
to think about text alternatives, etc.
... Anymore thoughts about how to engage people. Make a list of
where we think accessibility is needed, post it to WAI-Engage
or WebDocs itself, and seek volunteers to help with integration
of accessibility into the overall work.
Sharron: I think that is a great idea.
<scribe> ACTION: Shawn will query WebPlatform Docs about 1. why no notification and 2. where to post accessiiblity volunteer recruitment request. [recorded in http://www.w3.org/2012/10/26-eo-minutes.html#action01]
<trackbot> Created ACTION-222 - Will query WebPlatform Docs about 1. why no notification and 2. where to post accessiiblity volunteer recruitment request. [on Shawn Henry - due 2012-11-02].
Sharron: I think of posting for volunteers is good but should we not have a proess for EO to monitor?
Shawn: Ask for people to volunteer, put their name on it, and then when we get notification we can review.
Andrew: Anyone can log in and change even without putting it on out list, is that true?
Shawn: But there are so many pages and so many edits I can only assume no one wants to watch all of it. Could ask if we can watch a tag (like accessibility) and/or if someone like Chris IS watching all of it, he might alert us when accessibility info is added.
<Wayne> http://ai.stanford.edu/users/sahami/CS2013/
Suzette: Concepts pages have a stack of things about accessibility that look like they are randome, not really what is of most importance, and not particularly the items that should be worked on by the community.
Shawn: I agree and maybe we can
talk to Chris and Doug about that next week at TPAC.
... but since EO has not yet come up with the specific list of
what we should add to this, it is not yet clear how we can
proceed. We need to include Accessibility Basics in this
Concepts page.
... There may be some things that would good to develop within
WebPlatform Docs.
Sharron: Yes, I think it is improtant to have integrated materials
Andrew: And some testing pointers that will let people know that they can get more detail in WAI.
Wayne: How about something as simple as when you are taking their course on HTML, we might have specific pointers to Success Criteria.
Shawn...and Techniques
Sharron: Great idea, let's do
it.
... in the lsit of voluteers make the task that simple. Find
related topic and do the pointing as an example for others.
Wayne: I could volunteer in
January
... This is the curriculum guidelines at Stanford and have
posted their strawman for comment. This is what they will use
as computer science curriculum all around the world. Their
revisions are done every 3 to 5 years and the time is now.
http://ai.stanford.edu/users/sahami/CS2013/
... I just found out about it this week and have not been able
to comment.
<Wayne> Alvaro Monge
<scribe> ACTION: Wayne to find volunteer to flag any language about accessibility and to suggest where such language needs to be added. [recorded in http://www.w3.org/2012/10/26-eo-minutes.html#action02]
<trackbot> Created ACTION-223 - Find volunteer to flag any language about accessibility and to suggest where such language needs to be added. [on Wayne Dick - due 2012-11-02].
<shawn> http://www.w3.org/WAI/EO/wiki/Eval_Analysis
Shawn: Suzette do you want to mention the changes you made this week?
Suzette: The work on the
scenarios? It was design as a new issue, distinct from
development.
... so I have now included that concpet in the fourth row,
while developing design specification, but it may not be the
right place.
... don't know whether that captured what we spoke about last
week, if it should be recast as the commisioner of the web
site.
Shawn: May want to put in early prototypes, wireframes etc to make it more explicit. The role would be irrelevant, jsut the specifics of the issue of early consideration
<Andrew> page mockups
Suzette: I hesitate to add more, seems likely to be most effective to have a small number of scenarios rather than so many it is hard to keep them all in mind, to get our heads around.
<IanPouncey> Less is more
Sharron: I agree that a smaller number, and integrate the idea of early consideration into those that exist.
Shawn: In the WCAG-EM where we have six, could designate them as primary or secondary.
Suzette: Which would we designate as which?
Shawn: That is something that perhaps we ask WCAG-EM since it is their document.
Andrew: You ahve a good order here already.
Wayne: Yes I agree
Wanye: I'll take a few minutes to review with UI design in mind, and drop in anything I see that is missing.
<shawn> http://www.w3.org/WAI/EO/wiki/Eval_in_process
<Andrew> Address Accessibility Early and Often
Shawn: If you ahve specific
recommendations, we will put it here. If we have suggestions
for how to most effectively address accessiblity early on,
let's put it here. Thanks to Ian for adding to it.
... please work on this in any way. This is a basic start, feel
free to change.
Wayne: I will put some work on it next week.
Shawn: Any chance Suzette of making the changes by early next week?
Wayne: OK I will get going and
have it posted by Wednesday.
... there are specific phases in UI Design. It has converged
into a pretty standar set of steps. Putting accessibility
considerations into that standard set will not be
difficult.
Shawn: Can you take a look at this wiki page? What is there is just an outline and I was hoping Suzette that you might have some specific suggestions about the design stage.
Suzette: Yes, maybe by starting with a definition. Clarify the distinction between design and development.
Shawn: And we will need to make decisions about how detailed we will be vs high level considerations.
Ian: We might want to be more or less specific depending on the audience. Developers will tend to want very specific recommendations and designers maybe not as much.
Suzette: Considerations must be made of CMS, visual goals, text based etc. That kind of establishing who you are and what your project goals are - those all seem to be quite high level.
Shawn: Keep in mind that you are welocme to change headings, content, really anything here.
Suzette: It will be improtant for people to be clear about their communication goals.
Shawn: For those not at the F2F
in particular, put your ideas here in the wiki before Tuesday
of next week.
... we will be looking at your comments on Wednesday
<Andrew> http://www.w3.org/WAI/EO/wiki/Web_Accessibility_Preliminary_Evaluation
Shawn: Suzette, you wanted to comment on the new materials there from Wayne and Tom?
Suzette: I like that it is not
working through in order of the Guidelines but rather are more
geared to a developer's mindset. It seems a nice way to
approach this rather than the more generic, march trhough the
Guidelines way.
... things that make the text itself most accessible. I thought
this was a quite useful structure.
... seemed quite aligned with how developers work.
Wayne: But we did keep the constraints of the Guidelines in mind
Suzette: But it has an aspect of breaking free of them
Wayne: Perhaps put Headings as part of general considerations of text structure.
Ian: headings are a special case
Sharron: But maybe you could add other considerations that you mentioned - list structure, etc
Suzette: Functionally they are very much about navigation.
Wayne: We started as a list quite
closely geared to the Guidelines. As we used them to teach,
students said - can't you make this more useful for how we
actually work?
... this was the result.
... Jennifer said last time that there is a bunch of these kind
of lists out there, maybe we want to look at those and come up
with a synthesis. Tom and I feel like this is a good, solid
start to a working process for accessibility integration.
... has been vetted and evolved with input from many developers
who were part of the ATI at CSU.
Andrew: I have a few comments to add in there as appropriate.
Wayne: I think we could link it
the other way - for each item show how they address the
SCs
... this is not perfect and you will still need an audit at the
end. But it helps to prevent the need of total redesing. We
felt like this process will help avoid the design traps that
could cause a structural redesign.
<Andrew> one grouping of SC by topics is at http://www.w3.org/WAI/older-users/developing.html
<shawn> http://www.w3.org/WAI/EO/wiki/Participating_in_WAI
Shawn: I started a wiki page, we
may not have time to get to this at the F2F but in case we do,
I wanted to point people to it.
... what is the feeling of the group?
<shawn> [deferred - plenty to do on evaluation!]
Andrew: From experience, it seems wisest to stay on topic, not introduce soemthing that might distract from teh evaluation work.
Wayne: back to the PreLim Eval for a minute. Maps.
Andrew: Yes people are struggling with accessibility on geo-spatial applications.
Wayne: Yes it is important, becoming ubiquitous. I need feedback on that.
Sharron: Where do you want the feedback?
Wayne: I think it is a weak point
in the material I added to the wiki. Tried to add what I knew
about accessibility for the older method of maps to the newer
methods, but not sure it is successful.
... I put together the best I could in a few days but would
appreciate some input on that.
<shawn> For WCAG-EM - complete sampling survey <http://lists.w3.org/Archives/Public/w3c-wai-eo/2012OctDec/0017.html>
Shawn: Please take this survey, not public but open to EO
Sylvie: It is quite long, about 20 minutes to complete.
Wayne: Will they look at what we put on the wiki?
Shawn: Yes, we formally submitted those comments.
Sylvie: They ask about how do you choose the level of testing, how do you report, how do you choose pages, etc
Andrew: Very detailed about how you put the samples together for testing. Seems they are trying to get some real world experince
Sylvie: About 7 pages, more than 20 questions
Suzette: Tried to answer, but had to leave to get more information. When I returned I had to start all over.
Shawn: Would be good to have just the list of questions.
<shawn> Training pages - complete publication survey <https://www.w3.org/2002/09/wbs/35532/waitraining2c/>
Shawn: Tried to get this done last week, please do get to it.
<shawn> Update Availability for Upcoming EOWG Teleconferences
<shawn> Complete actions for all EOWG (above) - updated weekly
Shawn: update availability for
telconferences, complete action items, inlcuding those at the
top of the page (Action Items for ALL EO).
... anything else for today?
Sharron: Are we having a F2F at CSUN?
Shawn: An actual work day meeting or a lunch?
Sharron: I would go for a full work day
<Andrew> +1 if it was possible
trackbot, end meeting
This is scribe.perl Revision: 1.137 of Date: 2012/09/20 20:19:01 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: Sharron Inferring ScribeNick: Sharron Default Present: Wayne_Dick, Sharron, Shawn, Suzette, IanPouncey, Sylvie_Duchateau, +61.4.473.8.aaaa, Andrew Present: Wayne_Dick Sharron Shawn Suzette IanPouncey Sylvie_Duchateau +61.4.473.8.aaaa Andrew Regrets: Helle Jennifer Emmanuelle (maybe:_Shadi Andrew Suzette) Found Date: 26 Oct 2012 Guessing minutes URL: http://www.w3.org/2012/10/26-eo-minutes.html People with action items: shawn wayne[End of scribe.perl diagnostic output]