The OPAC should validate to xhtml 11) and CSS 2.1 before release. Preferably, the OPAC should meet WCAG 1.
This RFC is motivated by private and public2) reports and is licensed under the WTFPL3)
Although I'm not sure if it's been formalized, XHTML validation has been at least an implicit requirement since at least dev_week, as has validation against CSS 2.0. I have no problem mandating XHTML and CSS 2.1 validation for the OPAC; currently, the staff interface generally validates against XHTML except for a persistent (and insoluble?) problem specifying autocomplete=off in a way that validates against XHTML.
I agree that WCAG 1 compliance (and for US users, Section 508 compliance) are desirable, and at least one vendor has expressed interest into doing the legwork required to achieve this. The question is this: how far are the Koha OPAC and staff interface out of compliance? Is anybody willing to commit to doing the necessary cleanup?
— Galen Charlton 2009/05/06 08:43