(Accessibility) Kibana management issues

[rayafratkina]

Kibana Management

Index patterns

1. Table missing caption - 1.3.1 Info and Relationships - Level A
   Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text

2. Control inconsistency...
   Links to docs in the "Proceed with caution" block have different icon than other places (see images)

3.2.4 Consistent Identification - Level AA

3. Step 3 of creating new index pattern missing field label for select field

4. Display specific Index Pattern also missing field label for select field.

5. Multiple labels for single field

3.3.2 Labels or Instructions - Level A
Labels or instructions are provided when content requires user input.

Saved objects

1. The only table on the page has a caption but it's value is not descriptive of the purpose of the table -

1.3.1 Info and Relationships - Level A
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text

WAI-ARIA role of "status" is not valid for the caption tag. Status role is allowable in a "Widget"

2. Rows are missing scope to identify individual cells while navigating randomly through the table with screen reader

3. ARIA attributes must conform to valid values

 This condition exists for all the icons in the table.

4.1.2 Name, Role, Value - Level A
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.

4. Rich Text Areas ("element with scrollable content") does not have an obvious method of leaving the area via keyboard only

2.1.2 No Keyboard Trap - Level A
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

NOTE: The text area fields here do NOT function in the same way the text area fields in "Logstash - Pipelines".

"Logstash - Pipelines" text areas do NOT have a keyboard trap!

5. The labels intended for the Editable Input fields are pointing to the DIV element containing the input fields. Input fields are missing labels

    [3.3.2 Labels or Instructions](https://www.w3.org/WAI/WCAG21/quickref/?versions=2.0#labels-or-instructions) - Level A
 Labels or instructions are provided when content requires user input.

6. The table revealed by the flyout when examining relationships of a saved object, has a caption but it's value is not descriptive of the purpose of the table -

1.3.1 Info and Relationships - Level A
Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text

WAI-ARIA role of "status" is not valid for the caption tag. Status role is allowable in a "Widget"

7. Rows are missing scope to identify individual cells while navigating randomly through the table with screen reader

8. "Direct relationship" button could use additional screen-reader assistance (SC reads it as just as "Direct relationship button" but doesn't explain that clicking it can be used as a filter to change to show "Parent" and/or "Child" items in the table ). The control is a "button" but acts like a "select"
   3.2.4 Consistent Identification - Level AA
9. The "Type" button has the same issue

[elasticmachine]

Pinging @elastic/kibana-app-arch

[ppisljar]

Thank you for contributing to this issue, however, we are closing this issue due to inactivity as part of a backlog grooming effort. If you believe this feature/bug should still be considered, please reopen with a comment.