- From: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>
- Date: Fri, 21 Sep 2012 01:10:50 +0200
- To: Maciej Stachowiak <mjs@apple.com>
- Cc: Janina Sajka <janina@rednote.net>, janina@rednote.net, HTML Accessibility Task Force <public-html-a11y@w3.org>
Maciej Stachowiak, Thu, 20 Sep 2012 12:59:49 -0700: >> 1.) We have cross platform user agents, e.g. Firefox available for >> Windows, Android, Linux, etc. >> >> Are these separate stacks? Or one stack? [...] > Firefox for different platforms would not count as independent [stacks], >> 2.) Are AT-SPI/ATK and IAccessible2 one stack or two? [ ... ] > > I would say two different browsers using the same accessibility API > counts as independent [stacks], just as two browsers on the same OS would be > independent [stacks] (assuming they otherwise meet the criteria). But the same > browser using two different APIs would not be independent [stacks]. Two questions: (1) Should assistive technologies have any weight, in and by themselves or or only count when seen from the browser angle? For example Apples AT, VoiceOver, does currently not support @longdesc. The reasons for this are that a) Apple's browser does not support @longdesc and b) no other browser with @longdesc support has been made to work with VO in such a way that longdesc can generally be used with it. But this could change when Firefox soon gets VoiceOver support - then VoiceOver probably gets @longdesc support to. So if one looks at the situation from a Mac platform A11Y user's perspective, then such a user would be able to use an AT that has @longdesc support once Firefoxs get VO support. Does this not count as anything in this math? (That's how what you say above sounds lik.) Why should it not be relevant to see it from the VoiceOver user and ask: "Can one use @longdesc with it? Yes, if you use it with Firefox. OK. Nice this will count positively." (2) [This question is probably much simpler.] There are a large number of Webkit browsers, which vary a little bit with regard to what they support - e.g. accessibility wise. Would it only count if @longdesc was supported in e.g. Chromium or Webkit, whereas the derivate support - Chrome, Safari, iCab - should be looked away from? (I guess iCab is partly a derivate of "the Safari stuff" inside OSX and iOS too - its not only a Webkit derivate.) -- leif halvard silli
Received on Thursday, 20 September 2012 23:11:23 UTC