Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Chrome and Firefox report differently for link accessible name #2088

Open
shunguoy opened this issue Nov 7, 2024 · 0 comments
Open

Chrome and Firefox report differently for link accessible name #2088

shunguoy opened this issue Nov 7, 2024 · 0 comments
Assignees
@shunguoy
Labels
Bug Something isn't working engine Issues in the accessibility-checker-engine component Firefox When different than in Chrome T63

Comments

@shunguoy
Copy link
Contributor

shunguoy commented Nov 7, 2024 •
edited
Loading

test/v2/checker/accessibility/rules/a_text_purpose_ruleunit/A-nonTabable.html
test/v2/checker/accessibility/rules/a_text_purpose_ruleunit/A-slot-text-error1.html. (slot content)

Chrome:
Image

Firefox:
Image
@shunguoy shunguoy changed the title Chrome and Firefox report differently for link accessible name Chrome and Firefox report differently for a link Nov 7, 2024
@shunguoy shunguoy added the engine Issues in the accessibility-checker-engine component label Nov 8, 2024
@shunguoy shunguoy changed the title Chrome and Firefox report differently for a link Chrome and Firefox report differently for link accessible name Nov 8, 2024
@shunguoy shunguoy added the T63 label Nov 11, 2024
@shunguoy shunguoy mentioned this issue Nov 14, 2024
Open
4 tasks
@philljenkins philljenkins added Bug Something isn't working Firefox When different than in Chrome labels Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shunguoy shunguoy

Labels
Bug Something isn't working engine Issues in the accessibility-checker-engine component Firefox When different than in Chrome T63
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@philljenkins @shunguoy