From johumber at iupui.edu Wed May 1 12:56:02 2013 From: johumber at iupui.edu (Humbert, Joseph A) Date: Wed, 1 May 2013 19:56:02 +0000 Subject: [WG: Accessibility] Reminder: Accessibility WG Teleconference TOMORROW Thursday May 2nd, 2013 and Previous Meeting Minutes Message-ID: <906395B08AE7B542882AC81A31B69B7549997C2C@IU-MSSG-MBX110.ads.iu.edu> Hello everyone, This is a reminder that the next teleconference for the Accessibility WG will be TOMORROW Thursday May 2nd at 2 PM Eastern. Phone: 812-856-7060 PIN: 22348 Here are the notes for our previous teleconference: April 18, 2013: https://confluence.sakaiproject.org/display/2ACC/Accessibility+WG+Teleconference+Minutes+04-18-2013 Notes URL: * http://free.primarypad.com/p/awg-05-02-2013 Agenda Any Other Business 1. Discussion of progress on updating Sakai a11y help documentation 2. CK Editor content creation guidelines Sakai 2.9 Accessibility Review 3. A11y Jiras that need testing/review Sakai 2.9.x 4. Release Team Meeting Notes (If time is available) The full agenda on Etherpad! Joe Humbert, Adaptive Technology and Accessibility Specialist UITS Adaptive Technology and Accessibility Centers Indiana University, Indianapolis and Bloomington 535 W Michigan St. IT214 E Indianapolis, IN 46202 Office Phone: (317) 274-4378 Cell Phone: (317) 644-6824 johumber at iupui.edu http://iuadapts.Indiana.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130501/db91330e/attachment.html From nealcaidin at sakaifoundation.org Mon May 6 08:30:40 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Mon, 6 May 2013 11:30:40 -0400 Subject: [WG: Accessibility] Updating arkn.html for Accessibility Message-ID: Hi Documentation group, We are updating the Accessibility page in Sakai CLE so that it points to a Confluence page that can be updated more rapidly, as needed. Is this the right page, just double checking? https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.html All the existing text is going to be replaced with:

Accessibility information

Please click here for Sakai accessibility information Thanks, Neal -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130506/84a4dc72/attachment.html From nealcaidin at sakaifoundation.org Mon May 6 08:58:01 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Mon, 6 May 2013 11:58:01 -0400 Subject: [WG: Accessibility] Moving Accessibility Help documentation and translations to Confluence Message-ID: <757BE28C-1C2C-43D8-BE81-C7A3176F409A@sakaifoundation.org> FYI - ticket is https://jira.sakaiproject.org/browse/SAK-23579 Cheers, Neal Caidin Sakai CLE Community Coordinator nealcaidin at sakaifoundation.org Skype: nealkdin AIM: ncaidin at aol.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130506/51420e07/attachment.html From nealcaidin at sakaifoundation.org Mon May 6 12:17:34 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Mon, 6 May 2013 15:17:34 -0400 Subject: [WG: Accessibility] [WG: Docs] Updating arkn.html for Accessibility In-Reply-To: <22B638C885092643A53AC0646804BF4614D84C4D@IU-MSSG-MBX107.ads.iu.edu> References: <22B638C885092643A53AC0646804BF4614D84C4D@IU-MSSG-MBX107.ads.iu.edu> Message-ID: <2E65B35E-9912-4B89-90F9-5C8643AE4B5E@sakaifoundation.org> Hi Elizabeth, I'm not recollecting when the Confluence page should be ready. Probably Joe H. can comment. Here's the problem - I'm not sure if the scripts used to update Sakai CLE with the Knowledge base information will ever be run again. They might be, but I'm not sure. This is definitely not ideal. My suggestion is that we update them in both places with the same text? I'll update manually in Sakai CLE and you update the IU Knoweldge base? I don't expect this page to change for a long time, at least until a better online help system is figured out. So I think this will not be too bad to manage. What do you think? Thanks! Neal On May 6, 2013, at 1:37 PM, "Venstra, Elizabeth" wrote: > Yes, that should be the correct page. At any rate, the four-letter docid, arkn, is the correct one that maps to the document in our repository (https://www.indiana.edu/~sakaikb/display.cgi?docid=arkn ). I was planning on changing the document in our repository as of this coming weekend, May 11, which is when we?re deploying 2.9 here at Indiana?removing the detailed content, and simply telling readers to go to the Confluence page, with a link. But Neal?just so I understand correctly?are you saying that you plan to remove the link to our repository for this document, and point straight to the Confluence page, without going through our document arkn? Or do you want it to continue to use our document, which will then point to the Confluence page? I?m fine with either approach?both should get end users to the same information?but if I know that you?re going to go straight to the Confluence page, then I suppose I could just remove this document from our ?sakaiht? (a.k.a. Sakai help tool) domain . . . I won?t until I know for sure it?s not needed there, though. > > Question about timing?Joe had indicated to me that the Confluence page should be ready by May 3, but it looks like it still says ?Draft?. Are we still on track for it being ready for public consumption before this weekend? > > best, > > Elizabeth Venstra > Knowledge Management team > University Information Technology Services > Indiana University > erytting at indiana.edu > 812-855-0459 > > > > From: documentation-bounces at collab.sakaiproject.org [mailto:documentation-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin > Sent: Monday, May 06, 2013 11:31 AM > To: documentation at collab.sakaiproject.org > Cc: accessibility at collab.sakaiproject.org > Subject: [WG: Docs] Updating arkn.html for Accessibility > > Hi Documentation group, > > We are updating the Accessibility page in Sakai CLE so that it points to a Confluence page that can be updated more rapidly, as needed. > > > Is this the right page, just double checking? > > https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.html > > All the existing text is going to be replaced with: >

Accessibility information

> Please click here for Sakai accessibility information > > Thanks, > Neal -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130506/c48e3797/attachment.html From johumber at iupui.edu Mon May 6 12:35:05 2013 From: johumber at iupui.edu (Humbert, Joseph A) Date: Mon, 6 May 2013 19:35:05 +0000 Subject: [WG: Accessibility] [WG: Docs] Updating arkn.html for Accessibility In-Reply-To: <22B638C885092643A53AC0646804BF4614D85E06@IU-MSSG-MBX107.ads.iu.edu> References: <22B638C885092643A53AC0646804BF4614D84C4D@IU-MSSG-MBX107.ads.iu.edu> <2E65B35E-9912-4B89-90F9-5C8643AE4B5E@sakaifoundation.org> <22B638C885092643A53AC0646804BF4614D85E06@IU-MSSG-MBX107.ads.iu.edu> Message-ID: <906395B08AE7B542882AC81A31B69B75499F41E9@IU-MSSG-MBX110.ads.iu.edu> Hi! I'm not sure when the accessibility help documentation will no longer be "in draft". However, the current form of the draft provides almost all of the necessary content to aid assistive technology users with navigating Sakai. That being said, I do not see a problem in moving forward. Most changes from this point forward will be visual formatting for easier consumption. I'm sorry I can't give a better timeline. Thankx. Sincerely, Joe From: Venstra, Elizabeth Sent: Monday, May 06, 2013 3:30 PM To: Neal Caidin Cc: documentation at collab.sakaiproject.org; accessibility at collab.sakaiproject.org; Humbert, Joseph A Subject: RE: [WG: Docs] Updating arkn.html for Accessibility Whatever works for you, works for me. If it's possible on your end, and simpler, to simply remove the link to https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.html and replace it with a direct link to the Confluence page, that might be even better, because then it wouldn't look like a KB doc without actually being a KB doc, if you see what I mean. But if that's tricky, by all means, let's do your plan. I'll go ahead and draft that revision this week (whether or not I end up making it live this weekend) and send you the text I come up with. best, Elizabeth From: Neal Caidin [mailto:nealcaidin at sakaifoundation.org] Sent: Monday, May 06, 2013 3:18 PM To: Venstra, Elizabeth Cc: documentation at collab.sakaiproject.org; accessibility at collab.sakaiproject.org; Humbert, Joseph A Subject: Re: [WG: Docs] Updating arkn.html for Accessibility Hi Elizabeth, I'm not recollecting when the Confluence page should be ready. Probably Joe H. can comment. Here's the problem - I'm not sure if the scripts used to update Sakai CLE with the Knowledge base information will ever be run again. They might be, but I'm not sure. This is definitely not ideal. My suggestion is that we update them in both places with the same text? I'll update manually in Sakai CLE and you update the IU Knoweldge base? I don't expect this page to change for a long time, at least until a better online help system is figured out. So I think this will not be too bad to manage. What do you think? Thanks! Neal On May 6, 2013, at 1:37 PM, "Venstra, Elizabeth" > wrote: Yes, that should be the correct page. At any rate, the four-letter docid, arkn, is the correct one that maps to the document in our repository (https://www.indiana.edu/~sakaikb/display.cgi?docid=arkn ). I was planning on changing the document in our repository as of this coming weekend, May 11, which is when we're deploying 2.9 here at Indiana-removing the detailed content, and simply telling readers to go to the Confluence page, with a link. But Neal-just so I understand correctly-are you saying that you plan to remove the link to our repository for this document, and point straight to the Confluence page, without going through our document arkn? Or do you want it to continue to use our document, which will then point to the Confluence page? I'm fine with either approach-both should get end users to the same information-but if I know that you're going to go straight to the Confluence page, then I suppose I could just remove this document from our "sakaiht" (a.k.a. Sakai help tool) domain . . . I won't until I know for sure it's not needed there, though. Question about timing-Joe had indicated to me that the Confluence page should be ready by May 3, but it looks like it still says "Draft". Are we still on track for it being ready for public consumption before this weekend? best, Elizabeth Venstra Knowledge Management team University Information Technology Services Indiana University erytting at indiana.edu 812-855-0459 From: documentation-bounces at collab.sakaiproject.org [mailto:documentation-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin Sent: Monday, May 06, 2013 11:31 AM To: documentation at collab.sakaiproject.org Cc: accessibility at collab.sakaiproject.org Subject: [WG: Docs] Updating arkn.html for Accessibility Hi Documentation group, We are updating the Accessibility page in Sakai CLE so that it points to a Confluence page that can be updated more rapidly, as needed. Is this the right page, just double checking? https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.html All the existing text is going to be replaced with:

Accessibility information

Please click here for Sakai accessibility information Thanks, Neal -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130506/a8232cad/attachment-0001.html From johumber at iupui.edu Mon May 6 12:37:55 2013 From: johumber at iupui.edu (Humbert, Joseph A) Date: Mon, 6 May 2013 19:37:55 +0000 Subject: [WG: Accessibility] Creation of Verbose CK Editor Accessible Content Creation Guidelines Message-ID: <906395B08AE7B542882AC81A31B69B75499F4292@IU-MSSG-MBX110.ads.iu.edu> Hi AWG, Over the past few AWG teleconferences the group has been fleshing out a skeletal set of accessibility guidelines for content created using Sakai's rich text editor CK Editor. Due to many factors, I would like to move this topic to the list to solicit feedback and contributions from people on this list who may not attend the teleconference calls. Below is our current progress: CK Editor Accessibility Guideline Categories (CK Editor v3.6) Alternative text descriptions for Images * alt (heuristics TBD), if complex add a paragraph, if paragraph is a problem then longdesc Requiring of alternative text for image links * needs a alt if image is anchor for a link Heading structure * start with an h4, can use h5, h6 * except HTML Resource, all headings are allowable * what can be a heading candidate (short, title-like) * separate structure from visual styling (h6 with font size of 22) Semantically coded lists Proper list nesting * when not to use a list (one item) Use of only color to convey information. For example, "click the blue button on the left." Color Contrast * example? * link to checker * link to color picker tool Inclusion of Skip navigation links * heuristic? when to do this? * not possible? target blank - bring up with community see KNL-1001 o https://jira.sakaiproject.org/browse/KNL-1001 * would describe as Table of Contents Unique and Descriptive link text * make descriptive sense, identify uniquely Identifying downloadable files * example: report (pdf) * identify file type in link text Unique and Descriptive page titles (This may only be needed for external tools and Web pages). * only in HTML attachments We need create verbose descriptions, add details and create examples, etc. for each of these guidelines. I am including a draft of the first guideline that can be used as a model: Alternative text descriptions for Images For every image embedded into the rich text editor, concise and descriptive alternative text should be provided. However, if the image is complex, an equally verbose description (paragraph) should be provided in the surrounding content. Finally, if the longer alternative text is not feasible, create a link to an external Web page that contains an appropriate description. Heuristics * If the image is pure decorative or used for visual formatting, the alterative text description should be left blank to hide it from users of assistive technology * The alternative text should be no longer than 10 words or 160 characters. o If the image cannot be conveyed with this limitation, provide a longer description. * The image description should be contained in the surrounding content no further than 2 sentences before or after the image. o Where possible, use identifying descriptors to inform users of the description (e.g., Image caption, in the image on the left, etc.) o If the image description needs to occur farther away, link the description to the image (e.g. image Figure 1.3....In Figure 1.3 in section ****) * If an external link to the description is needed, make the purpose of the link clear in the link text (e.g., description of "Fresco Clean" image) Steps to add alternative text * Activate the "image" button on the toolbar. * Locate the "Alternative Text" input form control in the dialog that is loaded after you activate the button. * Place the appropriate alternative text in the form control following the guidelines in the heuristics section. Examples * Alt Text: "Scientist in a lab filling a vile with fluid" * Description: "A female forensic scientist is filling a vile containing a small about of blood with fluid to denature the sample as part of the process of the PCR analysis method of DNA profiling. In the background is a centrifuge which will aid in the process of extracting the DNA from the sample of blood." If people would like to volunteer to create the first draft for each guideline, we can then discuss the draft on list or hold a special (off-week) teleconference. I would like to set a goal of June 1 for the first draft of guidelines being sent to the list and an end date of June 31 for the completed guidelines. Comments? Questions? Joe Humbert, Accessibility Specialist UITS Adaptive Technology and Accessibility Centers Indiana University, Indianapolis and Bloomington 535 W Michigan St. IT214 E Indianapolis, IN 46202 Office Phone: (317) 274-4378 Cell Phone: (317) 644-6824 johumber at iupui.edu http://iuadapts.Indiana.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130506/96f98ef4/attachment-0001.html From nealcaidin at sakaifoundation.org Mon May 6 12:43:12 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Mon, 6 May 2013 15:43:12 -0400 Subject: [WG: Accessibility] [WG: Docs] Updating arkn.html for Accessibility In-Reply-To: <22B638C885092643A53AC0646804BF4614D85E06@IU-MSSG-MBX107.ads.iu.edu> References: <22B638C885092643A53AC0646804BF4614D84C4D@IU-MSSG-MBX107.ads.iu.edu> <2E65B35E-9912-4B89-90F9-5C8643AE4B5E@sakaifoundation.org> <22B638C885092643A53AC0646804BF4614D85E06@IU-MSSG-MBX107.ads.iu.edu> Message-ID: <1E7525EA-C857-400B-BE4C-0BC4ED775F34@sakaifoundation.org> Hi Elizabeth, I'm guessing that it would not be hard to break the link between the Indiana KB and Sakai for this one article. If you think that is the better way, I can look into it. Otherwise, we'll go with this plan. I'm glad I asked. At least we will all know what is going on. Wishing it will become simpler ? :-) -- Neal On May 6, 2013, at 3:29 PM, "Venstra, Elizabeth" wrote: > Whatever works for you, works for me. If it?s possible on your end, and simpler, to simply remove the link to https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.htmland replace it with a direct link to the Confluence page, that might be even better, because then it wouldn?t look like a KB doc without actually being a KB doc, if you see what I mean. But if that?s tricky, by all means, let?s do your plan. I?ll go ahead and draft that revision this week (whether or not I end up making it live this weekend) and send you the text I come up with. > > best, > Elizabeth > > From: Neal Caidin [mailto:nealcaidin at sakaifoundation.org] > Sent: Monday, May 06, 2013 3:18 PM > To: Venstra, Elizabeth > Cc: documentation at collab.sakaiproject.org; accessibility at collab.sakaiproject.org; Humbert, Joseph A > Subject: Re: [WG: Docs] Updating arkn.html for Accessibility > > Hi Elizabeth, > > I'm not recollecting when the Confluence page should be ready. Probably Joe H. can comment. > > Here's the problem - I'm not sure if the scripts used to update Sakai CLE with the Knowledge base information will ever be run again. They might be, but I'm not sure. This is definitely not ideal. > > My suggestion is that we update them in both places with the same text? I'll update manually in Sakai CLE and you update the IU Knoweldge base? I don't expect this page to change for a long time, at least until a better online help system is figured out. So I think this will not be too bad to manage. > > What do you think? > > Thanks! > Neal > > > > On May 6, 2013, at 1:37 PM, "Venstra, Elizabeth" wrote: > > > Yes, that should be the correct page. At any rate, the four-letter docid, arkn, is the correct one that maps to the document in our repository (https://www.indiana.edu/~sakaikb/display.cgi?docid=arkn ). I was planning on changing the document in our repository as of this coming weekend, May 11, which is when we?re deploying 2.9 here at Indiana?removing the detailed content, and simply telling readers to go to the Confluence page, with a link. But Neal?just so I understand correctly?are you saying that you plan to remove the link to our repository for this document, and point straight to the Confluence page, without going through our document arkn? Or do you want it to continue to use our document, which will then point to the Confluence page? I?m fine with either approach?both should get end users to the same information?but if I know that you?re going to go straight to the Confluence page, then I suppose I could just remove this document from our ?sakaiht? (a.k.a. Sakai help tool) domain . . . I won?t until I know for sure it?s not needed there, though. > > Question about timing?Joe had indicated to me that the Confluence page should be ready by May 3, but it looks like it still says ?Draft?. Are we still on track for it being ready for public consumption before this weekend? > > best, > > Elizabeth Venstra > Knowledge Management team > University Information Technology Services > Indiana University > erytting at indiana.edu > 812-855-0459 > > > > From: documentation-bounces at collab.sakaiproject.org[mailto:documentation-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin > Sent: Monday, May 06, 2013 11:31 AM > To: documentation at collab.sakaiproject.org > Cc: accessibility at collab.sakaiproject.org > Subject: [WG: Docs] Updating arkn.html for Accessibility > > Hi Documentation group, > > We are updating the Accessibility page in Sakai CLE so that it points to a Confluence page that can be updated more rapidly, as needed. > > > Is this the right page, just double checking? > > https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.html > > All the existing text is going to be replaced with: >

Accessibility information

> Please click here for Sakai accessibility information > > Thanks, > Neal -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130506/ca130b6b/attachment.html From nealcaidin at sakaifoundation.org Wed May 8 05:42:48 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Wed, 8 May 2013 08:42:48 -0400 Subject: [WG: Accessibility] [WG: Docs] Updating arkn.html for Accessibility In-Reply-To: <22B638C885092643A53AC0646804BF4614D85E06@IU-MSSG-MBX107.ads.iu.edu> References: <22B638C885092643A53AC0646804BF4614D84C4D@IU-MSSG-MBX107.ads.iu.edu> <2E65B35E-9912-4B89-90F9-5C8643AE4B5E@sakaifoundation.org> <22B638C885092643A53AC0646804BF4614D85E06@IU-MSSG-MBX107.ads.iu.edu> Message-ID: Hi Elizabeth, I wouldn't be removing the ilnk to arkn.html, I would be updating the html itself. But maybe I am missing something. I know how to create a different html file with a different name and check it into Sakai, but I don't know how to tell the Online Help to find that document. Perhaps it is just the directory structure? I don't know. Maybe Matt Jones or someone could help me figure it out. For me, the easiest thing is to update in both places, arkn.html for me and the Knowledge Base for you. Since we may never run the updater scripts again, that pull Indiana's KB information into Sakai then there is no link. But just in case it does get run one or more times before being permanently retired, at least it would overwrite with the same information. I hope that makes sense. Thanks, Neal On May 6, 2013, at 3:29 PM, "Venstra, Elizabeth" wrote: > Whatever works for you, works for me. If it?s possible on your end, and simpler, to simply remove the link to https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.htmland replace it with a direct link to the Confluence page, that might be even better, because then it wouldn?t look like a KB doc without actually being a KB doc, if you see what I mean. But if that?s tricky, by all means, let?s do your plan. I?ll go ahead and draft that revision this week (whether or not I end up making it live this weekend) and send you the text I come up with. > > best, > Elizabeth > > From: Neal Caidin [mailto:nealcaidin at sakaifoundation.org] > Sent: Monday, May 06, 2013 3:18 PM > To: Venstra, Elizabeth > Cc: documentation at collab.sakaiproject.org; accessibility at collab.sakaiproject.org; Humbert, Joseph A > Subject: Re: [WG: Docs] Updating arkn.html for Accessibility > > Hi Elizabeth, > > I'm not recollecting when the Confluence page should be ready. Probably Joe H. can comment. > > Here's the problem - I'm not sure if the scripts used to update Sakai CLE with the Knowledge base information will ever be run again. They might be, but I'm not sure. This is definitely not ideal. > > My suggestion is that we update them in both places with the same text? I'll update manually in Sakai CLE and you update the IU Knoweldge base? I don't expect this page to change for a long time, at least until a better online help system is figured out. So I think this will not be too bad to manage. > > What do you think? > > Thanks! > Neal > > > > On May 6, 2013, at 1:37 PM, "Venstra, Elizabeth" wrote: > > > Yes, that should be the correct page. At any rate, the four-letter docid, arkn, is the correct one that maps to the document in our repository (https://www.indiana.edu/~sakaikb/display.cgi?docid=arkn ). I was planning on changing the document in our repository as of this coming weekend, May 11, which is when we?re deploying 2.9 here at Indiana?removing the detailed content, and simply telling readers to go to the Confluence page, with a link. But Neal?just so I understand correctly?are you saying that you plan to remove the link to our repository for this document, and point straight to the Confluence page, without going through our document arkn? Or do you want it to continue to use our document, which will then point to the Confluence page? I?m fine with either approach?both should get end users to the same information?but if I know that you?re going to go straight to the Confluence page, then I suppose I could just remove this document from our ?sakaiht? (a.k.a. Sakai help tool) domain . . . I won?t until I know for sure it?s not needed there, though. > > Question about timing?Joe had indicated to me that the Confluence page should be ready by May 3, but it looks like it still says ?Draft?. Are we still on track for it being ready for public consumption before this weekend? > > best, > > Elizabeth Venstra > Knowledge Management team > University Information Technology Services > Indiana University > erytting at indiana.edu > 812-855-0459 > > > > From: documentation-bounces at collab.sakaiproject.org[mailto:documentation-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin > Sent: Monday, May 06, 2013 11:31 AM > To: documentation at collab.sakaiproject.org > Cc: accessibility at collab.sakaiproject.org > Subject: [WG: Docs] Updating arkn.html for Accessibility > > Hi Documentation group, > > We are updating the Accessibility page in Sakai CLE so that it points to a Confluence page that can be updated more rapidly, as needed. > > > Is this the right page, just double checking? > > https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.html > > All the existing text is going to be replaced with: >

Accessibility information

> Please click here for Sakai accessibility information > > Thanks, > Neal -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130508/e2fe8125/attachment.html From bkirschn at umich.edu Wed May 8 06:34:29 2013 From: bkirschn at umich.edu (Beth Kirschner) Date: Wed, 8 May 2013 09:34:29 -0400 Subject: [WG: Accessibility] [WG: Docs] Updating arkn.html for Accessibility In-Reply-To: References: <22B638C885092643A53AC0646804BF4614D84C4D@IU-MSSG-MBX107.ads.iu.edu> <2E65B35E-9912-4B89-90F9-5C8643AE4B5E@sakaifoundation.org> <22B638C885092643A53AC0646804BF4614D85E06@IU-MSSG-MBX107.ads.iu.edu> Message-ID: <203CF514-A42E-4190-BACE-C8AB56DA5628@umich.edu> Hi Neal, The arkn.html file is configured in the help.xml file within the same directory. There are several (e.g. help_pt_BR.xml) for alternate localized copies of the help docs. - Beth On May 8, 2013, at 8:42 AM, Neal Caidin wrote: > Hi Elizabeth, > > I wouldn't be removing the ilnk to arkn.html, I would be updating the html itself. But maybe I am missing something. I know how to create a different html file with a different name and check it into Sakai, but I don't know how to tell the Online Help to find that document. Perhaps it is just the directory structure? I don't know. Maybe Matt Jones or someone could help me figure it out. > > For me, the easiest thing is to update in both places, arkn.html for me and the Knowledge Base for you. Since we may never run the updater scripts again, that pull Indiana's KB information into Sakai then there is no link. But just in case it does get run one or more times before being permanently retired, at least it would overwrite with the same information. I hope that makes sense. > > Thanks, > Neal > > > On May 6, 2013, at 3:29 PM, "Venstra, Elizabeth" wrote: > >> Whatever works for you, works for me. If it?s possible on your end, and simpler, to simply remove the link to https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.htmland replace it with a direct link to the Confluence page, that might be even better, because then it wouldn?t look like a KB doc without actually being a KB doc, if you see what I mean. But if that?s tricky, by all means, let?s do your plan. I?ll go ahead and draft that revision this week (whether or not I end up making it live this weekend) and send you the text I come up with. >> >> best, >> Elizabeth >> >> From: Neal Caidin [mailto:nealcaidin at sakaifoundation.org] >> Sent: Monday, May 06, 2013 3:18 PM >> To: Venstra, Elizabeth >> Cc: documentation at collab.sakaiproject.org; accessibility at collab.sakaiproject.org; Humbert, Joseph A >> Subject: Re: [WG: Docs] Updating arkn.html for Accessibility >> >> Hi Elizabeth, >> >> I'm not recollecting when the Confluence page should be ready. Probably Joe H. can comment. >> >> Here's the problem - I'm not sure if the scripts used to update Sakai CLE with the Knowledge base information will ever be run again. They might be, but I'm not sure. This is definitely not ideal. >> >> My suggestion is that we update them in both places with the same text? I'll update manually in Sakai CLE and you update the IU Knoweldge base? I don't expect this page to change for a long time, at least until a better online help system is figured out. So I think this will not be too bad to manage. >> >> What do you think? >> >> Thanks! >> Neal >> >> >> >> On May 6, 2013, at 1:37 PM, "Venstra, Elizabeth" wrote: >> >> >> Yes, that should be the correct page. At any rate, the four-letter docid, arkn, is the correct one that maps to the document in our repository (https://www.indiana.edu/~sakaikb/display.cgi?docid=arkn ). I was planning on changing the document in our repository as of this coming weekend, May 11, which is when we?re deploying 2.9 here at Indiana?removing the detailed content, and simply telling readers to go to the Confluence page, with a link. But Neal?just so I understand correctly?are you saying that you plan to remove the link to our repository for this document, and point straight to the Confluence page, without going through our document arkn? Or do you want it to continue to use our document, which will then point to the Confluence page? I?m fine with either approach?both should get end users to the same information?but if I know that you?re going to go straight to the Confluence page, then I suppose I could just remove this document from our ?sakaiht? (a.k.a. Sakai help tool) domain . . . I won?t until I know for sure it?s not needed there, though. >> >> Question about timing?Joe had indicated to me that the Confluence page should be ready by May 3, but it looks like it still says ?Draft?. Are we still on track for it being ready for public consumption before this weekend? >> >> best, >> >> Elizabeth Venstra >> Knowledge Management team >> University Information Technology Services >> Indiana University >> erytting at indiana.edu >> 812-855-0459 >> >> >> >> From: documentation-bounces at collab.sakaiproject.org[mailto:documentation-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin >> Sent: Monday, May 06, 2013 11:31 AM >> To: documentation at collab.sakaiproject.org >> Cc: accessibility at collab.sakaiproject.org >> Subject: [WG: Docs] Updating arkn.html for Accessibility >> >> Hi Documentation group, >> >> We are updating the Accessibility page in Sakai CLE so that it points to a Confluence page that can be updated more rapidly, as needed. >> >> >> Is this the right page, just double checking? >> >> https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.html >> >> All the existing text is going to be replaced with: >>

Accessibility information

>> Please click here for Sakai accessibility information >> >> Thanks, >> Neal > > _______________________________________________ > accessibility mailing list > accessibility at collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/accessibility > > TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" From nealcaidin at sakaifoundation.org Wed May 8 07:00:03 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Wed, 8 May 2013 10:00:03 -0400 Subject: [WG: Accessibility] [WG: Docs] Updating arkn.html for Accessibility In-Reply-To: <203CF514-A42E-4190-BACE-C8AB56DA5628@umich.edu> References: <22B638C885092643A53AC0646804BF4614D84C4D@IU-MSSG-MBX107.ads.iu.edu> <2E65B35E-9912-4B89-90F9-5C8643AE4B5E@sakaifoundation.org> <22B638C885092643A53AC0646804BF4614D85E06@IU-MSSG-MBX107.ads.iu.edu> <203CF514-A42E-4190-BACE-C8AB56DA5628@umich.edu> Message-ID: <05B811F3-0F35-4AF8-A058-0DA631CD81C3@sakaifoundation.org> Currently in help.xml there is this chunk of data: arkn Accessibility Information /sakai_accessibility/arkn.html sakai.accessibility 1) I could make up a docId with "xxx" in the name to insure it is not connected to Indiana KB, replacing arkn 2) Make up an html file in that directory, call it whatever I want and change the location to point to it 3) Add the new html file to trunk (associate with a Jira) and update the help.xml in trunk (also associated with the Jira) If that is all there is to it, I can do that. Thanks, Neal On May 8, 2013, at 9:34 AM, Beth Kirschner wrote: > Hi Neal, > > The arkn.html file is configured in the help.xml file within the same directory. There are several (e.g. help_pt_BR.xml) for alternate localized copies of the help docs. > > - Beth > > On May 8, 2013, at 8:42 AM, Neal Caidin wrote: > >> Hi Elizabeth, >> >> I wouldn't be removing the ilnk to arkn.html, I would be updating the html itself. But maybe I am missing something. I know how to create a different html file with a different name and check it into Sakai, but I don't know how to tell the Online Help to find that document. Perhaps it is just the directory structure? I don't know. Maybe Matt Jones or someone could help me figure it out. >> >> For me, the easiest thing is to update in both places, arkn.html for me and the Knowledge Base for you. Since we may never run the updater scripts again, that pull Indiana's KB information into Sakai then there is no link. But just in case it does get run one or more times before being permanently retired, at least it would overwrite with the same information. I hope that makes sense. >> >> Thanks, >> Neal >> >> >> On May 6, 2013, at 3:29 PM, "Venstra, Elizabeth" wrote: >> >>> Whatever works for you, works for me. If it?s possible on your end, and simpler, to simply remove the link to https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.htmland replace it with a direct link to the Confluence page, that might be even better, because then it wouldn?t look like a KB doc without actually being a KB doc, if you see what I mean. But if that?s tricky, by all means, let?s do your plan. I?ll go ahead and draft that revision this week (whether or not I end up making it live this weekend) and send you the text I come up with. >>> >>> best, >>> Elizabeth >>> >>> From: Neal Caidin [mailto:nealcaidin at sakaifoundation.org] >>> Sent: Monday, May 06, 2013 3:18 PM >>> To: Venstra, Elizabeth >>> Cc: documentation at collab.sakaiproject.org; accessibility at collab.sakaiproject.org; Humbert, Joseph A >>> Subject: Re: [WG: Docs] Updating arkn.html for Accessibility >>> >>> Hi Elizabeth, >>> >>> I'm not recollecting when the Confluence page should be ready. Probably Joe H. can comment. >>> >>> Here's the problem - I'm not sure if the scripts used to update Sakai CLE with the Knowledge base information will ever be run again. They might be, but I'm not sure. This is definitely not ideal. >>> >>> My suggestion is that we update them in both places with the same text? I'll update manually in Sakai CLE and you update the IU Knoweldge base? I don't expect this page to change for a long time, at least until a better online help system is figured out. So I think this will not be too bad to manage. >>> >>> What do you think? >>> >>> Thanks! >>> Neal >>> >>> >>> >>> On May 6, 2013, at 1:37 PM, "Venstra, Elizabeth" wrote: >>> >>> >>> Yes, that should be the correct page. At any rate, the four-letter docid, arkn, is the correct one that maps to the document in our repository (https://www.indiana.edu/~sakaikb/display.cgi?docid=arkn ). I was planning on changing the document in our repository as of this coming weekend, May 11, which is when we?re deploying 2.9 here at Indiana?removing the detailed content, and simply telling readers to go to the Confluence page, with a link. But Neal?just so I understand correctly?are you saying that you plan to remove the link to our repository for this document, and point straight to the Confluence page, without going through our document arkn? Or do you want it to continue to use our document, which will then point to the Confluence page? I?m fine with either approach?both should get end users to the same information?but if I know that you?re going to go straight to the Confluence page, then I suppose I could just remove this document from our ?sakaiht? (a.k.a. Sakai help tool) domain . . . I won?t until I know for sure it?s not needed there, though. >>> >>> Question about timing?Joe had indicated to me that the Confluence page should be ready by May 3, but it looks like it still says ?Draft?. Are we still on track for it being ready for public consumption before this weekend? >>> >>> best, >>> >>> Elizabeth Venstra >>> Knowledge Management team >>> University Information Technology Services >>> Indiana University >>> erytting at indiana.edu >>> 812-855-0459 >>> >>> >>> >>> From: documentation-bounces at collab.sakaiproject.org[mailto:documentation-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin >>> Sent: Monday, May 06, 2013 11:31 AM >>> To: documentation at collab.sakaiproject.org >>> Cc: accessibility at collab.sakaiproject.org >>> Subject: [WG: Docs] Updating arkn.html for Accessibility >>> >>> Hi Documentation group, >>> >>> We are updating the Accessibility page in Sakai CLE so that it points to a Confluence page that can be updated more rapidly, as needed. >>> >>> >>> Is this the right page, just double checking? >>> >>> https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.html >>> >>> All the existing text is going to be replaced with: >>>

Accessibility information

>>> Please click here for Sakai accessibility information >>> >>> Thanks, >>> Neal >> >> _______________________________________________ >> accessibility mailing list >> accessibility at collab.sakaiproject.org >> http://collab.sakaiproject.org/mailman/listinfo/accessibility >> >> TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" > From nealcaidin at sakaifoundation.org Wed May 8 11:36:10 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Wed, 8 May 2013 14:36:10 -0400 Subject: [WG: Accessibility] Fwd: [WG: Docs] Updating arkn.html for Accessibility References: <22B638C885092643A53AC0646804BF4614D89B38@IU-MSSG-MBX107.ads.iu.edu> Message-ID: FYI . I'll keep you posted as other progress is made. Cheers, Neal Begin forwarded message: > From: "Venstra, Elizabeth" > Subject: RE: [WG: Accessibility] [WG: Docs] Updating arkn.html for Accessibility > Date: May 8, 2013 11:16:41 AM EDT > To: Neal Caidin , Beth Kirschner > > Swell! > > For what it?s worth?I?m working on revisions to arkn for our upgrade this weekend right now, and it will have a Sakai version (just in case) that looks like this: > > Accessibility information > > For accessibility information for persons using adaptive technology, visit Sakai 2.9 Accessibility Documentation. > > > > -----Original Message----- > From: Neal Caidin [mailto:nealcaidin at sakaifoundation.org] > Sent: Wednesday, May 08, 2013 10:44 AM > To: Beth Kirschner > Cc: Venstra, Elizabeth > Subject: Re: [WG: Accessibility] [WG: Docs] Updating arkn.html for Accessibility > > I *think* I know how to try this locally on my PC. Professional development activity :-) > > I know where to get help now! > > If/when I get this working, I can run it by the Accessibility working group so they can see how it looks. A little different than we had envisioned, but might be okay. > > Thanks, > Neal > > On May 8, 2013, at 10:34 AM, Beth Kirschner wrote: > > > No worries - your suggestion was a good one and completely possible. > > > > - Beth > > > > On May 8, 2013, at 10:33 AM, "Venstra, Elizabeth" wrote: > > > >> And let me say that my suggestion was based on an understanding of > >> the Sakai help tool that's extremely hazy at best--I'm sure Beth > >> knows much more about it. Just so that's clear. :) > >> > >> -----Original Message----- > >> From: Beth Kirschner [mailto:bkirschn at umich.edu] > >> Sent: Wednesday, May 08, 2013 10:31 AM > >> To: Neal Caidin > >> Cc: Venstra, Elizabeth; documentation at collab.sakaiproject.org > >> Subject: Re: [WG: Accessibility] [WG: Docs] Updating arkn.html for > >> Accessibility > >> > >> I don't think you should create a new xxx document - I believe what Elizabeth was suggesting was that you change the location field to a complete URL (e.g.https://confluence.sakaiproject.org/display/2ACC/Accessibility+Working+Group). But you'll need to update all three help*.xml files to make sure that it's available to all localized versions. The "name" value must be unique across all of the help docs, butI prefer meaningful names over "xxx" (so what you have below is good). > >> > >> - Beth > >> > >> P.S. I've dropped the accessibility list from this thread because I'm not a member. Feel free to forward it along if desired. > >> > >> On May 8, 2013, at 10:00 AM, Neal Caidin wrote: > >> > >>> Currently in help.xml there is this chunk of data: > >>> > >>> arkn > >>> Accessibility Information > >>> /sakai_accessibility/arkn.html > >>> >>> name="defaultForTool">sakai.accessibility > >>> > >>> > >>> 1) I could make up a docId with "xxx" in the name to insure it is > >>> not connected to Indiana KB, replacing arkn > >>> 2) Make up an html file in that directory, call it whatever I want > >>> and change the location to point to it > >>> 3) Add the new html file to trunk (associate with a Jira) and update > >>> the help.xml in trunk (also associated with the Jira) > >>> > >>> If that is all there is to it, I can do that. > >>> > >>> Thanks, > >>> Neal > >>> > >>> > >>> On May 8, 2013, at 9:34 AM, Beth Kirschner wrote: > >>> > >>>> Hi Neal, > >>>> > >>>> The arkn.html file is configured in the help.xml file within the same directory. There are several (e.g. help_pt_BR.xml) for alternate localized copies of the help docs. > >>>> > >>>> - Beth > >>>> > >>>> On May 8, 2013, at 8:42 AM, Neal Caidin wrote: > >>>> > >>>>> Hi Elizabeth, > >>>>> > >>>>> I wouldn't be removing the ilnk to arkn.html, I would be updating the html itself. But maybe I am missing something. I know how to create a different html file with a different name and check it into Sakai, but I don't know how to tell the Online Help to find that document. Perhaps it is just the directory structure? I don't know. Maybe Matt Jones or someone could help me figure it out. > >>>>> > >>>>> For me, the easiest thing is to update in both places, arkn.html for me and the Knowledge Base for you. Since we may never run the updater scripts again, that pull Indiana's KB information into Sakai then there is no link. But just in case it does get run one or more times before being permanently retired, at least it would overwrite with the same information. I hope that makes sense. > >>>>> > >>>>> Thanks, > >>>>> Neal > >>>>> > >>>>> > >>>>> On May 6, 2013, at 3:29 PM, "Venstra, Elizabeth" wrote: > >>>>> > >>>>>> Whatever works for you, works for me. If it's possible on your end, and simpler, to simply remove the link tohttps://source.sakaiproject.org/svn/help/trunk/help/src/sakai_accessibility/arkn.htmland replace it with a direct link to the Confluence page, that might be even better, because then it wouldn't look like a KB doc without actually being a KB doc, if you see what I mean. But if that's tricky, by all means, let's do your plan. I'll go ahead and draft that revision this week (whether or not I end up making it live this weekend) and send you the text I come up with. > >>>>>> > >>>>>> best, > >>>>>> Elizabeth > >>>>>> > >>>>>> From: Neal Caidin [mailto:nealcaidin at sakaifoundation.org] > >>>>>> Sent: Monday, May 06, 2013 3:18 PM > >>>>>> To: Venstra, Elizabeth > >>>>>> Cc: documentation at collab.sakaiproject.org; > >>>>>> accessibility at collab.sakaiproject.org; Humbert, Joseph A > >>>>>> Subject: Re: [WG: Docs] Updating arkn.html for Accessibility > >>>>>> > >>>>>> Hi Elizabeth, > >>>>>> > >>>>>> I'm not recollecting when the Confluence page should be ready. Probably Joe H. can comment. > >>>>>> > >>>>>> Here's the problem - I'm not sure if the scripts used to update Sakai CLE with the Knowledge base information will ever be run again. They might be, but I'm not sure. This is definitely not ideal. > >>>>>> > >>>>>> My suggestion is that we update them in both places with the same text? I'll update manually in Sakai CLE and you update the IU Knoweldge base? I don't expect this page to change for a long time, at least until a better online help system is figured out. So I think this will not be too bad to manage. > >>>>>> > >>>>>> What do you think? > >>>>>> > >>>>>> Thanks! > >>>>>> Neal > >>>>>> > >>>>>> > >>>>>> > >>>>>> On May 6, 2013, at 1:37 PM, "Venstra, Elizabeth" wrote: > >>>>>> > >>>>>> > >>>>>> Yes, that should be the correct page. At any rate, the four-letter docid, arkn, is the correct one that maps to the document in our repository (https://www.indiana.edu/~sakaikb/display.cgi?docid=arkn ). I was planning on changing the document in our repository as of this coming weekend, May 11, which is when we're deploying 2.9 here at Indiana-removing the detailed content, and simply telling readers to go to the Confluence page, with a link. But Neal-just so I understand correctly-are you saying that you plan to remove the link to our repository for this document, and point straight to the Confluence page, without going through our document arkn? Or do you want it to continue to use our document, which will then point to the Confluence page? I'm fine with either approach-both should get end users to the same information-but if I know that you're going to go straight to the Confluence page, then I suppose I could just remove this document from our "sakaiht" (a.k.a. Sakai help tool) domain . . . I won't until I know for sure it's not needed there, though. > >>>>>> > >>>>>> Question about timing-Joe had indicated to me that the Confluence page should be ready by May 3, but it looks like it still says "Draft". Are we still on track for it being ready for public consumption before this weekend? > >>>>>> > >>>>>> best, > >>>>>> > >>>>>> Elizabeth Venstra > >>>>>> Knowledge Management team > >>>>>> University Information Technology Services Indiana University > >>>>>> erytting at indiana.edu > >>>>>> 812-855-0459 > >>>>>> > >>>>>> > >>>>>> > >>>>>> From: > >>>>>> documentation-bounces at collab.sakaiproject.org[mailto:documentatio > >>>>>> n- bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin > >>>>>> Sent: Monday, May 06, 2013 11:31 AM > >>>>>> To: documentation at collab.sakaiproject.org > >>>>>> Cc: accessibility at collab.sakaiproject.org > >>>>>> Subject: [WG: Docs] Updating arkn.html for Accessibility > >>>>>> > >>>>>> Hi Documentation group, > >>>>>> > >>>>>> We are updating the Accessibility page in Sakai CLE so that it points to a Confluence page that can be updated more rapidly, as needed. > >>>>>> > >>>>>> > >>>>>> Is this the right page, just double checking? > >>>>>> > >>>>>> https://source.sakaiproject.org/svn/help/trunk/help/src/sakai_acc > >>>>>> es > >>>>>> sibility/arkn.html > >>>>>> > >>>>>> All the existing text is going to be replaced with: > >>>>>>

Accessibility information

>>>>>> href="https://confluence.sakaiproject.org/display/2ACC/Sakai+2.9+ > >>>>>> Ac > >>>>>> cessibility+Documentation+English">Please click here for Sakai > >>>>>> accessibility information > >>>>>> > >>>>>> Thanks, > >>>>>> Neal > >>>>> > >>>>> _______________________________________________ > >>>>> accessibility mailing list > >>>>> accessibility at collab.sakaiproject.org > >>>>> http://collab.sakaiproject.org/mailman/listinfo/accessibility > >>>>> > >>>>> TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" > >>>> > >>> > >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130508/22fc68c0/attachment-0001.html From nealcaidin at sakaifoundation.org Thu May 9 11:35:36 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Thu, 9 May 2013 14:35:36 -0400 Subject: [WG: Accessibility] New idea for linking Accessibility documentation Message-ID: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> Hi Accessibility group, Elizabeth Venstra from the Documentation group provided this idea, and Beth Kirshner gave me the technical information to implement. Instead of displaying the link to the Accessibility Confluence page, we can have the Confluence page display directly within Sakai online help! I've included a short screencast (30 seconds) to show how this works - http://screencast.com/t/K9Jw8wYRP What do you think? The only potential problem I see is with images sometimes going a little off-screen (or we would need to truncate in Confluence, etc). If you like this idea, I have to check one more technical detail and then I could check into Trunk so everyone could have a look. Right now it is just on my Mac, locally. Cheers, Neal From bkirschn at umich.edu Thu May 9 11:46:28 2013 From: bkirschn at umich.edu (Beth Kirschner) Date: Thu, 9 May 2013 14:46:28 -0400 Subject: [WG: Accessibility] New idea for linking Accessibility documentation In-Reply-To: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> References: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> Message-ID: FWIW, I'd either truncate or provide smaller images to make sure it displays well within the constrains of the help window. But looks good to me otherwise. - Beth On May 9, 2013, at 2:35 PM, Neal Caidin wrote: > Hi Accessibility group, > > Elizabeth Venstra from the Documentation group provided this idea, and Beth Kirshner gave me the technical information to implement. > > Instead of displaying the link to the Accessibility Confluence page, we can have the Confluence page display directly within Sakai online help! I've included a short screencast (30 seconds) to show how this works - http://screencast.com/t/K9Jw8wYRP > > What do you think? The only potential problem I see is with images sometimes going a little off-screen (or we would need to truncate in Confluence, etc). > > If you like this idea, I have to check one more technical detail and then I could check into Trunk so everyone could have a look. Right now it is just on my Mac, locally. > > Cheers, > Neal > > _______________________________________________ > accessibility mailing list > accessibility at collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/accessibility > > TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" From johumber at iupui.edu Thu May 9 11:52:10 2013 From: johumber at iupui.edu (Humbert, Joseph A) Date: Thu, 9 May 2013 18:52:10 +0000 Subject: [WG: Accessibility] New idea for linking Accessibility documentation In-Reply-To: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> References: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> Message-ID: <906395B08AE7B542882AC81A31B69B7549A2A777@IU-MSSG-MBX110.ads.iu.edu> Hi Neil, I don't think that is a problem. When I was working with Elizabeth Venstra on the IU Sakai side, my suggestion was that the link to confluence open in that frame because users may want to continue to use other help documentation. If need be we can modify the image or provide multiple images so they do not extend off-screen. These images are not announced by Assistive Technology, due to the way confluences codes images so image captions are already provided. Do you foresee this conflicting with the i18n plan? Thankx. Joe Humbert, Accessibility Specialist UITS Adaptive Technology and Accessibility Centers Indiana University, Indianapolis and Bloomington 535 W Michigan St. IT214 E Indianapolis, IN 46202 Office Phone: (317) 274-4378 Cell Phone: (317) 644-6824 johumber at iupui.edu http://iuadapts.Indiana.edu/ -----Original Message----- From: accessibility-bounces at collab.sakaiproject.org [mailto:accessibility-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin Sent: Thursday, May 09, 2013 2:36 PM To: accessibility at collab.sakaiproject.org Subject: [WG: Accessibility] New idea for linking Accessibility documentation Hi Accessibility group, Elizabeth Venstra from the Documentation group provided this idea, and Beth Kirshner gave me the technical information to implement. Instead of displaying the link to the Accessibility Confluence page, we can have the Confluence page display directly within Sakai online help! I've included a short screencast (30 seconds) to show how this works - http://screencast.com/t/K9Jw8wYRP What do you think? The only potential problem I see is with images sometimes going a little off-screen (or we would need to truncate in Confluence, etc). If you like this idea, I have to check one more technical detail and then I could check into Trunk so everyone could have a look. Right now it is just on my Mac, locally. Cheers, Neal _______________________________________________ accessibility mailing list accessibility at collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/accessibility TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" From mstores at indiana.edu Thu May 9 11:55:35 2013 From: mstores at indiana.edu (Mary Stores) Date: Thu, 09 May 2013 14:55:35 -0400 Subject: [WG: Accessibility] New idea for linking Accessibility documentation In-Reply-To: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> References: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> Message-ID: <20130509145535.9lqodv174cw4k8wc@webmail.iu.edu> Hello, I honestly have no idea what to think. It must be an image of some sort. If you do have a verbal explanation, Jing has never been one of the most screen reader compatible places to watch videos. If it will just appear as a text with a graphical link to screen reader users, and we've already agreed on what the text says, then for me I think it would be fine. Thanks, Mary Quoting Neal Caidin : > Hi Accessibility group, > > Elizabeth Venstra from the Documentation group provided this idea, > and Beth Kirshner gave me the technical information to implement. > > Instead of displaying the link to the Accessibility Confluence page, > we can have the Confluence page display directly within Sakai online > help! I've included a short screencast (30 seconds) to show how this > works - http://screencast.com/t/K9Jw8wYRP > > What do you think? The only potential problem I see is with images > sometimes going a little off-screen (or we would need to truncate in > Confluence, etc). > > If you like this idea, I have to check one more technical detail and > then I could check into Trunk so everyone could have a look. Right > now it is just on my Mac, locally. > > Cheers, > Neal > > _______________________________________________ > accessibility mailing list > accessibility at collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/accessibility > > TO UNSUBSCRIBE: send email to > accessibility-unsubscribe at collab.sakaiproject.org with a subject of > "unsubscribe" > From nealcaidin at sakaifoundation.org Thu May 9 12:11:07 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Thu, 9 May 2013 15:11:07 -0400 Subject: [WG: Accessibility] New idea for linking Accessibility documentation In-Reply-To: <20130509145535.9lqodv174cw4k8wc@webmail.iu.edu> References: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> <20130509145535.9lqodv174cw4k8wc@webmail.iu.edu> Message-ID: Hi Mary, I didn't know that about Jing. What are some good places for screen reader compatible videos? Instead of the link that we agreed on, the Sakai online help will directly display the content of the Confluence page. I hope that explains it. To answer Joe's question. I think this is in the spirit of what we discussed with the i18n group, it is just a slightly different technical step. They would need to modify their translation of the help XML file and put the link in directly to the Confluence page with their translation. I may need to get a few more details, but if everyone is game, I can check it into trunk, let you know it's there so you can take a look directly, and notify the i18n and explain the slight change. Once I understand how all the fields need to be filled out (I understand well enough to get it to work, but that might not be sufficient), I could provide instructions to i18n, or perhaps they know already? Thanks, Neal On May 9, 2013, at 2:55 PM, Mary Stores wrote: > Hello, > > I honestly have no idea what to think. It must be an image of some > sort. If you do have a verbal explanation, Jing has never been one of > the most screen reader compatible places to watch videos. > > If it will just appear as a text with a graphical link to screen reader > users, and we've already agreed on what the text says, then for me I > think it would be fine. > Thanks, > > Mary > > Quoting Neal Caidin : > >> Hi Accessibility group, >> >> Elizabeth Venstra from the Documentation group provided this idea, >> and Beth Kirshner gave me the technical information to implement. >> >> Instead of displaying the link to the Accessibility Confluence page, >> we can have the Confluence page display directly within Sakai online >> help! I've included a short screencast (30 seconds) to show how this >> works - http://screencast.com/t/K9Jw8wYRP >> >> What do you think? The only potential problem I see is with images >> sometimes going a little off-screen (or we would need to truncate in >> Confluence, etc). >> >> If you like this idea, I have to check one more technical detail and >> then I could check into Trunk so everyone could have a look. Right >> now it is just on my Mac, locally. >> >> Cheers, >> Neal >> >> _______________________________________________ >> accessibility mailing list >> accessibility at collab.sakaiproject.org >> http://collab.sakaiproject.org/mailman/listinfo/accessibility >> >> TO UNSUBSCRIBE: send email to >> accessibility-unsubscribe at collab.sakaiproject.org with a subject of >> "unsubscribe" >> > > > > _______________________________________________ > accessibility mailing list > accessibility at collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/accessibility > > TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" From johumber at iupui.edu Thu May 9 12:12:35 2013 From: johumber at iupui.edu (Humbert, Joseph A) Date: Thu, 9 May 2013 19:12:35 +0000 Subject: [WG: Accessibility] New idea for linking Accessibility documentation In-Reply-To: References: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> <20130509145535.9lqodv174cw4k8wc@webmail.iu.edu> Message-ID: <906395B08AE7B542882AC81A31B69B7549A2ACCF@IU-MSSG-MBX110.ads.iu.edu> Sounds good to me. - Joe -----Original Message----- From: accessibility-bounces at collab.sakaiproject.org [mailto:accessibility-bounces at collab.sakaiproject.org] On Behalf Of Neal Caidin Sent: Thursday, May 09, 2013 3:11 PM To: Stores, Mary A. Cc: accessibility at collab.sakaiproject.org Subject: Re: [WG: Accessibility] New idea for linking Accessibility documentation Hi Mary, I didn't know that about Jing. What are some good places for screen reader compatible videos? Instead of the link that we agreed on, the Sakai online help will directly display the content of the Confluence page. I hope that explains it. To answer Joe's question. I think this is in the spirit of what we discussed with the i18n group, it is just a slightly different technical step. They would need to modify their translation of the help XML file and put the link in directly to the Confluence page with their translation. I may need to get a few more details, but if everyone is game, I can check it into trunk, let you know it's there so you can take a look directly, and notify the i18n and explain the slight change. Once I understand how all the fields need to be filled out (I understand well enough to get it to work, but that might not be sufficient), I could provide instructions to i18n, or perhaps they know already? Thanks, Neal On May 9, 2013, at 2:55 PM, Mary Stores wrote: > Hello, > > I honestly have no idea what to think. It must be an image of some > sort. If you do have a verbal explanation, Jing has never been one of > the most screen reader compatible places to watch videos. > > If it will just appear as a text with a graphical link to screen > reader users, and we've already agreed on what the text says, then for > me I think it would be fine. > Thanks, > > Mary > > Quoting Neal Caidin : > >> Hi Accessibility group, >> >> Elizabeth Venstra from the Documentation group provided this idea, >> and Beth Kirshner gave me the technical information to implement. >> >> Instead of displaying the link to the Accessibility Confluence page, >> we can have the Confluence page display directly within Sakai online >> help! I've included a short screencast (30 seconds) to show how this >> works - http://screencast.com/t/K9Jw8wYRP >> >> What do you think? The only potential problem I see is with images >> sometimes going a little off-screen (or we would need to truncate in >> Confluence, etc). >> >> If you like this idea, I have to check one more technical detail and >> then I could check into Trunk so everyone could have a look. Right >> now it is just on my Mac, locally. >> >> Cheers, >> Neal >> >> _______________________________________________ >> accessibility mailing list >> accessibility at collab.sakaiproject.org >> http://collab.sakaiproject.org/mailman/listinfo/accessibility >> >> TO UNSUBSCRIBE: send email to >> accessibility-unsubscribe at collab.sakaiproject.org with a subject of >> "unsubscribe" >> > > > > _______________________________________________ > accessibility mailing list > accessibility at collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/accessibility > > TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" _______________________________________________ accessibility mailing list accessibility at collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/accessibility TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" From nealcaidin at sakaifoundation.org Mon May 13 06:04:49 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Mon, 13 May 2013 09:04:49 -0400 Subject: [WG: Accessibility] Sakai CLE 2.9.2-rc02 (Release Candidate 02) : Ready for QA testing In-Reply-To: References: Message-ID: <8FF81434-2F50-4E2F-A5E6-87E59E6F5666@sakaifoundation.org> Hi All, Testing has commenced for Release Candidate 02 of Sakai CLE 2.9.2 . Currently we have one QA server. Others may be added in the next several days. The goal is to complete testing this week, with a team check-in by teleconference on Thursday morning Eastern Daylight time (-4 GMT). The Test Plan is at https://confluence.sakaiproject.org/display/QA/2.9+Test+Fest Testing Focus ------------------------------------ * Jira testing - testing issues fixed from Release Candidate 01 * Deep Regression testing - CK Editor (akai Rich Text Editor), which is used throughout the Sakai CLE interface. * Shallow Regression testing -Lessons and Web Content tool. Time permitting other tools as well. * "Tester's Choice" - test anything you want, perhaps an area of Sakai CLE with which you are familiar or one which is important to your institution. Record your results. Report bugs in Jira. QA Check-in --------------------------------- When: Thursday at 9 am Eastern / 1 pm GMT Default Dial-in Number:+1-323-375-2185 Your Conference Code: 8600146 Join Online: http://etherpad.ctools.org/qa-2013-02-19 Find a Dial in number in your city: https://apps.calliflower.com/account/call_in_numbers?organizer=328940 Skype: Add ?calliflowerskype? as a contact in Skype. You can then call Calliflower directly from Skype. Please contact me if you have any questions - nealcaidin at sakaifoundation.org Regards, Neal Caidin Sakai CLE Community Coordinator nealcaidin at sakaifoundation.org Skype: nealkdin AIM: ncaidin at aol.com From mstores at indiana.edu Mon May 13 09:32:28 2013 From: mstores at indiana.edu (Mary Stores) Date: Mon, 13 May 2013 12:32:28 -0400 Subject: [WG: Accessibility] New idea for linking Accessibility documentation In-Reply-To: References: <09F58F69-D890-4945-96D6-4857DAD9C355@sakaifoundation.org> <20130509145535.9lqodv174cw4k8wc@webmail.iu.edu> Message-ID: <20130513123228.fj7whppi684wowko@webmail.iu.edu> Hi Neal, I have found the best solution is that if someone requests the video be sent as an attachment over email, they can then play it in their own media player. I am glad you sent the Jing video, though; it has been several years since I tried to access videos from there, and it's always good to know whether or not things might have changed. Thanks for your description. I have a clear understanding of what is going on now. I currently don't know of any video uploades sites that don't have accessibility issues. I do watch Youtube videos, and in a roundabout wy you can listen to Facebook videos. But other than that, I would have to do some research. Mary Quoting Neal Caidin : > Hi Mary, > > I didn't know that about Jing. What are some good places for screen > reader compatible videos? > > Instead of the link that we agreed on, the Sakai online help will > directly display the content of the Confluence page. I hope that > explains it. > > To answer Joe's question. I think this is in the spirit of what we > discussed with the i18n group, it is just a slightly different > technical step. They would need to modify their translation of the > help XML file and put the link in directly to the Confluence page > with their translation. I may need to get a few more details, but if > everyone is game, I can check it into trunk, let you know it's there > so you can take a look directly, and notify the i18n and explain the > slight change. Once I understand how all the fields need to be filled > out (I understand well enough to get it to work, but that might not > be sufficient), I could provide instructions to i18n, or perhaps they > know already? > > Thanks, > Neal > > > On May 9, 2013, at 2:55 PM, Mary Stores wrote: > >> Hello, >> >> I honestly have no idea what to think. It must be an image of some >> sort. If you do have a verbal explanation, Jing has never been one of >> the most screen reader compatible places to watch videos. >> >> If it will just appear as a text with a graphical link to screen reader >> users, and we've already agreed on what the text says, then for me I >> think it would be fine. >> Thanks, >> >> Mary >> >> Quoting Neal Caidin : >> >>> Hi Accessibility group, >>> >>> Elizabeth Venstra from the Documentation group provided this idea, >>> and Beth Kirshner gave me the technical information to implement. >>> >>> Instead of displaying the link to the Accessibility Confluence page, >>> we can have the Confluence page display directly within Sakai online >>> help! I've included a short screencast (30 seconds) to show how this >>> works - http://screencast.com/t/K9Jw8wYRP >>> >>> What do you think? The only potential problem I see is with images >>> sometimes going a little off-screen (or we would need to truncate in >>> Confluence, etc). >>> >>> If you like this idea, I have to check one more technical detail and >>> then I could check into Trunk so everyone could have a look. Right >>> now it is just on my Mac, locally. >>> >>> Cheers, >>> Neal >>> >>> _______________________________________________ >>> accessibility mailing list >>> accessibility at collab.sakaiproject.org >>> http://collab.sakaiproject.org/mailman/listinfo/accessibility >>> >>> TO UNSUBSCRIBE: send email to >>> accessibility-unsubscribe at collab.sakaiproject.org with a subject of >>> "unsubscribe" >>> >> >> >> >> _______________________________________________ >> accessibility mailing list >> accessibility at collab.sakaiproject.org >> http://collab.sakaiproject.org/mailman/listinfo/accessibility >> >> TO UNSUBSCRIBE: send email to >> accessibility-unsubscribe at collab.sakaiproject.org with a subject of >> "unsubscribe" > > From kamann at stanford.edu Mon May 13 15:48:31 2013 From: kamann at stanford.edu (Keli Sato Amann) Date: Mon, 13 May 2013 15:48:31 -0700 (PDT) Subject: [WG: Accessibility] are browser spell checks considered accessible? In-Reply-To: <1026891616.973534.1368485046889.JavaMail.root@stanford.edu> Message-ID: <296004316.979973.1368485311223.JavaMail.root@stanford.edu> Hi, SAK-19538 turns off the ckeditor spellchecker because it is an add-on that runs advertisements. The alternative is to enable the browser specific spellcheckers, which is probably what we will do. It sounds like a great suggestion, except that Alan Berg made a comment in the JIRA that this is "probably not accessible." I don't know if he has specific information, does anyone know much about whether this is an actual problem? Keli Amann User Experience Specialist Academic Computing Services, Stanford University From arwhyte at umich.edu Tue May 14 15:40:33 2013 From: arwhyte at umich.edu (Anthony Whyte) Date: Tue, 14 May 2013 15:40:33 -0700 Subject: [WG: Accessibility] University of Illinois Accessibility Report (Sakai 2.8, BB, D2L, Moodle) Message-ID: <8A11B730-ABE5-4893-8437-0C3C5A82A6B0@umich.edu> For article see http://campustechnology.com/Articles/2013/05/13/Study-Ranks-Accessibility-of-Top-Learning-Management-Systems.aspx?Page=2 For report see https://dl.dropboxusercontent.com/u/3486333/csun2013/lms_compared_paper_2013.html Cheers, Anth -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130514/5334781f/attachment.html From nealcaidin at sakaifoundation.org Wed May 15 05:31:42 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Wed, 15 May 2013 08:31:42 -0400 Subject: [WG: Accessibility] Sakai 2.9.2-rc02 testing status - new QA server online In-Reply-To: <8FF81434-2F50-4E2F-A5E6-87E59E6F5666@sakaifoundation.org> References: <8FF81434-2F50-4E2F-A5E6-87E59E6F5666@sakaifoundation.org> Message-ID: Please continue to help with testing RC02 - release candidate 02 for Sakai CLE 2.9.2 We now have two QA servers, one with the default security settings (AntiSamy off) and one with the most restrictive security settings (AntiSamy on/high). Details on the Test Plan at https://confluence.sakaiproject.org/display/QA/2.9+Test+Fest QA check-in tomorrow morning, Thursday, May 16 at 9 am Eastern / 1 pm GMT ---------------------------------------------------------------------------------- When: Thursday, May 16, at 9 am Eastern / 1 pm GMT Default Dial-in Number:+1-323-375-2185 Your Conference Code: 8600146 Join Online: http://etherpad.ctools.org/qa-2013-05-16 Find a Dial in number in your city: https://apps.calliflower.com/account/call_in_numbers?organizer=328940 Skype: Add ?calliflowerskype? as a contact in Skype. You can then call Calliflower directly from Skype. Cheers, Neal Caidin Sakai CLE Community Coordinator nealcaidin at sakaifoundation.org Skype: nealkdin AIM: ncaidin at aol.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130515/1ae10d41/attachment.html From johumber at iupui.edu Wed May 15 08:28:25 2013 From: johumber at iupui.edu (Humbert, Joseph A) Date: Wed, 15 May 2013 15:28:25 +0000 Subject: [WG: Accessibility] Reminder: Accessibility WG Teleconference TOMORROW Thursday May 16th, 2013 and Previous Meeting Minutes Message-ID: <906395B08AE7B542882AC81A31B69B754FF74CD5@IU-MSSG-MBX110.ads.iu.edu> Hello everyone, This is a reminder that the next teleconference for the Accessibility WG will be TOMORROW Thursday May 16th at 2 PM Eastern. Phone: 812-856-7060 PIN: 22348 Here are the notes for our previous teleconference: May 2nd, 2013: https://confluence.sakaiproject.org/display/2ACC/Accessibility+WG+Teleconference+Minutes+05-02-2013 Notes URL: * http://free.primarypad.com/p/awg-05-16-2013 Agenda Any Other Business 1. Changing leadership of the Sakai Accessibility Working Group 2. Discussion of progress on updating Sakai a11y help documentation 3. CK Editor content creation guidelines Sakai Accessibility Review 4. A11y Jiras that need testing/review 5. Develop list of Jiras to push for 2.9.3 Sakai 2.9.x 6. Release Team Meeting Notes (If time is available) The full agenda on Etherpad! Joe Humbert, Adaptive Technology and Accessibility Specialist UITS Adaptive Technology and Accessibility Centers Indiana University, Indianapolis and Bloomington 535 W Michigan St. IT214 E Indianapolis, IN 46202 Office Phone: (317) 274-4378 Cell Phone: (317) 644-6824 johumber at iupui.edu http://iuadapts.Indiana.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130515/4c31b01a/attachment-0001.html From ruzwyshyn at APUS.EDU Wed May 15 08:56:13 2013 From: ruzwyshyn at APUS.EDU (Uzwyshyn, Raymond) Date: Wed, 15 May 2013 15:56:13 +0000 Subject: [WG: Accessibility] accessibility Digest, Vol 49, Issue 12 In-Reply-To: References: Message-ID: Please remove me from this list. Thanks, Ray Ray Uzwyshyn, Ph.D., MLIS | Director of Libraries American Public University System American Military University ?| ?American Public University 111 W. Congress Street, Charles Town, WV 25414 T 304-885-5372 | F 304-724-0937 |? ruzwyshyn at apus.edu ?| www.apus.edu -----Original Message----- From: accessibility-bounces at collab.sakaiproject.org [mailto:accessibility-bounces at collab.sakaiproject.org] On Behalf Of accessibility-request at collab.sakaiproject.org Sent: Wednesday, May 15, 2013 11:28 AM To: accessibility at collab.sakaiproject.org Subject: accessibility Digest, Vol 49, Issue 12 Send accessibility mailing list submissions to accessibility at collab.sakaiproject.org To subscribe or unsubscribe via the World Wide Web, visit http://collab.sakaiproject.org/mailman/listinfo/accessibility or, via email, send a message with subject or body 'help' to accessibility-request at collab.sakaiproject.org You can reach the person managing the list at accessibility-owner at collab.sakaiproject.org When replying, please edit your Subject line so it is more specific than "Re: Contents of accessibility digest..." Today's Topics: 1. University of Illinois Accessibility Report (Sakai 2.8, BB, D2L, Moodle) (Anthony Whyte) 2. Sakai 2.9.2-rc02 testing status - new QA server online (Neal Caidin) 3. Reminder: Accessibility WG Teleconference TOMORROW Thursday May 16th, 2013 and Previous Meeting Minutes (Humbert, Joseph A) ---------------------------------------------------------------------- Message: 1 Date: Tue, 14 May 2013 15:40:33 -0700 From: Anthony Whyte Subject: [WG: Accessibility] University of Illinois Accessibility Report (Sakai 2.8, BB, D2L, Moodle) To: "accessibility at collab.sakaiproject.org WG" Message-ID: <8A11B730-ABE5-4893-8437-0C3C5A82A6B0 at umich.edu> Content-Type: text/plain; charset="us-ascii" For article see http://campustechnology.com/Articles/2013/05/13/Study-Ranks-Accessibility-of-Top-Learning-Management-Systems.aspx?Page=2 For report see https://dl.dropboxusercontent.com/u/3486333/csun2013/lms_compared_paper_2013.html Cheers, Anth -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130514/5334781f/attachment-0001.html ------------------------------ Message: 2 Date: Wed, 15 May 2013 08:31:42 -0400 From: Neal Caidin Subject: [WG: Accessibility] Sakai 2.9.2-rc02 testing status - new QA server online To: "sakai-dev at collab.sakaiproject.org (sakai-dev at collab.sakaiproject.org)" , "sakai-qa at collab.sakaiproject.org QA" , accessibility at collab.sakaiproject.org, "i18n at collab.sakaiproject.org i18n" Message-ID: Content-Type: text/plain; charset="windows-1252" Please continue to help with testing RC02 - release candidate 02 for Sakai CLE 2.9.2 We now have two QA servers, one with the default security settings (AntiSamy off) and one with the most restrictive security settings (AntiSamy on/high). Details on the Test Plan at https://confluence.sakaiproject.org/display/QA/2.9+Test+Fest QA check-in tomorrow morning, Thursday, May 16 at 9 am Eastern / 1 pm GMT ---------------------------------------------------------------------------------- When: Thursday, May 16, at 9 am Eastern / 1 pm GMT Default Dial-in Number:+1-323-375-2185 Your Conference Code: 8600146 Join Online: http://etherpad.ctools.org/qa-2013-05-16 Find a Dial in number in your city: https://apps.calliflower.com/account/call_in_numbers?organizer=328940 Skype: Add ?calliflowerskype? as a contact in Skype. You can then call Calliflower directly from Skype. Cheers, Neal Caidin Sakai CLE Community Coordinator nealcaidin at sakaifoundation.org Skype: nealkdin AIM: ncaidin at aol.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130515/1ae10d41/attachment-0001.html ------------------------------ Message: 3 Date: Wed, 15 May 2013 15:28:25 +0000 From: "Humbert, Joseph A" Subject: [WG: Accessibility] Reminder: Accessibility WG Teleconference TOMORROW Thursday May 16th, 2013 and Previous Meeting Minutes To: "accessibility at collab.sakaiproject.org" Message-ID: <906395B08AE7B542882AC81A31B69B754FF74CD5 at IU-MSSG-MBX110.ads.iu.edu> Content-Type: text/plain; charset="us-ascii" Hello everyone, This is a reminder that the next teleconference for the Accessibility WG will be TOMORROW Thursday May 16th at 2 PM Eastern. Phone: 812-856-7060 PIN: 22348 Here are the notes for our previous teleconference: May 2nd, 2013: https://confluence.sakaiproject.org/display/2ACC/Accessibility+WG+Teleconference+Minutes+05-02-2013 Notes URL: * http://free.primarypad.com/p/awg-05-16-2013 Agenda Any Other Business 1. Changing leadership of the Sakai Accessibility Working Group 2. Discussion of progress on updating Sakai a11y help documentation 3. CK Editor content creation guidelines Sakai Accessibility Review 4. A11y Jiras that need testing/review 5. Develop list of Jiras to push for 2.9.3 Sakai 2.9.x 6. Release Team Meeting Notes (If time is available) The full agenda on Etherpad! Joe Humbert, Adaptive Technology and Accessibility Specialist UITS Adaptive Technology and Accessibility Centers Indiana University, Indianapolis and Bloomington 535 W Michigan St. IT214 E Indianapolis, IN 46202 Office Phone: (317) 274-4378 Cell Phone: (317) 644-6824 johumber at iupui.edu http://iuadapts.Indiana.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130515/4c31b01a/attachment.html ------------------------------ _______________________________________________ accessibility mailing list accessibility at collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/accessibility End of accessibility Digest, Vol 49, Issue 12 ********************************************* This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system. From nealcaidin at sakaifoundation.org Wed May 15 10:02:36 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Wed, 15 May 2013 13:02:36 -0400 Subject: [WG: Accessibility] accessibility Digest, Vol 49, Issue 12 In-Reply-To: References: Message-ID: <79C8BFA9-A51F-4714-8253-CDAB699E6B09@sakaifoundation.org> Hi Ray, Instructions are at the bottom of the email. For convenience , here's how to unsubscribe: TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" I hope that helps. Cheers, Neal On May 15, 2013, at 11:56 AM, "Uzwyshyn, Raymond" wrote: > Please remove me from this list. > > Thanks, > > Ray > > Ray Uzwyshyn, Ph.D., MLIS | Director of Libraries > > American Public University System > American Military University | American Public University > 111 W. Congress Street, Charles Town, WV 25414 > T 304-885-5372 | F 304-724-0937 | ruzwyshyn at apus.edu | www.apus.edu > > -----Original Message----- > From: accessibility-bounces at collab.sakaiproject.org [mailto:accessibility-bounces at collab.sakaiproject.org] On Behalf Of accessibility-request at collab.sakaiproject.org > Sent: Wednesday, May 15, 2013 11:28 AM > To: accessibility at collab.sakaiproject.org > Subject: accessibility Digest, Vol 49, Issue 12 > > Send accessibility mailing list submissions to > accessibility at collab.sakaiproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://collab.sakaiproject.org/mailman/listinfo/accessibility > or, via email, send a message with subject or body 'help' to > accessibility-request at collab.sakaiproject.org > > You can reach the person managing the list at > accessibility-owner at collab.sakaiproject.org > > When replying, please edit your Subject line so it is more specific than "Re: Contents of accessibility digest..." > > > Today's Topics: > > 1. University of Illinois Accessibility Report (Sakai 2.8, BB, > D2L, Moodle) (Anthony Whyte) > 2. Sakai 2.9.2-rc02 testing status - new QA server online > (Neal Caidin) > 3. Reminder: Accessibility WG Teleconference TOMORROW Thursday > May 16th, 2013 and Previous Meeting Minutes (Humbert, Joseph A) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 14 May 2013 15:40:33 -0700 > From: Anthony Whyte > Subject: [WG: Accessibility] University of Illinois Accessibility > Report (Sakai 2.8, BB, D2L, Moodle) > To: "accessibility at collab.sakaiproject.org WG" > > Message-ID: <8A11B730-ABE5-4893-8437-0C3C5A82A6B0 at umich.edu> > Content-Type: text/plain; charset="us-ascii" > > For article see > > http://campustechnology.com/Articles/2013/05/13/Study-Ranks-Accessibility-of-Top-Learning-Management-Systems.aspx?Page=2 > > For report see > > https://dl.dropboxusercontent.com/u/3486333/csun2013/lms_compared_paper_2013.html > > Cheers, > > Anth > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130514/5334781f/attachment-0001.html > > ------------------------------ > > Message: 2 > Date: Wed, 15 May 2013 08:31:42 -0400 > From: Neal Caidin > Subject: [WG: Accessibility] Sakai 2.9.2-rc02 testing status - new QA > server online > To: "sakai-dev at collab.sakaiproject.org > (sakai-dev at collab.sakaiproject.org)" > , "sakai-qa at collab.sakaiproject.org > QA" , > accessibility at collab.sakaiproject.org, "i18n at collab.sakaiproject.org > i18n" > Message-ID: > Content-Type: text/plain; charset="windows-1252" > > Please continue to help with testing RC02 - release candidate 02 for Sakai CLE 2.9.2 > > We now have two QA servers, one with the default security settings (AntiSamy off) and one with the most restrictive security settings (AntiSamy on/high). Details on the Test Plan at https://confluence.sakaiproject.org/display/QA/2.9+Test+Fest > > QA check-in tomorrow morning, Thursday, May 16 at 9 am Eastern / 1 pm GMT > ---------------------------------------------------------------------------------- > When: Thursday, May 16, at 9 am Eastern / 1 pm GMT > > Default Dial-in Number:+1-323-375-2185 > > Your Conference Code: 8600146 > > Join Online: > http://etherpad.ctools.org/qa-2013-05-16 > > Find a Dial in number in your city: > https://apps.calliflower.com/account/call_in_numbers?organizer=328940 > > Skype: > Add ?calliflowerskype? as a contact in Skype. You can then call Calliflower directly from Skype. > > > Cheers, > > Neal Caidin > > Sakai CLE Community Coordinator > nealcaidin at sakaifoundation.org > Skype: nealkdin > AIM: ncaidin at aol.com > > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130515/1ae10d41/attachment-0001.html > > ------------------------------ > > Message: 3 > Date: Wed, 15 May 2013 15:28:25 +0000 > From: "Humbert, Joseph A" > Subject: [WG: Accessibility] Reminder: Accessibility WG Teleconference > TOMORROW Thursday May 16th, 2013 and Previous Meeting Minutes > To: "accessibility at collab.sakaiproject.org" > > Message-ID: > <906395B08AE7B542882AC81A31B69B754FF74CD5 at IU-MSSG-MBX110.ads.iu.edu> > Content-Type: text/plain; charset="us-ascii" > > Hello everyone, > > This is a reminder that the next teleconference for the Accessibility WG will be TOMORROW Thursday May 16th at 2 PM Eastern. > > Phone: 812-856-7060 > PIN: 22348 > > Here are the notes for our previous teleconference: > > May 2nd, 2013: https://confluence.sakaiproject.org/display/2ACC/Accessibility+WG+Teleconference+Minutes+05-02-2013 > > Notes URL: > > > * http://free.primarypad.com/p/awg-05-16-2013 > > Agenda > > Any Other Business > 1. Changing leadership of the Sakai Accessibility Working Group > 2. Discussion of progress on updating Sakai a11y help documentation > 3. CK Editor content creation guidelines > Sakai Accessibility Review > > > 4. A11y Jiras that need testing/review > > 5. Develop list of Jiras to push for 2.9.3 > > Sakai 2.9.x > > > 6. Release Team Meeting Notes (If time is available) > > The full agenda on Etherpad! > > Joe Humbert, Adaptive Technology and Accessibility Specialist UITS Adaptive Technology and Accessibility Centers Indiana University, Indianapolis and Bloomington > 535 W Michigan St. IT214 E > Indianapolis, IN 46202 > Office Phone: (317) 274-4378 > Cell Phone: (317) 644-6824 > johumber at iupui.edu > http://iuadapts.Indiana.edu/ > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130515/4c31b01a/attachment.html > > ------------------------------ > > _______________________________________________ > accessibility mailing list > accessibility at collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/accessibility > > > End of accessibility Digest, Vol 49, Issue 12 > ********************************************* > This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system. > > _______________________________________________ > accessibility mailing list > accessibility at collab.sakaiproject.org > http://collab.sakaiproject.org/mailman/listinfo/accessibility > > TO UNSUBSCRIBE: send email to accessibility-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe" -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130515/f1cc5b67/attachment-0001.html From nealcaidin at sakaifoundation.org Mon May 20 06:48:41 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Mon, 20 May 2013 09:48:41 -0400 Subject: [WG: Accessibility] Sakai CLE 2.9.2-rc03 coming soon In-Reply-To: References: <8FF81434-2F50-4E2F-A5E6-87E59E6F5666@sakaifoundation.org> Message-ID: <0073BCCD-9F48-4C7D-A199-D5489CE18CF3@sakaifoundation.org> [dev, qa, accessibility, i18n, prod] Hi all, It appears we are getting very close to the release of Sakai CLE 2.9.2 ! We are rolling out a Sakai CLE 2.9.2-rc03 (RC03) within the next day or two. RC03 only has a couple of fixes in it. So the plan is to test the fixes, "kick the tires" and then release for GA (general availability, aka production). "Kicking the tires" means some light testing to make sure nothing obvious is wrong. Therefore once RC03 is available we will take just about a day or two for testing, at most. If you have documentation that needs to be a part of the release notes - https://confluence.sakaiproject.org/display/DOC/Sakai+CLE+2.9+release+notes , please update them now, or by the end of this week. If you would like me to do this for you, please provide me the text to me. Please say if you have any concerns with the release process or with Sakai CLE 2.9.2 itself before it is, well, released. :-) Thanks, Neal Caidin Sakai CLE Community Coordinator nealcaidin at sakaifoundation.org Skype: nealkdin AIM: ncaidin at aol.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130520/5f109d77/attachment.html From nealcaidin at sakaifoundation.org Tue May 21 11:38:27 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Tue, 21 May 2013 14:38:27 -0400 Subject: [WG: Accessibility] CLE 2.9.2-RC03 - Wednesday testing only Message-ID: <60FAAC94-79E0-46CC-A5B8-4442CBDCD123@sakaifoundation.org> Hi All, https://confluence.sakaiproject.org/display/QA/2.9+Test+Fest Sakai CLE 2.9.2-RC03 has been released. We are only planning a "kick the tires" testing. Suggestions are on the Test Fest page above and I did create a Google doc. Primarily, if you run into any potential blocker issues, please let the email list(s) know as soon as possible so that it can be triaged. Testing is for Wednesday only. Pending approval by the TCC (Technical Coordination Committee) and the completion of RC03 testing, we will proceed with packaging the CLE 2.9.2 release! Keep your fingers crossed. Thanks, Neal Caidin Sakai CLE Community Coordinator nealcaidin at sakaifoundation.org Skype: nealkdin AIM: ncaidin at aol.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130521/5641b438/attachment.html From johumber at iupui.edu Tue May 21 12:20:13 2013 From: johumber at iupui.edu (Humbert, Joseph A) Date: Tue, 21 May 2013 19:20:13 +0000 Subject: [WG: Accessibility] Change in Leadership of the Sakai Accessibility Working Group Message-ID: <906395B08AE7B542882AC81A31B69B754FFDB4CA@IU-MSSG-MBX110.ads.iu.edu> Hello Members of the Sakai Accessibility Working Group, I am writing to inform all of you that I will be stepping down as the lead of the Sakai Accessibility Working Group (AWG) on June 30th, 2013. Do not worry, I will not be ending my involvement with the AWG, I will just not be taking the lead role. I have enjoyed overseeing the many activities of our group, and interacting directly with many of you. We, as a working group, have made significant improvements to the accessibility of the Sakai CLE platform. Someone from Indiana University has lead this group for almost the past 5 years. Now, it is time to pass the torch, and for one or more of you to step up to keep the momentum of this group going strong on all of the accessibility improvements to Sakai, which have been made over the last several years. I look forward to the continued improvement of the accessibility of Sakai for years to come. Thank you. Sincerely, Joe Humbert, Accessibility Specialist UITS Adaptive Technology and Accessibility Centers Indiana University, Indianapolis and Bloomington 535 W Michigan St. IT214 E Indianapolis, IN 46202 Office Phone: (317) 274-4378 Cell Phone: (317) 644-6824 johumber at iupui.edu http://iuadapts.Indiana.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130521/cfa9c6c9/attachment.html From nealcaidin at sakaifoundation.org Tue May 28 06:19:30 2013 From: nealcaidin at sakaifoundation.org (Neal Caidin) Date: Tue, 28 May 2013 09:19:30 -0400 Subject: [WG: Accessibility] Recruiting for Sakai CLE Accessibility team Message-ID: Dear all, The Accessibility group (aka a11y) could use additional people power. Indiana has been providing leadership for this group for about 5 years and they feel it is time to step down from that role, though still actively involved in the group. Ideally, we would like to find someone who could provide leadership for the group, but at least having more participants could provide an opportunity to share duties (convening meetings, etc). Accessibility, as I'm sure you are all aware, is an important aspect to the success of Sakai CLE, and continuing the great work of this group should be a priority for the community. If your institution might be able to contribute, please give it the utmost consideration so that CLE can continue to provide this important service at the highest level possible. Contact me if you wish to discuss. Thanks for your attention. Regards, Neal Caidin Sakai CLE Community Coordinator nealcaidin at sakaifoundation.org Skype: nealkdin AIM: ncaidin at aol.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130528/72a2dcaa/attachment.html From johumber at iupui.edu Thu May 30 06:05:14 2013 From: johumber at iupui.edu (Humbert, Joseph A) Date: Thu, 30 May 2013 13:05:14 +0000 Subject: [WG: Accessibility] Reminder: Accessibility WG Teleconference TODAY Thursday May 30th, 2013 Message-ID: <906395B08AE7B542882AC81A31B69B75500631AA@IU-MSSG-MBX110.ads.iu.edu> Hello everyone, This is a reminder that the next teleconference for the Accessibility WG will be Today Thursday May 30th at 2 PM Eastern. Phone: 812-856-7060 PIN: 22348 Notes URL: * http://free.primarypad.com/p/awg-05-30-2013 Agenda Any Other Business 1. CK Editor content creation guidelines Sakai Accessibility Review 2. A11y Jiras that need testing/review 3. Review of Lessonbuilder Tool Sakai 2.9.x 4. Release Team Meeting Notes (If time is available) The full agenda on Etherpad! Joe Humbert, Accessibility Specialist UITS Adaptive Technology and Accessibility Centers Indiana University, Indianapolis and Bloomington 535 W Michigan St. IT214 E Indianapolis, IN 46202 Office Phone: (317) 274-4378 Cell Phone: (317) 644-6824 johumber at iupui.edu http://iuadapts.Indiana.edu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://collab.sakaiproject.org/pipermail/accessibility/attachments/20130530/8748cd78/attachment.html