EIR 5.2.x

It seems to me that  sc's 5.2.1, .2, and .3 are so very closely linked 
that we should amalgamate from:
5.2.1 Web-Based Accessible (Level A): User agent user interfaces that 
are rendered using Web standard technologies conform to WCAG Level "A". 
(Level A)
5.2.2 Web-Based Accessible (Level AA): User agent user interfaces that 
are rendered using Web standard technologies conform to WCAG Level "AA". 
(Level AA)
5.2.3 Web-Based Accessible (Level AAA): User agent user interfaces that 
are rendered using Web standard technologies conform to WCAG Level 
"AAA". (Level AAA)

to:

5.2.1 Web-Based Accessible: User agent user interfaces that are rendered 
using Web standard technologies conform to the relevant WCAG Level: "A", 
"AA", "AAA". (Level A)

* Intent of Success Criterion 5.2.1 (former 1.2.1):

Web-based applications which are intended to replace or enhance a 
desktop user agent or its functionality, but are in-fact built and 
rendered using standard Web technologies, are becoming increasingly 
common. These Web applications, windowless browsers, rich internet 
applications, HTML5 canvas, etc., perform similar functions to their 
desktop cousins and so must also conform to the accessibility 
requirements placed on a desktop user agent.

* Examples of Success Criterion 5.2.1 (former 1.2.1) :

Success criteria 2.5.1 requires that a user agent enable a user to 
change settings that impact accessibility. In this case we would expect 
that a Web-Based user agent should also enable a user to change 
accessibility settings specific to its functionality, which may in some 
cases enhance or override that of the platform on which it is executing: 
window-less browser, native operating system, etc.

* Related Resources for Success Criterion 5.2.1 (former 1.2.1):

WAI-ARIA 1.0 User Agent Implementation Guide
W3C Web Design and Applications Activity.


If we wish to keep them all separate then I suggest only varying the 
examples as follows:

* Examples of Success Criterion 5.2.2 (former 1.2.2) :

Success criteria 2.5.4 requires that a user agent enable a user to save 
and retrieve multiple sets of user agent preference settings. In this 
case we would expect that a Web-Based user agent should also enable this 
functionality.


* Examples of Success Criterion 5.2.3 (former 1.2.3) :

Success criteria 2.5.8 requires that a user agent provide a 
configuration wizard to help the user configure the 
accessibility-related aspects of the user agent preferences. To achieve 
'AAA' conformance we would also would expect that a Web-Based user agent 
provide this functionality.

NOTE: start of the second sentence of these examples is different just 
so we can choose which we like best.

Cheers
Si.

=======================

Simon Harper
University of Manchester (UK)

More: http://simon.harper.name/about/card/

Received on Thursday, 27 January 2011 17:57:06 UTC