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

fixrule(element_orientation_unlocked) Reports "inapplicable" while ACT b33eff expects "Failed" #2092

Open
1 of 2 tasks
philljenkins opened this issue Nov 12, 2024 · 1 comment
Open
1 of 2 tasks

fixrule(element_orientation_unlocked) Reports "inapplicable" while ACT b33eff expects "Failed" #2092

philljenkins opened this issue Nov 12, 2024 · 1 comment
Assignees
@philljenkins @shunguoy
Labels
ACT Issues/Rules related to ACT engine Issues in the accessibility-checker-engine component

Comments

@philljenkins
Copy link
Contributor

philljenkins commented Nov 12, 2024 •
edited
Loading

Checker rule element_orientation_unlocked reports inconsistent with ACT rule(s) below:

  • Failed examples should be failed by at least one of the Checker rules fail reason codes.
  • Checker should be mapping (report against) the same success criteria as what is expected by the ACT rule.
  1. Partial: Orientation of the page is not restricted using CSS transforms b33eff:

Reference

Screenshot 2024-11-12 at 4 37 10 PM
@philljenkins philljenkins mentioned this issue Nov 12, 2024
Closed
2 tasks
@philljenkins
Copy link
Contributor Author

philljenkins commented Nov 12, 2024 •
edited
Loading

It's not clear why its reported to ACT as "inapplicable", while running the Checker browser extension flags it as a Violation

Reported to ACT:

Failed Example 4: https://www.w3.org/WAI/content-assets/wcag-act-rules/testcases/b33eff/8f341a73c698daf157613c32a521878ed5aa7310.html
    �[31m--Expected failed, but returned earl:inapplicable
    Failures: []
    Review: []
    Pass: []
    All: [
      "html_skipnav_exists:Potential_1:POTENTIAL",
      "style_highcontrast_visible:Manual_1:MANUAL",
      "skip_main_exists:Fail_1:FAIL"
    ]�

Reported on Chrome v3.1.77

  • Violation
  • The element <html> is restricted to either landscape or portrait orientation using CSS transform property
  • Elements should not be restricted to either landscape or portrait orientation using CSS transform property
  • Element location
    <html lang="en">

Rule mapping spreadsheet

Screenshot 2024-11-12 at 4 59 40 PM

test case Fail Example 4 code:

Screenshot 2024-11-12 at 5 01 32 PM

@philljenkins philljenkins added ACT Issues/Rules related to ACT engine Issues in the accessibility-checker-engine component labels Nov 12, 2024
@shunguoy shunguoy mentioned this issue Nov 14, 2024
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@philljenkins philljenkins

@shunguoy shunguoy

Labels
ACT Issues/Rules related to ACT engine Issues in the accessibility-checker-engine component
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@philljenkins @shunguoy