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.

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

Evaluate Dashboard UI against Accessibility standards #3149

Closed
nwmac opened this issue Jun 2, 2021 · 6 comments
Closed

Evaluate Dashboard UI against Accessibility standards #3149

nwmac opened this issue Jun 2, 2021 · 6 comments
Assignees
Labels
kind/tech-debt Technical debt QA/manual-test Indicates issue requires manually testing team/area3 Helm Yes!
Milestone

Comments

@nwmac
Copy link
Member

nwmac commented Jun 2, 2021

We need to conduct an evaluation of the Dashboard UI against accessibility standards.

Specifically for now:

Write up a report on compliance and identify key areas needing improvement and specific actions we need to take to reach compliance (or at least reach an acceptable level of compliance, TBD)

(Note, we may also need to evaluate against https://www.section508.gov/create/software-websites in the future)

@lvuch
Copy link
Contributor

lvuch commented Jul 8, 2021

Tools and resources to use:
https://www.a11yproject.com/checklist/#appearance
https://www.a11yproject.com/resources/#browser-extensions
accessibilityinsights.com

@gaktive gaktive added this to the v2.6.x milestone Jul 13, 2021
@lvuch
Copy link
Contributor

lvuch commented Jul 15, 2021

Here are some items from a pass on cluster dashboard page using accessibilityinsights.com fast pass:
https://mysuse-my.sharepoint.com/:w:/g/personal/lauren_harden_suse_com/EQr68YXSmqFLhuI4NjRf71wBMsXEM-bB_N1X2FZ7Yp-HEA

@nwmac nwmac modified the milestones: v2.6.x, Project Jul 20, 2021
@lvuch
Copy link
Contributor

lvuch commented Jul 27, 2021

Chatted with product brand team (Jesus and Cynthia)

  • They need an instance to run/test the Axe tool they plan to use for automated testing. This tool requires integration in CI process.
  • Aim is to begin early September

Technical requirements
- instance of running
- clarify: is any client or agency required to meet AAA grade? Cynthia has confidence we can meet A and AA. AAA is likely more than we would need. @nwmac Let me know if you know otherwise.

@lvuch
Copy link
Contributor

lvuch commented Jul 28, 2021

From Chris Nuber (RFed) client had asked if Rancher had a VPAT/508 compliance on the federal side

@bdekany
Copy link

bdekany commented Aug 23, 2021

Hi,

I've try to integrate pa11y-ci to package.json.
Testing the login page is easy and generate a report (30+ issues against WCAG2 baseline)

But it's hard to test the actual dashboard as login and password field doesn't have CSS Element id nor class.

My pa11y configfile : rancher26.json

{
  "defaults": {
    "chromeLaunchConfig": {
      "ignoreHTTPSErrors": "true"
    }
  },
  "urls": [
    {
      "url": "https://rancher26.mylabserver.com/",
      "userAgent": "Mozilla"
    },
    {
      "url": "https://rancher26.mylabserver.com/dashboard/home",
      "userAgent": "Mozilla",
      "actions": [
        "set field div.mb-20 div.labeled-input.edit input to admin",
        "set field div div.labeled-input.edit input to password",
        "click element .btn.role-primary",
        "wait for path to be /dashboard/home"
      ]
    }
  ]
}

Installation on openSUSE:

sudo zypper in nodejs14 cairo gtk3 mozilla-nss libxshmfence1
sudo npm install -g pa11y-ci --unsafe-perm

Run command:
pa11y-ci -c rancher26.json

@gaktive gaktive self-assigned this Aug 27, 2021
@zube zube bot added the team/area3 Helm Yes! label Apr 18, 2022
@nwmac nwmac added the kind/tech-debt Technical debt label Jun 20, 2022
@nwmac nwmac added the QA/manual-test Indicates issue requires manually testing label Jan 30, 2024
@gaktive
Copy link
Member

gaktive commented Dec 11, 2024

This ticket has been superseded by newer accessibility tickets. #8986 is one example

@gaktive gaktive closed this as completed Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/tech-debt Technical debt QA/manual-test Indicates issue requires manually testing team/area3 Helm Yes!
Projects
None yet
Development

No branches or pull requests

5 participants