When the web standards trump agency requirements

Q: As a member of the common web services panel, are we essentially mandated/required to ensure that what we create meets the accessibility and usability guidelines as stated on the Web Toolkit website? The reason I ask is I am wanting some guidance on how best to deal with situations where a Government client’s requirements directly conflict with the guidelines stated above. What trumps in this scenario - the requirements of the client or ensuring what we develop meets the standards expected of DIA? I am aware that public service departments are now mandated to have all web pages meeting the standards but some guidance on this scenario would be welcome.

A: Interesting request and opportunity to clarify here. The answer is pretty straightforward:

• The Web Standards apply only to those core govt agencies mandated to meet them

• The Web Standards are not applicable to non-govt or private sector orgs

• Mandated govt agencies need to make sure their websites meet the Standards (as per Cabinet Mandate)

• All Govt agencies subject to the Government Rules of Sourcing are mandated to make sure their outsourced web work meets the Web Standards (Rule 58)

• Responsibility for meeting the Web Standards rests with each individual agency

• If an agency knowingly builds a website that doesn’t meet the Standards, the risk of doing so is owned by that agency

• An agency may not understand that some of their requirements contravene the mandatory Web Standards: in these cases a vendor that understands this might notify the client of the issue, the potential drawbacks for users, and the risk to the agency