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

Sympa Accessibility Issue - 15 - No clear visual focus indicator when accessing elements by keyboard. #1744

Closed
rm1-uiuc opened this issue Nov 28, 2023 · 6 comments · Fixed by #1756
Labels
bug layout WWSympa web design

Comments

@rm1-uiuc
Copy link

The University of Illinois at Urbana-Champaign, Technology Services Accessibility Testing team conducted an Accessibility Review of Sympa on September 25, 2023 and found 26 issues that need to be fixed to make the interface accessible for visual impaired users.

Version

6.2.72

Installation method

Source Package

Expected behavior

Using a Screen Reader, there needs to be a clear visual focus indicator when access elements by keyboard.

Actual behavior

There is no clear visual focus indicator when accessing elements by keyboard. Users with poor vision would not understand where the current focus is. In the screenshot below, my current focus is on word prixlist, but since it doesn’t have a focused box/border around the element, it is not distinguishable.

WCAG Level AA 2.4.7 Focus Visible)

image

Fig 17 Focus indictor issue.

Steps to reproduce

Sympa Accessibility Issue -15 was determined by manual functional testing performed by the user navigating with keyboard only or using assistive technology such as screen reader. See attached review for more info on specific location in interface.

Additional information

Attached is the Accessibility Review conducted on Sept 25,2023
Tech Services Review - Accessibility Evaluation Report for Sympa.pdf

@rm1-uiuc rm1-uiuc added the bug label Nov 28, 2023
@ikedas ikedas added the layout WWSympa web design label Nov 28, 2023
@ldidry
Copy link
Contributor

ldidry commented Nov 29, 2023

I quickly tried some CSS rules:

#sympa-top-bar menu .menu li:not(.active) > a:not(.button):focus {
    background: #6A5687 !important;
}
a:focus {
    border-bottom-style: solid;
    border-bottom-width: 1px;
}

@ikedas @racke, could you test them and tell what do you think of them?

Same question for @rm1-uiuc if you can test them with a Sympa.

@ikedas
Copy link
Member

ikedas commented Nov 29, 2023

I have a question: What style should we adopt for "focus indicator"?

  • G149 and so on provide some examples.
  • G165 suggests that default focus indicator for the platform should be used.
  • G195 suggests that author-supplied, visible focus indicator should be used.

@ikedas
Copy link
Member

ikedas commented Nov 29, 2023

I realized that removing these lines recovers the default focus indicator:

a:focus {
outline: 0;
text-decoration: none;
}

With Chrome it works as below:
image

@rm1-uiuc
Copy link
Author

rm1-uiuc commented Dec 5, 2023

The default focus indicator should not be relied upon, as the default indicator in some browsers is not easily perceivable by some users with visual impairments.

@ikedas
Copy link
Member

ikedas commented Dec 6, 2023

The default focus indicator should not be relied upon, as the default indicator in some browsers is not easily perceivable by some users with visual impairments.

Could you please present an easily recognizable one across browsers? I rather think that the arbitrary focus indicator designs that, instead of the default one, vary from application to application will confuse users.

@ikedas
Copy link
Member

ikedas commented Dec 15, 2023

If no good alternative can be found soon, we'd be better to adopt the default one for the time being.

ikedas added a commit that referenced this issue Feb 17, 2024
♿ — WWSympa: No visual focus indicator when accessing elements by keyboard (#1744)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug layout WWSympa web design
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants