I am going to butt in here. As the current system developer, I have some insights into the design of FreeToastHost as to accessibility support.
Here is my bottom line answer on this...
FreeToastHost uses a number of open source libraries and frameworks in its implementation that *do* have accessibility support built in to them via the use of ARIA tags and other recommended practices to support screen readers and the like. Additionally, as I have become more aware of these things, I try to include them as I remember to.
However, there are a number of parts of our system web pages that are custom made and may not have the accessibility support. Also, most clubs do not know how to add this support to their home pages, meeting information pages, and custom page HTML that *they* create. There actually is an accessibility checker plug-in for the editor we use, but no one has ever asked us to deploy that plug-in, and the last time I experimented with it I ran into a number of problems with the plug-in.
Because of the above, our support for accessibility is *uneven* and *inconsistent*. It would be nice to provide consistent, documented support for it in the future, but we would really need to work with some users for an extended period of time who were in a position to provide feedback and help us make it work well. Without that feedback loop, we are essentially limited to what we have now. As Brian notes, we are volunteers with zero budget, so unless we can get some support from our users for these sorts of specialized use cases, we are severely constrained.
Last edit: 6 years 7 months ago by SteveTheTechie.
The topic has been locked.