-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Tentative: match new PR about 2E "unless the element is marked as presentational" #50002
base: master
Are you sure you want to change the base?
Conversation
Hi @giacomo-petri, I'm coming from the review of PR 2405. This looks good to me for the most part, Scott's addressed some of the initial confusion. I noted some semantic confusion in the naming of the test sections vs what is being tested. While Unless there's something I'm missing, the heading and test setup should match to avoid confusion for folks when reading. Thank you for this work! |
Done |
Thanks @giacomo-petri! You have some lint errors, once you've addressed those I'll be happy to approve this. |
Thanks all:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates! Almost ready!
<fieldset data-expectedlabel="legend" data-testname="html: fieldset wrapping legend[role none]" class="ex-label"><legend role="none">legend</legend></fieldset> | ||
|
||
<h2>HTML fieldset with role="none" wrapping legend</h2> | ||
<fieldset role="none" data-expectedlabel="" data-testname="html: fieldset[role none] wrapping legend" class="ex-label"><legend>legend</legend></fieldset> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might not be a valid test assumption, as the WebDriver methods don't guarantee a a return value for an element that is ignored by accessibility. That said, maybe it will but we won't know until all the CI bots run. This type of scenario may be more reliable to test once the new WebDriver accessibility extensions land. Ditto for the next one.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For example, this could be the cause of the Gecko CI crash, though I haven't looked into it yet.
<table role="none" data-expectedlabel="" data-testname="html: table[role none] wrapping caption" class="ex-label"><caption>caption</caption></table> | ||
|
||
<h2>HTML table role="none" wrapping caption with role="none"</h2> | ||
<table role="none" data-expectedlabel="" data-testname="html: table[role none] wrapping caption[role none]" class="ex-label"><caption role="none">caption</caption></table> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Like the fieldset[role=none] test above, this may not be a valid test assumption due to an artifact of the WebDriver methods not defining the expected return type when a DOM element no longer has a backing AX element due to the none role. Wait until all the CI bots complete, since there are implementation detail differences this will likely illustrate.
Co-authored-by: James Craig <[email protected]>
Co-authored-by: James Craig <[email protected]>
- added readonly testcases with and w/o disabled - replaced [role none] witg [role=none] in data-testname
replaced role none with role=none
added cross reference comment
add cross reference comment
expectations moved from svg to circle
table fix (added THs and TDs)
Closes: web-platform-tests/interop-accessibility#167
Relates and match: w3c/aria#2405
Ambiguity: https://www.w3.org/TR/accname-1.2/#comp_host_language_label
This PR adds tests for:
Note: since I created tests for acc name related to presentational roles conflict resolution, I have also included tests to verify that the computed role aligns with the expected result.