- From: Aaron Leventhal <aleventhal@google.com>
- Date: Mon, 8 Jul 2019 13:26:51 -0400
- To: Matt King <a11ythinker@gmail.com>
- Cc: Bryan Garaventa <bryan.garaventa@levelaccess.com>, Simon Pieters <simon@bocoup.com>, ARIA Working Group <public-aria@w3.org>
- Message-ID: <CA+1LECQMhva+0sKn7_K7zUneVjZaVVA3uZJ9dRCQkCZsGWwrgA@mail.gmail.com>
I believe they would not get walked for the name calculation. The name calc is recursive, and the name rule for each item walked is consulted. If the rule for a role says that names do not come from descendants, there is no need to recurse into the descendants. On Mon, Jul 8, 2019 at 1:23 PM Matt King <a11ythinker@gmail.com> wrote: > Hmmm… does that mean that if someone put a group inside a link or button > that the group descendants would not get walked? Or is that different > because they have children presentational. If so, then how is that > difference covered? > > > > *From:* Aaron Leventhal <aleventhal@google.com> > *Sent:* Monday, July 8, 2019 7:08 AM > *To:* Bryan Garaventa <bryan.garaventa@levelaccess.com> > *Cc:* Matthew King <mck@fb.com>; Simon Pieters <simon@bocoup.com>; ARIA > Working Group <public-aria@w3.org> > *Subject:* 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 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.levelaccess.com_&d=DwMFaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=O5KcpICX8LHGtRJi41yDlw&m=dNhcM0HAGmN0k1jBT2L-4ZZxvSGqAzKSD-c0CnzLskw&s=GwB8g_FKiGiv0GII9xH7xjrQR6R58fPv4bywmkCXIrU&e=> > > > > *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 > >
Received on Monday, 8 July 2019 17:27:26 UTC