Re: ACTION 475 - Benefits Accessibility

Hi Simon,

This is not bad if the goal is to provide a /concept/ suitable for guidelines, but it doesn't seem to be attempting to provide a /definition/ suitable for a standard, meaning something one could use to determine whether a product complies with a success criteria that applies to "features that benefit accessibility".

I love the quote from Mike Brown that "concepts are for scientists and definitions are for lawyers". Unfortunately, standards often have to be written in a lawyerly fashion if you want them to be enforced consistently. Do we want to go for something general, or something objectively measurable?

     Thanks,
     Greg

-------- Original Message  --------
Subject: ACTION 475 - Benefits Accessibility
From: Simon Harper <simon.harper@manchester.ac.uk>
To: UAWG list <w3c-wai-ua@w3.org>
Date: 12/7/2010 3:06 AM
> Hi there,
>
> I was assigned ACTION-475 'Create definition of 'benefit accessibility' or reword all SC in GL 3.3'
>
> So this is what I've come up with.
>
> "Features which benefit accessibility fall into two groups: (1) those features which have been explicitly created to aid accessibility, possibly in an attempt to follow guidelines such as these; or (2) those which assist accessibility but emerge from other functionality not originally created for accessibility purposes. Further, these accessibility benefits may be explicit such as the ability to control the User Agent from the keyboard; or implicit such as the ability to style a page based on a user supplied style sheet."
>
> Cheers
> Si.
>
> =======================
>
> Simon Harper
> University of Manchester (UK)
>
> More: http://simon.harper.name/about/card/
>