Tested accessibility fix for CE setup wizard - contributor needed

Hi

This is a focused development follow-up to my earlier Installation & Booting thread. The cause has now been identified, a small XML change has been tested successfully on CoreELEC 22 Amlogic-NO, and I am seeking a contributor who can review the change and submit it as a GitHub pull request.

RE: my original thread:

Could this accessibility fix now be taken forward as a pull request for CoreELEC 22 / Amlogic-NO?

The current coreelec-22 version of:

skins/Default/1080i/service-CoreELEC-Settings-wizard.xml

still contains the explicit texturefocus and texturenofocus overrides on:

  • buttons 1401 and 1402

  • radio buttons 1406 and 1407 for SSH and Samba

  • navigation buttons 1500 and 1501

Removing those two texture lines from the relevant controls allowed the skin’s normal button styling to be used and, in my testing, made the focused and unfocused states clearly distinguishable. I tested this on an Amlogic-NO CoreELEC 22 nightly on an Odroid N2+, including the Previous/Next buttons and the SSH/Samba options.

I appreciate the concern previously raised that removing the textures might make some controls appear more like plain text because the texture also provides the button boundary. In my testing the controls remained understandable, while the improvement in identifying keyboard/remote focus was substantial. If an explicit replacement texture is preferred, the important accessibility requirement is still that the focused state has a strong, readily perceptible contrast rather than relying on a faint outline or a small difference in colour.

@emveepee, you previously said that you might be able to submit a PR if the CoreELEC team would accept it. Would you or another contributor be willing to open a pull request against coreelec-22 so that the change can be reviewed properly?

I am still happy to test a PR branch or a build containing the proposed changes.

PS If this topic belongs elsewhere, please move it rather than close it. I have tried to identify the most appropriate development category.

You will need to open a PR with your changes so we check it by ourselves.

Tx - I have now opened a pull request containing the XML changes I tested:

As I am not a developer, I have presented it as a tested accessibility improvement for review rather than assuming that removing the texture overrides is necessarily the final preferred implementation.