Nickname:
Title:
State: RAISED OPEN PENDINGREVIEW CLOSED POSTPONED
Product: None AccNam AAM 1.2 ARIA 1.0 ARIA 1.0 Authoring Practices ARIA 1.0 Implementation Guide ARIA 1.0 Primer ARIA 1.0 Test Plan ARIA 1.1 ARIA 1.1 Authoring Practices ARIA 1.1 Core Mapping Specification ARIA 1.1 Name Computation ARIA 1.1 Test Plan ARIA 1.2 ARIA 1.2 Core AAM specification ARIA 2.0 ARIA 2.0 Authoring Practices ARIA 2.0 Core AAM ARIA 2.0 Name Calculation ARIA HTML 5 Implementation Guide CSS AAM Digital Publishing AAM Digital Publishing Roles Module Miscellaneous SVG AAM Accessibility Mapping spec. WCAG 2 Techniques for ARIA
Raised By: Sina Bahram Aditya Bajaj Benjamin Beaudry Curt Bellew Zoë Bijl Shari Butler ANDREA CARDONA Dominic Cooney Michael Cooper James Craig Joanmarie Diggs Isaac Durazo Howard Edwards James Edwards Frank Elavsky Mayuri Faldu Steve Faulkner Reinaldo Ferraz Alexander Flenniken Bryan Garaventa Rashmi Garimella Matt Garrish Jaunita George Ariella Gilmore Michael Goddard Glen Gordon Shirisha Gubba Jon Gunderson Markku Hakkinen Sarah Higley Hans Hillen Isabel Holdsworth Stanley Hon Patrick Hung Matthew King Greta Krafsig Peter Krautzberger JaEun Jemma Ku Christopher Lane Charles LaPierre Gez Lemon Aaron Leventhal Laurence Lewis biao liu Brian Liu Xu David MacDonald Sazzad Mahamud Mark McCarthy Erika Miguel Daniel Montalvo Sheila Moussavi James Nurthen Scott O'Hara Adam Page Michael Pennisi Roberto Perez Janina Sajka Trisha Salas Stefan Schnabel Harris Schneiderman Boaz Sender Cynthia Shelly Tzviya Siegman Avneesh Singh Neil Soiffer Francis Storr Melanie Sumner Alexander Surkov James Teh Seth Thompson Jan Williams Benjamin Young Valerie Young Helen Zhou 骅 杨 Cynthia Shelly
Description: Potential infinite loop Take this example: <td>I contain a <button>button</button>!</td> Computing the name for the cell, I believe you’ll hit this: 1. Hit step 2.F, name from contents 2. Walk child nodes until you hit the <button> 3. Button hits step 2.E., which says get the name from the text alternative of the button 4. One of the two will happen: a. Button satisfies 2.D and has a native attribute defining text alternative (really need this specified) b. Button does not satisfy 2.D and drops back into 2.E and goes back to step 3 here Now, take this: <td>I contain a <button aria-label=”fun button”>button</button>!</td> Computing the name for the cell, I believe you’ll hit this: 1. Hit step 2.F, name from contents 2. Walk child nodes until you hit the <button> 3. Button hits step 2.E., which says get the name from the text alternative of the button 4. Hit step 2.C, and this is an embedded control with an aria-label defined, but ignored, so we jump to step 2.E again 5. Step 2.E and goes back to step 3 here
Add notes (no markup allowed, URIs get automatically hyperlinked):
No related emails.
I am looking at issue 752: https://www.w3.org/WAI/ARIA/track/issues/752 I don’t see the infinite loop here. Step 2E now says: Otherwise, if the current node is a control embedded within the label (e.g. the label element in HTML or any element directly referenced by aria-labelledby) for another widget, where the user can adjust the embedded control's value, then include the embedded control as part of the text alternative in the following manner In Cynthia’s example: <td>I contain a <button aria-label=”fun button”>button</button>!</td> button is not within a label. It is within a TD. So, in the case of 2F. TD is a cell that allows name from content and the algorithm will cycle through the children. When the current node becomes “pushbutton” ( a button ) the HTML spec. states how to compute its name and step 2C will compute the name based on the aria-label supplied. In other words, there is no infinite loop given the current text. So, I recommend that we close the issue. I am closing the issue.