Kibana: Reserved state of users or roles not reflected by screen reader

[aphelionz]

Steps to reproduce (assumes ChromeVox or similar)

1. Open Kibana in a new tab
2. Tab to Management
3. Tab to the "Roles" section
4. Tab to a reserved role, such as kibana_user
5. Examine the resultant page with a screen reader

Actual Result

1. No fields are editable, therefore not tabbable due to being reserved. However, the screen reader reflects nothing

Expected Result

1. No fields are editable, therefore not tabbable due to being reserved. The screen reader should reflect this somehow.

Category: #18866 Kibana 6.3 Meta Issues
Relevant WCAG Criteria: 3.3.2 Labels or Instructions

[kobelb]

@legrego do you happen to know if this is still an issue with the new User/Role management screens?

[kobelb]

I stopped being lazy and investigated this myself. When we EUIfied the user management screen, we added the following disclosure to the top, which should be sufficient for screen readers to pick up:

When we EUIfy the role management page as part of the Spaces effort, we'll want to add a similar disclosure.

[legrego]

Thanks for investigating -- I'll make sure to update the role management screen to match

[AlonaNadler]

Any update on this issue, is it relevant in 6.4 and 6.5?

[legrego]

This is resolved in 6.5 with the rewrite of the Role Management screen

[kobelb]

Closing issue as this will be resolved in 6.5