erinrwhite / stagingreview-mods

0 stars 0 forks source link

[Findability] User can't determine where a page is within the VA.gov website #13

Open erinrwhite opened 5 months ago

erinrwhite commented 5 months ago

This ticket was generated during the pilot process for the new VA.gov experience standards. Please tag @platform-governance-team-members on Slack if you need assistance interpreting this ticket.

Product Information

Team: Testing team Product: Testing product Feature: Testing feature

Findings details

VA.gov Experience Standard - issue: User can't determine where a page is within the VA.gov website. VA.gov Experience Standard - category: Findability Launch-blocking: Yes Collab Cycle Reviewer: @erinrwhite (IA)

Description

Page doesn't accurately represent where the application is within VA.gov. The first segment of the URL matches the current page's H1, but second segment ""PACT Act"" doesn't represent an actual part of VA.gov.</p> <h2>Recommended action</h2> <p>Similar to other form flows, I recommend updating the title to <code>[SLUG] | Veterans Affairs</code> which can be the same across all pages. Example: <code>Learn how the PACT Act may affect you | Veterans Affairs</code> (Note: the income limits tool, which is similar to this tool, does not follow this pattern but should.)</p> <h2>References</h2> <ul> <li><strong>WCAG Success Criteria:</strong> N/A</li> <li><strong>Modality:</strong> N/A</li> <li><strong>Design System Component:</strong> N/A</li> <li><strong>Design System Pattern:</strong> N/A</li> <li><strong>Content Style Guide:</strong> <a rel="noreferrer nofollow" target="_blank" href="https://design.va.gov/content-style-guide/page-titles-and-section-titles">Page titles and section titles</a></li> <li><strong>Context:</strong> N/A</li> <li><strong>Accessibility Defect Severity:</strong> N/A</li> </ul> <hr /> <h3>Next Steps for the VFS Team</h3> <ul> <li>[ ] <strong>Questions?</strong> For the most timely response, comment on Slack in your team channel tagging <code>@platform-governance-team-members</code> with any questions or to get help validating the issue.</li> <li>[ ] <strong>Ticket ownership:</strong> Platform OCTO leadership asks that we document all issues we identify. If you believe that this issue is out of scope or not your team's responsibility, it is still your responsibility to resolve the issue. Please comment on Slack in your team channel tagging <code>@platform-governance-team-members</code>, providing an explanation and who you believe is responsible. Governance team will research and follow up.</li> <li>[ ] <strong>Close this ticket</strong> when the issue has been resolved or validated by your Product Owner.</li> </ul> </div> </div> <div class="page-bar-simple"> </div> <div class="footer"> <ul class="body"> <li>© <script> document.write(new Date().getFullYear()) </script> Githubissues.</li> <li>Githubissues is a development platform for aggregating issues.</li> </ul> </div> <script src="https://cdn.jsdelivr.net/npm/jquery@3.5.1/dist/jquery.min.js"></script> <script src="/githubissues/assets/js.js"></script> <script src="/githubissues/assets/markdown.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/highlight.min.js"></script> <script src="https://cdn.jsdelivr.net/gh/highlightjs/cdn-release@11.4.0/build/languages/go.min.js"></script> <script> hljs.highlightAll(); </script> </body> </html>