You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to new functionality not yet included in the product? Please describe.
A clear and concise description of what the new feature will provide.
Is your feature request related to a problem or a change to existing functionality? Please describe.
Link color in the footer does not provide good contrast.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Change the footer background color and link colors to match current Emory Libraries' color scheme. This request does not include a full revamp of the footer.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or workarounds you've considered.
Status quo
How will this impact users?
A clear and concise description of how many and which types of users would benefit from this feature, or any who may be negatively impacted by the change.
Users interacting with links in the footer have difficulty reading the text.
Additional context
Add any other context or screenshots about the feature request here.
The ETD application was built in 2017 on a very short timeframe and soon after, the Libraries implemented a new style guide.
This request was discussed with Mark Bussey in an ETD meeting on 3/6/23 and the Emory team provides new colors, this could be addressed within our maintenance agreement.
Related request includes adding a new link to the footer.
The text was updated successfully, but these errors were encountered:
Is your feature request related to new functionality not yet included in the product? Please describe.
A clear and concise description of what the new feature will provide.
Is your feature request related to a problem or a change to existing functionality? Please describe.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or workarounds you've considered.
How will this impact users?
A clear and concise description of how many and which types of users would benefit from this feature, or any who may be negatively impacted by the change.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: