- From: Joanmarie Diggs <jdiggs@igalia.com>
- Date: Fri, 9 Jun 2017 13:38:26 -0400
- To: Rich Schwerdtfeger <richschwer@gmail.com>, Jon R Gunderson <jongund@illinois.edu>
- Cc: ARIA Group <public-aria@w3.org>
According to the Core-AAM, there's both a state and an object attribute: https://rawgit.com/w3c/aria/master/core-aam/core-aam.html#ariaAutocompleteInlineListBoth Thus in addition to the object attribute described by Rich, it appears that a new row is needed to test the implementation of the expected state. This expectation is parallel to what is expected (and tested) for ATK, so perhaps that could serve as an example? --joanie On 06/09/2017 01:25 PM, Rich Schwerdtfeger wrote: > It is in the object attributes which is a string of key/value pairs. You > will see autocomplete:<value> > > > Rich Schwerdtfeger > > > > >> On Jun 8, 2017, at 2:05 PM, Gunderson, Jon R <jongund@illinois.edu >> <mailto:jongund@illinois.edu>> wrote: >> >> Rich or Joanie, >> >> I can’t find an autocomplete property for MSAA or IAccessible2 interfaces. >> >> There is an autocomplete state in IAccessible2 is that what is being >> defined, or is this suppose to be an attribute thing? >> >> https://www.w3.org/wiki/ARIA_1.1_Testable_Statements#aria-autocomplete >> >> Jon >> >> >> Jon Gunderson, Ph.D. >> Coordinator >> Accessible IT Group >> Disability Resources and Education Services >> College of Applied Health Sciences >> University of Illinois at Urbana-Champaign >> >> E-mail: jongund@illinois.edu <mailto:jongund@illinois.edu> >> WWW: http://disability.illinois.edu/academic-support/aitg >> >
Received on Friday, 9 June 2017 17:39:14 UTC