Good morning, I did an accessibility test of a form that I built through AirTable and found the following issues that I would like to suggest that you repair. I would like to create a similar form that will be available to the public through our website, but until the accessibility improves, I will not be able to do so. Checkbox box and other input field borders need stronger color contrast. Linked text need stronger color contrast. Markers indicating the Required status of questions do not have strong enough color contrast. Checkbox field needs a label in order for screen reader users to know what “clickable” means. Single Line Text fields should really have programmatically identified labels for screen reader users. Perhaps the title/question as worded in the form could be used as the label. For mulit-select option with the list format, it would be nice if the checkboxes were programmed to be announced as checkboxes to screen reader users. Also, if these options were truly in a list format, a screen reader user should be able to hear “List with [ # ] list items,” before entering the list. For the single-select option with the list format, it would be nice if the radio buttons were programmed to be announced as radio buttons to screen reader users. Also, if these options were truly in a list format, a screen reader user should be able to hear “List with [ # ] list items,” before entering the list. I would like to request that the form design be double checked to make sure it does not cause a keyboard trap when a screenreader/keyboard users tabs through a page in which the form is embedded. In my quick test, it appeared to me that it does cause a keyboard trap prior to submitting a response. Once a response is submitted, the Add another response button is not accessible to the screenreader/keyboard user, but the user is no longer trapped in the iFrame. When required fields are not filled out, the error message does not have strong enough color contrast. Fields that require a URL allow submissions of non-URL content. I think that adding an error message that appears when the submission does not include http:// is good usability, if not accessibility. The Submit button and " Never submit passwords through Airtable forms. Report abuse." message at the bottom of the form, does not have strong enough color contrast. I did not see where the Report Abuse link was included in the Tab order.
... View more