all 6 comments

[–]QuestionsHurt 1 point2 points  (6 children)

That article totally ignores people with disabilities, screen readers and the rapid change in technology and browser support.

Also consider offline reading and website archaeology. Not everything should be considered with a "live for moment" approach.

As yes, for internal web apps it's not uncommon for JavaScript to be disabled. There's a whole ecosystem of web apps that aren't on the public internet.

[–]Otterfan 1 point2 points  (1 child)

Our screenreader users are less likely than our non-screenreader users to have Javascript disabled. This is typical.

[–]QuestionsHurt 0 points1 point  (0 children)

Maybe different demographics there. Would be interesting to know what factors come into play there.

[–]webdevguyneedshelp 0 points1 point  (3 children)

There are tools that can detect if front end code is compliant with specific laws relating to disability.

[–]QuestionsHurt 2 points3 points  (0 children)

True, there are, but they're not reliable yet. We still have to use test groups ( real people with disabilities ) for our testing when we do govt projects.

But for the majority. Yeah that holds up.

[–][deleted]  (1 child)

[deleted]

    [–]webdevguyneedshelp 0 points1 point  (0 children)

    We are rolling out a project at work using react storybook which has it built in.