Accessibility Features (Section 508)
Would like to request accessibility features to be added to the site's templates including:
FORMS:
Add label tags around the form's labels, and associate the labels with their form fields using IDs (explanation: http://webaim.org/techniques/forms/screen_reader.php#labels)
Group form controls using fieldsets and legends, where appropriate (explanation: http://webaim.org/techniques/forms/screen_reader.php#group).
NAVIGATION:
Add a "skip navigation feature" to allow keyboard users to skip over the navigation menus, when they are tabbing thru links on a page. (explanation: http://webaim.org/techniques/skipnav/#focus).
These features would make the sites more accessible to disabled users (people who cannot use mouse, blind people using screenreader software, etc) and help make them more compliant with the US government's Section 508 guidelines.
rachseng
shared this idea
-
ALHFAM Webmaster
commented
We are also waiting for some new designs for accessibility. Currently I can't add alt text to images or slideshows on the page when I'm in edit mode. Please tell me you have added these features now.
-
Sam Lyrin commented
I would say the biggest problem is the form labels. I'm working on a workaround, but it would be great if WildApricot could do something about it on the back end. The fix would be to wrap the form labels that already exist inside of html <label> tags and linking them to the correct form field using the "for" attribute.
-
Orlando Ski and Travel Club
commented
Reply from WA was dated July 12, 2015 and still no progress?
-
Orlando Ski and Travel Club
commented
Unlike Canada, here in USA we are laws requiring our websites to accessible by everyone and subject to lawsuits if our websites are not. We need themes that include this in mind.
-
Alex Sirota commented
Is there any official statement on the state of accessibility in Wild Apricot websites?
-
Bill Pullen
commented
We have been asked by users whether our site is accessible using a screen reader.
-
Dmitry Buterin commented
We would appreciate further input on this from everyone. Obviously it is hard to impossible to ensure accessibility for all pages/functions in one go so we would appreciate more details - which of Wild Apricot specific pages/functions currently are the biggest bottlenecks in your organization accessibility-wise?
-
Thanks for your input. This makes perfect sense and we will consider this in our development plan (though it will be a while - quite a bit of other stuff in the pipeline already)
