I’m a newbie and so far I seen a couple of issues, first SG is not accessible for hearing and seeing impaired (ADA.) For instance narrator has limited capability and will not work on question text and only on the first of multiple answer options (the reminder are not read out loud.) Next Date format if MM/DD/YYYY is selected and when a mobile device is used the date is switched to YYYY/MM/DD. I was told this fix may take 1 day to week to fix. Has anyone else reported any these issues? As I cannot wait for these bugs to be fixed does anyone have any workarounds?
I have a workaround for you until we get this fixed! The following steps will allow you to store your dates in a separate textbox, all properly formatted as mm/dd/yyyy.
- Create a textbox question on any page after the date question. Call it whatever you’d like.
- On the “layout” tab of the new textbox question, scroll to the CSS Hook section at the bottom. Add the hook “date”, like this: http://i.imgur.com/19JiC0R.png
- On the “logic” tab of the new textbox question, mark it as hidden by default, like this: http://i.imgur.com/4hj2eZt.png
- Save your action, and you should be good to go!
//Caitlin – workaround script 09/21/15
//converts all dates to mm/dd/yyyy (incl dates entered on mobile)
var date = $(“.date input:text”).val();
date = date.split(“-“);
date = (date+”/”+date+”/”+date);
If you have any issues getting this set up, just let me know, and I can get it added for you.
Thank you for your time, unfortunately this code did not work for us. I tried emailing you. However your solution gave our team some great ides to develop a custom script solution (vs the javascrpt.) This code rearrange the dates so they matched. If you would like a copy of this fix please let us know.
Also there was a skip placed after this hidden question (part of the questionnaire logic.) With an auto submit on this page, the skip no longer automatically performed. The respondent needed to hit the “next” button (on a blank screen) to proceed. We also created a workaround for this situation.
Thanks so much for using Community. One of the members of our escalations team, Caitlin, is currently creating a workaround for you as we speak. You should be hearing from her very soon.
Regarding the accessibility question, what screen reader are you are you using? We currently support and recommend using JAWS. Here’s a link to our documentation on accessibility.
Thank you for your patience!
Holly White, Survey Fire Dancer