# WAVE issues from post

**URL:** https://meta.discourse.org/t/wave-issues-from-post/180370
**Category:** UX
**Tags:** accessibility
**Created:** [February 19, 2021, 5:40pm UTC](https://meta.discourse.org/t/wave-issues-from-post/180370 "2021-02-19T17:40:57Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![aaronbauman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aaronbauman/32/204191_2.png) [@aaronbauman](https://meta.discourse.org/u/aaronbauman)
#### Post date: [February 19, 2021, 5:40pm UTC](https://meta.discourse.org/t/wave-issues-from-post/180370/1 "2021-02-19T17:40:57Z")

</div>

Running WAVE on Discourse hosted reveals a handful of WCAG accessibility issues.  
Posting each in a separate #Contribute > UX thread.  
Hopefully these are repeatable using WAVE on your own instance, but if not I can provide details on any of these items.

results from a test thread:

|Guideline|Type of Page/Process|Found by||Notes|Level|  
|—|—|—|—|—|—|—|  
|Linked image missing alt text|2.4.4 Link Purpose (In Context) ||WAVE||Images that are the only thing within a link must have descriptive alternative text.|A|  
|Empty button|1.1.1 Non-text Content ||WAVE||Bell button|A|  
|Empty links|2.4.4 Link Purpose (In Context) ||WAVE||post content|A|  
|Skipped heading level|1.3.1 Info and Relationships ||WAVE||h4 after h1|A|  
|Redundant alt text|1.1.1 Non-text Content ||WAVE||post content|A|  
|Redundant title text|||WAVE||post content||