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

Fix Issue #1082 added lang attribute for language specific pronunciation #1173

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

thattonBL
Copy link
Contributor

  • lang attribute added to parent div of all UV elements which should cascade down

…enable language specific pronunciation

- lang attribute added to parent div of all UV elements which should cascade down
Copy link

vercel bot commented Oct 24, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
universalviewer ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 24, 2024 11:58am

@demiankatz
Copy link
Contributor

Thanks, @thattonBL, this seems to be working as expected (in terms of adding the lang attribute -- the interaction of this attribute with various screen readers is beyond my ability to test). Before we merge this, though, I wonder if we should add better lang attribute support to iiif-metadata-component, since the metadata in that panel may be a different language from the interface, and those elements do not currently appear to be labeled. I think we have enough data in the panel to label each value, so we should probably start doing that. I don't have time to investigate it just yet, but it may not be too difficult when time permits!

@LanieOkorodudu
Copy link
Collaborator

@thattonBL and @demiankatz, I've tested this fix on the Vercel app, verifying the fix in Dev Tools and comparing it with the dev branch. All changes function as expected. I validated the lang attribute across all available languages, confirming it is correctly applied and behaving as intended.

@demiankatz
Copy link
Contributor

demiankatz commented Oct 28, 2024

So I think the question now is whether we merge this as-is (incremental progress) or wait until some more nuance has been added. Do you have an opinion, @scoutb-cogapp?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Community Sprint IN TESTING
Development

Successfully merging this pull request may close these issues.

4 participants