Thanks for your responses, Steve and Ryan. I neglected to say that this is
for a US Federal Government website -- so by compliant she meant Section
508.
I'd not considered the "keyboard trap" issue and will definitely include
that information in my response to the developer.
Dona
On Thu, Mar 7, 2013 at 7:02 PM, Steve Green
< <EMAIL REMOVED> >wrote:
> It sounds like we are in significant, if not total, agreement.
>
> WCAG requires websites to be 'reasonably usable', not 'equally usable'. We
> may not like it, but that's how it's written. Therefore if we are testing
> for compliance with WCAG, that's the criterion we must use. If a text
> version passes all the success criteria (and I am not saying it would),
> then the website is WCAG-compliant even if it's an ugly solution.
>
> As testers, it's not our job to justify anything - we just test against
> whatever criteria are applicable in the context of each project. We may
> encourage our clients to go further in order to improve the user
> experience, but they have no obligation to do so.
>
> Steve Green
>
>
