Absence of success criterion for markup/properties that prevent configuring pages/interfaces to meet accessibility needs

Name: Treasury Board of Canada Secretariat (Common Look and Feel Office)
Email: clf-nsi@tbs-sct.gc.ca
Affiliation: Government of Canada
Document: W2
Item Number: Guideline 4.1: Maximize compatibility with current and future user agents...
Part of Item: 
Comment Type: general comment
Summary of Issue: Absence of success criterion for markup/properties that prevent configuring pages/interfaces to meet accessibility needs
Comment (Including rationale for any proposed change):
Why is there no success criterion that deals with markup/properties that prevent users from configuring pages/interfaces to meet their accessibility needs? 



Many languages have the ability to lock down interfaces/visual design (such as”!important” in CSS) and doing so can have a negative impact on the level of accessibility for users who need to configure the page/interface to meet their accessibility needs (such as users that need to change the colour scheme in order to visually perceive the information). 

Proposed Change:
Add success criterion that deals with markup/properties that prevent users from configuring pages/interfaces to meet their accessibility needs

Received on Monday, 28 January 2008 19:17:51 UTC