Dear WordPress.org: Let’s Talk About Your Underline Situation
🔗 **Source:** [Dear WordPress.org: Let’s Talk About Your Underline Situation](https://iconick.io/underlines/)
> [!note]+ Document Notes
> ```markdown
>
> ---
> tags: [Accessibility, WordPress, Design]
> author: iconick
> source: iconick.io
> reference: [https://iconick.io/underlines/]
> date created: {{date:YYYY-MM-DD}} {{time:HH:mm}}
>
> ---
>
> # 🏷️ Title: Dear WordPress.org: Let’s Talk About Your Underline Situation
>
<!-- deep-read:sections start -->
## 🧰 Action Inbox
- [H1] Draft .org proposal to allow multiple link cues — context/https://iconick.io/underlines/ #articleseed
- [H2] Add WebAIM/WCAG references to proposal — context/https://webaim.org/techniques/hypertext/ #xref
- [H3] Share findings with Theme/Accessibility Teams — context/https://make.wordpress.org/accessibility/ #share
- [H4] Prototype theme variants with three WCAG-compliant patterns — context/https://iconick.io/underlines/ #articleseed
- [H5] Run focus/contrast tests in CI for themes — context/https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html #xref
- [H6] Invite The WPCC to fund user testing — context/https://wpcommunitycollective.org/ #share #addendum
## 🧭 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
- The article challenges mandatory always-underlined links in themes.
- It argues WCAG allows multiple non-color cues beyond permanent underlines.
- Stakeholders include theme authors, The WPCC, Accessibility, and Design teams.
- Risks include inconsistent implementations and regressions without guardrails.
- Bottom line: permit WCAG-compliant alternatives with strong reviews.
## 📖 Main Content
- The author says WordPress enforces a dated visual pattern.
- WCAG permits non-color distinction, not only underlines.
- WebAIM supports non-color cues plus focus states with contrast.
- The article proposes flexible, testable options for themes.
- It urges guidance, education, and audits instead of one rule.
### 🗒️ Notes
### [H1] WCAG permits non-color link distinction
> [!quote] [Dear WordPress.org: Let’s Talk About Your Underline Situation](https://iconick.io/underlines/) by [[iconick]] via [[iconick.io]]. Published 2025-10-08. Accessed {{date:YYYY-MM-DD}}.
> “Link underlines or some other non-color visual distinction are required”
WCAG allows multiple cues, not only underlines.
[view highlight](https://iconick.io/underlines/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Bold plus contrast can satisfy WCAG
> [!quote] [Dear WordPress.org: Let’s Talk About Your Underline Situation](https://iconick.io/underlines/)
> “If the link is a different color and bold it would not fail”
Bold with contrast and focus meets guidance.
[view highlight](https://iconick.io/underlines/#H2) #xref ID:rw_[MISSING]
### [H3] WebAIM supports additional interaction cues
> [!quote] [Dear WordPress.org: Let’s Talk About Your Underline Situation](https://iconick.io/underlines/)
> “Color alone is not used… and an additional distinction… on hover and keyboard focus.”
Cues on hover and focus improve recognition.
[view highlight](https://iconick.io/underlines/#H3) #xref ID:rw_[MISSING]
### [H4] Current rule makes themes feel dated
> [!quote] [Dear WordPress.org: Let’s Talk About Your Underline Situation](https://iconick.io/underlines/)
> “It’s making WordPress themes instantly recognizable in a way that feels dated.”
Rigid styling harms perceived modernity.
[view highlight](https://iconick.io/underlines/#H4) #articleseed ID:rw_[MISSING]
### [H5] Multiple WCAG-compliant options exist
> [!quote] [Dear WordPress.org: Let’s Talk About Your Underline Situation](https://iconick.io/underlines/)
> “Use bold… underlines on hover/focus… 3:1 contrast… focus indicators.”
Offer options with tests and reviews.
[view highlight](https://iconick.io/underlines/#H5) #xref #articleseed ID:rw_[MISSING]
### [H6] Principles stress testing and context
> [!quote] [Dear WordPress.org: Let’s Talk About Your Underline Situation](https://iconick.io/underlines/)
> “Never rely on color alone… Ensure keyboard focus… Test contrast… Consider context… Test with real users.”
Adopt process checks and user testing.
[view highlight](https://iconick.io/underlines/#H6) #xref #addendum ID:rw_[MISSING]
## 📚 References
- WCAG 2.2 — Use of Color (1.4.1) https://www.w3.org/WAI/WCAG22/Understanding/use-of-color.html
- WCAG 2.2 — Contrast Minimum (1.4.3) https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html
- WCAG 2.2 — Focus Visible (2.4.7) https://www.w3.org/WAI/WCAG22/Understanding/focus-visible.html
- WebAIM: Links and Hypertext https://webaim.org/techniques/hypertext/
- Make WordPress Accessibility Team https://make.wordpress.org/accessibility/
- The WP Community Collective https://wpcommunitycollective.org/
## 🗣️ Paraphrase
- WordPress should not require always-underlined links.
- WCAG allows alternative non-color cues with contrast and focus.
## 📰 Newsletter
- WordPress friends, link styles need an update.
- WCAG allows several accessible patterns beyond permanent underlines.
- Consider bold+contrast, hover/focus underlines, and clear focus rings.
- See WebAIM’s guidance for practical checks.
- Join Accessibility and Themes teams to test prototypes.
- Helpful reads: WCAG Use of Color, Contrast Minimum, Focus Visible.
## ✅ Action Items
#### DevRel
- Publish a demo repo with three link patterns and tests.
- Run office hours on WCAG-compliant link cues.
- Add a “link semantics” doc and checklist.
#### OSPO
- Define accessibility guardrails in policy playbooks.
- Add automated contrast and focus checks to pipelines.
- Track compliance KPIs in executive reports.
#### Community
- Host pairing sessions for theme authors on focus indicators.
- Fund quick user tests with assistive tech users.
- Share results and templates openly.
#### WordPress
- Core: align design tokens for focus styles.
- Accessibility: propose guideline updates with examples.
- Meta: update Theme Review docs and lints.
- Design: provide tokens for link states and outlines.
- Documentation: add examples-first patterns and tests.
#### The WPCC
- Sponsor microgrants for accessible theme prototypes.
- Run governance clinic on standards vs. prescriptions.
- Publish impact report on testing outcomes.
### FAIR
- Ship an audit checklist for link cues and contrast.
- Add covenant for public test artifacts and results.
- Create reusable scorecards for design accessibility.
## 🧪 Hypotheses
- Allowing multiple cues will not reduce accessibility conformance.
- Flexible patterns will improve perceived modernity of themes.
- Clear reviews and tests will keep regressions low.
### 📊 Methodology
- A/B test themes using alternative cues with users.
- Measure task success, error rate, and time-to-recognize links.
- Automate contrast and focus visibility tests in CI.
### ❓ Questions
- Which cue combinations perform best across devices?
- How should Theme Review measure focus visibility?
- What training reduces author errors fastest?
### 🔮 Future Research
- Study link recognition for low-vision users on mobile.
- Evaluate bold+contrast vs. hover underline across locales.
- Assess developer linting that prevents regressions.
### 💡 Implications
- Practice: design tokens should include robust focus states.
- Policy: prefer outcome-based standards over prescriptions.
- Funding: support user testing as a shared service.
### 🧠 Learning Styles Assessment
- Reading level estimate: Flesch-Kincaid Grade ~9–10.
#### 👀 Visual learners
- Present: examples are implied.
- Improve: before/after link state visuals.
#### 🔊 Aural learners
- Present: none noted.
- Improve: brief audio summary.
#### 🗣️ Verbal learners
- Present: definitions and guidelines.
- Improve: glossary for contrast and focus terms.
#### 🧩 Kinesthetic learners
- Present: actionable principles.
- Improve: step-by-step testing labs.
#### 🧠 Logical learners
- Present: criteria and rationale.
- Improve: decision trees for pattern choice.
#### 🧑🤝🧑 Social learners
- Present: community involvement hints.
- Improve: cohort testing guides.
#### 🧘♀️ Solitary learners
- Present: clear principles.
- Improve: self-check worksheets.
#### 🌿 Naturalistic learners
- Present: not applicable.
- Improve: ecosystem analogies unnecessary here.
### 📊 Accessibility Assessment
#### Screen reader semantics
- Present: standards cited.
- Improve: ARIA guidance references.
#### Keyboard navigation
- Present: focus visibility emphasized.
- Improve: tab order examples.
#### Contrast and readability
- Present: 3:1 link-to-text ratio noted.
- Improve: include 4.5:1 body text checks.
#### Text resizing and reflow
- Present: not specified.
- Improve: confirm 200% reflow.
#### Media and captions
- Present: not applicable.
- Improve: caption guidance if examples added.
#### Forms and interactions
- Present: interaction cues discussed.
- Improve: error handling examples.
#### Standards reference
- Map gaps to WCAG 2.2 AA criteria.
### 🌍 DEIB Assessment
#### Cultural breadth
- Present: general web context.
- Improve: multilingual guidance links.
#### Inclusive language
- Present: respectful, clear framing.
- Improve: more plain-language summaries.
#### Neurodiversity support
- Present: consistent structure.
- Improve: more icon+text labels.
#### Representation
- Present: neutral topic.
- Improve: inclusive imagery if visuals added.
#### Psychological safety
- Present: collaborative tone.
- Improve: explicit moderation guidelines for reviews.
### ✅ Logical Validity
#### Strong reasoning
- Cites WCAG text allowing non-color cues [H1].
- Uses WebAIM interpretation to support interaction cues [H3].
- Proposes testable alternatives with standards alignment [H5].
#### Fallacies
- Possible overgeneralization on “dated” perception [H4].
- Fix: provide user research data.
#### Tone of voice
- Constructive, collaborative, standards-aligned.
### 🛡️ DARVO Analysis
- Deny: none; acknowledges shared goals.
- Attack: none; no personal attacks.
- Reverse victim/offender: none; proposes cooperation.
## 🎯 Conclusion
- WordPress should allow multiple WCAG-compliant link treatments.
- Adopt clear guidance, tests, and reviews to ensure accessibility.
## 🧱 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.
### [H1] WCAG permits non-color link distinction
> [!quote] [Dear WordPress.org: Let’s Talk About Your Underline Situation](https://iconick.io/underlines/) by [[iconick]] via [[iconick.io]]. Published 2025-10-08. Accessed {{date:YYYY-MM-DD}}.
> “Link underlines or some other non-color visual distinction are required”
Two lines: context and use. Cite data if relevant.
[view highlight](https://iconick.io/underlines/#H1) #xref #articleseed ID:rw_[MISSING]
### [H2] Bold plus contrast can satisfy WCAG
> [!quote] [Dear WordPress.org: Let’s Talk About Your Underline Situation](https://iconick.io/underlines/)
> “If the link is a different color and bold it would not fail”
Two lines: context and use.
[view highlight](https://iconick.io/underlines/#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] Themes allow multiple non-color link cues
- Scope: theme styling choices with WCAG 2.2.
- Links: [[WCAG-1.4.1]] [[Theme-Review]]
#### [Z2] CI enforces link contrast and focus
- Scope: theme repos with accessibility pipelines.
- Links: [[Contrast-Testing]] [[Focus-Visible]]
---
### ✏️ Fleeting Queue (Extract by Selection)
- Purpose: Capture quick actions or sparks for Fleeting notes.
- Extraction: Select one line → Refactor.
- [F1] Draft proposal allowing multiple cues — context/https://iconick.io/underlines/ #fleeting #inbox
- [F2] Build tokens for focus rings — context/https://make.wordpress.org/design/ #fleeting #inbox
- [F3] Schedule user tests — context/https://wpcommunitycollective.org/ #fleeting #inbox
## 🏷️ Tag Coverage
Tag Coverage — #articleseed: 2 • #xref: 3 • #share: 2 • #addendum: 1 • #bmf: 0 • #aphorisms: 0
```
<!-- deep-read:sections end -->