- From: <bugzilla@jessica.w3.org>
- Date: Mon, 10 Feb 2014 23:54:03 +0000
- To: public-html-admin@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24615
Bug ID: 24615
Summary: Define Accessibility API behavior for dynamic changes
to input element type attribute
Product: HTML WG
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: HTML a11y APIs (editor: Steve Faulkner, Cynthia
Shelly)
Assignee: faulkner.steve@gmail.com
Reporter: cyns@microsoft.com
QA Contact: sideshowbarker+html-a11y-api@gmail.com
CC: mike@w3.org, public-html-admin@w3.org,
public-html-bugzilla@w3.org,
public-html-wg-issue-tracking@w3.org
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.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 10 February 2014 23:54:06 UTC