Skip to content

Conversation

@brianteeman
Copy link
Contributor

@brianteeman brianteeman commented Mar 24, 2024

Updated to v6
adds some new functions

  • update to latest library
  • increase/decrease line height (disable until/if fixed upstream)
  • disable animations (NEW)
  • default emoji icon no longer skewed
  • link to optional accessibility statement (NEW)
  • dark mode
  • Angie icon set (https://github.com/angieradtke/Accessibility-plugin-icons)
  • Auto(partial)hide icon and expand on focus
  • extract css to external file to allow greater customisation
  • add position option
  • add custom function to use open dyslexie font leave for another day
  • translate "hotkey"

Still to do

Working with upstream to resolve multiple bugs

Testing Instructions

Actual result BEFORE applying this Pull Request

Expected result AFTER applying this Pull Request

Link to documentations

Please select:

  • Documentation link for docs.joomla.org:

  • No documentation changes for docs.joomla.org needed

  • Pull Request link for manual.joomla.org:

  • No documentation changes for manual.joomla.org needed

adds some new functions
[x] increase/decrease line height
[x] disable animations
[x] default emoji icon no longer skewed
[ ] link to optional accessibility statement
[ ] dark mode
[ ] Angie icon set
@joomla-cms-bot joomla-cms-bot added Language Change This is for Translators NPM Resource Changed This Pull Request can't be tested by Patchtester PR-5.1-dev labels Mar 24, 2024
@Quy
Copy link
Contributor

Quy commented Apr 7, 2024

Can you please add #39102 to the to-do list?

@HLeithner
Copy link
Member

This pull request has been automatically rebased to 5.2-dev.

@HLeithner HLeithner changed the title wip Update accessibility toolbar [5.2] wip Update accessibility toolbar Apr 24, 2024
@brianteeman
Copy link
Contributor Author

Allowing User to insert JS in backed, is kind of the same as allowing User insert PHP in backend.

Doh - silly me

@brianteeman
Copy link
Contributor Author

Since I started this PR upstream has completely changed (again)

It is now possible to create our own ui for the toolbar instead of the hacky solutions that were previously available

See the Custom Styling section https://ranbuch.github.io/accessibility/site/

@brianteeman
Copy link
Contributor Author

Note: The icons from Angie will need to be adjusted if we want to use them as an icon font (doesnt support multiple colors/shades) although I guess if the latest upstream changes are used to create our own UI for the toolbar then svg could be used

@drmenzelit
Copy link
Contributor

Doing some tests today. The hotkeys work for me, but ctrl+alt+q (animations) in Chrome but not in Firefox
ctrl+alt+r activate the reading guide an opens something from my graphic card too, but that is something specific from my PC

@brianteeman
Copy link
Contributor Author

yeah the hotkeys are weird. No idea what to do there

@drmenzelit
Copy link
Contributor

grafik
grafik

IBM Equal Access Accessibility Checker and in the Firefox Accessibility tab I get some errors / things to review... can we do something here?

@brianteeman
Copy link
Contributor Author

As you said you didnt want to create our own ui these are both upstream issues to resolve.

@brianteeman brianteeman deleted the accessibility branch June 27, 2024 07:04
@brianteeman brianteeman restored the accessibility branch July 29, 2024 07:38
@brianteeman
Copy link
Contributor Author

i think it is probably better to use the fontawesome web asset than the icons generated by angie

@chmst
Copy link
Contributor

chmst commented May 7, 2025

My vision is fontawesome icons as default but an option for custom icons.

@brianteeman
Copy link
Contributor Author

dont be confused with the icons for the toolbar actions and the icon for the button

@LadySolveig
Copy link
Contributor

Just for reference, I have submitted a PR upstream for the tabindex issue ranbuch/accessibility#87 PR ranbuch/accessibility#86

@brianteeman
Copy link
Contributor Author

I gave up looking at this due to the complete lack of any communication from the accessibility team

@LadySolveig
Copy link
Contributor

@brianteeman would you mind reopening this PR? So that hopefully we can bring the new version into 5.4

@brianteeman
Copy link
Contributor Author

It cant be re-opened as the 5.2-dev branch has been deleted here so github wont let me.

While I was working on it I discovered loads of bugs which he fixed but it really requires a rewrite of the plugin to be able to use the icons the way we want to. The implementation that ranbuch did for non-material icons is a pia

@LadySolveig
Copy link
Contributor

LadySolveig commented May 14, 2025

Do you want to open a new one or should I do it? Would really like to work with you on this.

@brianteeman
Copy link
Contributor Author

I gave up looking at this due to the complete lack of any communication from the accessibility team

Do as you wish. I won't waste any more if my time on it as the accessibility team clearly are not interested

@LadySolveig
Copy link
Contributor

Thank you, then I am pleased to build on the work you have already done.

@brianteeman brianteeman deleted the accessibility branch May 14, 2025 22:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Feature Language Change This is for Translators NPM Resource Changed This Pull Request can't be tested by Patchtester

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants