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

Add data-order to support the sorting of navigation buttons #53

Closed
kirsty-hames opened this issue Oct 19, 2022 · 1 comment · Fixed by #54
Closed

Add data-order to support the sorting of navigation buttons #53

kirsty-hames opened this issue Oct 19, 2022 · 1 comment · Fixed by #54

Comments

@kirsty-hames
Copy link
Contributor

For consistency with other navigation buttons, Visua11y should support data-order to meet AA accessibility adaptlearning/adapt-contrib-core#61

Unless all navigation buttons support data-order the display order won't be entirely configurable.

@kirsty-hames kirsty-hames self-assigned this Oct 19, 2022
github-actions bot pushed a commit that referenced this issue Jan 12, 2023
# 1.0.0 (2023-01-12)

### Breaking

* update theme bg image selector (fixes #59) (#61) ([d039d8d](d039d8d)), closes [#59](#59) [#61](#61)

### Fix

* Added release automation ([c295f6c](c295f6c))
* P ([a8e885a](a8e885a))
* Readability padding right override (fixes #57) ([bbce1f0](bbce1f0)), closes [#57](#57)
* Schema text updates (fixes #55) ([e89f13e](e89f13e)), closes [#55](#55)
* visually hide rather than remove images (#62) ([5272116](5272116)), closes [#62](#62)

### Separated

* contrast, opacity, animations, zoom, invert, background images and optical profiles ([22dbe99](22dbe99))

### Update

* Add data-order to support navigation sorting (fixes #53) (#54) ([0a4a6c1](0a4a6c1)), closes [#53](#53) [#54](#54)
@github-actions
Copy link

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant