I've been discussing this with Rich: rather than creating IATable3 and having summary return a VARIANT which could then return either a BSTR (for HTML) or an object (for other non-browser implementations), a solution with less impact would be to deprecate summary and add a comment that describedBy should be used when the description is provided by an object (or tree of objects) or accDescription otherwise. That seems acceptable for non-browser implementations as well. What do you think?
Pete On 8/23/2011 8:50 AM, Pete Brunet wrote: > For the 1.3 release, let me know if anyone is opposed to creating > IATable3 with summary and caption changed to return a VARIANT instead of > an IUnknown. > > On 8/22/2011 9:48 AM, Brett Lewis wrote: >> Hi, >> What prompted this thread for me is my trying to obtain caption and >> summary via the IAccessibleTable interface. >> By convention using name and description is fine but doesn't really seem >> to correctly implement IAccessibleTable and is only somewhat intuitive. >> I like the idea of having the get_summary and get_Caption return a >> variant with either the text or the IAccessible. >> Brett >> >> >> -----Original Message----- >> From: Alexander Surkov [mailto:[email protected]] >> Sent: Monday, August 08, 2011 8:58 PM >> To: James Teh >> Cc: IAccessible2 mailing list; Brett Lewis >> Subject: Re: [Accessibility-ia2] HTML table summary mapping to IA2 >> >> Hi, Jamie. It appears AT want to get summary and caption (not a name or >> description since they can be different). >> >> Brett, do you have scenarios to share? >> >> Thank you. >> Alex. >> >> >> On Tue, Aug 9, 2011 at 12:42 PM, James Teh <[email protected]> wrote: >>> Hi Alex, >>> >>> Why are accName/accDescription insufficient? >>> >>> Thanks, >>> Jamie >>> >>> On 9/08/2011 1:36 PM, Alexander Surkov wrote: >>>> Hi. >>>> >>>> IATable2 provides caption and summary properties that return >>>> accessible objects. HTML table summary is provided by @summary >>>> attribute so there's no accessible object that's created from DOM >>>> element. This can be workarounded by artificial accessible object >>>> creation that is attached or not attached to the tree but this >>>> complicates implementation and I would try to avoid it. Can we extend >>>> the IAccessibleTable2 by summaryText and captionText attributes or >>>> introduce summary and caption object attributes on table accessible >>>> if interface change is not desired for this? >>>> >>>> Thank you. >>>> Alexander. >>>> _______________________________________________ >>>> Accessibility-ia2 mailing list >>>> [email protected] >>>> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 >>> -- >>> James Teh >>> Vice President, Developer >>> NV Access Inc, ABN 61773362390 >>> Email: [email protected] >>> Web site: http://www.nvaccess.org/ >>> _______________________________________________ >>> Accessibility-ia2 mailing list >>> [email protected] >>> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 >>> >> _______________________________________________ >> Accessibility-ia2 mailing list >> [email protected] >> https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 >> > > > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 > _______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
