Sakai Accessibility Working Group Updates/Questions
Chris Knapp
Good morning,
Hope everyone’s February is off to a great start!
Unfortunately, we didn’t have anyone show up to last Friday’s Sakai Accessibility Working Group meeting so I thought I would send out a quick email to provide a couple of updates…
First, on today’s Core Team call Shawn Foster and I discuss SAK-45795 which has to do with a keyboard trap happening in the “Forums” tool when using a Google screenreader extension.
I am going to go back and do some additional testing to see if I can replicate the issue using JAWS and/or NVDA but it brings up the bigger question of whether we should post something somewhere that list out all Sakai supported browsers and screen readers??
For example, during our interactive test session this past Thursday, Gonzalo (who is the Accessibility Lead for the University of Michigan) suggested that we maybe stick to JAWS, NVDA and Voiceover as the screen readers that we test for/support.
I said that we could also make an argument for adding in the Orca screenreader for Linux users, but I think its probably a pretty small percentage of folks we’re talking about.
I guess what I’m getting at, is that because we have limited QA and developer time and resources to dedicate toward accessibility testing and fixes, would it make sense to list out the Sakai supported browsers and screen readers? And if the answer is ‘yes,’ than which browsers and screen readers do you think should be included on our list of those supported by Sakai?
Please email me if you would like to provide your feedback—I will consolidate the responses so we can review/discuss during an upcoming Sakai Accessibility Working Group meeting.
Second, I am looking for one or more volunteer(s) to help me with updating/maintaining the “Accessibility Working Group” page on the Sakai Confluence site.
I have been able to capture the notes from our most recent meetings (see below)—I could just use some assistance with updating/maintaining our “Accessibility Working Group” page on the Confluence site.
In addition to keeping up on our meeting notes (again, I am willing to continue to write-up the notes at the conclusion of our meetings and hand them off to a designated helper) we probably need someone to go through and review content and revise/update it as necessary.
Please let me know if you are able to help out.
Below are those meeting notes I reference above…
Sakai Accessibility Working Group – Meeting Notes:
Friday, February 4
Nobody showed up – spent the time working through accessibility-related Jira tickets in our “WAM-A11Y” filters.
Friday, January 21
Only Sophie Poost from AAPD and I were on the call.
I shared copies of the Sakai 21 and Sakai 22 test scripts with her and said that she could reference these to try and troubleshoot any issues that their interns might be running into with Sakai.
Also shared a link to the Sakai User Guide.
We used most of the rest of the meeting to do an interactive test session…
I demoed the new Conversations tool.
I also showed her our “WAM-A11Y” filter in Jira and talked through our review process.
Friday, January 7
Terry Golightly and John Buckingham attended.
Shared the link to Josh’s Calenderly poll to determine a day/time for the virtual focus group session for people to provide input on accessibility considerations that should be considered as part of the Sakai technical Road Map.
This session has since been scheduled for Friday, January 14 at 2pm.
Also updated Terry and John on the latest developments RE: the Sakai accessibility/VPAT plan:
*Completed testing on the “Sakai 21 Accessibility Regression Test Script”
*Mentioned how Chandrika and Ujwala (two of Dede’s student workers at Marist) are going through and completing the “Sakai 22 Accessibility LITE” test script which involves doing preliminary keyboard testing of the test script that we use for our accessibility testing
*Continue to work on building out several new tabs which were added to the Sakai 22 test script—have completed tabs for “Calendar” and “Discussions/Forums/Conversations” so far and still need to add “Contact Us,” “Dropbox,” Polls,” “Profile,” and “Sylabus”
*Vision-Aid has begun testing on the new Sakai 22 test script—will start with testing all of the new tabs that have been added to the Sakai 22 test script, and then will test all of the high stakes tools (i.e. Tests & Quizzes, Lessons, Assignments, Gradebook, Rubrics, etc.) and then finish with testing the remainder of the tabs.
*Chris continues to work with Shawn and Gonzalo to refine the new “WAM-A11Y Jira Review Process” to work through the backlog of accessibility-related Jiras.
*EDF is going to have a developer dedicated to working on accessibility-related fixes—Chris to follow-up with Miguel next week when he is back in the office.
Spent the rest of the meeting discussing accessibility issues that Terry and John thought should be flagged to be worked on by the EDF developer.
Terry mentioned that when she is logged in as admin on 21, and she is trying to search for a Course, for example, the border of the search box is almost inperceivable to a low vision user – this might be a color contrast issue, or because the line used for the border is only one pixel thick, or some combination of these)
John brought up SAK-45731
Terry mentioned a similar issue with the checkmarks used on the checklists in Lessons – how when they are checked on they turn to a grey color that has poor contrast with the background.
Terry suggested that the developers might not have access to a good external color checker tool to use during the development process and provided information about the following color picker that she has used and really likes.
https://www.tpgi.com/color-contrast-checker/
|
|
Need Additional Color Contrast Help? Evaluating your design for color contrast is a critical aspect of accessibility testing and organizations may benefit from appropriate user experience training and expertise to ensure proper contrast. |
Again, thank you for your time/consideration.
Chris Knapp
Accessiversity CEO and Managing Member, Knapp Strategic Projects & Consulting LLC
Leave Your Print On A More Accessible World!