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

More context for copy and StackBlitz buttons for screen readers #1217

Open
julien-deramond opened this issue Apr 22, 2022 · 3 comments
Open
Assignees
Labels
👂 accessibility bootstrap-side Things to implement in Bootstrap first 📖 documentation Improvements or additions to documentation 🧩 enhancement v5

Comments

@julien-deramond
Copy link
Contributor

In our examples, we have a section where the corresponding source code is displayed (e.g. https://boosted.netlify.app/docs/5.1/components/accordion/#example). In this section, we can have up to two buttons to copy the source code in the clipboard and a try-it button that creates a reproduction environment in StackBlitz.

Those two buttons have no context for screen readers so they are displayed as a list of "Copy button", "Copy button", "Copy button", etc.

The purpose of this issue is to enhance this behavior to make them more accessible by providing some context for those buttons. It will probably have an impact on how the example shortcode is built.

It would be better to provide such an enhancement directly in Bootstrap to have their feedback as well.

@julien-deramond julien-deramond added v5 👂 accessibility 📖 documentation Improvements or additions to documentation bootstrap-side Things to implement in Bootstrap first 🧩 enhancement labels Apr 22, 2022
@MewenLeHo
Copy link
Contributor

@julien-deramond: is this issue still needed? Especially after twbs/bootstrap#37498

@julien-deramond
Copy link
Contributor Author

The idea at the time was to provide some context in the title to differenciate the copy buttons in the page (and StackBlitz edit buttons). Seems to be different than what's been done in the Bootstrap PR. Do you think it would bring some value for screen readers users? If not, you can close this issue.

@MewenLeHo
Copy link
Contributor

For screen readers users I think it's good.
But we may need it for users with others disabilities, like people using voice command for instance.
Any opinion @Aniort?

@MewenLeHo MewenLeHo self-assigned this Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
👂 accessibility bootstrap-side Things to implement in Bootstrap first 📖 documentation Improvements or additions to documentation 🧩 enhancement v5
Projects
None yet
Development

No branches or pull requests

2 participants