# נגישות ושפה מתנשאת ואופמיזמים **URL:** \ **Category:** UX\ **Created:** [9 באוקטובר,‏ 2023,‏ 7:15am UTC](https://meta.discourse.org/t/accessibility-and-patronizing-language-and-euphemisms/281591 "2023-10-09T07:15:19Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\ **Post date:** [10 באוקטובר,‏ 2023,‏ 3:26pm UTC](https://meta.discourse.org/t/accessibility-and-patronizing-language-and-euphemisms/281591/6 "2023-10-10T15:26:42Z")
> [@speeps](#): > > Yet it obviously does not work without JS at all. Discourse serves a basic HTML read-only view when JS is disabled, or the browser version is too old and not supported anymore. However, in a effort to reduce our request payload and get better speeds for mobile users, specially for users on old Android phones, we don’t ship the basic HTML view if we detect that the user-agent can handle JS just fine. The trade-off is the behavior you just found, the intersection of the three groups: - User in mobile - User in a recent modern browser - User who manually disabled JS Will get this sad screen, instead of the basic HTML view we ship for other users. This was a deliberate choice after checking the number of users who would get a faster site against the users who would not. > [@speeps](#): > > patronizing. That message is there for users who actually get the basic HTML view, like users in Internet Explorer 6. > [@speeps](#): > > Chromium (Vanadium Flavor) on GrapheneOS (Android) on a Pixel. We made no effort of making the basic HTML view scale well for mobile, as it was designed for search engine bots and users on old desktops. If you want to see how it would look, you can try sending an old browser UA string. Otherwise, you will need to hit that JS toggle and enable JS for Discourse. --- _[View the full topic](https://meta.discourse.org/t/accessibility-and-patronizing-language-and-euphemisms/281591)._