Closed Katherine-Osos closed 2 months ago
@rileyorr That's a great callout! Right now on get.gov, I think only "sign in" links open in a new tab, and all others open in the same tab. So I followed that pattern for consistency. But do you mind creating a ticket to come up with a better linking strategy that aligns with accessibility best practices?
@Katherine-Osos should a linking strategy go in https://github.com/cisagov/manage.get.gov/issues/1917?
Those are great points, thank you! I did some digging in the Google Drive and discovered we have a .gov content style guide with a section about links . If this is an actively used document I think it makes sense to have a ticket to update the linking guidelines in that document. Since the accessibility plan is a source of truth of how accessibility is incorporated into the design and development process I'd suggest we include a content section that links to that content style guide, especially since there's also a section in that document about plain language guidelines.
Let me know what y'all think! I'm happy to spin up the ticket and connect it to https://github.com/cisagov/manage.get.gov/issues/1917 if that works.
Sounds great to me, @rileyorr! I defer to @Katherine-Osos.
Agreed - go ahead and create a new ticket, @rileyorr. And thanks for connecting all the pieces!
Thank you both! I've created the ticket here: https://github.com/cisagov/manage.get.gov/issues/2107
Ticket
Resolves #274
Changes
Updated content within the FAQ for this question: Why don’t I see my domain when I sign in to the registrar?
Updates should match text in this Google Doc.
Review updates
You can review the updates at this link.