Openverse is a search engine for openly-licensed media.
The OpenverseOpenverseOpenverse is a search engine for openly-licensed media, including photos, audio, and video. Openverse is also the name for the collection of related code repositories that make up the project. find Openverse at https://openverse.org. team builds the Openverse Catalog, APIAPIAn API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways., and front-end application, as well as integrations between Openverse and WordPress. Follow this site for updates and discussions on the project.
The OpenverseOpenverseOpenverse is a search engine for openly-licensed media, including photos, audio, and video. Openverse is also the name for the collection of related code repositories that make up the project. find Openverse at https://openverse.org. Biweekly update is an every-two-weeks summary of the work completed by the Openverse team.
This period we added +14,778,368 new images and +4,484 new audio files. A majority of these images came from our new iNaturalist integration, written by community contributor @beccawidom. We’ve so far only ingested a small subset of their collection, but have added some remarkable images to Openverse as a result. We have open PRs to make some optimizations to the iNaturalist DAG moving forward.
Call for a11yAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) testing on our new audio track
At the end of last week we merged a substantial PR from @dhruvkb which makes major accessibilityAccessibilityAccessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) and usability improvements to our audio track component. Tracks can be played/paused, seeked (bonus tip: you can do a faster seek by pressing Shift+left/right arrows), and navigated to all from a single root element. Previously, the component required navigating to individual controls to perform a specific action. We’ve also added a helpful snackbar when navigating by keyboard that announces the available controls to users. Here’s a quick video of how it works:
Which you can compare to the previous behavior, along with observing my failed attempts to seek the audio tracks while focused on the play/pause buttons:
While we’ve done local testing in MacOS with Safari and VoiceOver, and with NVDA on Windows, we are not daily screen reader users. Frankly, we’ve also found reference implementations of audio players from SoundCloud, as an example, to be woefully inadequate in their accessibility. We would love if any regular screen reader users or general #accessibility experts could take a look at our staging audio results page and give us some feedback. We’ll be posting a full request to our Make blog later this week.
Thanks to smart diagnostic work and memory profiling from @sarayourfriend and a rapid, high-quality refactor from @olgabulat, we were able to mitigate our frontend memory leak and close the project ahead of schedule.
It’s the last day to leave your thoughts on our team priorities for the month; we’ve had a lively discussion with several community members chiming in. Let us know what you’d like to see us work on!
We’re making steady progress on our Catalog milestone to refactor all of our existing provider scripts. This standardization will make making bulk changes to provider script behavior a breeze, and allow us to make optimizations and improvements centrally that will improve the data quality and performance of all of our provider scripts.