Loading...
 
Skip to main content

Features / Usability


Accessibility and code validation

When I run the validator.w3.org/unicorn code validator I get all kinds of errors/warnings for CSS files. If I make changes in those files to correct the validation errors, am I going to have to do it all again when I next update Tiki?

Also, I am extremely pleased that the vast majority of the options we've used in Tiki have been accessible for screen readers. I have managed to get my site accessible except for one problem on the registration page (we require a user name and password to entire our site). There is a small image of an X to close the page that contains an "on click" event handler that creates an accessibility error. Can someone help me figure out how to get to the appropriate code so I can change it?

Thank you in advance!

As a side note, I'm willing to help work on making Tiki code meet US accessibility guidelines if someone can tell me how to get started.

We want Tiki's pages to validate, of course, so things that cause validation errors should be corrected in the code itself rather than be left in the released package. About validation errors, one thing is that Tiki is using some proprietary or CSS3 rules such as for border radius, as these are superior to older techniques and browsers are supporting them more. So errors related to these, at least from the perspective of the mainstream user, aren't significant. Setting the HTML5 doctype at validator.w3.org results in a lot fewer errors. I don't know what the implication is related to US accessibility standards, though.

Related to this is that Tiki uses a number of external libraries like jQuery, and I've noticed these produce some validation errors, especially if you're checking against CSS2.1. I need to check about what to do about these.

About the registration page accessibility problem, I can't tell you offhand, but will add a bug report about it. You are welcome to subscribe to the "tikiwiki-devel" mailing list where more developers can be reached. That would probably be a good idea for communicating on the topic. There is a wiki page on this topic at http://dev.tiki.org/AccessibilityQuestion which I thought would have more content since this has come up before and work has been done, but the page needs, I would imagine, something like a statement of goals (what standards to meet, specifically), methods (what in Tiki needs to be addressed), and problems to be solved/work to be done (specific improvements, etc.) as the page currently doesn't show much except for old bug reports.

-- Gary - ZukaThemesQuestion