Jake-- curious what your laws are for accessibility in the UK. In the US, I've always undestood the accessibility laws are to accommodate sight impaired (screen readers) and alternate input (kb only, for example).
Is no-JavaScript part of the laws you're talking about? I support simple apps, and flexible designs that work for screen readers, mobile phones, print, etc. But I also support feature-rich applications and fast design time. So I'm very pro-javascript if it makes the app easier for users and doesn't break the app's basic (typically read-only) functionality. If we're trying to expand the utility of web apps, we need to embrace the tools available.
As for gets/posts-- in my exerience, users have no expectation of a button vs. a link. Images that serve as buttons/links also complicate the distinction. Users *definitely* don't know the difference between GET/POST (nor should they need to).
Jake-- curious what your laws are for accessibility in the UK. In the US, I've always undestood the accessibility laws are to accommodate sight impaired (screen readers) and alternate input (kb only, for example).
Is no-JavaScript part of the laws you're talking about? I support simple apps, and flexible designs that work for screen readers, mobile phones, print, etc. But I also support feature-rich applications and fast design time. So I'm very pro-javascript if it makes the app easier for users and doesn't break the app's basic (typically read-only) functionality. If we're trying to expand the utility of web apps, we need to embrace the tools available.
As for gets/posts-- in my exerience, users have no expectation of a button vs. a link. Images that serve as buttons/links also complicate the distinction. Users *definitely* don't know the difference between GET/POST (nor should they need to).
-Seth
N. Bethesda, MD USA