Gallery of Accessible Web Templates and Widgets
13 Aug 2010

See also: IRC log


Andi_Snow_Weaver, Cynthia, David_Neimeier, Elizabeth, Gregg, Jamal, Jeanne, John, Judy, Peter_Korn, Rob, Scott


introductions, agenda overview, basics on logistics, mailing list, wiki etc


JB announces the mailing list (not public) and a wiki page (public) for working. Call is hosted by W3C, and IRC #gallery

description of the gallery challenge

Everyone should have received an email describing the challenge. Are there any questions on the descriptions?

Emphasis less on shared templates or components, then on a showcase of techniques. There is a broad variety of ways that information can be made accessible, one thought is to take the same content and show many different ways to make it accessible.

There are discussion of that, although most seemed to be interested in a repository, more than techniques.

This is a way of getting more templates included in authoring tools. That accomplishes more than a showcase that people go to.

If there were one or more datasets of government information, we challenge broadly for people to come up with implementations of this dataset that is highly usable, and documented for accessibility. But not to preclude templates that are not sharable under an open license.

Sources are 1. Publically funded, sharable work, 2. Crowdsourcing and 3. For developers who have work under development that can showcase work.

Can we connect the Geolocation data with the accessible needs, and presented so people with disabilities can use them.

Perhaps there could be a bridge with Geolocation and be a proof of concept - a pilot project - that we could include and work together.

Presenting Geolocation work is a challenge in itself. There is cross fertilization possible. There is a strong focus on the visual impairment, but I would like to see more for reading and cognative disabilities.

JB requests that idea be discussed when we work on how to set up the gallery.

The description mentions social networking, but does not mention education and job training.

identification of priority gaps to address with new templates & widgets

- basic templates that show standards and basic how-to primer

scribe: there are good examples in WCAG 2.0 of sites that are attractive and accessible.

- accessible video players

<Judy> (1) standard accessible controls

<Judy> (2) accessible interfaces for plug-in video players

- specific need for accessible pattern, like video player, large amounts of data, chart & graphs, etc.

- types of information and broad user interaction. Some of the user interaction for controls for broad information. Use the government datasets, such as crime information or population data. These are obvious candidates for accessible maps and graphs. Data.gov will be a treasure trove of information. Not every presentation of a dataset will use the same components.

Social Security Administration has a interest insharing interfaces for government data.

I'm worried that we are losing track of who the intended user of this challenge? We may be losing track of that and becoming too broad.

There was a strong interest from federal agencies who want to share data across agencies.

FCC has a new accessibility and innovation initiative. That is something to keep in mind, we want to have a long term area for answering questions.

We could start small and move some items into a broader initiative.

We could organize by audience (web developer, graphic designer) or by the code type. It could also be organized by the type of authoring tool, because the tools have very different templates.

In some of the discussion and brainstorming so that people could tag the templates by authoring tool, so that people can sort and filter by it.

Priority gap: Spacial data such as maps. The sighted user has a lot more information than the non-sighted user. Video players. The choices for a lot of templates for a few technologies, or templates for a variety of solutions.

Or pick a few issues and show them across a variety of tools.

We are doing this with volunteers, so we will end up with a richer collection and leave it open so that existing work can be turned in. We want it to keep going. Set up a framework that can handle diverse things. We may want to focus, but keep it wide open.

There are existing repositories of templates that we could draw in or reference that will give us a quick running start.

It is up to the web developer how to display the information. Instead of saying "these are the 5-8 implementations in every toolkit" but the challenge is to invite people to show all the ways to make things accessible, or to show new accessible interaction methods.

identification of communities to reach out to to engage in the development effort

a related part is people to engage in a core planning effort. I want to identify a regular time where people can meet to plan the core effort. Of the people who are here and people want to add, what pieces would people be interested in? What communities should we reach out to?

The commercial entities that make or sell these widget sets and the Open Source ones, Jquery, Dojo. For the commercial, just invite them. For open source, the AEGIS project is in touch with many of them. IBM is doing a lot through the ARIA effort.

There are also government agencies.

There are also the community of tech-minded accessibility advocates.

User groups and bar camps

What component sets are they using? commercial, open source, or in-house?

Chris Kampf (sp) has a lot of contacts in the Free Software, @@ at Drupal

Academic community - U of Washington. The semester start is a good time to interest students.

Note: the first 60 days is not usually good for students, but if we build a longer term structure, that will work for students.

If it is collecting techiques that exist and bringing them together, then that would work.

Wendy Chisholm, Jutta Treviranus, (@@ from Cynthia)

Organizing the Gallery: the data gallery is valid data each done in their own component sets.

Education and Employment: @@.gov, SocialSecurity.gov, Webinars

Outreach to unconferences and barcamps

Robert Wood Johnson Foundation has a contest for health information. How to include accessibility when you are writing content. Knowbility.

next steps, next meetings

Is this time good? [No objections]

Thanks for all the time and effort. The White House is really interested, the Chairman is really interested and we are reporting back on it.

Provisionally hold next Friday 1:30 to 3:00 Eastern

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/08/13 19:12:45 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/1/2/
Succeeded: s/ interest of / interest in/
Succeeded: s/that idea be set up when /that idea be discussed when/
Succeeded: s/whenwe/when we/
No ScribeNick specified.  Guessing ScribeNick: jeanne
Inferring Scribes: jeanne
Default Present: +1.202.418.aaaa, Judy, +1.301.589.aabb, Scott, Andi_Snow_Weaver, +31.20.737.aacc, Jamal, David_Neimeier, +1.617.324.aadd, Jeanne
Present: Andi_Snow_Weaver Cynthia David_Neimeier Elizabeth Gregg Jamal Jeanne John Judy Peter_Korn Rob Scott
Got date from IRC log name: 13 Aug 2010
Guessing minutes URL: http://www.w3.org/2010/08/13-gallery-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.

[End of scribe.perl diagnostic output]