-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Challenge Portal Header #1362
Comments
Work progress document: https://docs.google.com/document/d/11blju-lsqhzP4RlJ5f7vkR39q1eXFjnybFXkVeb-JjE/edit?usp=sharing |
Work done:
Notes: Due to a new branching instruction - a new branch was recreated from eval-main in order to deploy the feature into Eval version. Previous branches were deleted or archived. |
@jairoanaya Same request as in other user stories, please check the Definition of Done list. |
@r-bartlett-gsa definition of done addressed. Regarding changing the background could you confirm it should look like the following screenshot: I confirm I replicated the unexpected responsive behavior. Reviewing the issue in detail. Expect to provide additional inputs. |
Thank you @jairoanaya! I confirm the background color in your comment above. |
@r-bartlett-gsa after reviewing this issue I found the following: The reported problem occurs because an internal element is not responsive as shown in the following picture. This issue is expected to be resolved (by itself) by implementing #1388. I suggest waiting for the implementation of the 'Manager's dashboard.' Do you agree? |
@jairoanaya Sounds like a plan. Let's wait until #1388 is completed and reassess then. Thank you! |
@r-bartlett-gsa I confirm the background color has been changed (on the logged in state), please review if the changes satisfy the acceptance criteria. |
Hi @jairoanaya and @r-bartlett-gsa , in the screenshots from wireframes as well as the mobile responsive view, the logout button is white. On the desktop view, the button is blue. I'm pinging @mhotch24 for responsive and a11y testing. |
@jairoanaya and @TCKapGrp No changes to button colors and styles are needed at this time. The consistency of button colors and styles across all apps will be addressed as part of fit & finish updates at a later time. |
Usability Findings:
Feature Accessibility Findings:
|
@jairoanaya Please address the following accessibility issue by updating header nav button aria labels so they match the actual label text:
|
Context: for this feature I combined the header from Challenge.gov and eval platform. I have the following questions: Switch Task does not have any function, still implementing the button? @r-bartlett-gsa changing the color for logout button requires a minimum effort and can be done on this usability feedback, should I include it now or wait for fit & finish? |
@jairoanaya Please do not implement Switch Task button and do not update the current Logout button at this time. These items will be updated at a later time, consistently across all apps. Please update aria labels so they meet A11y requirements (even if it does not match/follow eval) |
@r-bartlett-gsa @mhotch24 the following feedback has been implemented and deployed to https://challenge-portal-eval-dev.app.cloud.gov/
|
Note: This work needs to be deployed to challenge portal eval dev environment (challenge_gov repo > eval main branch)
User Story
As a site user with challenge manager or public solver roles, in order to build my trust using challenge.gov site, I would like to see consistent branding and styling from any page of the site.
Acceptance criteria:
Tasks:
Definition of Done
Doing (dev team)
- [ ] Automated testing has been added or updated in response to changes in this PR- [ ] Database changes have been peer reviewed for index changes and performance bottlenecks- [ ] Automate accessibility tests passed- [ ] Feature toggles if appropriateStaging
Deploy to production (production-like environment for eval capability) (dev team)Production
User and security documentation has been reviewed for necessary updates (Renata/Tracy/Dev team)The text was updated successfully, but these errors were encountered: