W3C logo Web Accessibility Initiative (WAI) logo

WSTF Minutes 1 December 2003 Meeting

Agenda

agenda in e-mail list archives: http://lists.w3.org/Archives/Public/public-wai-eo-site/2003Dec/0004.html

Attendees

Minutes

[15:07] Shawn: Review of action items

Task List Groupings

[15:08] Shawn: Task list.

[15:08] Shawn: Blossom's proposal for regrouping sent to mailing list

[15:09] Blossom: I found these questions hard to group. I'm maybe 80% satisfied, not perfect, but has some meaningful grouping.

[15:10] Blossom: I'd be perfectly happy if someone found a better way to group.

[15:12] Shawn: Sailesh asked whether we should debate this. I'm on the fence about spending any more time on this. Should we acknowledge that the task list is going to be hard to process because it is so long, and leave it at that?

[15:12] Blossom: How do people feel about the groupings?

[15:13] Justin: My original one is almost exactly like Blossom's.

[15:13] Justin: What she has works for me.

[15:15] Carol: I think this is good, but we should agree on it and move on.

[15:15] MattSEA: Agree. We could spend forever on this and never get to the design part.

[15:17] Shawn: I'm not sure the task list is comprehensive. Let's look at different roles and make sure it's complete.

[15:19] Justin: Jon had the idea of an experience continuum, and people agreed that the continuum was a good idea, so I took his list and grouped it based on experiences.

[15:20] Shawn: Blossom, Justin, what do you think about munging your two lists and calling it done? See if that works for everybody, and if not then abandon the idea of grouping.

[15:20] Justin: OK.

[15:21] Blossom: Category called general resources?

[15:21] Shawn: I'm less inclined to group by resources. Justin's was document-centric, and I'd like it to be more idea-centric.

[15:22] Shawn: In organizing by documents it's problematic when you deal with online forms.

[15:23] Shawn: Could be a curriculum or tutorial as well.

[15:24] Blossom: If I'm looking for forms accessibility, I want to find all the resources I can.

[15:26] Shawn: Last call to think about the tasks. It'll be easier to do user roles once the list is finalized.

[15:26] carol: I'll look at this over the weekend.

Interim Revisions

[15:27] Shawn: Interim revisions. Blossom and I played around with some ideas.

[15:27] Shawn: Some said go ahead, some said where do we draw the line.

[15:28] Shawn: I was one who really wanted to make some changes.

[15:28] Shawn: I watched the video again of the user who was blind, and really wanted to make the changes.

[15:28] Shawn: However, I think it'd be harder to push through these changes than I originally thought.

[15:29] Shawn: I also want to push the redesign ASAP.

[15:30] carol: If we push, what is the process?

[15:30] Shawn: Includes explaining to the powers that be why we're making the changes we're making.

[15:30] Shawn: Issue is getting time with her to discuss it.

[15:31] Justin: Major roadblocks that are obstructing people?

[15:31] Shawn: A couple medium ones: Home page, nav, resources page.

[15:31] Blossom: How high in the priority list is making the site more accessible?

[15:32] Shawn: It was usability issues, not accessibility issues. I hear your point.

[15:33] ACTION: shawn revisit quick changes

[15:33] MattSEA: I volunteer to make the quick changes.

[15:33] Justin: Me too

[15:33] Blossom: me too

[15:34] Shawn: One issue that wouldn't change was creating an online request to join.

[15:34] MattSEA: Probably best that I do that, given work with the systems team.

Gathering Ideas

[15:36] Shawn: A lot of us have ideas on what to do. When Sailesh suggested gathering those, I said I thought it would be a distraction at the time. Another discussion on WAI-IG said we'd be looking for input from other folks. When is it appropriate to do that?

[15:36] Shawn: Meeting? Telecon? WAI-IG call for comments, personal connections?

[15:38] MattSEA: Wendy and I are probably going to SXSW in March. Could get a few designers into the fold.

[15:39] Shawn: We're planning for a prototype site by end of Feb. Could be good for usability phase.

[15:39] Justin: I know a designer who could help.

[15:41] Shawn: What about IG?

[15:42] MattSEA: Could be good, could be really bad. I'd suggest gathering comments, taking the ones that work and contacting them.

[15:42] Blossom: Lots of site surveys out there. Good way to gather information.

[15:43] Shawn: We need to gather the ideas we have, then give people who feel like they need to have a say that opportunity.

[15:44] Shawn: Not sure that we need to actively solicit feedback, though - since we already have lots.

[15:44] Blossom: What quantity is good enough to move forward, and how much is too much?

Information Architecture

[15:45] Shawn: Information architecture.

[15:45] Michael: How was the content I sent?

[15:47] Justin: brief overview would be helpful.

[15:48] Michael: Idea is that you take all of the content on the site, throw it on a table and let people sort it into buckets. From there, you close down what those buckets are, and where any outliers are.

[15:48] Michael: Typically, in the open sort you'll have good buckets.

[15:49] Michael: Things are conceptually very similar.

[15:50] Shawn: In the e-mail Michael sent talked about the importance of knowing the content and the totality of the information you want to present. My job was to work on the list.

[15:51] Shawn: I was surprised at how small and simple it was, and how it fell into buckets.

[15:52] Shawn: Michael, what is your availability for doing card sorting? How about others?

[15:53] Michael: My availability isn't great. I could do one or two sessions, but don't have time to do lots of sorting.

[15:55] ACTION: shawn Finalize list

[15:55] ACTION: Carol finish spreadsheet

[15:55] carol: I do 1x3 labels with mail merge and stick them onto 3.5x5 cards.

[15:58] Michael: It'll take an hour per person, and then an hour to gather the data.

[16:00] Michael: I can do 2 people.

[16:00] carol: I can do 3 people.

[16:01] Shawn: It would be good if you could coordinate on user characteristics. Use the same list as with UT recruiting. Could you send to the list characteristics of the people you do so that others can do different ones.

Design

[16:03] Shawn: I thought it'd be good to think about the next level of design before we break for the holidays.

[16:04] carol: The list is the hard part.

[16:05] Michael: Who's going to determine what goes into the gallery?

[16:06] Shawn: There's a page that talks about that.

[16:07] Shawn: Might want to list anything we want to add to the site in the next year.

[16:09] Michael: How do people feel about getting designers?

[16:09] Shawn: We have some resources.

[16:11] Michael: I could probably get a design firm to donate their services.

[16:11] Blossom: Me too. this good to get different designs and compare & choose.

[16:12] Michael: It might be good to find an agency that could produce mockups, colors, etc.

[16:12] Shawn: We agreed at the outset that we wanted to have a high design site. I like Blossom's idea that we solicit ideas, as long as they recognize that we may or may not use their design.

[16:13] Shawn: What we don't want is for people to reuse the current home page.

[16:13] Michael: I can contact some people.


Last updated $Date: 2003/12/08 18:21:41 $ by $Author: shawn $