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

[Feature] Explore accessibility for category filters #192

Open
1 task done
isabelxklee opened this issue Feb 27, 2024 · 8 comments
Open
1 task done

[Feature] Explore accessibility for category filters #192

isabelxklee opened this issue Feb 27, 2024 · 8 comments
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work

Comments

@isabelxklee
Copy link

Problem

The current UX for category filters is not the most accessible for a couple reasons:

  1. When selected, the category title gets truncated to an abbreviation.
  2. To unselect a filter, the user must specifically click on a small "x" next to the category title (the category itself is not clickable).
  3. Selecting a filter hides the other options, making elements unnecessarily jump around the page.

Also see "Additional context" section for other, related issues about the category filters functionality.

Current UX:

Screen.Recording.2024-02-27.at.3.25.55.PM.mov

Description

I'm open to different ideas, but I think the best solution would be to use a more common category filter UX.

  1. Keep all the filter options visible, regardless of selection status.
  2. Use visual contrast to indicate which filters are selected.
  3. Make the entire filter be clickable, instead of a small target area.
  4. OPTIONAL: use more explicit language, like "remove filter" or "clear filters".

Example that I think works well from Thingtesting:
Screenshot 2024-02-26 at 10 26 16 PM

Alternatives

Open to suggestions!

Additional context

Related to Issue #81 and PR #180.

Implementation

  • I would be interested in implementing this feature.
@isabelxklee isabelxklee added ✨ goal: improvement Improvement to an existing feature 💻 aspect: code Concerns the software code in the repository 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work 🟩 priority: low Low priority and doesn't need to be rushed labels Feb 27, 2024
@isabelxklee
Copy link
Author

Heyo @possumbilities, I just created this issue! Let me know if you think there's anything else I should add. 👀

@aniketmdinde
Copy link

I would like to contribute to this issue. Can you assign it to me?

@isabelxklee
Copy link
Author

isabelxklee commented Mar 2, 2024

I would like to contribute to this issue. Can you assign it to me?

Please read the contribution guideline.

Here is also additional context from @TimidRobot:

Instead of asking for issues to be assigned, do the work and submit a pull request (PR). Even if multiple people submit PRs for the same issue, they can all list their own PRs on their application. It is the quality of work that is important, not whether it is merged.

@possumbilities
Copy link
Contributor

I've been thinking on this and here's something I'd like to add to the discussion. The lists of items vertically works because of how small everything is, and despite them being perhaps (and arguably) not the best UX, if we move to the "pill-style" buttons then those often work better horizontally in their flow (even if they line wrap).

That extra visual space might result in very long vertical lists, reducing the usability of the filters.

There may be solutions here, but its going to require thorough consideration before its something that's solid enough to build out.

@isabelxklee
Copy link
Author

@possumbilities That's a good point! I'm going to keep researching UX patterns that might be more appropriate for this context. I agree that the vertical lists can easily get too long, especially considering the length of the category names. 👀

@possumbilities possumbilities added the help wanted Open to participation from the community label Mar 8, 2024
@possumbilities
Copy link
Contributor

possumbilities commented Mar 8, 2024

Another solution worth exploring from this pending PR, that's similar in UX (but for tags):

@Cappybara12
Copy link

Improve list behavior and filter functionality to maintain list visibility when applying filters.

Additional context

Attaching a gif showing the enhanced list behavior and filter functionality in action. Here's my approach

All_CreativeCommonsResourceArchive-GoogleChrome2024-03-2015-00-41-ezgif com-video-to-gif-converter

@Murdock9803
Copy link
Member

Murdock9803 commented Mar 24, 2024

@possumbilities How about a 3 dropdowns - design for filtering of resources ? This will minimize the space taken, and also account for a better user experience. Please give your thoughts on this, as I have planned the designs and want to start working.
@everyone please give suggestions 🙌
Screenshot 2024-03-18 005453
The design looks clean and after a filter is selected, for example website, only website will display below the medium tab and can be easily unselected. Same goes for other tabs like topic and language.

The language dropdown will not be very large vertically, it will be as a CSS grid of 2 columns.

@possumbilities possumbilities added 🧹 status: ticket work required Needs more details before it can be worked on and removed 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work labels Aug 16, 2024
@TimidRobot TimidRobot added 🏁 status: ready for work Ready for work and removed 🧹 status: ticket work required Needs more details before it can be worked on labels Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💻 aspect: code Concerns the software code in the repository ✨ goal: improvement Improvement to an existing feature help wanted Open to participation from the community 🟩 priority: low Low priority and doesn't need to be rushed 🏁 status: ready for work Ready for work
Projects
Status: Backlog
Development

No branches or pull requests

6 participants