# Accessibility concerns re email, Lynx, JAWS **URL:** https://meta.discourse.org/t/accessibility-concerns-re-email-lynx-jaws/35675 **Category:** Feature **Created:** [11월 17, 2015, 5: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:** 23
### Author: ![grahamperrin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/grahamperrin/32/71406_2.png) [@grahamperrin](https://meta.discourse.org/u/grahamperrin) #### Post date: [11월 16, 2016, 3:26오전 UTC](https://meta.discourse.org/t/accessibility-concerns-re-email-lynx-jaws/35675/23 "2016-11-16T03:26:27Z")
> [@fbender](#): > > … Lynx is debatable, though not necessarily a sufficient reason to improve some aspects of Discourse. … I tested with Lynx following interest from valued community members who are sometimes (or often) in areas with low bandwidth; who typically prefer Lynx in such situations. Not a long test (only ten minutes or so), but enough to be pleased with the appearance, the orders of things and so on. An example screenshot: ![](https://global.discourse-cdn.com/meta/original/3X/c/e/ce18f30846989d2834fc8e6545e1c2c798200406.png) Without detracting from the foci on accessibility: - please, how much effort might be required to enable **log in** for users of Lynx? Beyond that point: from what I saw of the NLI (_not_ logged in) views, I assume that already there is support for most of the features that logged _in_ users will treat as essential or desirable. * * * Side notes: - should tags in meta include _accessibility_? (I found no more recent/relevant topic for Lynx) - noted in Firefox, with thanks, the Discourse response to keying `End`. Wow :clap: --- _[View the full topic](https://meta.discourse.org/t/accessibility-concerns-re-email-lynx-jaws/35675)._