abletec

Mike, thanks for your kb article re: cron jobs not working. Saved me *a lot* of time. Very valuable--thanks!

Thanks, Mike, for your sensitivity & for your work on bringing your own website into voluntary compliance. If you'd like any help, feel free to contact me. Despite my posts, I actually don't bite, or, if I *really* feel the need to do so, I have all my shots lol.
 
The program I had been using was marginally accessible at best, & the last update broke even that modicum, along w/really core functions. I've been doing damage control almost the entire week, & I was really hoping I'd be able to use Blesta. I still haven't entirely given up, but I am encountering some significant hurdles. I guess we'll see. Sigh. Sometimes it all just feels so hard.
 
The developers of the program I've been using to this point have made it very clear that they don't & won't support screenreader users, so we're on our own. That's fine--I don't expect any quarter--but I do think that if you're going to sell software, that at the very least, compliance w/web standards is in order. Hopefully the gentlemen at Blesta will take the lead in all this, because, as you so aptly point out, no one to date has done so in this particular space.
 
Good luck & much success w/your ventures.

Thanks, Mike, for your sensitivity & for your work on bringing your own website into voluntary compliance. If you'd like any help, feel free to contact me. Despite my posts, I actually don't bite, or, if I *really* feel the need to do so, I have all my shots lol.
 
The program I had been using was marginally accessible at best, & the last update broke even that modicum, along w/really core functions. I've been doing damage control almost the entire week, & I was really hoping I'd be able to use Blesta. I still haven't entirely given up, but I am encountering some significant hurdles. I guess we'll see. Sigh. Sometimes it all just feels so hard.
 
The developers of the program I've been using to this point have made it very clear that they don't & won't support screenreader users, so we're on our own. That's fine--I don't expect any quarter--but I do think that if you're going to sell software, that at the very least, compliance w/web standards is in order. Hopefully the gentlemen at Blesta will take the lead in all this, because, as you so aptly point out, no one to date has done so in this particular space.
 
Good luck & much success w/your ventures.

I see what you mean if the software can't tell you which is enabled and disabled you can get confused. I wonder if labels would help tell the software, I just checked my own website on http://achecker.ca/checker/index.php  I have loads of issues so I'm going to try and see if I can improve my site to comply with the WAI.

I agree that it might be best if the guys did it towards the ADA, and whilst they are at it maybe a colour blind theme in black and yellow or something to help the colourblind too. The guys will be back in the office on Monday who can help you further but I do think the guys will be interested in this as it would make Blesta stand out more from the crowd too as I don't believe other systems have this.

You're more than welcome and fingers crossed the guys can put this forward.

Licensecart, you wrote in part:
"...unless you mean the widget plugins and other things which need to be moved to the left or right to enable and disable them."
 
& that is precisely what I'm referring to. However, having said that, it looks as though I may have at least made some headway in this regard. Time will tell, I guess.
 
The standards at w3c.org/wai are pretty clear about what constitutes accessibility. 1 of those standards requires that controls be usable via both keyboard & mouse. This actually helps others besides those w/sight impairments as well, i.e., those w/certain mobility impairments, for example, who use their computer via their voices. Failure to comply w/those standards is, in my opinion, a little like putting a sign on the door that says "Welcome to all, except those who have disabilities that require accessible accommodations." I know that's not the intent, but it is the result nonetheless, & the effect of denial of opportunities that results from inaccessible software is pretty staggering. It's clearly 1 thing if there's no way to make the program usable, but both WordPress & Drupal have implemented systems by which widgets are accessible via keyboard, so this is not an impossibility.
 
Case law is still evolving considerably regarding this whole area , but I think if one sells software in the US, it's likely wise to begin thinking about taking steps to implement accessibility, as doing so may well be adjudged to be a requirement under the Americans with Disabilities Act in the very foreseeable future. Again, time will tell, I guess. I will now officially exit my soapbox & continue to see if I can make any additional headway w/this software. I really appreciate your reply.