Current html rich text editor failed the compatibility tests for the screen reader used at our college (TextHelp).

Please find attached the list of pitfalls.

Visually impaired students need to enable the "web standard forms" in their profiles to work with the editor, as the screen reader did not recognise any of the icons displayed on the editor interface (html option). However, changing this option in the user profile is not intuitive so, it would be helpful that the editor interface included a n "ALT-Text" button or just a button for "Adding new entry".

Thank you in advance for your attention.
_______________________________________________________________________________

Screen reader tests:

• The acronym "VLE" is not pronounced property. It would have been much more accessible to use the term "Moodle", like in the rest of the European languages, instead of this unnecessary acronym.

• Navigation for Moodle courses pages is not accessible in general as the scroll bar was not recognized by the screen reader, and the magnifier does not display it easily. Courses comprising many topics/weeks will not be therefore properly displayed by the screen reader and the learner will miss some of the topics.

• While navigating between topics, in the same course, the screen reader found some control characters that could confuse visually impaired readers.

• Courses structured in the form of a table are displayed OK for both the magnifier and the screen readers.

• - Forum, Journal, Blog: These activities use the current Moodle html editor, which still has several accessibility issues, as it is well documented in Moodle.org.

The screen reader failed to identify the different icons shown at the rich-text editor menu, as well as the text box where the learner needs to type his/her contributions.

• - Chat: Incompatible with the screen reader, since it cannot find the chat box.

• - Assignment: The screen reader failed to spot the "Browse" button, but was able to read correctly the "Upload file" one.

• - Quiz: The questions that passed the screen reader test were: multiple choice, true/false and matching.

• - Glossary: The screen reader failed to spot the "search" button, so the learner would have to read the whole list of terms included in the glossary, until she/he could find a particular term.

I hope that these findings may be useful.