Visitar URL original
USWDS - Link: Update placement and allow for opt out · Issue #5942 · uswds/uswds · GitHub
Skip to content

USWDS - Link: Update placement and allow for opt out #5942

Open

Description

@mejiaj

Place label after link to follow W3C recommendation. Allow developers who have a custom implementation the option to easily remove label .

Originally suggested by @aduth in #5166 (comment)

Activity

  1. added
    Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.
    Role: DevDev expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.
    on May 29, 2024
  2. added
    Needs: DiscussionAn unresolved decision blocks progress. Name the decision; remove this label when decided.
    and removed
    Role: DevDev expertise is relevant. Project Active Role tracks ownership; this label is not an assignment.
    on May 30, 2024
  3. moved this from TBD to Needs refinement in USWDS Core Project Dataon May 30, 2024
  4. added
    Needs: ConfirmationReported behavior needs validation. Remove after recording reproduction or investigation results.
    and removed
    Needs: DiscussionAn unresolved decision blocks progress. Name the decision; remove this label when decided.
    on May 30, 2024
  5. brunerae commented on May 30, 2024

    @brunerae
    Contributor

    Passing this to the A11Y team (@amycole501 / @alex-hull ) to confirm if this is something you all think makes sense to pursue. Your action items:

    • Confirm if this ask is logical/something we want to pursue and leave a comment with your thoughts
    • Add a value to the weight field indicating how important this work would be/level of priority

    After you've done the above, please update the Issue by:

    If we want to pursue the work

    • Removing Needs: Confirmation label
    • Changing Active Role field from A11Y to Dev
    • Changing Status field from Needs refinement to Ready to schedule

    If don't want to pursue the work

    • Removing Needs: Confirmation label
    • Changing Active Role field from A11Y to Fed
    • Add label Status: will not pursue
    • Changing Status field from Needs refinement to Fed Final Review

    Thank you!

  6. removed
    Needs: ConfirmationReported behavior needs validation. Remove after recording reproduction or investigation results.
    on Jun 5, 2024
  7. moved this from Needs refinement to Ready to Schedule in USWDS Core Project Dataon Jun 5, 2024
  8. amycole501 commented on Jun 5, 2024

    @amycole501

    I agree that the "external link" or warning of opening in a new window needs to come after the link is announced to improve clarity. While the issue isn't a blocker for users, it is at least possibly confusing. Moving the announcement to the end of the link announcement will sound more like "Visit our website link name (link opens in a new window") which makes more sense to English speakers and users of English assistive tech.

  9. aduth commented on Jan 7, 2025

    @aduth
    Contributor

    Allow developers who have a custom implementation the option to easily remove label .

    To support this, and continuing my original comment's context of our needing to support multilingual labels, I wonder if the existing theme option could be expanded to support different value types, such as:

    • A string to override the default label (currently supported)
      • Example: $theme-external-link-sr-label-tab-new: "opens new tab"
    • A false value to disable the screen reader label
      • Example: $theme-external-link-sr-label-tab-new: false
    • A map of locale ➡️ label values, applied with [lang] selector
      • Example: $theme-external-link-sr-label-tab-new: ("en": "opens new tab", "es": "abrir nueva pestaña")

    Here's an example implementation: b5a332a...aduth:aduth-external-link-multilingual

    (Not opening a pull request yet since it doesn't resolve the label placement after link, which is more difficult to solve)

  10. removed their assignment
    on Sep 10, 2026
  11. added
    Type: SpikeA bounded investigation to answer a specific question; use native Task for the issue type.
    on Sep 10, 2026
  12. chandracarney commented on Sep 10, 2026

    @chandracarney
    Contributor

    In June, we discussed that this needs a quick further look. Here are our initial thoughts:

    • Needs research / verification / investigation by someone with accessibility expertise.
    • Possible light engineering to make the update, and a light review from another engineer.
  13. added theissue type on Sep 16, 2026
  14. added
    Package: LinkWork affecting Link. Apply only when this area helps route or find the issue.
    Type: ResearchResearch or audit work with a specific question and outcome; use native Task for the issue type.
    on Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Affects: Accessibility 🟡Affects access for disabled users or assistive tech. Record the barrier; not a severity score.Context: SassIssue is in SassPackage: LinkWork affecting Link. Apply only when this area helps route or find the issue.Type: ResearchResearch or audit work with a specific question and outcome; use native Task for the issue type.Type: SpikeA bounded investigation to answer a specific question; use native Task for the issue type.

    Type

    Projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions