WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessibility and web applications

for

From: Liko, Todd
Date: Apr 2, 2014 9:18AM

Thank you all for your replies. So far there has not been any common opinions, which is to be expected. Some clients want a black and white answer, as in, do I have to do it. I am not a proponent of 'do I have to it' if it adds functionality, usability and accessibility to a page, within reason of course.

The decision on how to move forward will be mine, so I hope to make the best one.

Don Mauck: I see your point, however, the application does not handle legal commitments or financial transactions. G168 says the technique is to seek confirmation from the user that the selected action is his or her intended action. I interpret this to apply to action buttons such as submit and so on. Surely, I would not expect to have to apply this everytime the user selects a link.

Srinivasu Chakravarthula: I agree with your suggesting to adding it as an instruction, the question is it required. This is probably the option I will recommend.

Patrick H. Lauke: Your suggestion of adding a window.onunload event handler is interesting. I am not a web application programmer, but would this not require javascript to be on?

Thanks again all.

Todd.
From: <EMAIL REMOVED> [ <EMAIL REMOVED> ] On Behalf Of Don Mauck [ <EMAIL REMOVED> ]
Sent: April 2, 2014 10:42 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Accessibility and web applications

I do think this could fall under WCAG2.0 3.3.4, quite possibly (G168). I believe that if the visual user can see it on the screen the screen reader needs to read that as well. Many, many web pages do give an error when requesting to leave the page.