Repository navigation
DRYD-2178: Accessibility > Resolve Redundant Title Alerts - #11
Merged
Merged
Conversation
mikejritter
approved these changes
Oct 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this do?
Removes redundant
titleattribute from Table cell and header. react-virtualized adds atitleattribute whenever the passed label is a string. So the title always duplicated the visible text. The changes are:cellRenderer, wrapcellDatain a fragment so that it stops being a plain stringheaderRendererwithout thetitleWhy are we doing this? (with JIRA link)
https://collectionspace.atlassian.net/browse/DRYD-2178. A redundant
titleattribute triggers a WAVE a11y alert.How should this be tested? Do these changes have associated tests?
Unit tests have been added
For manual test:
"cspace-layout": "file:../cspace-layout.js",Dependencies for merging? Releasing to production?
Publish a patch release after merging
Has the application documentation been updated for these changes?
Changelog has been updated
Did someone actually run this code to verify it works?
@spirosdi ran it locally