# Keros Accessibility pass failures

**URL:** <https://meta.discourse.org/t/keros-accessibility-pass-failures/87013>\
**Category:** Product Support\
**Tags:** accessibility\
**Created:** [May 8, 2018, 8:11pm UTC](https://meta.discourse.org/t/keros-accessibility-pass-failures/87013 "2018-05-08T20:11:44Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![Niko\_Taitano](https://avatars.discourse-cdn.com/v4/letter/n/a698b9/32.png) [@Niko\_Taitano](https://meta.discourse.org/u/Niko_Taitano)\
**Post date:** [May 8, 2018, 8:11pm UTC](https://meta.discourse.org/t/keros-accessibility-pass-failures/87013/1 "2018-05-08T20:11:44Z")

</div>

Hello Discourse team,

We recently ran an automated Accessibility pass using Keros on our site, and had quite a few fail instances. A lot of the failures related to things like Landmarks not having unique roles (aria-label) or ARIA attributes not having valid values.  
I was just wondering how I should go about reporting those kinds of issues here? Should I list a few examples for each section (like Landmarks, Headings, Native Widgets, etc.)? Any feedback would be greatly appreciated. Thanks!

---

_[View the full topic](https://meta.discourse.org/t/keros-accessibility-pass-failures/87013)._