[cle-release-team] [WG: Accessibility] SAM-1692

[Neal Caidin]

I'm putting a label of "292triage" on it so that we can review if this is something we can fix for 2.9.2.

Thanks,
Neal

On Nov 20, 2012, at 4:26 AM, Jean-Francois Leveque <jean-francois.leveque at upmc.fr> wrote:

> We don't know if the current trunk changes are at least a partial fix.
> 
> I suggest we don't merge unless we know more.
> 
> This is not a new issue, but this is, AFAICT, the first time we really 
> think about this issue.
> 
> Cheers
> J-F
> 
> On 19/11/2012 21:13, Steve Swinsburg wrote:
>> The fix required is no longer a samigo issue.
>> 
>> It will touch every page of every tool, since it goes into the HTML attribute for the page. And the fix may be very difficult for tools that use plain HTML templates like RSF, Wicket, and possibly Trimpath.
>> 
>> This has obviously been 'broken' for a very long time, probably since the beginning of Sakai, so I am skeptical that it has only just become an issue for screen reading software.
>> 
>> There is a lot of work in resolving this. Are we 200% sure that the fix suggested is the correct one? What if there is no default language declared in the HTML tag? What happens to the screen reader? That would be easier than trying to make every page dynamic, if it worked.
>> 
>> Cheers
>> Steve
>> 
>> Sent from my iPhone
>> 
>> On 20/11/2012, at 6:50, "Humbert, Joseph A"<johumber at iupui.edu>  wrote:
>> 
>>> If the change sets the primary language attribute to the user specified language,  it should fix the problem according to the comments.  I'm not exactly which tools are effected by this.  Anyone could test this I would assume by changing the language in the user settings and checking the primary language attribute of the HTML element to make sure it matches.  Our student tester, who tested this before, is out of the country currently.
>>> 
>>> According to the comment it looks like at overarching ticket is needs and sub-tasks for each instance.  I'm not sure how much work this would take, but I can devote time to testing today, tomorrow and next week.
>>> 
>>> 
>>> 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/
>>> ________________________________________
>>> From: Neal Caidin [nealcaidin at sakaifoundation.org]
>>> Sent: Monday, November 19, 2012 2:39 PM
>>> To: Humbert, Joseph A
>>> Cc: cle-release-team at collab.sakaiproject.org; accessibility at collab.sakaiproject.org
>>> Subject: Re: [WG: Accessibility] SAM-1692
>>> 
>>> Hi Joe,
>>> 
>>> Do you think we will get this tested in time for 2.9.1 ? Who would be in a good position to test this change?
>>> 
>>> It wasn't clear to me if the changes actually fixed the problem or if this is an interim workaround? (maybe needs a new ticket for a more comprehensive fix?)
>>> 
>>> Thanks,
>>> Neal
>>> 
>>> On Nov 19, 2012, at 2:31 PM, "Humbert, Joseph A"<johumber at iupui.edu>  wrote:
>>> 
>>>> It can cause significant issues for international users of adaptive technology.
>>>> 
>>>> 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/
>>>> ________________________________________
>>>> From: accessibility-bounces at collab.sakaiproject.org [accessibility-bounces at collab.sakaiproject.org] on behalf of Neal Caidin [nealcaidin at sakaifoundation.org]
>>>> Sent: Monday, November 19, 2012 1:15 PM
>>>> To: cle-release-team at collab.sakaiproject.org; accessibility at collab.sakaiproject.org
>>>> Subject: [WG: Accessibility] SAM-1692
>>>> 
>>>> Hi all,
>>>> 
>>>> A couple of questions about SAM-1692.
>>>> 
>>>> https://jira.sakaiproject.org/browse/SAM-1692
>>>> 
>>>> 
>>>> It looks like it touches a lot of tools. If we include this in 2.9.1 will this require a lot of regression testing? The change does look almost trivial though. Just wondering if this merge should be targeted for 2.9.1 or not? Still requires validation testing.
>>>> 
>>>> Thanks,
>>>> 
>>>> Neal Caidin
>>>> 
>>>> Sakai CLE Community Coordinator
>>>> nealcaidin at sakaifoundation.org
>>>> Skype: nealkdin
>>>> AIM: ncaidin at aol.com
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team