I am working on a custom form.
I notice that when using the keyword replacements the actual question for option and tickbox questions is not really linked to the input (for example, in an option the options are yes or no, and the labels 'yes' or 'no' are linked to the input but it doesn't really specify what you're saying yes to) so I would like to add a title attribute to the input.
Also I am adding onclick to the options to show/hide potential options.
My question is this; right now I am first using the keywords to layout the form, then loading up the frontend, copying the source code and then pasting it back into my form contents bodycopy and adding title and onclick then.
Is this the way I should be doing this? Any other better methods? 
No, this does not sound like the best method to do this. Hard coding that isn't the best idea because the beauty of the custom form is using keywords. We do this in many places, and just use javascript to hide and show extra content based on what a user chooses in a select menu. We use jquery on our site, so here is an example of how we do it:
So, you target the id of the select menu, and then check to see if a user choose your specific selection. Obviously this example is for select menus, but you can use the same code by using a click function rather than change.
Good luck.
Thanks, I use jquery to since most of what I use it for is from you! :lol:
Do you know whether using this method works with screenreaders or would they have to refresh the page to see the changes? Part of my argument for cutting down on the PDF forms we have is to make it easier for the visually impaired to complete them so that is a concern for us.
Honestly I cannot say yes or no on that. I really have no idea. Isn't there some JAWS simulators online that could help with testing?
Well, there is Fangs, don't know of anything else. Do you have a page that I can visit to try Fangs on it? I'm having a bit of trouble getting it to work with my form so that way I could check to see if it will be suitable before I spend a long time on turning it into a click event.
Sadly they are all administration pages, or permissions based forms. So, I don't have any that are public...sorry about that!
No worries, be good practice for me anyway.
My javascript course starts in a fortnight… will be good.
For anyone wanting to test accessibility this is quite a good strategy and it links to this article on making ajax work with screen readers.
Also check out this
Thank you for the links ndrw; will talk to my boss about installing NVDA.