24615 2014-02-10 23:54:03 +0000 Define Accessibility API behavior for dynamic changes to input element type attribute 2016-03-19 13:00:02 +0000 1 1 1 Unclassified HTML WG HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) unspecified PC Windows NT NEW P2 normal --- 1 cyns faulkner.steve chaals joelancer1394 mike public-html-admin public-html-bugzilla public-html-wg-issue-tracking surkov.alexander sideshowbarker+html-a11y-api oldest_to_newest 100224 0 cyns 2014-02-10 23:54:03 +0000 Same issue as https://www.w3.org/Bugs/Public/show_bug.cgi?id=13560 In the Windows accessibility APIs, the role/control type of an accessibility api object cannot be changed dynamically. The object must be destroyed and re-created. Doing so without losing focus or confusing AT is difficult and likely to be buggy. Not sure if this is also problematic on other platforms. Need to specify in mapping doc how this will be handled in APIs. Consider a WCAG failure for changing input type attribute at runtime. 100272 1 surkov.alexander 2014-02-11 13:32:40 +0000 for the record: in Firefox the accessible object is recreated and focus is refired.