4 ms·

So goodbye to accessibility.

• wirrbel 12y ago
  how does this reduce accessibility? javascript interpreters are not hard to find nowadays.
  • easytiger 12y ago
    There are in fact a huge number of both usability and accesability issues with this that do not exist with the original: http://www.gnu.org/software/gnu-c-manual/gnu-c-manual.html http://www.gnu.org/software/gnu-c-manual/gnu-c-manual.html
    • wirrbel 12y ago
      does javascript reduce "accessibility" as in: does it keep average users and handicapped users from accessing the pages? The usual texinfo output is probably more accessible from a technical standpoint, but from a usage perspective it is not. Markup formats like ReST/Sphinx are much more semantic and improve accessibility for the impaired as well. Simple JS is not the problem here.
      • easytiger 12y ago
        > The usual texinfo output is probably more accessible from a technical standpoint, but from a usage perspective it is not. Can't possibly agree with that. Slap a fancy clean font on it and it prob solves half the issues people have with it. From a usage perspective this page is crippled compared with the original. > does it keep average users and handicapped users from accessing the pages? If the third part tools they need to navigate and consume the content stop working, then yes, yes it does.
  • deleted 12y ago
    [deleted]
• _ak 12y ago
  Bullshit. Modern screenreaders in browsers directly look at the visible parts of the DOM. Wilfully turning off Javascript in the browser is not an accessibility issue.
  • easytiger 12y ago
    Well the content is loaded dynamically so that is going to screw a lot of utilities up.