[Bug 10657] integration of "aria-autocomplete" with the various autocompletion mechanisms in html5

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10657





--- Comment #5 from steve faulkner <faulkner.steve@gmail.com>  2010-09-22 08:23:29 ---
(In reply to comment #4)
> (In reply to comment #3)> "How should I integrate "aria-autocomplete" with the
> various autocompletion > mechanisms in HTML5, specifically list="" on <input>,
> autocomplete="" on > <form> and various controls, and UA-specific behaviour on
> all editable > controls?"AFAICT, aria-autocomplete shouldn't be integrated with
> them. However, it might make sense to expose the autocompleting nature of
> autocomplete="" and list="" to AT independently of aria-autocomplete. (Though
> this raises the question: What should be exposed if the native autocompletion
> features are used but there's also aria-autocomplete=none.)

henri wrote
> them. However, it might make sense to expose the autocompleting nature of
> autocomplete="" and list="" to AT

I agree, wherever native HTML5 features have accessibility API mappings they
should be exposed.

For IA2
expose Object attribute autocomplete 
A2_STATE_SUPPORTS_AUTOCOMPLETION
http://accessibility.linuxfoundation.org/a11yspecs/ia2/docs/html/_accessible_states_8idl.html#afecbfb195aaf7050dc8f75a7833bd5faad7825464a6f27e9f42f11104ce2ae7

For ATK
expose Object attribute autocomplete 
ATK_STATE_SUPPORTS_AUTOCOMPLETION
http://library.gnome.org/devel/atk/unstable/atk-AtkState.html

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Wednesday, 22 September 2010 08:23:31 UTC