This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24615 - Define Accessibility API behavior for dynamic changes to input element type attribute
Summary: Define Accessibility API behavior for dynamic changes to input element type a...
Status: NEW
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia Shelly) (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: steve faulkner
QA Contact: HTML a11y API spec bugbot
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-10 23:54 UTC by Cynthia Shelly
Modified: 2016-03-19 13:00 UTC (History)
7 users (show)

See Also:

Attachments

Description Cynthia Shelly 2014-02-10 23:54:03 UTC 
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.
Comment 1 alexander surkov 2014-02-11 13:32:40 UTC 
for the record: in Firefox the accessible object is recreated and focus is refired.