Anchor link

Readers use them to skip long content and land on the right section. Authors expose anchors by giving headings or blocks stable ids, then linking to those ids from in-page navigation, tabs, or body copy. The address bar can also show a fragment when someone shares a link.

• Anchor navigation (concordia/components/anchor-navigation) builds a nav of #fragment links from the dialog.
• Tabs map buttons to #tab-id panels.
• Parsys (parsys.jsp, iparsys.jsp) can inject hidden <a name="..."> anchors derived from resource paths for deep links to components.

Content authors also add anchors by setting id on headings in RTE where the profile allows it.

• Long pages with clear sections (policies, FAQs, program details).
• Tabs and accordion targets when URL fragments should open a specific panel (behaviour varies by script).

• Cross-page navigation; use standard href paths.
• Replacing a proper heading structure; anchors supplement, not replace, headings.

Do

• Use short, unique ids (admissions-deadlines, not x7f3).
• Test keyboard focus: targets should move focus to focusable elements or headings with tabindex="-1" if required by policy.

Don't

• Don't duplicate id values on one page.