- From: Charles McCathie Nevile <chaals@yandex-team.ru>
- Date: Thu, 01 May 2014 18:06:53 +0200
- To: "public-html-a11y@w3.org" <public-html-a11y@w3.org>
Hi. This mail is an attempt to pick a set of tests for longdesc that will need to be met according to our CR Exit Criteria (which is a set smaller than "all valid longdesc tests"). I'd like to send this to the group for discussion today. I think the absolutely required minimum is that for each of the following tests (these are the local names in my version, but the W3C repository uses effectively the same scheme) we show 2 user agents that make the longdesc discoverable, and that allow users to access it. ext img - ext desc ext img - ext desc with spaces ext img - internal desc ext img - ext desc with absolute base ext img - ext desc with relative base empty img - external desc img in <iframe> longdesc updated by javascript Rich claims that all accessibility APIs provide access to the dom, but we have additional results showing that most of these tests are directly reflected to at least MSAA. We are looking for more results for accesibility APIs - and on more platforms. If there are no comments, we will shortly start a Call for Consensus on this... cheers Chaals -- Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex chaals@yandex-team.ru Find more at http://yandex.com
Received on Thursday, 1 May 2014 16:07:27 UTC