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

[TASK][Security Serverless]: Add semantic headings to Fleet Integration forms #181922

Merged
merged 2 commits into from
Apr 30, 2024
Merged

[TASK][Security Serverless]: Add semantic headings to Fleet Integration forms #181922

merged 2 commits into from
Apr 30, 2024

Conversation

1Copenut
Copy link
Contributor

@1Copenut 1Copenut commented Apr 26, 2024

Summary

refactored the Fleet "Add Integration" form to properly nest headings by level. This improves the experience for screen reader users and helps us improve our standing against WCAG SC 1.3.1 - Info and Relationships (Level A). Screenshot attached below.


Local refactor with nested heading levels

Screenshot 2024-04-26 at 4 39 24 PM

Related issues

Please see the related issue link below. This issue originated from an accessibility review of the Security Serverless project.

Checklist

Delete any items that are not applicable to this PR.

For maintainers

@1Copenut 1Copenut added WCAG A release_note:skip Skip the PR/issue when compiling release notes backport:skip This commit does not require backporting accessibility: cognition Accessibility issues including cognition, awareness, understanding v8.15.0 labels Apr 26, 2024
@1Copenut 1Copenut self-assigned this Apr 26, 2024
Comment on lines +143 to +145
<EuiTitle size="xs">
<h3 id={titleElementId}>{packageInput.title || packageInput.type}</h3>
</EuiTitle>
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opted to switch this out for <EuiTitle/> because I could pass a size prop and ensure the headings were the same size as other H3s on the page without custom CSS.

@1Copenut
Copy link
Contributor Author

Buildkite test this

@1Copenut 1Copenut marked this pull request as ready for review April 29, 2024 13:17
@1Copenut 1Copenut requested a review from a team as a code owner April 29, 2024 13:17
Copy link
Member

@kpollich kpollich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great change! 🚀

@botelastic botelastic bot added the Team:Fleet Team label for Observability Data Collection Fleet team label Apr 29, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/fleet (Team:Fleet)

@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #83 / dashboard app - group 1 dashboard embeddable data grid are added when a cell filter is clicked

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
fleet 1.3MB 1.3MB +48.0B

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @1Copenut

@1Copenut
Copy link
Contributor Author

I've run the Flaky Test Runner a couple of times on flaky FTR suites to make sure I hadn't introduced issues. Both runs passed with 0 issues, and failures were outside the changeset I created. Going to go ahead and merge this PR.

@1Copenut 1Copenut merged commit a9b4fc8 into elastic:main Apr 30, 2024
20 checks passed
@1Copenut 1Copenut deleted the tpierce/security-integrations-headings branch April 30, 2024 20:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accessibility: cognition Accessibility issues including cognition, awareness, understanding backport:skip This commit does not require backporting release_note:skip Skip the PR/issue when compiling release notes Team:Fleet Team label for Observability Data Collection Fleet team v8.15.0 WCAG A
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants