You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It only is an issue displayed in the FF a11y tree. Axe nor Chrome dev tools do show anything about it.
There are two issues, the yellow and the red:
The red is cause by the usage of :after, which is again implemented via buttonFocusRing.
While the yellow is caused by outline: none;
Both are only throwing, as long as the code is wrapped inside :focus-visible (@include focus-visible). When using @include focus, the issue is not present anymore.
The code above is inside button--tertiary.scss.
I assume that it is not a real issue. But to be sure, we should check with VoiceOver and NVDA. But my assumption is that it reports a potential "visual" issue.
The text was updated successfully, but these errors were encountered:
As seen above:
It only is an issue displayed in the FF a11y tree. Axe nor Chrome dev tools do show anything about it.
There are two issues, the yellow and the red:
:after
, which is again implemented viabuttonFocusRing
.outline: none;
Both are only throwing, as long as the code is wrapped inside
:focus-visible
(@include focus-visible
). When using@include focus
, the issue is not present anymore.The code above is inside
button--tertiary.scss
.I assume that it is not a real issue. But to be sure, we should check with VoiceOver and NVDA. But my assumption is that it reports a potential "visual" issue.
The text was updated successfully, but these errors were encountered: