Meeting minutes
Accessibility Evaluation Tools List
Current prototype: https://
Charlotte: I will share my screen to highlight some of the new features. I've been working with Vera and Eric on the project since September. We want to share the newest iteration based on the user testing we did last week and we found overall our users we happy with the general design, made some suggestions for small improvements. Half of our users were accessibility beginners, a few were lecturers and our user group had various levels of experience in accessibility with technical skills from nearly none to expert.
… shares prototype
Charlotte: We have implemented some of the feedback we got from our tests. They mostly were very complementary of the design, one comment about "wall of text" but understanding of what the needs were. They liked the filtering system but many overlooked it - we changed the color pattern to make it more visible.
… the filter assistant has been changed since we last shared it. Using the tool actually helped some of them understand that there was more to accessibility than they has assumed. A big issue was that people who were unfamiliar with the Guidelines (like the desingers) felt that the tool was very technical and was not really meant for them. Example "progressive enhancement" mentioned in A-checker
… they did not see terms that they did recognice (example clor/contrast) We thought about how to make newbies feel more welcome. May ask pvendors to talk about their tool in words that are easier to understand. May not be feasible for all vendors but might be good to encourage plain language, short sentences. Any suggestions from this group?
Laura: Speaking to your question, what is under 'sort by'?
Charlotte: Alpha, most recently updated, etc Most people are looking for most recently updated but it was rejected as a solution because it could be a way for vendors to rig the system.
Sharron: Still seems the best solution to me
Laura: +1
<shadi> https://
<shadi> - Role: Designer, Developer, QA, Learning/Teachning
Shadi: Thanks for all this work - it looks great! On your specific question if we would resort by recent updates, it might be better. You seem to be collecting data as you test. Eric (previous editor) had a filter by role - have you consdiered doing that? Roles like teaching, developer, designer, QA. It may be a filter that is presented differently like a tab or something that allows people to identify?
Charlotte: (shows a previous filtering option) Like this perhaps? We tried this and those users were a bit skeptical, what if the filter chooses the wrong things for me?
<BrianE> +1 to allow filtering by job role
Shadi: Maybe changing the wording to instead of it being my identity it may be more friendly to identify the task.
Charlotte: Vera had a suggestion to choose filters in that way roles/task baced. We also considered to maybe let two vendors provide those roles or a difficulty rating. Some of the ideas we are considering.
<Laura> +1 to sorting by role
Mark: What you've done here is fantastic! +1 from me for the filter moved to the top. We may have people who don't fall into those roles precisely - also need to think about a procurement role, maybe able to select more than one role.
… we are so locked down what we can use, we need to see if it works in the one browser that we are able to use in government. I do see the need for the job role filter but may need to expand it.
… maybe as Shadi said, maybe it is task based, what are you trying to do.
… some may not know what box they fit into, the roles may not mean that much to them.
Charlotte: We will explore roles, vs tasks and option to filter along those lines.
… if anyone wants to suggest anything, we will add that to the weekly survey.
Shadi: Mark I don't thisnk this is only government I think role defintion is always hard. Another thought I had was the distinguish between role/task and the level of expertise. We need to keep these separate. Second thing was have you considered a way to skip any of the questions in the filter assitant? Maybe rather than the banner across the top for the role/task make it part of the filter assistant, like a Swiss army knife.
Charlotte: We do have the capability to skip a question but participants did not use it. They tended to do extra work, so we concluded that we need to explain the skip capacity more clearly.
Shadi: It was also not clear to me that at any point in the filtering process you can show results.
Charlotte: Also wanted to share with you the changes to the filter list. We noticed that several of the filtering terms are unclear. We may need to add many more info buttons. Vera and I are not accessibility experts ourselves and may need some guidance about the exact input for the info boxes. If anyone would like to volunteer to help us, we want to be sure it is correct and informative since the info boxes are used a lot.
Charlotte: The accessibility checks are now based on beta 2.1 and there may some things that are not well named so we will ask a question about that in the survey. Media type was not understood at all - text, video, audio, etc.
… will ask for input about that.
BrianE: In the ask for help with the tool tips, I am not a content expert but I can provide technical suggestions.
Daniel: Appreciate the work, it is looking so good. I agree with Brian that it needs technical support for accessibility.
… especially the heading structure.
Charlotte: We will implement this (showing screen) and want to be sure that people use it in the way we expect.
… we show the toggle on 'and' when we choose more than one
Brent: What's the use case for 'or'
Charlotte: We are not sure we will find much use of it, but we wanted to be sure people understand that this works differently.
… want to be sure that the filters list includes all the checks and not necessary to do them one at a time.
Shadi: If I remember correctly, the QuickRef presents 'or' vs 'and' visually differently.
Shadi: (shares QuickRef screen)
<shadi> https://
Charlotte: Lecturers have asked for tools that test a prototype or design that is not yet online. Want to know if such a tool exists.
Shadi: At this point I am not aware of such tools being submitted to the list.
Brent: Do we have a way to suggest a category that are not currently listed?
Charlotte: Maybe so, example VR accessibility tools
Shadi: Prototypes might be hard to meet, may be more of a wish list, don't see how the implementation would work.
Charlotte: More tools could be added for designers but are not there yet.
Shadi: Good point like designer tools (IBM, Adobe) that are plugins to authoring tools. May be a way to add such plugins to the Tools List.
Charlotte: Would anyone know how to search for it - authoring plugin? We would like to improve the link between the Tools List and other WAI resources. We would like suggestions for which resources and where to put them. In the filter assistant?
… maybe helping them to know more about how to do manual tests.
Brent: Any additional questions for Charlotte?
WAI Curricula Content Author Modules
<dmontalvo> Previous work
<dmontalvo> Text Alternatives
<dmontalvo> Data Visualizations
<dmontalvo> Proposal:
<dmontalvo> Images
<dmontalvo> Data Tables
<dmontalvo> e
Daniel: This is a question on the inclusion of the concept of data visualization. The modules are meant to help content authors, editors, not just writers. We tried two different modules one that covers short image description and another one for more complex image content.
… we realized last week that it was not working. One issue was that splitting it into two separate modules breaks the previous pattern. Another issue is that not all complex images can be understood as data visualization.
… with that in mind, the TF recommends to change the name and scope of the two modules.
… had discussed text alternatives in two separate modules. Have redefined so all text alternatives will be discussed in one module. The reference to data visualization will be referenced in both images module (including simple and complex) and in the data tables module.
Daniel: Still a rough draft and need to allow EO to weigh in.
Sharron: Makes sense to me now that I understand it.
Brent: So the links are to previous and current and we will ask if it is OK with everyone to move forward with this structure.
Daniel: The first question is does this make sense? Second is other than cross referencing what other ideas do you have about addressing data visualization and how we can help instructors to teach this complex topic?
Brent: Any other comments?
Daniel: We'll have Starfish survey by next week and meanwhile will put a couple of questions in the weekly survey
EOWG Face to Face meeting
Brent: Two meetings in consideration, will make both of them fully hybrid meetings for inclusion of remote participation. First is in May at AccessU in May and second in Vancouver in September for TPAC. We have confirmed the dates for May, highest selected days were the Friday and Saturday after the conference. Wanted to check in with those who will join remotely. May 13 and 14 seem to be the dates that have risen to the top.
Mark: It is not going to be feasible to participate on the weekend and even Friday evenings will be doubtful.
<Jade> +1 what Mark said
Brent: Hearing the problematic nature of Friday (afternoon and evening in Europe) and Saturday as part of the weekend.
Sharron: Also will try some of the asynchronous methods we are using for AccessU to provide a more immersive experience for those participating remotely.
Brent: Review of locations. Look at survey and feel free to suggest others
Daniel: I want to note my agreement that it will be difficult to participate remotely during a weekend time and Friday evening too.
Wrap
Sharron: Please watch for the weekly survey there will be a few items for review and input and look at W4TW. Thanks all, have a good weekend, bye