- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Tue, 03 Dec 2013 16:43:24 +0100
- To: Alistair Garrison <alistair.j.garrison@gmail.com>, Eval TF <public-wai-evaltf@w3.org>
Hi Alistair, Is this sufficient "Step 1.c: Define an Accessibility Support Baseline"? - http://www.w3.org/WAI/ER/conformance/ED-methodology-20131129#step1c Best, Shadi On 3.12.2013 14:53, Alistair Garrison wrote: > Dear All, > > The situation - evaluating web pages which use feature detection (for example Modernizr) or conditional comments to change the DOM content presented to the user. > > When evaluating such web pages I personally think it prudent to ask the developer which browser / device combinations they were targeting so that the DOM content in each combination could be checked - as the content will, and is designed to, change. With responsive design it is seemingly becoming more and more prevalent, but I don't think we cover it in our document. > > Suggestion - We should include a section in the document which specifies additional actions which the evaluator might consider if they meet this situation. For example, asking the developer which browser / device combinations they were targeting so that the combinations could be checked. > > In addition, for such pages which are often the more complex (JavaScript heavy) should we not define a default baseline for what browsers / browser capabilities we should be checking with? > > Thoughts / comments? > > All the best > > Alistair > -- Shadi Abou-Zahra - http://www.w3.org/People/shadi/ Activity Lead, W3C/WAI International Program Office Evaluation and Repair Tools Working Group (ERT WG) Research and Development Working Group (RDWG)
Received on Tuesday, 3 December 2013 15:43:55 UTC