Re: Engaging stakeholders in the testing process

Hi Hadi,

These are great questions and thank you for the feedback. I'm glad that you
got access to the test harness.

   - I agree that both screen reader and browser makers should be included
   in the process. We already include AT developers in our process as outlined
   in the Working Mode document in our Wiki
   <https://github.com/w3c/aria-at/wiki/Working-Mode>. I think there may be
   room to better include browser makers in our process as well, or at the
   very least document how we handle situations where a failing test is caused
   by a browser and not a specific AT. I created issue #288
   <https://github.com/w3c/aria-at/issues/288> for this and put it on our
   agenda.
   - I created issue #289 <https://github.com/w3c/aria-at/issues/289> for
   the problem with the "Assign me" button and added it to the agenda. If I
   have time, I'll investigate this before our meeting next week.
   - I created issue #290 <https://github.com/w3c/aria-at/issues/290> for
   the problem of not being able to save the test results and added it to the
   agenda. If I have time, I'll investigate this before our next meeting.
   - I created issue #291 <https://github.com/w3c/aria-at/issues/291> for
   the question about switching to another conferencing tool like Zoom.

Thanks,

*Michael Fairchild, *CPWA
<https://www.accessibilityassociation.org/cpwacertification> *•*
*Senior **Accessibility
Consultant*

Deque Systems <https://deque.com>


On Tue, Aug 4, 2020 at 7:30 PM Hadi Rangin <hadir@uw.edu> wrote:

> Hello everyone,
>
>
>
> Thanks to Michael Cooper/Matt King, and Jon Gunderson I have now access to
> the test harness and got a tour in it.
>
> Earlier today, I looked into the menubar test case and tested the first
> task with Chrome and Jaws and NVDA. Assuming the menubar test code  has
> been done correctly, I am not getting the expected outcome. This would mean
> that either the browser and/or the screen readers are not doing the job
> properly.
>
>
>
> While I have no problem recording my observation, I strongly believe that
> both screen reader and browser makers should be part of this process to see
> first-hand how the information is rendered and trace any potential bugs in
> their system so they can fix the issues as we go. I understand that we want
> to record our findings but I believe our main goal is to help them to
> produce the expected output. If it is the main goal, I think we can achieve
> it a lot sooner and easier if they become part of this testing process.
>
> Maybe I haven’t understood the mission of this group but for me it is a
> typical collaboration that we have with various software companies. I
> always have them work and engage them in the testing process. It would be
> great if we can use a few minutes of our next meeting to talk why they are
> not engaged in this process.
>
>
>
> As I was using the test site, I noticed that the Assign me button in the
> Test Queue page is rendered by Jaws and NVDA as:
>
> “Assign me to the test run function(){var
> e=this.props,t=e.apgExampleName,n=e.atName,r=e.browserName;return"".concat(t,"
> for ").concat(n," on ").concat(r)}”
>
>
>
> unfortunately, My student and I were not able to save my test results. We
> clicked on it with Enter, space and mouse and I even screamed at it but it
> didn’t help! We took a screenshot from our test result for the case it is
> needed.
>
>
>
> I am also wondering if the team has any objection to switch to a more
> accessible conferencing tool like Zoom.
>
>
>
> Thanks,
>
> Hadi
>
>
>