# Accessibility concerns re email, Lynx, JAWS

**URL:** https://meta.discourse.org/t/accessibility-concerns-re-email-lynx-jaws/35675
**Category:** Feature
**Created:** [2015年十一月17日 05:29 UTC](https://meta.discourse.org/t/accessibility-concerns-re-email-lynx-jaws/35675 "2015-11-17T05:29:11Z")
**Posts on this page:** 1
**Showing post:** 15

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [2015年十一月23日 21:01 UTC](https://meta.discourse.org/t/accessibility-concerns-re-email-lynx-jaws/35675/15 "2015-11-23T21:01:03Z")

</div>

We have in the past worked with 2 blind users to improve things (@MarcoZehe and @ndarilek ) see:

> [@Accessibility software and discourse](https://meta.discourse.org/t/accessibility-software-and-discourse/13711):
>
> I spent some time trying to use the site with both JAWS (in a recent version of IE) and on a Mac in Chrome. The results were not particularly good. Has there been any work on this since the messages last year?

We received advice from @stevefaulkner an expert in the field and acted on it.

We will continue to improve Discourse based on feedback.

As it stands the biggest pain point, which is a devil to solve is Email parsing. At the moment our parser requires the response is “at the top” if it is inlined or anything non-traditional stuff gets rejected. That tripped @MarcoZehe last time when he tried to respond. I would like to improve on it and we are logging all email failures so we can extrapolate better logic.

---

_[View the full topic](https://meta.discourse.org/t/accessibility-concerns-re-email-lynx-jaws/35675)._