Live data from Hacker News

Would you build a pure client-side JavaScript App using Pageforest?

pageforest.com

41–43 of 43 posts

Re: Would you build a pure client-side JavaScript App using Pageforest?

#41
post #40
post #37

Earlier quoted context omitted.

Thanks so much for the thoughtful feedback. BTW, can you explain why you can't do page rendering in JavaScript for accessibility? Is there reason screen readers can deal with dynamically generated HTML?

It's not that page rendering can't be done with JavaScript and still be accessible. My experience with it via testing is that due to the large number of screen readers, and then differences within versions of the even the most common screen readers (JAWS for example) is that you can't really expect a consistent experience for your users where you get much more consistency with vanilla HTML. The single largest complai…

Very interesting. I wonder why Chrome wasn't mentioned at all in the survey.

I would love to find some tools, like a Chrome extension, that could display an accessibility score for a web page and provide guidance on solving problems. For those of us not using screen readers, it's easy to overlook errors without realizing it.

Re: Would you build a pure client-side JavaScript App using Pageforest?

#42
post #41
post #40

Earlier quoted context omitted.

It's not that page rendering can't be done with JavaScript and still be accessible. My experience with it via testing is that due to the large number of screen readers, and then differences within versions of the even the most common screen readers (JAWS for example) is that you can't really expect a consistent experience for your users where you get much more consistency with vanilla HTML. The single largest complai…

Very interesting. I wonder why Chrome wasn't mentioned at all in the survey. I would love to find some tools, like a Chrome extension, that could display an accessibility score for a web page and provide guidance on solving problems. For those of us not using screen readers, it's easy to overlook errors without realizing it.

The survey I linked to is the 2009 version there's also a follow up with more info. My guess is that after a year Chromes market share was so small as to be not worth discussing. The newer survey, which I should have linked initially, still doesn't mention but does show improvement over the time span between surveys.

http://webaim.org/projects/screenreadersurvey3/

There's a few addons for firefox that focus on section 508 compliance but many of them are poorly maintained. You might want to look into this one, which I have not used myself however.

https://addons.mozilla.org/en-us/firefox/addon/qompliance/

Re: Would you build a pure client-side JavaScript App using Pageforest?

#43
I really like the concept, reminds me of CouchApps (http://couchapp.org/).

That being said, I agree with andrewjshults that sooner or later you will need to write server side code, even if it is to proxy client side requests to another domain.

mckoss, would it be worth making a server side implementation of your service for http://www.akshell.com - a server side JavaScript platform with syncrhonous I/O and a browser based IDE. We're open sourcing the whole stack, so there would be a lot less lock in than with AppEngine. Drop me a line on our mailing list if you're interested: http://groups.google.com/group/akshell

Post reply on HN