- From: Victoria Menezes Miller <menezesmiller@gmail.com>
- Date: Fri, 31 Aug 2012 11:50:37 +0200
- To: Shawn Henry <shawn@w3.org>, wai-eo-editors <wai-eo-editors@w3.org>
- Cc: Peter Dev <thiessenp@acm.org>
Received on Friday, 31 August 2012 10:14:04 UTC
Hi, Shawn, I received the feedback below from Peter late last night. Best, Vicki On Thu, Aug 30, 2012 at 11:14 PM, Peter Thiessen <thiessenp@acm.org> wrote: Right, thanks for the reminder. I'm in the same busy boat. I'll give it a quick skim. I know 2 obvious cross-over points and 1 iffy one. Rough notes, below: Multi Interface Access -MWABP 3.5.3 Design for Multiple Interaction Methods (focus,pointer,touch,*) http://www.w3.org/TR/mwabp/#bp-presentation-interaction -WCAG2 2.1 Keyboard Accessible Don't Require Scripting -MWABP 3.6.4 Support a non-JavaScript Variant if Appropriate (non-JS fallback) http://www.w3.org/TR/mwabp/#bp-devcap-scripting-support -WCAG 2.0 Conformance Requirement: Conformance Requirement 4: Only Accessibility-Supported Ways of Using Technologies and Conformance Requirement 5: Non-Interference. Don't Surprise the User (may be a stretch) -MWABP 3.5.4 Preserve Focus on Dynamic Page Updates (careful-avoid confusion) http://www.w3.org/TR/mwabp/#bp-presentation-focus (ARIA crossover) -WCAG2 Guideline 3.2 Predictable: Make Web pages appear and operate in predictable ways. (predictable) Wish I had more time. I plan to do this on the weekend more thoroughly though. cheers, +peter
Received on Friday, 31 August 2012 10:14:04 UTC