Hi, Pete.

> 1) It makes sense to not deprecate IAccessible2::relations since it
> can be useful for AT tools. In this case maxRelations argument is not
> really needed and it can be marked as ignored but it's not big deal.
>
> Is there a reason to not deprecate it, i.e. do we need implementers to spend
> the time on it?  What can be done with it that can't be done with
> IA2_2:relationTargetsOfType?

I bet this method is in use in accProbe and aViewer already and it
must be pretty handy for them. If next IAccessible2 introduces more
relation types then tools developers don't need to change their code,
release new version, etc. On the another hand relation type is a
string so technically the server can implement non standard relations.
The method to get all of them is quite useful in this case.

Thank you.
Alex.


On Fri, Mar 15, 2013 at 9:57 AM, Pete Brunet <p...@a11ysoft.com> wrote:
> Hi Alex,
>
> On 3/4/13 10:29 PM, Alexander Surkov wrote:
>
> Hi, Pete. More feedback.
>
> 1) It makes sense to not deprecate IAccessible2::relations since it
> can be useful for AT tools. In this case maxRelations argument is not
> really needed and it can be marked as ignored but it's not big deal.
>
> Is there a reason to not deprecate it, i.e. do we need implementers to spend
> the time on it?  What can be done with it that can't be done with
> IA2_2:relationTargetsOfType?
>
> 2) IAccessible2_2::accessibleWithCaret: "Returns the hypertext
> accessible in the subtree of this object, and the caret offset within
> it". It doesn't say which object is returned. In my understanding it
> should be the deepest one.
>
> I changed that to: Returns the deepest hypertext accessible...  Hopefully
> Arnstein will comment if this is not correct.
>
> 3) Honestly I failed to understand IA2Actions
> (http://a11ysoft.com/ia2/docs/html/_accessible_action_8idl.html), it
> seems referred methods like textAtOffset
> (http://a11ysoft.com/ia2/docs/html/interface_i_accessible_text.html#a9bd84b099ac7ce2435280549e90c8827)
> say nothing about IA2Action support. I'd be great to provide an
> example how it works. Otherwise it sounds too generic.
>
> I'm glad you noticed this.  The preamble text is wrong.  I copied it from
> IA2TextBoundaryType as a prototype and didn't finish the work.  These are
> the actions we defined for adding support for HTML5 media.  I changed the
> preamble text to:
>
> /** This enum defines values which are predefined actions for use when
> implementing
>  support for media.
>
>  This enum is used when specifying an action for
> IAccessibleAction::doAction.
> */
>
> 4) changelog (http://a11ysoft.com/ia2/changelog.txt) lists
> IA2_RELATION_GROUPING_OBJECT_FOR, IA2_RELATION_POPUP_INITIATOR_FOR
> relations, however they aren't listed in interface
> http://a11ysoft.com/ia2/docs/html/_accessible_relation_8idl.html
>
> Fixed.
>
> 5) IA2_RELATION_CONTAINING_DOCUMENT: makes sense to mention that
> returned object implements IAccessibleDocument interface.
>
> I added: The target object implements the IAccessibleDocument interface.
>
> Otherwise it looks good.
>
> Thanks Alex, I refreshed the IA2 files
>
> - The change log: http://a11ysoft.com/ia2/changelog.txt
> - IA2 spec: http://a11ysoft.com/ia2/docs/html/
> - The individual IDL files: http://a11ysoft.com/ia2/api/
>   or the full IDL file: http://a11ysoft.com/ia2/ia2_api_all.idl
>
> Did anyone try the new proxy?
>   http://a11ysoft.com/ia2/proxy-dll/
>
>
> Thank you.
> Alex.
>
>
> On Tue, Mar 5, 2013 at 6:34 AM, Pete Brunet <p...@a11ysoft.com> wrote:
>
> Please review the following.  This should be the final unless updates are
> needed.
>
> - The change log: http://a11ysoft.com/ia2/changelog.txt
> - IA2 spec: http://a11ysoft.com/ia2/docs/html/
> - The individual IDL files: http://a11ysoft.com/ia2/api/
>   or the full IDL file: http://a11ysoft.com/ia2/ia2_api_all.idl
> - The proxy: http://a11ysoft.com/ia2/proxy-dll/
>
> Pete
>
> On 2/26/13 12:30 AM, Pete Brunet wrote:
>
> If don't hear anything over the next couple of days, I'll assume this won't
> be in 1.3 and I'll finish up the work I need to do to republish the spec on
> a11ysoft.com for one more look at it before I get in touch with the Linux
> Foundation IT guys to get it published there.
>
> On 2/25/13 11:58 PM, Alexander Surkov wrote:
>
> Probably we should let IA2 1.3 go without addressing this issue. In
> Firefox we still can use IA2 to expose it in non-standard way (like
> new object attribute).
> Alex.
>
>
> On Tue, Feb 26, 2013 at 2:49 PM, James Teh <ja...@nvaccess.org> wrote:
>
> On 26/02/2013 4:12 PM, Pete Brunet wrote:
>
> So Is the following what you want?  It moves the method from
> IA2_2 to IAText2 thus resolving an issue for Jamie.
> HRESULT IAccessibleText2::offsetOfChildText (
>        [in] IUnknown* child,
>        [out] long* offset
>     );
>
> ...
>
>    S_OK is returned if the parent accessible implements IAccessibleText.
>    S_FALSE is returned if the parent accessible does not implement
> IAccessibleText; [out] value is -1.
>
> This text needs to be changed for the new method.
>
> That said, this certainly does look nicer to me. I still think it's a bit of
> a hack, especially given that IAccessibleHyper* should really cover this,
> but at least it's an isolated hack.
>
>
> Jamie
>
> --
> James Teh
> Director, NV Access Limited
> Email: ja...@nvaccess.org
> Web site: http://www.nvaccess.org/
> Phone: +61 7 5667 8372
> _______________________________________________
> Accessibility-ia2 mailing list
> Accessibility-ia2@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
>
> _______________________________________________
> Accessibility-ia2 mailing list
> Accessibility-ia2@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
>
>
> --
> Pete Brunet
>
> a11ysoft - Accessibility Architecture and Development
> (512) 467-4706 (work), (512) 689-4155 (cell)
> Skype: pete.brunet
> IM: ptbrunet (AOL, Google), ptbru...@live.com (MSN)
> http://www.a11ysoft.com/about/
> Ionosphere: WS4G
>
>
> --
> Pete Brunet
>
> a11ysoft - Accessibility Architecture and Development
> (512) 467-4706 (work), (512) 689-4155 (cell)
> Skype: pete.brunet
> IM: ptbrunet (AOL, Google), ptbru...@live.com (MSN)
> http://www.a11ysoft.com/about/
> Ionosphere: WS4G
>
> _______________________________________________
> Accessibility-ia2 mailing list
> Accessibility-ia2@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
>
>
> --
> Pete Brunet
>
> a11ysoft - Accessibility Architecture and Development
> (512) 467-4706 (work), (512) 689-4155 (cell)
> Skype: pete.brunet
> IM: ptbrunet (AOL, Google), ptbru...@live.com (MSN)
> http://www.a11ysoft.com/about/
> Ionosphere: WS4G
_______________________________________________
Accessibility-ia2 mailing list
Accessibility-ia2@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2

Reply via email to