Reporting XHTML 1.0 Strict validation errors

Reporting XHTML 1.0 Strict validation errors

by Joseph Rézeau -
Number of replies: 2
Picture of Core developers Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers Picture of Translators

Hello and a Happy New Year to all moodle developers!

I have been spending a few days of my Xmas holidays validating the Questionnaire module against XHTML 1.0 Strict. I am left with a few validation errors located not in that module itself but in other Moodle files. I am seeking advice on the following.

  1. Where should XHTML 1.0 Strict validation errors be discussed: in this General developer forum or in the Accessibility forum?
  2. When reported in the bug tracker, which Component label should be used: Accessibility?
  3. Should these errors be systematically reported?
  4. Should they be reported as bugs*** or improvements?
  5. Which priority should be selected?

*** The bug tracker documentation says:

- Bugs are classified as 1 of the following:

  • Bug - A problem which impairs or prevents Moodle from functioning correctly.
  • Improvement - An enhancement to an existing Moodle feature.

XHTML 1.0 Strict validation errors do not "prevent Moodle from functioning correctly". Should they be entered as Improvements, then?

All the best,

Joseph

Average of ratings: -
In reply to Joseph Rézeau

Re: Reporting XHTML 1.0 Strict validation errors

by Martin Dougiamas -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers
I think the accessibility forum is a bit more appropriate. Same in the tracker, use "Accessibility" plus whatever other modules it's related to.

Yes, they should be reported, as bugs (because we say we're XHTML strict compliant). Low priority usually though.

Cheers!
In reply to Joseph Rézeau

Re: Reporting XHTML 1.0 Strict validation errors

by Nicolas Connault -
Hi Joseph,

The XHTML strict requirement is part of the 1.8 sub-tasks, there is a generic tracker issue for these errors, which you can re-open by adding your report as a comment, and re-close it when it the errors you found have been fixed.

http://tracker.moodle.org/browse/MDL-7861