Hi Ira,

This issue has started to come up regularly over the last few weeks so it is definitely becoming a priority for us. We have also recently received some reports on accessibility compliance which highlighted some issues that need to be resolved.

In the poll for requested features for 2.6, this issue actually polled quite poorly! We'll be doing a similar exercise for 2.7 shortly now that 2.6 is released so the more votes for this the more of a priority it will be, so keep an eye out for that 2.7 poll.

https://totara.community/mod/forum/discuss.php?d=19000

As you can see from that we estimated that fixing most of the accessibility issues would take about 25 developer days so it would be a significant effort, though we do intend to continuously improve our accessibility support moving towards 2.7.

Moodle are also taking Accessibility more seriously and have some open tickets themselves and of course those patches when released will be merged into Totara:

http://docs.moodle.org/26/en/Accessibility

http://docs.moodle.org/dev/Accessibility

In a related forum post from a year ago there is a good study comparing Blackboard, D2L, Sakai and Moodle for accessibility and Moodle does pretty well:  https://totara.community/mod/forum/discuss.php?d=2808 though obviously there is always room for improvement!

If you happen to know of any reputable assessment or official accreditation agencies which could do an analysis of a Totara installation for WCAG Compliance we'd be happy to work with you in getting more reports, identifying issues and improving our WCAG/508 accessibility compliance as much as possible.