Why WordPress Themes Require Underlines on Links

Why WordPress Themes Require Underlines on Links 🔗 **Source:** [Why WordPress Themes Require Underlines on Links](https://www.joedolson.com/2025/10/why-wordpress-themes-require-underlines-on-links/) > [!note]+ Document Notes > tags: [WordPress, Accessibility, Themes] > author: Joe Dolson > source: joedolson.com > reference: [https://www.joedolson.com/2025/10/why-wordpress-themes-require-underlines-on-links/] > date created: 2025-10-11 00:00 > > # 🏷️ Title: Why WordPress Themes Require Underlines on Links >  ## 🧭 Table of Contents - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🗒️ Notes](#️-notes) - [📚 References](#-references) - [🗣️ Paraphrase](#️-paraphrase) - [📰 Newsletter](#-newsletter) - [✅ Action Items](#-action-items) - [🧪 Hypotheses](#-hypotheses) - [📊 Methodology](#-methodology) - [❓ Questions](#-questions) - [🔮 Future Research](#-future-research) - [💡 Implications](#-implications) - [🧠 Learning Styles Assessment](#-learning-styles-assessment) - [📊 Accessibility Assessment](#-accessibility-assessment) - [🌍 DEIB Assessment](#-deib-assessment) - [✅ Logical Validity](#-logical-validity) - [🛡️ DARVO Analysis](#-darvo-analysis) - [🎯 Conclusion](#-conclusion) ### 🔗 References - Include links cited in or relevant to the article. ## 📝 Summary - What happened: The author responds to a critique of WordPress’s rule that theme defaults must show underlined links. - Why it matters: Default underlines are easy to test and universally recognized; alternatives raise review complexity and risk inaccessible defaults. - Key stakeholders: Theme developers, theme reviewers, WordPress users (especially those relying on accessibility cues), accessibility leads. - Risks and tradeoffs: Flexibility vs. testability; innovation vs. consistency; reviewer time vs. accessibility assurance. - Bottom line: Keep underlines as the default; allow alternate, WCAG-conforming styles as optional, ideally with third‑party verification. ## 📖 Main Content - Core arguments: - Defaults vs. options: “By default WordPress themes have to have underlined links. That doesn’t mean that a theme can’t have alternate styles.” - Testability: Underlines are trivial to verify; alternatives (bold+color, background badges, icons, combos) require nuanced, time-consuming checks. - Reviewer bandwidth: Human time is the bottleneck; guidelines must remain simple to assess reliably by non-experts. - Universality: Underlines are the most widely recognized indicator of a link. - Context/definitions: - WCAG: Standards for web accessibility; color contrast and non-color indicators are recurrent concerns. - Theme Review: Largely manual, volunteer-driven, thus favors low-ambiguity checks. - Uncertainties/contested: - Whether a border-style “underline” counts if it’s part of a full border. - Degree of reviewer latitude to accept principle-aligned exceptions. ### 🗒️ Notes - “The WordPress theme requirements are about defaults.” - Alternatives can exist as user-selectable styles; default must be clearly a link. - Testing burden increases with color layers, iconography, and editor color changes. - Icons lack universal recognition and can fail to load; still may meet WCAG but weaker. - Combination treatments can pass if underline is present; ambiguity with multi-side borders. - The real blocker: reviewer time; underlines make passes fast and reliable. - Openness to exceptions if backed by strong third‑party verification. - Preference: guidelines testable “by non-experts with a relatively low error threshold.” ## 📚 References - WCAG 2.2 Overview (W3C): https://www.w3.org/WAI/standards-guidelines/wcag/ - Understanding Non-text Contrast (W3C): https://www.w3.org/WAI/WCAG22/Understanding/non-text-contrast.html - WP Accessibility Day 2023 — Jonathan Whiting, “Understanding Color and Contrast Requirements in WCAG 2”: https://www.wpaccessibility.day/ - Post Status (community context): https://poststatus.com/ ## 🗣️ Paraphrase - Paragraph A: WordPress requires underlined links as the default to keep reviews simple and reliable; themes can still offer other link styles as options. - Paragraph B: Many creative link treatments can satisfy WCAG, but they demand far more testing and are less universally recognized than an underline; exceptions should come with third‑party validation. ## 📰 Newsletter - This week in WordPress accessibility: Joe Dolson explains why default underlined links remain a must in themes—speedy, reliable reviews and universal recognition win out. Alternatives? Sure, but make them optional and WCAG-solid. If you’re experimenting with bold+color or background badges, revisit color contrast in the editor and focus states. Recommended watch: Jonathan Whiting’s talk on WCAG color/contrast. Building award-winning accessibility? Start with defaults users instantly understand—and back exceptions with evidence. ## ✅ Action Items #### DevRel - Publish examples of WCAG-conforming alternate link styles with testing notes and code. #### OSPO - Define policy for third‑party accessibility verification acceptable for theme exceptions. #### Community - Run a contrast-testing sprint for popular alt link patterns across themes. #### WordPress - Core: Clarify guidance on border-bottom vs. full border as an “underline.” - Core Performance: Ensure alt styles don’t regress contrast in dark/light modes. - Core AI: Prototype linters suggesting non-color link indicators. - Core Program Team: Document reviewer latitude criteria for exceptions. - Mobile: Validate link affordances at large text sizes and dynamic type. - Playground: Add link-style contrast test scenarios. - Community: Share a11y office hours focused on link affordances. - Training: Create a lesson on link recognition and WCAG indicators. - Marketing: Promote “defaults first” a11y best practices. - Support: Add KB on troubleshooting link visibility. - Design: Provide tokens for underline thickness/offset and focus styles. - Documentation: Examples-first page: “Accessible link styles.” - Photos: N/A - TV: Caption segments on link a11y demos. - Polyglots: Note translations for “link” icon labels/tooltips. - Accessibility: Maintain an issues heatmap for link affordance failures. - Meta: Track theme review time per link-style pattern. - CLI: Add scaffold with accessible link CSS defaults. - Hosting: Include a11y scans in default checks. - Tide: Flag themes whose default links lack non-color cues. - Openverse: N/A - Themes: Provide lints for contrast and underline-on-default. - Plugins: Offer optional link-style packs with built-in tests. #### The WPOCC - Fund third‑party audits for innovative, WCAG-conforming link designs. ### FAIR - Require provenance and signatures on third‑party a11y verifications; publish exception criteria. ## 🧪 Hypotheses - Underlined default links reduce reviewer time versus color/weight/icon alternatives. - Users recognize underlined links faster than icon-annotated links at equal contrast. - Editor color changes increase failure rates for bold+color link patterns. - Reviewer error rates rise when link defaults rely on color contrast alone. ### 📊 Methodology - Time-and-motion studies of theme reviews across link patterns. - Usability tests (first-click time, error) comparing underline vs. icon vs. bg-badge. - Automated and manual contrast checks under theme/editor permutations. - Inter-rater reliability analysis for reviewer decisions on exceptions. ### ❓ Questions - What minimal criteria would allow safe, non-underline defaults? - Can we standardize tokens to keep alt styles reliably accessible? - Would a verification marketplace meaningfully offload reviewer time? ### 🔮 Future Research - Cross-locale studies on icon/link symbol recognition. - Robust heuristics for “underline equivalence” (e.g., border semantics). ### 💡 Implications - Practice: Ship underlines by default; gate alt styles behind checks. - Policy: Allow exceptions with third‑party verification and documented test scope. - Security: Reduce spoofed/indistinguishable links via non-color cues. - Education: Emphasize editor interaction with link styling. - Funding: Support audits for innovative but accessible patterns. ### 🧠 Learning Styles Assessment - Reading level: Flesch–Kincaid Grade ≈ 10–11. #### 👀 Visual learners - Present: Clear examples by description; talk reference. - Improve: Before/after link-style screengrabs with contrast values. #### 🔊 Aural learners - Present: Talk recommendation. - Improve: 3-minute audio summary of arguments. #### 🗣️ Verbal learners - Present: Definitions and principled reasoning. - Improve: Glossary of link affordance terms. #### 🧩 Kinesthetic learners - Present: N/A. - Improve: Sandbox to toggle link styles and run contrast checks. #### 🧠 Logical learners - Present: Testability argument; stepwise checks. - Improve: Decision tree for approving exceptions. #### 🧑‍🤝‍🧑 Social learners - Present: Community context (Post Status). - Improve: Guided discussion prompts for meetups. #### 🧘‍♀️ Solitary learners - Present: Concise, rationale-driven text. - Improve: Self-check quiz on WCAG link cues. #### 🌿 Naturalistic learners - Present: N/A. - Improve: Lifecycle framing on maintenance cost of alt styles. ### 📊 Accessibility Assessment #### Screen reader semantics - Present: Headings and structure implied. - Improve: Ensure code examples include accessible names if added. #### Keyboard navigation - Present: Emphasis on focus outlines in combinations. - Improve: Demonstrate visible focus for example patterns. #### Contrast and readability - Present: Strong focus on color contrast complexities. - Improve: Provide numeric contrast examples and thresholds. #### Text resizing and reflow - Present: Mentions font resizing impacts for icons. - Improve: Show 200% zoom tests for all patterns. #### Media and captions - Present: External talk recommended. - Improve: Link to talk with confirmed captions/transcript. #### Forms and interactions - Present: N/A. - Improve: N/A. #### Standards reference - Map to WCAG 2.2: 1.4.1, 1.4.3, 1.4.11, 1.4.1 (Use of Color), 2.4.7 (Focus Visible). ### 🌍 DEIB Assessment #### Cultural breadth - Present: Global web standards (WCAG). - Improve: Multi-language examples of link cues. #### Inclusive language - Present: Clear, neutral tone. - Improve: Add plain-language summary of WCAG terms. #### Neurodiversity support - Present: Consistent structure, direct claims. - Improve: More chunking and icon+text callouts. #### Representation - Present: Community sources noted. - Improve: Cite users with disabilities and real-world tests. #### Psychological safety - Present: Respectful critique; constructive. - Improve: Community guidelines for productive disagreements. ### ✅ Logical Validity #### Strong reasoning - Causal: Default underline → faster, reliable testing; supported by stepwise test comparisons. - Inductive: Universality of underlines as link indicators; consistent with UX conventions. #### Fallacies - None apparent; acknowledges valid alternatives but cites testing costs and recognition limits. #### Tone of voice - Professional, pragmatic, and open to exceptions with evidence. ### 🛡️ DARVO Analysis - No denial, attack, or role-reversal tactics observed; author invites third‑party validation and nuance. ## 🎯 Conclusion - Bottom line: Keep underlines as the default for themes to ensure quick, reliable accessibility; allow alternate WCAG-conforming styles as options, ideally backed by third‑party verification. - Next steps: Document reviewer latitude, define exception criteria, publish tested alt-style recipes, and fund audits for innovative patterns. ## 🧱 Refactor Appendix (append after 🎯 Conclusion) ### 📚 Literature Split Pad - Purpose: Stage Konik CEE units that become per-source Literature notes. - Split level: H3. - Include verbatim quotes under 25 words and a [view highlight] link. ### Underlined defaults speed reliable theme reviews > [!quote] [Why WordPress Themes Require Underlines on Links](https://www.joedolson.com/2025/10/why-wordpress-themes-require-underlines-on-links/) by [[Joe Dolson]] via [[joedolson.com]]. Published 2025-10-10. Accessed 2025-10-11. > “Requiring an underline is very easy to test: Is there an underline? Yes – it passes.” Reviewer bandwidth is the bottleneck; defaults must be low-ambiguity. [view highlight](https://www.joedolson.com/2025/10/why-wordpress-themes-require-underlines-on-links/#H1) #xref #articleseed ID:rw_[MISSING] ### Alternatives can exist as optional, WCAG-conforming styles > [!quote] [Why WordPress Themes Require Underlines on Links](https://www.joedolson.com/2025/10/why-wordpress-themes-require-underlines-on-links/) > “By default WordPress themes have to have underlined links. That doesn’t mean that a theme can’t have alternate styles.” Use optional styles; verify contrast and focus states under editor changes. [view highlight](https://www.joedolson.com/2025/10/why-wordpress-themes-require-underlines-on-links/#H2) #xref ID:rw_[MISSING] --- ### 🔖 Atomic Split Pad (Zettel Candidates) - Purpose: Promote reusable claims into Atomic notes. - Split level: H4. - Each item: one idea, present tense, specific, testable. #### [Z1] Underlines maximize link recognizability across contexts - Supported by UX convention and non-color cue requirements. - Links: [[Link-Affordance]] [[WCAG-Use-of-Color]] #### [Z2] Reviewer time limits drive simpler accessibility rules - Observed in theme review process; underline rule reduces ambiguity. - Links: [[A11y-Governance]] [[Testability-vs-Flexibility]] --- ### ✏️ Fleeting Queue (Extract by Selection) - Purpose: Capture quick actions or sparks for Fleeting notes. - Extraction: Select one line → “Refactor: Extract selection to new note (content only).” - Keep each line short and self-contained. - [F1] Draft decision tree for link-style exceptions — context/https://www.joedolson.com/2025/10/why-wordpress-themes-require-underlines-on-links/ #fleeting #inbox - [F2] Build contrast test harness for editor color changes — context/https://www.joedolson.com/2025/10/why-wordpress-themes-require-underlines-on-links/ #fleeting #inbox - [F3] Collect third‑party verification providers list — context/https://www.joedolson.com/2025/10/why-wordpress-themes-require-underlines-on-links/ #fleeting #inbox ---