[Using Sakai] Sakai unusable by blind student
Wilma Hodges
wilma at longsight.com
Fri Mar 20 09:31:55 PDT 2015
There is also a community effort for improving accessibility called the
RA11y Plan which is currently underway. The goals are to complete a
comprehensive VPAT of the current version and complete an audit to certify
accessibility (such as the National Federation of the Blind certification).
You can find more details at the link below.
https://confluence.sakaiproject.org/display/2ACC/rA11y+Plan
*Wilma Hodges*
Director of Training & eLearning Initiatives
Longsight
wilma at longsight.com
www.longsight.com
On Fri, Mar 20, 2015 at 11:11 AM, Gayle Stein <gstein at rutgers.edu> wrote:
> We're hoping to accessibility test Sakai 11 during the community QA
> process, but will need help doing so. If you're interested, please let
> Neal (and me) know so we can coordinate our efforts--Gayle
>
> ==
> Gayle K. Stein, MS, MLS, Ph.D.
> * Associate Director for Instructional Technology
> * Director, Accessible Information Technology Initiatives
> * Adjunct member of the faculty and internship coordinator, Information
> Technology and Informatics undergraduate program, School of
> Communication and Information
> * Member, University Senate and Research and Graduate & Professional
> Education Committee
> * Member, Institutional Review Board
> * Member, CIC Information Technology and Accessibility Group, Learning
> Technologies Group, Online Learning Group
>
>
> On 3/20/15, 11:08 AM, Matthew Jones wrote:
> > Yeah, if this is happening in the quiz context, this sounds like it
> > likely be from some content that was imported from QTI from a published
> > with badly named images. I'd check that course they were having a
> > problem with, as the core Sakai shouldn't have this type of problem and
> > has been used and tested on screen readers in the past.
> >
> > Thinking about it, the suggestion to require an alt would be good for
> > images that instructors create, but wouldn't catch the content that was
> > imported either unfortunately, which *feels* like is a good amount of
> > the content created in Samigo.
> >
> >
> > On Fri, Mar 20, 2015 at 11:02 AM, Jeff Davidson
> > <jdavidso at southalabama.edu <mailto:jdavidso at southalabama.edu>> wrote:
> >
> > Diego:
> > We have recently requested and a community Jira has been created for
> > requiring alt text for images using the Sakai editor to help with
> > accessibility compliance.
> > We are focusing on our course accessibility to ensure all PDFs,
> > videos and images are accessible (those things over which we have
> > control beyond Sakai itself).
> > The issue of accessibility will likely become more and more
> > prominent and a priority for all universities in the future.
> > Jeff
> >
> > On Fri, Mar 20, 2015 at 9:25 AM, Diego del Blanco Orobitg
> > <diego.delblanco.sakai at gmail.com
> > <mailto:diego.delblanco.sakai at gmail.com>> wrote:
> >
> > Hi Marilyn:
> >
> > I'm not expert at all in accessibility, but this that you are
> > commenting is very important.
> > I don't know what images, the user is finding with the
> > alphanumeric code becuase most of the images in Sakai Skin have
> > a normal name... maybe these images has been uploaded by the
> > instructors that created the content. Or maybe they are Sakai
> > images.
> >
> > Anyway, some time ago, for one customer I had, we designed a
> > patch to allow select the skin by user, so a user can have a
> > different skin and view the platform in other way. We did some
> > skins with high contrast and bigger size of the letters. Maybe
> > this idea can go beyond that, and if we were able to to create a
> > skin with a very simplified interface without any images that
> > worked better for the screen readers, and assign it to people
> > that needs that, it would make things easier for all.
> >
> > Review all the sakai images and change the name for something
> > more descritptive and add an "alt" on them surely is something
> > that can be done too and I think it won't need a lot of work.
> >
> > In the other hand, again, one thing is Sakai interface and other
> > is the content that the teacher uploads. Maybe a way to make
> > mandatory the "alt" field when a teacher uploads an image,
> > or/and, some education for the instructors when they create the
> > contents or questions, can help too.
> >
> > About the first solution I proposed some time ago to change skin
> > when you enter with a parameter in the
> > URL,...https://jira.sakaiproject.org/browse/KNL-860 but this
> > was not introduced in the main code. It's an option. I'd like
> > more another option to allow to you, as a user, to select your
> > own skin in preferences. So we can have skins for screen
> > readers, high contrast skins, big fonts skins... or any other
> > thing that helps the people with accessibility problems.
> >
> > I propose the accessibility group to think about this. I think
> > that Sakai, with the new Morpheus skin, has an opportunity to
> > improve this question.
> >
> > Diego
> >
> >
> >
> >
> > 2015-03-20 6:35 GMT-07:00 Marilyn Dispensa <mdispensa at ithaca.edu
> > <mailto:mdispensa at ithaca.edu>>:
> >
> > Hi everyone,
> >
> >
> > A blind student on campus has been sharing his experiences
> > with various technologies. He says Sakai is extremely
> > difficult to use and has the disability office take content
> > from Sakai site and deliver to him separately. I didn't get
> > much specifics but when using JAWS he says there are many
> > images that have a long alphanumeric file name and unless he
> > memorizes those numbers, he can't navigate. He said it took
> > 3 hours to take a 12 question quiz.
> >
> >
> > I've noticed that Sakai Project has accessibility efforts
> > https://sakaiproject.org/accessibility
> >
> > And the wiki actually talked a bout
> >
> >
> > T
> > <
> https://confluence.sakaiproject.org/pages/viewpage.action?pageId=82250209
> >here
> > also seems to be an accessibility working group.
> >
> >
> https://confluence.sakaiproject.org/display/2ACC/Accessibility+Working+Group
> >
> >
> > It seems like there is some testing done, but it is unclear
> > about the completeness of that effort.
> >
> >
> > I'm curious if anyone has any experience with Sakai and
> > actual visually impaired students. If he agrees, I might try
> > to record his experience and share it with the community.
> >
> > Maybe there is a user issue or maybe there's a way to go on
> > this.
> >
> > Marilyn
> >
> >
> > --------------------------------------
> > Marilyn Dispensa
> > Instructional Technology Coordinator
> > Information Technology Services
> > Ithaca College
> > 953 Danby Road
> > Ithaca, NY
> > 607-274-3647 <tel:607-274-3647>
> > mdispensa at ithaca.edu <mailto:mdispensa at ithaca.edu>
> > http://www.ithaca.edu/its/iss
> > @indispenzable
> >
> >
> > _______________________________________________
> > sakai-user mailing list
> > sakai-user at collab.sakaiproject.org
> > <mailto:sakai-user at collab.sakaiproject.org>
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-user
> >
> > TO UNSUBSCRIBE: send email to
> > sakai-user-unsubscribe at collab.sakaiproject.org
> > <mailto:sakai-user-unsubscribe at collab.sakaiproject.org> with
> > a subject of "unsubscribe"
> >
> >
> >
> >
> > --
> > *Diego del Blanco Orobitg*
> > Spain & LATAM Regional Manager (/ANI Sakai
> > <http://www.anisakai.es/>/)
> > Apereo LATAM Representative (/Apereo Foundation
> > <http://www.apereo.org/>/)
> >
> > Ph: +1-480-521-8527 <tel:%2B1-480-521-8527>
> > Em: ddelblanco at anisakai.com <mailto:ddelblanco at anisakai.com>
> > Sk: ddelblanco.ani
> >
> >
> > _______________________________________________
> > sakai-user mailing list
> > sakai-user at collab.sakaiproject.org
> > <mailto:sakai-user at collab.sakaiproject.org>
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-user
> >
> > TO UNSUBSCRIBE: send email to
> > sakai-user-unsubscribe at collab.sakaiproject.org
> > <mailto:sakai-user-unsubscribe at collab.sakaiproject.org> with a
> > subject of "unsubscribe"
> >
> >
> >
> >
> > --
> > Jeff Davidson
> > Manager, Learning Mgt Syst Srvs
> > USAonline
> > University of South Alabama
> > (251) 380-2845 <tel:%28251%29%20380-2845>
> > (251) 380-2713 <tel:%28251%29%20380-2713> (fax)
> >
> > _______________________________________________
> > sakai-user mailing list
> > sakai-user at collab.sakaiproject.org
> > <mailto:sakai-user at collab.sakaiproject.org>
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-user
> >
> > TO UNSUBSCRIBE: send email to
> > sakai-user-unsubscribe at collab.sakaiproject.org
> > <mailto:sakai-user-unsubscribe at collab.sakaiproject.org> with a
> > subject of "unsubscribe"
> >
> >
> >
> >
> > _______________________________________________
> > sakai-user mailing list
> > sakai-user at collab.sakaiproject.org
> > http://collab.sakaiproject.org/mailman/listinfo/sakai-user
> >
> > TO UNSUBSCRIBE: send email to
> sakai-user-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
> _______________________________________________
> sakai-user mailing list
> sakai-user at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-user
>
> TO UNSUBSCRIBE: send email to
> sakai-user-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-user/attachments/20150320/5e62a21b/attachment-0001.html
More information about the sakai-user
mailing list