Accessible DIY Forms

Embedded DIY Forms are causing our site to fail standard Accessibility standards.

Please fix the code behind the forms so that organisations using eTapestry can meet these standards.

The specific problem we are seeing:

Form input fields require a properly formatted label. The label should be a <label> element, not any other text element. It should also have a ‘for’ attribute that matches the ID of the field it is the label for.

E.g. <label for=”title”>Title</label>  <select id=”title”><option>Mr.</option>”><option>Mrs.</option></select>

  • Guest
  • Aug 2 2018
I have no idea what to pick
  • Attach files
  • Guest commented
    22 Jul 15:30

    How disappointing to see that this idea is SEVEN YEARS OLD and nothing has been done to fix this. I wish Blackbaud valued my donors who have access needs the way I do, but I guess not!


    These problems still persist with DIY forms, also causing my org's website to fail a standard accessibility audit:

    - Radio buttons are not accessible by keyboard - they are styled with a pseudo-element, and the actual labels are hidden

    - No indication when radio button is selected (state not defined)

    - Mandatory fields are not adequately identified

    - Labels for form fields are not programmatically linked

    Attachments Open full size
  • Guest commented
    May 16, 2023 01:25

    This should be made an urgent development priority. It's truly terrible that there hasn't been any progress on resolving this in the last 5 years.

    Attachments Open full size

Related ideas