Closed brianalloyd closed 3 years ago
@brianalloyd What does "Review unauth portfolio research document" mean? Are you referring to https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/public-websites/how-we-work/research-opportunties.md? I'd like to reference the list of research questions that I'm compiling: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/public-websites/how-we-work/potential-research-for-unauth.md
@cindymerrill yes, that was the document, wasn't sure of title. Thanks for the follow up.
I've shared my high-level research idea with John, and he was supportive. The research plan is targeted to complete by April 9, which will be next sprint, not this one. So should this ticket be moved out of this sprint and into the next one, @brianalloyd ?
Started writing a research plan (only partway through): https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/public-websites/research/202104-baseline-wayfinding/research-plan.md
Finished first draft of research plan. Shared with Lauryl and got some feedback. Also shared with John, Meg, and Shawna. Waiting to see what feedback I get from them before sharing more widely.
Revised some of the research plan per feedback from Meg Peters. John shared it with the search team; no feedback from there. Will hear Shawna's feedback and discuss with her, John, and Meg on Thursday (4/15).
Revised research plan a bit with Shawna's feedback.
Revised to incorporate feedback from Shawna, Meg, and Lauryl. Shared with PMs, and Josh & Angela for their feedback. Plan to share with Lauren by the end of the day Friday to launch recruiting.
Revised to incorporate feedback from Josh and Angela. Plan to share with Lauren first thing on Monday morning to launch recruiting.
All done with Acceptance Criteria, so closing ticket.
Renamed ticket for clarity and reusability for cloning for future research studies
Issue Description
As part of the integration of the new researcher on the Unauth/PW crew a summary of projects and potential research opportunities was provide but not prioritized. Please review and propose first research project
Research Document for Reference
Acceptance Criteria
Appendix
Ensure your code changes are covered by E2E tests (expand)
- Add E2E tests if none exist for this addition/change. - Update existing E2E tests if this code will change functionality. - Include axe checks, including hidden contentRun axe checks using the Chrome or Firefox browser plugin (expand)
- Ensure no heading levels are skipped. - Ensure all buttons and labeled inputs use semantic HTML elements. - Ensure all buttons, labeled elements and images are identified using HTML semantic markers or ARIA roles. - Ensure form fields have clearly defined boundaries or outlines. - Ensure form fields do not use placeholder text. - Ensure form fields have highly visible and specific error states.Test for color contrast and color blindness issues (expand)
- All text has appropriate contrast.Zoom layouts to 400% at 1280px width (expand)
- Ensure readability and usability are supported when zoomed up to 400% at 1280px browser width - Ensure no content gets focused offscreen or is hidden from view.Test with 1 or 2 screen readers (expand)
- Ensure the page includes a skip navigation link. - Ensure all links are properly descriptive. - Ensure screen reader users can hear the text equivalent for each image conveying information. - Ensure screen reader users can hear the text equivalent for each image button. - Ensure screen reader users can hear labels and instructions for inputs. - Ensure purely decorative images are not announced by the screenreader.Navigate using the keyboard only (expand)
- Ensure all links (navigation, text and/or image), form controls and page functions can be reached with the tab key in a logical order. - Ensure all links (navigation, text and/or image), form controls and page functions can be triggered with the spacebar, enter key, or arrow keys. - Ensure all interactive elements can be reached with the tab key in a logical order - Ensure all interactive elements can be triggered with the spacebar, enter key, or arrow keys. - Ensure focus is always visible and appears in logical order. - Ensure each interactive element has visible focus state which appears in logical order.How to configure this issue
product support
,analytics-insights
,operations
,service-design
,tools-be
,tools-fe
)backend
,frontend
,devops
,design
,research
,product
,ia
,qa
,analytics
,contact center
,research
,accessibility
,content
)bug
,request
,discovery
,documentation
, etc.)