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 11510 - PFWG Issue-88 request that actions not be exposed when aria-disabled="true"
Summary: PFWG Issue-88 request that actions not be exposed when aria-disabled="true"
Status: RESOLVED WONTFIX
Alias: None
Product: ARIA
Classification: Unclassified
Component: Core AAM (show other bugs)
Version: 1.0
Hardware: PC Windows XP
: P1 normal
Target Milestone: ---
Assignee: Andi Snow-Weaver
QA Contact: ARIA UA Implementors
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-09 16:06 UTC by Andi Snow-Weaver
Modified: 2011-04-18 23:54 UTC (History)
0 users

See Also:

Attachments

Description Andi Snow-Weaver 2010-12-09 16:06:54 UTC 
See Issue 88: http://www.w3.org/WAI/PF/Group/track/issues/88
Comment 1 Andi Snow-Weaver 2011-02-17 15:54:53 UTC 
Andi to send e-mail to Sally Cain requesting clarification and let her know our preference is to expose the actions even though nothing will happen if they are invoked.
Comment 2 Andi Snow-Weaver 2011-02-17 16:18:37 UTC 
Sally "recorded" this action but it was actually raised by Aaron Leventhal. 

Cynthia, please confirm that the behavior of native widgets is to expose the actions even if the widget is disabled. Then I will e-mail the PFWG about the issue.
Comment 3 Cynthia Shelly 2011-04-18 23:54:55 UTC 
Native behavior is inconsistent.  WinForms sets the Default Action MSAA field to null, but callign dodefaultaction still triggers it.  WPF leaves the field populated, but UIA invoke does not do anything.  IE does not modify the field, and dodefaultaction does nothing.  I recommned that we do not make a recommendation here, since the different UI frameworks behave differently.