Student projects/Automatic accessibility checking: Difference between revisions
David Knight (talk | contribs) No edit summary |
David Knight (talk | contribs) mNo edit summary |
||
Line 36: | Line 36: | ||
*Version 1 | *Version 1 | ||
**[http://www.closethatdoor.com/moodle/moodle_func_js.zip Javascript ZIP] | **[http://www.closethatdoor.com/moodle/moodle_func_js.zip Javascript ZIP] | ||
**[http://www.closethatdoor.com/moodle/moodle_poc_v1.zip PHP ZIP] | |||
---- | ---- | ||
Revision as of 20:50, 7 May 2008
Note: This page outlines ideas for the Automatic accessibility checking project. It's a specification under construction! If you have any comments or suggestions, please add them to the page comments.
The objective of this project is to make a tool that can check Moodle´s accessibility automatically before realising a version.
Project Outline: Create a button that will pull the source and submit it to a validation service. The errors and warnings will be pulled back to the page, and displayed in a simple GUI. This will be accomplished by AJAX.
Abstract flow:
- Send Request
- Get Source
- Die (If unable to grab source)
- Submit Source
- Die (If unable to communicate with the validation server)
- Retrieve Errors
- Die (If unable to read errors)
- Display Errors
- Get Source
UML Diagram:
- Version 1
GUI:
- Version 1
Code:
- Version 1
Note: Check size limit of http post, the size is 1-2mb. But it can pass 80mb?
Future Extensions:
Create code so it is easy to edit and create extensions on to it. The GUI will be easily updated to include future options.
See also
- GSOC/2008
- Automatic accessibility checking application abstract
- Using Moodle GSOC: Automatic Accessibility Checking forum discussion