Localization usually involves the translated replacement of strings by the host app. We can localize (aka, "translate") menu items in the LuxMenuBar because it allows us to add custom menu items in the host application. We should allow the same kind of customization in the LuxUniversityFooter so that we can translate the policy link text. The current hard coded values should be set as the default. Right now it is not exposed to the host app for modification.
Acceptance criteria
[ ] If this change touches any of the files referenced in .rubocop_todo.yml create a new ticket to address the rubocop todo.
[ ] I can successfully use this feature with Voice Over in Safari.
[ ] I have checked this feature using one of the following browser extensions and confirmed that it does not add any level A or level AA issues:
axe dev tools
Lighthouse
Wave
[ ] ...
Implementation notes, if any
The LuxUniversityFooter should be able to receive a prop that is an array of objects with two values, the link-text and link-url.
User story
Localization usually involves the translated replacement of strings by the host app. We can localize (aka, "translate") menu items in the LuxMenuBar because it allows us to add custom menu items in the host application. We should allow the same kind of customization in the LuxUniversityFooter so that we can translate the policy link text. The current hard coded values should be set as the default. Right now it is not exposed to the host app for modification.
Acceptance criteria
.rubocop_todo.yml
create a new ticket to address the rubocop todo.Implementation notes, if any
The LuxUniversityFooter should be able to receive a prop that is an array of objects with two values, the
link-text
andlink-url
.So it would look something like this in HTML: