|
|
|
|
|
by sellyme
2021 days ago
|
|
> In GitHub's case, they only recently screwed it up in a major way, so surely it shouldn't be a big deal to add back the functionality? Unless you're under the impression that websites are only requiring JavaScript out of spite, it seems like it would be a pretty big deal. > why do so many people feel such a strong need to tell me this issue of mine is a non-issue for everybody else? Because it's self-imposed, your justification involved calling JavaScript a "newer technology", and people tend not to react well to the belief that "I don't want to run JavaScript" is comparable to disability. |
|
You picked up on "newer technology" as if it's pertinent to the matter. It is not. This usability checkpoint is still 100% valid today. I gave reference to that document to show that the matter is related to accessibility, and to provide evidential support to userbinator's view that the term has been hijacked by the web giants and munged up to exclude whatever is inconvenient to them.
You, like others in this thread, bring "disability" and "self-imposition" to this discussion. I dare you to imagine a world where not everybody who wishes to make basic use of GitHub is able, even if willing, to run JavaScript in every conceivable context. Can you imagine such a world? In this totally imaginary world this inaccessibility is not self-imposed. Given such a world, would you be willing to accept that my simple request is reasonable?