WebAIM - Web Accessibility In Mind

E-mail List Archives

Thread: Canvas Accessibility Testing & Evaluation Project

for

Number of posts in this thread: 6 (In chronological order)

From: Hadi Rangin
Date: Mon, Apr 04 2016 10:02AM
Subject: Canvas Accessibility Testing & Evaluation Project
No previous message | Next message →

[Sorry for cross-posting]

Hello everyone,

We are finally ready to publish the result of Canvas Accessibility Testing & Evaluation Project.
Thanks to Instructure and all colleagues and friends who collaborated on this complex and time-consuming project.

You can find the comprehensive report, testing & evaluation results, as well as the CSUN 2016 presentation at:
http://blog.bargirangin.com/2016/04/canvas-testing-evaluation-cate.html

Thanks,

Hadi Rangin
IT Accessibility Specialist
Mary Gates Hall 064C
University of Washington
Phone: (206) 685-4144, Direct: (206) 221-1532
E-mail: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >

From: Lucy Greco
Date: Mon, Apr 04 2016 2:32PM
Subject: Re: Canvas Accessibility Testing & Evaluation Project
← Previous message | Next message →

thanks for sharing this. i have to questions.

1 why didn't you test the instructor interface.?
second i see several references to how jaws did some thing or did not
do some thing i.e. in a dialog jaws users were able to read content out
side of the dialog.in your introduction you spoke about using nvda was the
testing results different for nvda? if not you should indicate for the
screen reader user not for jaws. i think from my experience with the system
in nvda you are using the turn jaws to mean all screen readers. please
confirm lucy

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


On Mon, Apr 4, 2016 at 9:02 AM, Hadi Rangin < = EMAIL ADDRESS REMOVED = > wrote:

> [Sorry for cross-posting]
>
> Hello everyone,
>
> We are finally ready to publish the result of Canvas Accessibility Testing
> & Evaluation Project.
> Thanks to Instructure and all colleagues and friends who collaborated on
> this complex and time-consuming project.
>
> You can find the comprehensive report, testing & evaluation results, as
> well as the CSUN 2016 presentation at:
> http://blog.bargirangin.com/2016/04/canvas-testing-evaluation-cate.html
>
> Thanks,
>
> Hadi Rangin
> IT Accessibility Specialist
> Mary Gates Hall 064C
> University of Washington
> Phone: (206) 685-4144, Direct: (206) 221-1532
> E-mail: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
>
> > > > >

From: Robert Fentress
Date: Mon, Apr 04 2016 2:47PM
Subject: Re: Canvas Accessibility Testing & Evaluation Project
← Previous message | Next message →

Hi, Lucy.

We tested both the Teacher and Student interfaces to some degree. Due to
the complexity involved, we were not able to test everything, but we
covered both roles to some extent. We tested with both JAWS and NVDA, as
well as VoiceOver and the results did differ in interesting and important
ways, I think. We did not really generalize to say screen reader users as a
whole could do a certain thing, though I suppose one could make that
analysis to some degree from the data.

Best,
Rob

On Mon, Apr 4, 2016 at 4:32 PM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:

> thanks for sharing this. i have to questions.
>
> 1 why didn't you test the instructor interface.?
> second i see several references to how jaws did some thing or did not
> do some thing i.e. in a dialog jaws users were able to read content out
> side of the dialog.in your introduction you spoke about using nvda was the
> testing results different for nvda? if not you should indicate for the
> screen reader user not for jaws. i think from my experience with the system
> in nvda you are using the turn jaws to mean all screen readers. please
> confirm lucy
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
> On Mon, Apr 4, 2016 at 9:02 AM, Hadi Rangin < = EMAIL ADDRESS REMOVED = > wrote:
>
> > [Sorry for cross-posting]
> >
> > Hello everyone,
> >
> > We are finally ready to publish the result of Canvas Accessibility
> Testing
> > & Evaluation Project.
> > Thanks to Instructure and all colleagues and friends who collaborated on
> > this complex and time-consuming project.
> >
> > You can find the comprehensive report, testing & evaluation results, as
> > well as the CSUN 2016 presentation at:
> > http://blog.bargirangin.com/2016/04/canvas-testing-evaluation-cate.html
> >
> > Thanks,
> >
> > Hadi Rangin
> > IT Accessibility Specialist
> > Mary Gates Hall 064C
> > University of Washington
> > Phone: (206) 685-4144, Direct: (206) 221-1532
> > E-mail: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
> >
> > > > > > > > > >
> > > > >



--
Robert Fentress
Senior Accessibility Solutions Designer
540.231.1255

Technology-enhanced Learning & Online Strategies
Assistive Technologies
1180 Torgersen Hall
620 Drillfield Drive (0434)
Blacksburg, Virginia 24061

From: Lucy Greco
Date: Mon, Apr 04 2016 2:52PM
Subject: Re: Canvas Accessibility Testing & Evaluation Project
← Previous message | Next message →

thanks rob. i wonder then in the spots of the report wair you speak about
jaws then is it just jaws that had the problem or did nvda have the same
problem. i.e. the dialog and jaws not beeing restricted to the dialog.
thanks again for doing all this hard hard work lucy

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


On Mon, Apr 4, 2016 at 1:47 PM, Robert Fentress < = EMAIL ADDRESS REMOVED = > wrote:

> Hi, Lucy.
>
> We tested both the Teacher and Student interfaces to some degree. Due to
> the complexity involved, we were not able to test everything, but we
> covered both roles to some extent. We tested with both JAWS and NVDA, as
> well as VoiceOver and the results did differ in interesting and important
> ways, I think. We did not really generalize to say screen reader users as a
> whole could do a certain thing, though I suppose one could make that
> analysis to some degree from the data.
>
> Best,
> Rob
>
> On Mon, Apr 4, 2016 at 4:32 PM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
>
> > thanks for sharing this. i have to questions.
> >
> > 1 why didn't you test the instructor interface.?
> > second i see several references to how jaws did some thing or did
> not
> > do some thing i.e. in a dialog jaws users were able to read content out
> > side of the dialog.in your introduction you spoke about using nvda was
> the
> > testing results different for nvda? if not you should indicate for the
> > screen reader user not for jaws. i think from my experience with the
> system
> > in nvda you are using the turn jaws to mean all screen readers. please
> > confirm lucy
> >
> > Lucia Greco
> > Web Accessibility Evangelist
> > IST - Architecture, Platforms, and Integration
> > University of California, Berkeley
> > (510) 289-6008 skype: lucia1-greco
> > http://webaccess.berkeley.edu
> > Follow me on twitter @accessaces
> >
> >
> > On Mon, Apr 4, 2016 at 9:02 AM, Hadi Rangin < = EMAIL ADDRESS REMOVED = > wrote:
> >
> > > [Sorry for cross-posting]
> > >
> > > Hello everyone,
> > >
> > > We are finally ready to publish the result of Canvas Accessibility
> > Testing
> > > & Evaluation Project.
> > > Thanks to Instructure and all colleagues and friends who collaborated
> on
> > > this complex and time-consuming project.
> > >
> > > You can find the comprehensive report, testing & evaluation results, as
> > > well as the CSUN 2016 presentation at:
> > >
> http://blog.bargirangin.com/2016/04/canvas-testing-evaluation-cate.html
> > >
> > > Thanks,
> > >
> > > Hadi Rangin
> > > IT Accessibility Specialist
> > > Mary Gates Hall 064C
> > > University of Washington
> > > Phone: (206) 685-4144, Direct: (206) 221-1532
> > > E-mail: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
> > >
> > > > > > > > > > > > > > >
> > > > > > > > > >
>
>
>
> --
> Robert Fentress
> Senior Accessibility Solutions Designer
> 540.231.1255
>
> Technology-enhanced Learning & Online Strategies
> Assistive Technologies
> 1180 Torgersen Hall
> 620 Drillfield Drive (0434)
> Blacksburg, Virginia 24061
> > > > >

From: Robert Fentress
Date: Mon, Apr 04 2016 3:01PM
Subject: Re: Canvas Accessibility Testing & Evaluation Project
← Previous message | Next message →

Yes, I would say, generally, if we say in the report that something didn't
work with JAWS, we are only saying that. For instance, as I understand it,
there were certain freak outs (to use the technical term) that were only
experienced with JAWS. For the specifics though, I'd make reference to the
Excel file, as it breaks things out by AT quite explicitly.

On Mon, Apr 4, 2016 at 4:52 PM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:

> thanks rob. i wonder then in the spots of the report wair you speak about
> jaws then is it just jaws that had the problem or did nvda have the same
> problem. i.e. the dialog and jaws not beeing restricted to the dialog.
> thanks again for doing all this hard hard work lucy
>
> Lucia Greco
> Web Accessibility Evangelist
> IST - Architecture, Platforms, and Integration
> University of California, Berkeley
> (510) 289-6008 skype: lucia1-greco
> http://webaccess.berkeley.edu
> Follow me on twitter @accessaces
>
>
> On Mon, Apr 4, 2016 at 1:47 PM, Robert Fentress < = EMAIL ADDRESS REMOVED = > wrote:
>
> > Hi, Lucy.
> >
> > We tested both the Teacher and Student interfaces to some degree. Due to
> > the complexity involved, we were not able to test everything, but we
> > covered both roles to some extent. We tested with both JAWS and NVDA, as
> > well as VoiceOver and the results did differ in interesting and important
> > ways, I think. We did not really generalize to say screen reader users
> as a
> > whole could do a certain thing, though I suppose one could make that
> > analysis to some degree from the data.
> >
> > Best,
> > Rob
> >
> > On Mon, Apr 4, 2016 at 4:32 PM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
> >
> > > thanks for sharing this. i have to questions.
> > >
> > > 1 why didn't you test the instructor interface.?
> > > second i see several references to how jaws did some thing or did
> > not
> > > do some thing i.e. in a dialog jaws users were able to read content
> out
> > > side of the dialog.in your introduction you spoke about using nvda was
> > the
> > > testing results different for nvda? if not you should indicate for
> the
> > > screen reader user not for jaws. i think from my experience with the
> > system
> > > in nvda you are using the turn jaws to mean all screen readers. please
> > > confirm lucy
> > >
> > > Lucia Greco
> > > Web Accessibility Evangelist
> > > IST - Architecture, Platforms, and Integration
> > > University of California, Berkeley
> > > (510) 289-6008 skype: lucia1-greco
> > > http://webaccess.berkeley.edu
> > > Follow me on twitter @accessaces
> > >
> > >
> > > On Mon, Apr 4, 2016 at 9:02 AM, Hadi Rangin < = EMAIL ADDRESS REMOVED = > wrote:
> > >
> > > > [Sorry for cross-posting]
> > > >
> > > > Hello everyone,
> > > >
> > > > We are finally ready to publish the result of Canvas Accessibility
> > > Testing
> > > > & Evaluation Project.
> > > > Thanks to Instructure and all colleagues and friends who collaborated
> > on
> > > > this complex and time-consuming project.
> > > >
> > > > You can find the comprehensive report, testing & evaluation results,
> as
> > > > well as the CSUN 2016 presentation at:
> > > >
> > http://blog.bargirangin.com/2016/04/canvas-testing-evaluation-cate.html
> > > >
> > > > Thanks,
> > > >
> > > > Hadi Rangin
> > > > IT Accessibility Specialist
> > > > Mary Gates Hall 064C
> > > > University of Washington
> > > > Phone: (206) 685-4144, Direct: (206) 221-1532
> > > > E-mail: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
> > > >
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> >
> >
> >
> > --
> > Robert Fentress
> > Senior Accessibility Solutions Designer
> > 540.231.1255
> >
> > Technology-enhanced Learning & Online Strategies
> > Assistive Technologies
> > 1180 Torgersen Hall
> > 620 Drillfield Drive (0434)
> > Blacksburg, Virginia 24061
> > > > > > > > > >
> > > > >



--
Robert Fentress
Senior Accessibility Solutions Designer
540.231.1255

Technology-enhanced Learning & Online Strategies
Assistive Technologies
1180 Torgersen Hall
620 Drillfield Drive (0434)
Blacksburg, Virginia 24061

From: Lucy Greco
Date: Mon, Apr 04 2016 3:45PM
Subject: Re: Canvas Accessibility Testing & Evaluation Project
← Previous message | No next message

thanks so much for the quick responces

Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces


On Mon, Apr 4, 2016 at 2:01 PM, Robert Fentress < = EMAIL ADDRESS REMOVED = > wrote:

> Yes, I would say, generally, if we say in the report that something didn't
> work with JAWS, we are only saying that. For instance, as I understand it,
> there were certain freak outs (to use the technical term) that were only
> experienced with JAWS. For the specifics though, I'd make reference to the
> Excel file, as it breaks things out by AT quite explicitly.
>
> On Mon, Apr 4, 2016 at 4:52 PM, Lucy Greco < = EMAIL ADDRESS REMOVED = > wrote:
>
> > thanks rob. i wonder then in the spots of the report wair you speak
> about
> > jaws then is it just jaws that had the problem or did nvda have the same
> > problem. i.e. the dialog and jaws not beeing restricted to the dialog.
> > thanks again for doing all this hard hard work lucy
> >
> > Lucia Greco
> > Web Accessibility Evangelist
> > IST - Architecture, Platforms, and Integration
> > University of California, Berkeley
> > (510) 289-6008 skype: lucia1-greco
> > http://webaccess.berkeley.edu
> > Follow me on twitter @accessaces
> >
> >
> > On Mon, Apr 4, 2016 at 1:47 PM, Robert Fentress < = EMAIL ADDRESS REMOVED = > wrote:
> >
> > > Hi, Lucy.
> > >
> > > We tested both the Teacher and Student interfaces to some degree. Due
> to
> > > the complexity involved, we were not able to test everything, but we
> > > covered both roles to some extent. We tested with both JAWS and NVDA,
> as
> > > well as VoiceOver and the results did differ in interesting and
> important
> > > ways, I think. We did not really generalize to say screen reader users
> > as a
> > > whole could do a certain thing, though I suppose one could make that
> > > analysis to some degree from the data.
> > >
> > > Best,
> > > Rob
> > >
> > > On Mon, Apr 4, 2016 at 4:32 PM, Lucy Greco < = EMAIL ADDRESS REMOVED = >
> wrote:
> > >
> > > > thanks for sharing this. i have to questions.
> > > >
> > > > 1 why didn't you test the instructor interface.?
> > > > second i see several references to how jaws did some thing or
> did
> > > not
> > > > do some thing i.e. in a dialog jaws users were able to read content
> > out
> > > > side of the dialog.in your introduction you spoke about using nvda
> was
> > > the
> > > > testing results different for nvda? if not you should indicate for
> > the
> > > > screen reader user not for jaws. i think from my experience with the
> > > system
> > > > in nvda you are using the turn jaws to mean all screen readers.
> please
> > > > confirm lucy
> > > >
> > > > Lucia Greco
> > > > Web Accessibility Evangelist
> > > > IST - Architecture, Platforms, and Integration
> > > > University of California, Berkeley
> > > > (510) 289-6008 skype: lucia1-greco
> > > > http://webaccess.berkeley.edu
> > > > Follow me on twitter @accessaces
> > > >
> > > >
> > > > On Mon, Apr 4, 2016 at 9:02 AM, Hadi Rangin < = EMAIL ADDRESS REMOVED = > wrote:
> > > >
> > > > > [Sorry for cross-posting]
> > > > >
> > > > > Hello everyone,
> > > > >
> > > > > We are finally ready to publish the result of Canvas Accessibility
> > > > Testing
> > > > > & Evaluation Project.
> > > > > Thanks to Instructure and all colleagues and friends who
> collaborated
> > > on
> > > > > this complex and time-consuming project.
> > > > >
> > > > > You can find the comprehensive report, testing & evaluation
> results,
> > as
> > > > > well as the CSUN 2016 presentation at:
> > > > >
> > >
> http://blog.bargirangin.com/2016/04/canvas-testing-evaluation-cate.html
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Hadi Rangin
> > > > > IT Accessibility Specialist
> > > > > Mary Gates Hall 064C
> > > > > University of Washington
> > > > > Phone: (206) 685-4144, Direct: (206) 221-1532
> > > > > E-mail: = EMAIL ADDRESS REMOVED = <mailto: = EMAIL ADDRESS REMOVED = >
> > > > >
> > > > > > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > >
> > >
> > >
> > >
> > > --
> > > Robert Fentress
> > > Senior Accessibility Solutions Designer
> > > 540.231.1255
> > >
> > > Technology-enhanced Learning & Online Strategies
> > > Assistive Technologies
> > > 1180 Torgersen Hall
> > > 620 Drillfield Drive (0434)
> > > Blacksburg, Virginia 24061
> > > > > > > > > > > > > > >
> > > > > > > > > >
>
>
>
> --
> Robert Fentress
> Senior Accessibility Solutions Designer
> 540.231.1255
>
> Technology-enhanced Learning & Online Strategies
> Assistive Technologies
> 1180 Torgersen Hall
> 620 Drillfield Drive (0434)
> Blacksburg, Virginia 24061
> > > > >