[WG: I18N & L10N] Does Client Side JavaScript Have Access to Internationalization Resource Strings in Sakai 2.x?

[Richwine, Brian L]

Hi,

I'm musing over a fix for an accessibility problem where the value attribute of input elements doesn't include any pronounceable words (like the "|<", "<", ">", and ">|" list paging control buttons). By default, screen reading software doesn't read punctuation. If configured to read punctuation, a screen-reader would pronounce "|<" as "Vertical Bar less than" which requires the user to do a good bit of thinking to interpret it as "First".

I'm musing over a jQuery routine that could replace the input elements with a visually equivalent button element that has the required extra text for a screen-reader so low-vision/blind users can always hear "First", "Previous", "Next", and "Last".

It makes we wonder, can a client side JavaScript routine access the i18n resource strings for a tool in Sakai 2.x?

Thanks,
  Brian

Brian Richwine
Adaptive Technology Support Specialist
Adaptive Technology and Accessibility Centers
Indiana University - Bloomington/Indianapolis
http://iuadapts.indiana.edu
(812) 856-4112

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/i18n/attachments/20101203/f3fd89c7/attachment.html