-
Notifications
You must be signed in to change notification settings - Fork 23
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Accname discussion - multiple references #97
Comments
IE 11, Firefox: "Outside Text Screen Text Outside Text" AccName Prototype Test is correct because of: "Important: Each node in the subtree is consulted only once. If text has been collected from a descendant, but is referenced by another IDREF in some descendant node, then that second, or subsequent, reference is not followed. This is done to avoid infinite loops" I.e. aria-labelledby=p is evaluated as in Issue 98 and aria-labelledby=q is ignored |
But much more interesting is the original example: Edit: Here I am of the opinion that choise 2 is correct. ("If traversal of the current node is due to recursion and the current node is an embedded control as defined in step 2E, ignore aria-label and skip to rule 2E."). I agree with @jongund at https://lists.w3.org/Archives/Public/public-aria/2021Jan/0001.html If this is true, then the output would be correct in Chrome and incorrect in Firefox + AccName Prototype Test |
@JAWS-test wrote:
It's useful to know this. Thank you. I also want to remind the readers that the discussion should be about what the algorithm should do, regardless of what the browsers currently do. |
Answer: "Outside Text Screen Text" I think that's what the spec intends. But I can get there in two slightly different ways, and even get different results, depending on how I read the algorithm. The differences come from the following:
Below are the two ways I can get "Outside Text Screen Text," which I believe is what authors expect to get. Version 1Step 1 Step 2: Compute text for current node button (test) Processing IDREF p: Processing child node q: Processing child node test: Results for IDREF p: "Outside Text Screen Text" Processing IDREF q: Final result: "Outside Text Screen Text" Version 2Step 1 Step 2: Compute text for current node button (test) Processing IDREF p: Processing child node q: Processing child node test: Results for IDREF p: "Outside Text Screen Text" Processing IDREF q: Final result: "Outside Text Screen Text" |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
To facilitate discussion of https://lists.w3.org/Archives/Public/public-aria/2021Jan/0052.html it was decided to post into separate github issues. Please also see #98
What should the accessible name be for the button (#test)
Please post your answer and reasoning - referencing the steps in the ACCNAME spec which result in your decision.
The text was updated successfully, but these errors were encountered: