# 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:** 6

<div class="post-metadata">

**Author:** ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)\
**Post date:** [May 11, 2018, 12:16am UTC](https://meta.discourse.org/t/keros-accessibility-pass-failures/87013/6 "2018-05-11T00:16:12Z")

</div>

If you are using automated scanners, be warned, these tools are _particularly_ unreliable when used against JavaScript apps like Discourse – they expect “old school” websites where everything is served in HTML in the server HTTP request. Discourse serves JavaScript which programmatically builds each page on demand as the user clicks / taps on things.

---

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