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

Further accessbility improvements to search result titles #2150

Closed
zackkrida opened this issue May 21, 2023 · 5 comments
Closed

Further accessbility improvements to search result titles #2150

zackkrida opened this issue May 21, 2023 · 5 comments
Labels
♿️ aspect: a11y Concerns related to the project's accessibility ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend 🧹 status: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback
Projects

Comments

@zackkrida
Copy link
Member

Problem

Currently search result titles announce the type of media (currently image or audio) and the title of a work. Visually, however, users are privy to much more information, including the CC licenses.

Description

We may want to announce what amounts to the full CC attribution for these works, including the license info and author name.

Alternatives

Conversely, this may be too much information for users and detract from the experience of moving through the results quickly to find a suitable image.

Additional context

@zackkrida zackkrida added 🚦 status: awaiting triage Has not been triaged & therefore, not ready for work ✨ goal: improvement Improvement to an existing user-facing feature labels May 21, 2023
@openverse-bot openverse-bot added this to Backlog in Openverse May 21, 2023
@dhruvkb
Copy link
Member

dhruvkb commented May 21, 2023

I am not remotely an accessibility expert but imo, the exact same amount of information as accessible to screen readers as to a person reading the screen directly. So while I'm pro-"adding more info to the SR text", I'm anti-"full attribution in the SR text".

@dhruvkb dhruvkb added 🟨 priority: medium Not blocking but should be addressed soon ♿️ aspect: a11y Concerns related to the project's accessibility 🧱 stack: frontend Related to the Nuxt frontend 💬 talk: discussion Open for discussions and feedback 🧹 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 May 21, 2023
@dhruvkb
Copy link
Member

dhruvkb commented May 21, 2023

Added the "discussion" and "ticket work required" labels till we finalise what the exact text should be.

@sarayourfriend
Copy link
Contributor

I agree with @dhruvkb. SR accessibility doesn't necessarily mean providing the exact same full context so long as there are other ways of obtaining the same information. @zackkrida Did you get this feedback from someone based on experience using the site from a screen reader? As Dhruv and you've both pointed out, we don't want to make the site harder to navigate for someone using a screen reader. Perhaps making license filters more readily accessible is the best way to make sure screen reader users know the context of specific results rather than fully describing the licenses on each result.

@zackkrida
Copy link
Member Author

I think we should add "{media} on Openverse" to the titles, we don't need to include any other information. Just the most basic amount of content to let you know you're visiting the page of a single, named work.

@zackkrida
Copy link
Member Author

I'm actually going to close this and create a separate issue for the problem described in this comment, which refers to single result page SEO titles. The original issue, I believe, was referring to the individual result titles on a search result page, and how they should be presented. In that case I think sharing the title is sufficient, and delving into the single result can be used to determine the specific license and suitability of the result for use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
♿️ aspect: a11y Concerns related to the project's accessibility ✨ goal: improvement Improvement to an existing user-facing feature 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: frontend Related to the Nuxt frontend 🧹 status: ticket work required Needs more details before it can be worked on 💬 talk: discussion Open for discussions and feedback
3 participants