Moodle plugins directory: Accessibility | Moodle.org
Accessibility
PLEASE NOTE: This plugin is no longer being actively maintained by Brickfield. The main challenge is with the third-party external ATBar, which is not being maintained at all by its authors, at some point has lost all of its docs, and doesn't have an up-to-date SSL.
If someone has funding, and would like to cover the updating of this plugin, we would be happy to engage with you on this.
We are planning on sharing a new plugin which will provide guidance to users with their font size, font colour, and other display options, depending on their browser. We will update this plugin description once it's available.
The block allows users to customise Moodle to their visual needs. It supports changing of text sizes and colour schemes. Customisations save to the user's session, allowing them to persist between pages, and can also be saved to the database allowing them to apply permanently.
The block also integrates ATBar from Southampton University ECS. This provides extra tools and customisation options, including dictionary lookup and Text-to-speech. Visual customisations performed with ATBar don't currently persist, and can be used as well as or instead of the block's own customisations.
Please don't report bugs here
If you experience an error with the block, or would like to request a feature, please use the "Bug Tracker" link below.
I'm using Moodle version 1.9.18 and have downloaded your block version 2009082600 and am getting the following error when selecting a colour scheme:
Message: 'style' is null or not an object
Line: 7
Char: 1374
Code: 0
URI: http://31.222.137.126/zibi/lib/yui/dom/dom-min.js
This is preventing some objects from being displayed following selection.
Will later versions cure this and can they be used in Moodle v. 1.9?
Thanks
I have no plans to backport the current version to Moodle 1.9. The original version of the block was written for 1.9, and can still be obtained from github: https://github.com/marxjohnson/moodle-block_accessibility/tree/MOODLE_19_STABLE
It lacks some of the features in the current version (notably the ATBar integration), but should otherwise work. Please note that this version is no longer actively maintained.
Thanks for the response. Unfortunately that is the version that I have...
Regards
Geoff
/**
* Periodically clear the TTS cache so it doesn't get out of hand.
*/
public function cron() {
global $CFG;
$count = 0;
$cache = $CFG->dirroot.'/blocks/accessibility/toolbar/server/TTS/cache';
$count += $this->clear_old_cache($cache.'/chunks');
$count += $this->clear_old_cache($cache);
mtrace(get_string('clearedoldcache', 'block_accessibility', $count));
}
That seems to be trying to write to a cache within 'dirroot'. Worse there isn't a subdirectory called 'toolbar' anyway, so it just errors out (a lot). Am I being stupid or is something badly wrong here?
Thanks for pointing that out. That's some old code that was used when the toolbar was packaged as part of the block, and served from the Moodle server. It's now served remotely, although it probably shouldn't have been writing cache to dirroot in the first place, you're correct. I'll remove this cron code and upload a new version.
Is there any plans ro release the block for Moodle 2.4?
Cheers,
Paul
Yes I plan to update all my plugins to work with Moodle 2.4. However I can't promise when this will be at the moment as no-one is paying me to do it
Hopefully sometime over the next month.
However, the previously mentioned problem with cron remains (and almost killed our system). The .zip install file did not create the directory referenced in the cron job, which hung our system cron (resulting in multiples of that process, many multiples). Created the directory path referenced in the cron function and that cleared the cron issue.
Hopefully all else is working since I love the block otherwise.
...dwheeler colgate university
THIS WILL BREAK YOUR CRON PROCESS AND CRASH YOUR SITE.
Not a big deal, just remove the cron function completely, and it'll work fine. Author, please re-package without the cron stuff, it broke my servers!
Nice plugin though, thanks.
I'm using this with Moodle 2.4 and it seems to be causing problems with login. Following a successful login the user gets redirected to blahblah/moodle4/blocks/accessibility/userstyles.php
which results in a blank page.
The login is successful as manually changing the URL to blahblah/moodle4/ does result in displaying the user's logged in home page.
Any suggestions?
Allen, I will be installing this on my Moodle, I'll keep you posted if it breaks. I recommend you uninstall the plugin, and see if that fixes your Moodle site.