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

(Accessibility) User Management - Create User Input Assistance #43000

Closed
barlowm opened this issue Aug 9, 2019 · 3 comments
Closed

(Accessibility) User Management - Create User Input Assistance #43000

barlowm opened this issue Aug 9, 2019 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Users/Roles/API Keys Project:Accessibility Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! WCAG A

Comments

@barlowm
Copy link
Collaborator

barlowm commented Aug 9, 2019

Steps to reproduce (assumes NVDA or JAWS Screen Reader or similar)

NVDA Screen Reader is a free Screen Reader which can be downloaded from the NV Access Website.

Deque has a page of shortcuts for help on using NVDA as well as a Quick Reference Guide for using NVDA

Steps to reproduce

  1. Log in to Kibana
  2. Using keyboard only, navigate to the Management / Security / Users page
  3. Click Create new user

Actual Result
There are no instructions to the user indicating which fields are required or that the password is 6 char minimum.

Error messages are properly displayed if the input fields are not valid, but only once the user clicks the "Create user" to save the new entries
When using NVDA Screen Reader, NVDA does not automatically report that there is an error (NVDA does not read the "Please address the errors in your form" to the user, nor does it report which fields are in error unless the user moves the cursor around.

<div class="euiCallOut euiCallOut--danger euiForm__errors">
    <div class="euiCallOutHeader">
        <span class="euiCallOutHeader__title">
            Please address the errors in your form.
        </span>
    </div>
</div>

The error message does not have a role=alert or an aria-live:assertive

Recommended correction

<div role="alert" aria-live="assertive" 
        class="euiCallOut euiCallOut--danger euiForm__errors">
    <div class="euiCallOutHeader">
        <span class="euiCallOutHeader__title">
            Please address the errors in your form.
        </span>
    </div>
</div>

Meta Issue
Accessibility Audit for Kibana 7.0

Kibana Version:
7.3.0

OS:
Tested on Windows 7.

Browser:
Tested in Chrome.

Screen reader: [if relevant]
NVDA

Relevant WCAG Criteria: WCAG Criterion
3.3.1 Error Identification - Level A

Relevant ARIA spec: WAI-ARIA Authoring Practices 1.1
role="alert" aria-live="assertive"

@myasonik myasonik added the Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! label Feb 10, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-security (Team:Security)

@legrego legrego added the bug Fixes for quality problems that affect the customer experience label Oct 23, 2020
@afharo
Copy link
Member

afharo commented Nov 9, 2020

I think it needs to be fixed in the elastic/eui repo: elastic/eui#4238

@afharo
Copy link
Member

afharo commented Nov 10, 2020

Closing this issue as it is fixed in elastic/eui#4238

Changes will be applied to Kibana on the bi-weekly EUI update

@afharo afharo closed this as completed Nov 10, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Users/Roles/API Keys Project:Accessibility Team:Security Team focused on: Auth, Users, Roles, Spaces, Audit Logging, and more! WCAG A
Projects
None yet
Development

No branches or pull requests

5 participants