-
Notifications
You must be signed in to change notification settings - Fork 0
Meeting Archive
- Working session for "Navigating the WAI Website"
- Spreadsheet of resources
- Discuss survey to solicit pain points of navigating WAI
- How to distribute survey
- One of the first activities is to survey community to get more concrete evidence of issues people have with finding information on WAI
- Also look at how to express the WAI contents in a way that works for more people, as we don't have the ability to change the information architecture of the WAI site
- needs different ways to show the mappings of content
- how are we going to define the resources (skill level, type of resource, for example)?
- Anya noted curricula pages - could be good example of how to arrange pages/map pages
- Kris Anne has created a Google doc to create survey questions for group to contribute
- need to figure out the best survey platform to use
- need to figure out how to send out the survey to reach a wide audience
- should we consult with WAI staff about content/context of survey?
- Anya suggested that the underlying structure of the resource is based on WCAG success criteria, so that when referencing a resource, there would be a natural mapping to other related resources
- Suggestion made that we start the survey on a smaller group of people to help the initial direction, then go wider for more input
- Suggestion made to look at some of the surveys that the COGA task force has done to get info about content preferences of neurodivergent people
Next Steps
- Contribute survey question ideas to Google doc
- Will need to request access
- New members?
- Discuss Navigating the WAI Website resource
- Welcome New Members
- Review scope docs for two resources
- Welcome new members
- Scope/Requirements documents
- Where to host requirements
- GitHub issue? Wiki? Markdown page?
- What to include in docs?
- Process to iterate on requirements
- Where to host requirements
- Preparing for publication
- Review community group name
- Help with site design and development
- Discuss scope of current resources
Attendees: Frankie, Len, Andrew, Laurie, Brian and Kris Anne
-
Name change - want to do that so we can get everything updated before we begin to publish resources.
-
Does anyone know designers who could help us design the Github page we are using to publish our resources? We'd like it to look professional to show off all our good work.
-
New Resources in Github.
Three in Github currently
- Procurement
- Resources for young coders
- WAI finding for the W3C website
What new resources would people want?
- accessible templates?
- how to guides?
- playbooks like...
- Conference presentations?
What will get people involved? Capacity questions? Who has time? What are your strengths that you can bring to the group? Where can we brainstorm asynchronously? Not just the issues in Github, because some things could get lost in that long issue. Can we use the wikis if we can figure out editing? Maybe Slack? Meetings for resources could happen in smaller groups, and then overall meetings could be to come together and get together about it.
- Review of topic ideas
- Brainstorm of new ideas
Attendees: Chris, Judith, Kris Anne, Brian
- Reviewed topic ideas
- Looking to move forward with the ideas in September and want people to take lead on resources
- Chris is interested in procurement
- need to shape it well for the people that are doing procurement, because they most likely won't become experts.
- want to pull in existing resources and fill in gaps
- make it as easy as possible
- Show what a mature model for procurement is but then start with small iterative steps.
- Brian to take lead on Teaching a11y to young coders
- Will be pushing forward in first week of Sept.
- Kris Anne will lead or co-lead on the Wayfinding resource
- will coordinate with Shawn
- After meeting, will create project pages to list scope, lead editor(s), contributors, etc.
Cancelled
- Review of previous meeting
- Questions about work statement, etc.
- Meeting invitations
- GitHub walk-through
https://www.w3.org/2024/07/30-adva11yresources-minutes.html
- Introductions
- Work statement
- Discuss the ideal meeting time
- How do we include everyone considering a large disparity in time zones?
- Review Community Group Name
- Solicit help
- Site design
- Site development
- Begin to submit ideas for resources
Participants: Judith Hellerstein, Mike Gifford, Sharron Rush, Shawn Henry, Sylvie Duchateau, Andrew Arch, Chris O'Brien, Frankie Wolf, Jade Matos-Carew, Brian Elton, Kris Anne Kinney, Dr M. Shabbir, Scribe: Kris Anne Kinney
Brian reviewed the Agenda
Brian: Reviewing the Work statement listed in the Agenda
Sharron: Question, the process you spoke about, the approval process, will there be no approval process?
Brian: so people can write their own resources and they will be part of our own website, not WAI.
Sharron: Ok, so if that is the case, how do we enforce credibility or quality?
Brian: Let me explain the workflow part and then we'll address that question.
... Someone can head a resource with a small team if needed.
... Keep checking in with the larger group.
... Publication will happen only on internal Github pages, not published on WAI.
... We can discuss it as a group, and make sure it's credible and correct.
... we want people to put their names against the resources. What will you take credit for?
Sharron: I don't want to cause confusion if we don't have consistency. If it's written and published by the W3C people expect this to be a good resource.
Brian: We still as a group will vet the resources and if there is something strongly opinionated we can give another side. We can work to weed out things that will be confusing or one-sided. Trying to find a balance between letting people create resources they want but making them valuable for a wide range of people.
Jade: I agree that there needs to be a process in place of standard setting. If we want to set ourselves apart we need to have a process in place. It can be collective credibility.
Brian: If the whole part of a working group is consensus building and when it's in place, resources sometimes don't get made. They don't have to reach a consensus to create a resource. We do want resources that are well-reviewed and it's a good resource and not just a collection of individual contributors.
... everything is up for review and feedback and adjustment.
... if a workflow we can adjust that too.
... We have many ways to keep in touch.
... We do want participants to be active participants. Keep up on the group itself, and be part of at least one work stream.
... ALL of this is up for change and editing.
Brian: We don't have to discuss this now, we can do it in Github. We want meetings to be efficient and do things offline.
...hoping for biweekly meetings. changing times/days to help match up times for others.
... once a month you should be able to join because it fits your timezone.
... basing it off ET but we are flexible.
... any major disagreements with this?
Judith: Maybe we should use UTC time so it adjusts automatically for people.
Brian: I will pick days/nights and set up calendar items. If there is a lot of times people can't join, we can adjust.
Brian: https://github.com/w3c-cg/aar/issues/3 ... Please put name ideas in that github issue.
Brian: If you know of any designers who can help us with web page structure or a logo, please let us know. It can be a simple site for now, but we would like it to visually appealing. Its based off of Github, so it can be consistently managed for edits and PRs. Mike: There was a slack discussion about how github is setup and where they are moving to. Brian: We don't need a huge integration just yet.
Brian: There is still an avenue to publish on the WAI website. We just need to engage with Shawn the whole way through.
Shawn: We have a new content specialist joining in August.
Brian: With the Content editor we can have less formality on publications.
Kris Anne: I am hopeful we can still participate with WAI to help with input on updates and fixes for the current WAI resources.
Shawn: I do hope that once we come up with her priority list we can do that.
Brian: If you have a resource you want to champion and push forward, submit an idea on Git Hub.
https://github.com/w3c-cg/aar/issues
Note: We were unable to save the chat in its entirety. What follows are the key comments
Andrew: Workflow states: The wider group will do final review. Is more needed?
Mike: We do so need better procurement guidance
Chris: I was thinking the same.
Andrew: Hear Hear to procurement
Note: Procurement links were pasted into the chat. These have been captured in issue #4
Jade: A lot of the resources don't address the reality of being stuck in a procurement process with loads of pushy finance people and project deadlines and suppliers who don't know anything!
Mike: (referring to communication methods) There is W3C Slack too.
Mike: On procurement, there is also https://acreditor.section508.gov which is a lot differeent from the great ACR work for WCHA-EM. I was on the team developing OpenACR so a bit biased. But there is a lot of confusion around Accessibility Reporting formats.
Mike: (referring to multiple meeting times) That sounds like a good approach. UTC avoids annoying daylight savings issues too. ET is a better home (than EST or EDT)
Mike: (referring to meeting time) It can always be moved later if we find folks can't come. Monday & Friday are always bad.
Jade: Maybe a mix of Tuesdays and Wednesdays?
Frankie: How do we get on the W3C Slack? Seems I don't have it.
Mike: I can invite you (as can anyone who is part of the Slack I think). (emails exchanged in chat. redacted here for privacy)