Tech Challenge/Gallery

27 Aug 2010

See also: IRC log


Deborah, Greg, Jamal, Jeanne, John, Judy


Gathering Existing templates and widgets

gathering existing templates & widgets, next steps

There are probably several collections of material that is highly usable, many from public agencies, that if they are broken out of their agency and made available publically, would be very useful.

Social Security has put together a set of Best Practices for document accessibility. It is a brief description of the issue. It illustrates how the problem is solved, and gives sample code to show exactly how it is done. Targeted at developers.

The accessibility committee of the Accessibility Council of CIOs is collecting information across agencies that people can use and share.

Both federal government sources and outside sources should identify the leading authoring tools. Do we have any statistics on the different CMS tools, so that we can create templates specifically for the tools.

<Judy> questions on gathering: what templates, widget, other tools; which authoring tools does it align with; how share;

If we can find examples, and see that an agency gave out their code, that will encourage them to give out their code.

It goes back to the examples and pointing people to the correct locations.

WASP examples for teachers to give to students, the UMinn has hundreds of links of examples.

Web Accessibility Standards Project is done within the last year, it is oriented for beginners

UMinn at Duluth has 600-700 links to examples

Opera has done some work recently.

<Judy> When sharing links in email, please provide the link name, the link, one sentence describing the resource, one sentence mentioning questions for this task force to think about

While it is fine to have part of the project be educational in nature, I think that tends to be preaching to the choir, the person is already interested in accessibility. A much broader thing is building accessibility is putting accessibility into the tools.

Once we have an idea of what is available, then we can go public with the tool developers and apply pressure with a crowdsourcing effort which shows what can be built.

The CIO Council will pick segments and go to companies that make products that the government wants to perform better, and let them know that the government would like to see more accessibility built into those tools.

scribe: the first candidates will probably be document authoring tools. This gets away from 508 which allows picking the "most accessible tool" and toward getting tools that do what we really need them to.

[Judy explains W3C process for ATAG] to show we are at the proof of what can be done stage.

I would like to have 508 officials start asking vendors how well they comply with ATAG 2.0?

When TEITAC was finished in April 2008, ATAG was not as complete as it is today, and the Access Board did not want to take it up.

Some of the ATAG ideas have made it into the ANPRM. We aren't going for harmonization, but we are going for @@.

Tim Creagan said at the DC Barcamp, to suggest that people submit comments to the Access Board to add references to ATAG 2.0

A short list of required fields should be requested.

Are there other agencies we should be reaching out to? The IRS and SSA are the two that good for accessibility.

Send an email to NASCIO to ask them about states with good accessibility information.

We really want to know how close the resources are to being plugged in? Not educational but close to ready to use.

Collecting from vendors will be taken up when we have more people on the call. Rob Sinclair from Microsoft wanted to participate in this.

<Zakim> Judy, you wanted to raise the question of how to "vet" material

identifying priority gaps & suggestions of how to address

IS there a list of the top 10 useful things that people would want to go to a gallery for and get people building. Forms, templates, widgets?

CAPTCHA template, registration form, commenting form, more information about jQuery or other AJAX about the "More" button.

<Judy> 1) captcha template; 2) registration form; 3) comment form; 4) the "more" button (expanded info button)

a lightbox (something popped in the center of the screen to show more detail)

expandable, nested navigation

maps - how to make an accessible map template

<Judy> 5) lightbox popped up in center of screen to show more detail

<Judy> 6) accessible nested nav

disability.gov did an accessible media player

<Judy> 7) accessible map template

<Judy> 8) accessible video player

accessible media player

open street maps - Kate Chapman

calendar/date picker

<Judy> 9) calendar date-picker

directions in public transportation where you put in start and stop locations for getting directions. This could be a subset of the map template

a tag picker

<Judy> 10) accessible directions capability of maps

<Judy> 11) accessible filter for tag clouds

the best way to get the main content of the page.

skipnav, headings, landmark roles (ARIA)

<Judy> 12) best practice skip nav implementations

These are all building blocks - they are not at the shell of the page, they are parts of the page. This is good, but will people want the shell template of the page?

It would be convenient if there was a template for the page with all the headers and footers.

What about a template shell and the widgets in a menu that could be selected from a pulldown.

<Judy> 13) labels on forms

It wouldn't get in my way to have the accessible template shell, but I don't need the basics, I need the advanced functionality that provide what people need

<Judy> 14) checkbox option lists

But simple things are important, and many people are struggling with the basics. Basic forms are very necessary.

<Judy> 15) accessible wiki-markup type component

accessible wiki markup widget, a combination of text and wiki markup language.

preparing appeal for broader outreach to different communities

I would like to send out a broad message the first full week in September. There are other groups who may help us with crowd-sourcing. What ideas do we have for a message to help with gathering and building.

Once we have somewhere to send the information. Somewhere to put it.

scribe: and make sure you have approval to share the code.
... we can start twitter and an email list. To ask WASP and W3C. One of the other possibilities is from Peter Korn in the AEGIS project which is funded by the European Commission. The Australian and Canadian goverments are partnering with W3C right now.

Related to promoting it, have we figured out who will host it? I brought it up with @@ about hosting it.

It will be a focused discussion on our next call. There are multiple offers to host it.

scribe: we need to solve the "where" question before sending out the appeal.

What is the domain name? accessibility.gov. Also learnaccessibility.com could be donated to the project.

Communities for outreach: students are time sensitive because the semester is starting right now. Advanced cources might want to help with development.

<Judy> jc: univ of wash, through wendy

don't look for random students, look for focused people - Glenda Simms, HTML Writers Guild. Go to the bigger sources.

<Judy> jc: utx, through glenda

<Judy> jb: uwisc, through gregg

<Judy> jc: ugeorgia, leslie

Ann Walters in U-Georgia, Leslie Jensen-Inman U-Tenn

debra can send out through the California State University system.

Communities through the barcamp/unconference network

Jenisen Ascension. Should he join this discussion?

CSUN conference proposals - having a presentation at CSUN - in March, we can ask people to contribute.

Unconferences: Montreal today, London in September. We send out that list to the unconferences and ask for input.
... Toronto midsummer, Boston again

Jamal will work on a submission for CSUN - partnering with Judy

Judy has offered to draft a description of what we are asking for from the community.

scribe: that will be ready for the call next Wednesday.

Also ask for suggestions of how to run a bar camp in their local area.

It is important, but tangential, so we may want to point to it in a message from us. I think we want to have extended planning info on a wiki planning site.

next meetings

those responding said that Wednesday was better than Friday.

<Judy> ...though judy noted a conflict w/ Wednesday

<Judy> ...and said would do more schedule-checking online as people return from vacation

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2010/09/17 17:31:33 $