- From: Nils Ulltveit-Moe <nils@u-moe.no>
- Date: Sat, 23 Apr 2005 23:37:34 +0200
- To: shadi@w3.org
- Cc: public-wai-ert@w3.org
Hi Shadi, This page shows a bit about accessibility and PDF: http://www.webaim.org/techniques/acrobat/ Pointing into formats like Flash or PDF is not easy to achieve in a general way, since the underlying format is unknown, proprietary and in some cases binary. The formats act more like programming languages than a traditional document format. If the issue is on a specific position of a page orientated format, like PDF, you can point out the coordinates and the page where it occures. If it is animated, like Flash, then you have to add the time the page failed as well. One thing that may be achieved, is to focus the testing on the functionality different groups of disabled can see via the browsers accessibility interface. It is then possible to see if synchronous text is being written to the accessibility interface at the same time as the presentation is being shown on the screen or trap other accessibility related events in the browser. Also this leads to the question of when you are testing the formats themselves, and when you are testing the tool (i.e. browser) functionality. However, the browser accessibility interface is probably the only interface proprietary vendors will relate to when it comes to providing accessibility adapted formats, so this would be a least common denominator for all plugin format vendors for a given browser platform. However, if you are testing via the accessibility interface, that does not solve the problem of pointing to the source. Regards, Nils fre, 22,.04.2005 kl. 19.18 +0200, skrev Shadi Abou-Zahra: > Hi, > > > For XML-based markup languages, we have XPath, XPointer; for > > CSS, we have line and column numbers; and for some other > > popular formats (PDF, Flash, ...) we're still in the dark. > > That hits the nail right on it's head. However, there is some related > work that has been done in the Annotea project; I'm contacting some of > the people there. Also Jim and Nick (who has just joined the group) may > be able to share some experience around this topic too. > > It would be a major milestone if we can move forward on this item so I > ask everyone to try and contribute to it... > > Best, > Shadi > > > --- --- > Shadi Abou-Zahra, Chair and Team Contact for the ERT WG > World Wide Web Consortium (W3C), http://www.w3.org/ > Web Accessibility Initiative (WAI), http://www.w3.org/WAI/ > Evaluation and Repair Tools WG, http://www.w3.org/WAI/ER/ > 2004, Route des Lucioles - 06560 Sophia-Antipolis - France > Voice: +33(0)4 92 38 50 64 Fax: +33(0)4 92 38 78 22 > > -- Nils Ulltveit-Moe <nils@u-moe.no>
Received on Saturday, 23 April 2005 21:33:01 UTC