[Building Sakai] [WG: Accessibility] SAK-22041. Velocimacro change to support screen readers

[Adrian Fish]

There's an issue linked to SAK-23003 where Joe does describe the problem
and the steps to fix it.

https://jira.sakaiproject.org/browse/SAK-22798

I created SAK-23003 as that is where the code is that generates the
deficient markup.


On 7 December 2012 16:05, Aaron Zeckoski <azeckoski at unicon.net> wrote:

> Looks like the issue describes an a11y problem:
> "The chef_dateselectionwidget Velocity macro produces unlabeled input
> controls"
> "The chef_dateselectionwidget Velocity macro produces unlabeled input
> controls. This means that any tool using the macro is going to cause
> problems for screen readers. The solution would be to pass parameters
> for use in the title attributes of each of the select elements, but
> this would need testing across all users of the macro. It's a real
> shame that velocimacros won't take a parameter hash allowing us to
> just test for the existence of the param within the macro code."
> https://jira.sakaiproject.org/browse/SAK-23003
>
> If not then it needs to adjusted to be correct.
> If so, the accessibility group needs to comment on and agree with the
> suggested solution before there is any discussion about the technical
> methodology.
>
> -AZ
>
>
> On Fri, Dec 7, 2012 at 10:49 AM, Adrian Fish <adrian.r.fish at gmail.com>
> wrote:
> > None really. The macro never applies a title to the date selection
> inputs so
> > all of the tools using the macro will be producing inaccessible markup
> to a
> > degree. All I'm really after is somebody to validate,  or rubbish, what I
> > think should be done. Hence my mail to the dev list.
> >
> > Cheers,
> > Adrian.
> >
> >
> > On 7 December 2012 15:29, Humbert, Joseph A <johumber at iupui.edu> wrote:
> >>
> >> What input would you like from the accessibility group?
> >>
> >> 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/
> >> -----Original Message-----
> >> From: accessibility-bounces at collab.sakaiproject.org
> >> [mailto:accessibility-bounces at collab.sakaiproject.org] On Behalf Of
> Aaron
> >> Zeckoski
> >> Sent: Friday, December 07, 2012 9:47 AM
> >> To: Adrian Fish; accessibility at collab.sakaiproject.org
> >> Cc: sakai-dev
> >> Subject: Re: [WG: Accessibility] [Building Sakai] SAK-22041. Velocimacro
> >> change to support screen readers
> >>
> >> Since this appears to be accessibility related it should go to the a11y
> >> team.
> >> -AZ
> >>
> >> On Fri, Dec 7, 2012 at 9:30 AM, Adrian Fish <adrian.r.fish at gmail.com>
> >> wrote:
> >> > Apologies for my abject idiocy. This is the ticket I meant ...
> >> >
> >> > https://jira.sakaiproject.org/browse/SAK-23003
> >> >
> >> > I'm not surprised you didn't quite follow :)
> >> >
> >> >
> >> > On 7 December 2012 13:19, Aaron Zeckoski <azeckoski at unicon.net>
> wrote:
> >> >>
> >> >> I'm not quite following. Is this a question and the patches from
> >> >> David M? If so, there are lots of comments in the ticket but the
> >> >> short version is that I think more work is required before this could
> >> >> go into core (it's definitely not OK to go in as it is today).
> >> >>
> >> >> -AZ
> >> >>
> >> >>
> >> >> On Fri, Dec 7, 2012 at 7:42 AM, Adrian Fish <adrian.r.fish at gmail.com
> >
> >> >> wrote:
> >> >> > I'd like a bit of input on a bug ticket, please. It impacts a lot
> >> >> > of tools ...
> >> >> >
> >> >> > https://jira.sakaiproject.org/browse/SAK-22041
> >> >> >
> >> >> > This is a high impact change as the macro is used across huge
> >> >> > swathes of the core codebase. I suggest we add a new macro,
> >> >> > effectively a renamed copy of the current one but with extra
> >> >> > parameters. I could also mod the current one so it at least uses
> >> >> > the supplied id as the title in the markup. From then on we can
> >> >> > gradually mod the tools to call the new macro.
> >> >> >
> >> >> > Or we could just leave it for now ...
> >> >> >
> >> >> > Cheers,
> >> >> > Adrian.
> >> >> >
> >> >> > _______________________________________________
> >> >> > sakai-dev mailing list
> >> >> > sakai-dev at collab.sakaiproject.org
> >> >> > http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> >> >> >
> >> >> > TO UNSUBSCRIBE: send email to
> >> >> > sakai-dev-unsubscribe at collab.sakaiproject.org
> >> >> > with a subject of "unsubscribe"
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
> >> _______________________________________________
> >> 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"
> >
> >
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20121207/1fba055a/attachment.html