Borders are Focus- Required for Accessibility!!
Hello Community,
In reference to the thread - Bug Update- July 09, 2020, all who mentioned it as Focus as part of Accessibility tools are right. It is not a bug but a required feature for accessibility.
The purpose of this is to ensure the focus indicator is clearly visible. The focus indicator is important for sighted people with mobility impairments.
Many of you might like to have a switch on/off button for it. So if you do not want it to be enabled for your profile, you could turn it off. Our team still working on accessibility and still more changes are in the process to make it more user friendly.
We will keep you updated with new improvements.
Thank you for your patience and support.
@ASilentObserver Is there a set goal for getting Arrowback for there room page I know some users got it back but some of us didn't
@SamuelFrancis I believe it is still in process of getting fixed for all Sam. I will pass the feedback to the team. Thank you for the reminder!
@ASilentObserver
Thank you for the update, Obs!
Thankyou for keeping updated.
@ASilentObserver
Thankyou thos accessability thong is super helpful just wish there were more options for tinting the screen colour.
Thankyou for all your doing
-Joy
@JoyIntoDarkness
Joy, are you referring to the ability to change contrast on screen so colours get inverted, etc. ?
I do not know if you've tried but, the Visual Toolkit available, by pressing the AudioEye button (the symbol of a human/4 colours on the bottom left/right of the screen) provides for that, and other visual assistance.
Here is a tutorial, on it's usage, if you need it.
@ASilentObserver No, it's a bug. I looked it up: :focus-visible
This selector is useful to provide a different focus indicator based on the users input modality (mouse vs. keyboard).
Focus does need to be visible for users who use the keyboard to navigate the page, or an assistive device that emulates the keyboard. This is because the user needs to know which element on the screen has keyboard focus.
Focus should not be visible for users who use a mouse or touch screen to navigate the page. This is because the user already knows which element they are pointing at.
For example, in 7 Cups' code, here is the code used for the white outline around the teacup icon etc. at the top of the page.
#navbar-main a:focus,#navbar-main button:focus{outline:3px solid #fff !important}You can see that this code uses :focus to specify when the outline is visible. This wrongly makes the outline visible to mouse users. The code should instead use :focus-visible to specify when the outline is visible. This would make the outline visible to keyboard users, but hide it from mouse users.
[I]f you have a piece of info, but its authenticity is uncertain, instead of spreading it further, it is better to verify it first. When incorrect info passed around without verifying, it can make the atmosphere uncomfortable in the community.
Charlie
@RarelyCharlie
The Keyboard Focus is already available under the AudioEye Visual toolkit (the accessibility icon on the left bottom of the page), and hence, adding it again for both Mouse and Keyboard users would be redundant, I believe.
Also, the AudioEye Visual Toolkit also has an option to enlarge the pointer, so you know where you're selecting, if that was a related issue.
If the reason for the border focus was caused by 7Cups' coding- I'd like to point out that the issues they're trying to address is already done by the AudioEye Visual Toolkit. If it was not, my post is of not much significance. I replied only because you used the words, " ...in 7 Cups' code..." that led me to believe 7Cups had included this code, and it was not an AudioEye enhancement.
@bouncySalamander26 That's correct, it's in 7 Cups' code. I blocked AudioEye, so I'm not seeing any AudioEye code.
But yes, that's a good point. If AudioEye already does this, why has 7 Cups done it again?
Charlie
@ASilentObserver
Thank you for letting us know.
