- From: Alexander Surkov <surkov.alexander@gmail.com>
- Date: Tue, 15 Oct 2013 12:49:55 -0400
- To: Joseph Scheuhammer <clown@alum.mit.edu>
- Cc: David Bolter <david.bolter@gmail.com>, "W3C WAI Protocols & Formats" <public-pfwg@w3.org>
Hi, Joseph. This one goes probably from native markup. So if div was used instead input then test should be working. So the question is should aria-autocomplete:none override value provided by input control? Or more generic question does ARIA win over native markup when they are in direct conflict like <input disabled="true" aria-disabled="false">? Alex. On Tue, Oct 15, 2013 at 10:00 AM, Joseph Scheuhammer <clown@alum.mit.edu> wrote: > Hi Alex, > > FF 23.0.1 fails a test case for aria-autocomplete='none' under AT-SPI. > > The object properties are correct: "autocomplete:none" is exposed. However, > STATE_SUPPORTS_AUTOCOMPLETION is also exposed. > > That's incorrect. If the accessible does not have autocompletion, it should > not declare that it supports autocompletion. > > Test case: > https://www.w3.org/WAI/PF/testharness/test?testsuite_id=3&testcase_id=17&platform_id=1 > > Test file: > https://dvcs.w3.org/hg/pfwg/raw-file/default/ARIA/1.0/tests/test-files/roles-properties-supported/roles-properties-supported-combobox-aria-autocomplete-none.html > > Thanks. > > -- > ;;;;joseph. > > > 'A: After all, it isn't rocket science.' > 'K: Right. It's merely computer science.' > - J. D. Klaun - >
Received on Tuesday, 15 October 2013 16:50:23 UTC