A A A A A

Qualtrics Accessibility Interest Group

Collaborations

User Account

Qualtrics Accessibility Interest Group: Teleconference Details

Teleconference details

Agenda

Minutes

Alice identified five carry-over items to address – in addition to the issues list on ATHEN list
• Documentation
• General
• Navigation
• Styling
(http://collaborate.athenpro.org/group/qualtrics/issuesets/)

1. need to return to regular meeting dates/times, and include larger community

2. developers do not meet on these conference calls and need to be present

3. the definition that Qualtrics currently is using is 'usable by JAWS v.?, IE v?

4. The red/green buttons that are intended to indicate whether or not questions selected by those developing surveys are a problem (color denoting meaning), and I have experienced problem questions (Matrix) however the green – all is well with accessibility button is given

5. We have submitted several standards based solutions to make fixes, however, the implementation of the fixes often results in an even larger barrier (accessibility).

Bryce: Two of the above items can be addressed now:
Red /Green buttons will be fixed – by changing the Icon
Will get a developer on the phone in the future – resources now allocated

Hadi: Thanks extended to Bryce for bringing this to a higher management level

Neal: This is not said in anger, it’s just the way it is as I see it. UW purchased this application, now, it appears, it’s up to us to pay to make it work. That is not a business model I’m familiar with. Let’s say I can get over this. Jon wants to give them lines of code for particular modules. This is a band aid approach that will not likely work in the long term. What happens when jaws updates? what about window-eyes? What about system access? What about NVDA? Will the code still work? JAWS 12 has been out for 6 months. Yesterday they did an update to version 12. JAWS 11 has been out for about a year. Last month, they did an update to version 11. does the code still work? How many versions of internet explorer will this code work with? What about Firefox? What about safari on the Mac? And what happens when these browsers update? what happens when Apple decidesto update VoiceOver? Will the code work?

I don’t think we can keep going down this road forever. Qualtrics has to learn enough from our findings, to be able to know that what they do is accessible in the future. I believe this is

what they are willing to do.

I sent these notes to Alice after the call so she wouldn’t have to take notes on them during the call. I think the rest of the minutes will show that we are heading in the right direction. Only problem is, do we have any money left after doing this for two years to keep working on this.

Bryce: Confident that engineers will be able to proceed after this process to address future changes and the changing world of browsers and assistive technologies.

Neal: Is a Qualtrics-lite a better long-term solution – starting over with a lite version that works?

Hadi: does a lot of testing with lots of products – do we have a list of what questions actually work and don’t work.

Bryce: There are question types that are at this time identified by Qualtrics as being accessible:
http://www.qualtrics.com/university/accessibility/

Alice: Qualtrics needs to make a survey that illustrates each of the accessible question types.
Neal: Add an edit field to identify assistive technology used, browser, and platform including versions

Hadi: Wants to make sure that the data is not lost.

Alice and Neal: We have to be able to record data immediately, while taking the survey, rather than go to survey, and then go to another data base.

Hadi and Neal: There should not be a link for screen reader version.
Alice: those creating surveys, assume when signaled “accessible” that it includes keyboard accessibility, text enlargement, in addition to screen reader specificity.

Action Items:
Qualtrics (Bryce) will develop a survey for testing that includes the questions that are identified as accessible – will add next and back button and progress bar.
We will be able to access the data from that survey – through a public report link

Alice and Bryce (and others who do not use AT) will tab through survey to test via keyboard only, and also identify platform, browser, and

Then, a follow-up phone call to identify problem and solution – very specific and focused will be scheduled and follow. Participants of this call must have taken the survey.

Time line: – Bryce will have survey by end of week and send out link to take, and link to view results. – Next call will be scheduled with the developers ASAP after survey taken.

Participants