Re: AccName exclusion of groups and menus from content when calculating treeitem and menuitem names

I think it's accounted for by the fact that as the browser looks at
descendants for contributions to a name, and it runs across the group, the
rule is that a group can get  name from author but not from contents.

On Fri, Jun 28, 2019 at 12:55 PM Bryan Garaventa <
bryan.garaventa@levelaccess.com> wrote:

> Hi Matt,
>
> I’m including the ARIA WG on this thread as well since it’s important for
> AccName understanding in general.
>
>
>
> As a quick answer, yes this is accounted for in the prototype, but no this
> isn’t documented anywhere in the spec as yet.
>
>
>
> This is however included within the draft outline I sent through some
> weeks back, which is meant to account for these types of exclusions and
> subtree logic when parsing child node structures. The outline is important
> because it includes concepts and additions that don’t appear as spec text
> as yet, yet does reflect decisions we have already agreed to when these
> were previously discussed.
>
>
>
> I need to get some help to setup a wiki page on the AccName repo where I
> can post this outline and then it will be easier to refer people to this
> instead.
>
>
>
> Since it’s the end of the quarter, my time is limited at the moment, but
> I’ll be able to dedicate more time to getting this organized soon I hope.
>
>
>
> All the best,
>
> Bryan
>
>
>
>
>
>
>
>
>
> Bryan Garaventa
>
> Principal Accessibility Architect
>
> Level Access, Inc.
>
> Bryan.Garaventa@LevelAccess.com
>
> 415.624.2709 (o)
>
> www.LevelAccess.com <http://www.levelaccess.com/>
>
>
>
> *From:* Matthew King <mck@fb.com>
> *Sent:* Tuesday, June 25, 2019 5:34 PM
> *To:* Aaron Leventhal (aleventhal@google.com) <aleventhal@google.com>;
> Bryan Garaventa <bryan.garaventa@levelaccess.com>
> *Cc:* Simon Pieters <simon@bocoup.com>
> *Subject:* AccName exclusion of groups and menus from content when
> calculating treeitem and menuitem names
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
> Aaron,
>
>
>
> I learned from you that accname is supposed to ignore descendant groups,
> and I think menus, when calculating the name of a treeitem or menuitem from
> content. However, Simon has been looking for where this is documented (he
> is helping me develop a new APG section on naming and describing).
>
>
>
> For example, it is my understanding that when calculating the name of the
> parent tree item in the following, the group is ignored and the name is
> “Fruits”:
>
>
>
> <ul role=*"tree"*>
>
>   <li role=*"treeitem"*>Fruits
>
>     <ul role=*"group"*>
>
>       <li role=*"treeitem"*>Apples</li>
>
>       <li role=*"treeitem"*>Bananas</li>
>
>       <li role=*"treeitem"*>Oranges</li>
>
>     </ul>
>
>   </li>
>
> </ul>
>
>
>
> Similarly, I also have been under the impression that when calculating the
> name of the following parent menuitem from content, the submenu items are
> supposed to be ignored to also come up with a name of “Fruits”:
>
>
>
> <ul role=*"menu"*>
>
>   <li role=*"menuitem"*>Fruits
>
>     <ul role=*"menu"*>
>
>       <li role=*"menuitem"*>Apples</li>
>
>       <li role=*"menuitem"*>Bananas</li>
>
>       <li role=*"menuitem"*>Oranges</li>
>
>     </ul>
>
>   </li>
>
> </ul>
>
>
>
> Bryan, do you account for this in your implementation of the algorithm? Do
> you know where it is documented? If it is not, should I raise an issue
> against accname?
>
>
>
> Thanks,
>
> Matt
>