Note: You are currently viewing documentation for Moodle 2.0. Up-to-date documentation for the latest stable version is available here: Student projects/Automatic accessibility checking.

Student projects/Automatic accessibility checking: Difference between revisions

From MoodleDocs
mNo edit summary
mNo edit summary
Line 46: Line 46:
Create code so it is easy to edit and create extensions on to it. The GUI will be easily updated to include future options.
Create code so it is easy to edit and create extensions on to it. The GUI will be easily updated to include future options.


=Tasks=
===Tasks===


==See also==
==See also==

Revision as of 20:54, 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


UML Diagram:



GUI:



Code:



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.

Tasks

See also