Accessibility

  • Resolved mikemc2410

    (@mikemc2410)


    7 years ago

    Hi, this is s great plugin but there is still an issue with accessibility. If you check your form at [ redundant link removed ] you will see that there is still a form element that is not labeled.
    Any chance of correcting this in the near future?

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • thethemefoundry

    (@thethemefoundry)

    7 years ago

    Hey there, @mikemc2410 👋

    Happy to help! Which page of your site is the from on? I had a good look and I can’t see any from without all its labels.

    Let us know!

    Thread Starter mikemc2410

    (@mikemc2410)

    7 years ago

    Hi, the web page is here https://www.disability-seating.co.uk/test/, the test page is http://wave.webaim.org/report#/https://www.disability-seating.co.uk/test/.

    Its a hidden form element.

    Mike

    thethemefoundry

    (@thethemefoundry)

    7 years ago

    Thanks, @mikemc2410.

    We investigated this and the field that validation complains about is HoneyPot input which is only used to filter out spam robots. Since there’s no user input required for that field, it’s hidden with no label. Adding a label could just confuse screen readers which we certainly don’t want to do. Even with this error reported by scan, your form is still complies with all accessibility standards.

    Hope this clears your doubts! 🙂

    Thread Starter mikemc2410

    (@mikemc2410)

    7 years ago

    Apparently one of the accessibility issues is that there are users that will turn off css and then the field is visible.
    One recommendation is that the form field should also have a descriptive label that is similarly hidden, but clearly indicates to screen reader users that they should not enter anything in the field ie leave this field blank, this also resolves the issue when accessibility users turn off css.

    thethemefoundry

    (@thethemefoundry)

    7 years ago

    That’s definitely a good point, @mikemc2410.

    We’ll add the label with instructions to leave the field blank so it fulfills requirements for both use cases mentioned.

    Thank you for bringing this up. Have a great remainder of your day! 🙂

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Accessibility’ is closed to new replies.