LIBCIR-478. Added component for displaying MD-SOAR Accessibiity info#39
Merged
mohideen merged 4 commits intomdsoar-mainfrom Apr 7, 2026
Merged
LIBCIR-478. Added component for displaying MD-SOAR Accessibiity info#39mohideen merged 4 commits intomdsoar-mainfrom
mohideen merged 4 commits intomdsoar-mainfrom
Conversation
Added a "UmdAccessibilityComponent" (and related component, "UmdAccessibilityContentComponent"), modeled after the stock DSpace "PrivacyComponent (and "PrivacyContentComponent"). This page seemed to best fit within the "info" section of MD-SOAR, so modified the "info-routes.ts" and "info-routing-paths.ts", so that the page would be available at the "/info/mdsoar-accessibility" path. Note: The stock DSpace already has an "/info/accessibility" endpoint, which is used for managing accessibility settings. Text for the page was from https://docs.google.com/document/d/1DNrMGF3AI1EGSinB16tn_ytVLI5OUBxLq23OKxUo5-U (last modified on Mar 31, 2026) https://umd-dit.atlassian.net/browse/LIBCIR-478
Added an "Accessibility" link (placed after the "Browse By" dropdown) that links to the MD-SOAR accessibility information page. https://umd-dit.atlassian.net/browse/LIBCIR-478
Added an additional section to the "MdsoarAngularCustomization.md" document describing the MD-SOAR Accessibility Information page. https://umd-dit.atlassian.net/browse/LIBCIR-478
Made the following fixes based on recommendations from Perplexity AI and after verifying that they were valid: * Removed "UmdAccessibilityComponent" from "eager-theme.module.ts" because this file is for "eagerly loaded" components that are needed on first load, which the case for the Accessibility page * Fixed a missing "li" tag pair in the accessibility page HTML * Replaced hard-coded "/info/mdsoar-accessibility" path in "menu-resolver.service.ts" with "getUmdAccessibiltyPath()". Co-authored-by: Perplexity AI <[email protected]> https://umd-dit.atlassian.net/browse/LIBCIR-478
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
2 participants
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.
Added a "UmdAccessibilityComponent" (and related component, "UmdAccessibilityContentComponent"), modeled after the stock DSpace "PrivacyComponent (and "PrivacyContentComponent").
This page seemed to best fit within the "info" section of MD-SOAR, so modified the "info-routes.ts" and "info-routing-paths.ts", so that the page would be available at the "/info/mdsoar-accessibility" path.
Note: The stock DSpace already has an "/info/accessibility" endpoint, which is used for managing accessibility settings.
Text for the page was from https://docs.google.com/document/d/1DNrMGF3AI1EGSinB16tn_ytVLI5OUBxLq23OKxUo5-U (last modified on Mar 31, 2026)
https://umd-dit.atlassian.net/browse/LIBCIR-478