ChrisBrown's account

I tried again, just for the sake of paranoia. Yes I am still getting the error {"code":400,"message":"Documents uploaded to accessible transactions must be accessibility enabled.","messageKey":"error.validation.ada.notTaggedDocument","name":"Validation Error"}

I have attempted this again by putting the links directly into the browser and it does have the same result. Signer one does have the ability while signer 2 does not. the package id of the test i just made is 9l986UOWaUgeJgEYrgbx9dFoMqg= in case you can look it up on your side.

I have sent the email with the two links. My apoligies for taking so long to do so, but i had to rearrange the application to generate them both without having to complete the first

I do believe that is correct where the account is set up with the same email address as is used for the signer. i assume that is what you mean by sender in this context. unfortunately, i am unable to change the signer email address. this is an existing process that will not change easily. what do you mean change another sender for this package? from what i understand, once the account is made in esignlive with an email address, it cannot be changed. Do you mean that this can be changed? or am i missing something?

I will have to take a closer look and see what kind of impact this has, but i do not think this will be a viable option either. I do not believe that the owners of this app will accept adding a new email address and processes to check it as acceptable. After i investigate the impact, i will ask them what they think. Please let me know when you get an answer as to if this is deliberate behavior. If not, when could we expect a fix for this?