E-mail List Archives
Thread: RE: Question about guideline 31 for Accessible and UsableWebSites
Number of posts in this thread: 1 (In chronological order)
From: L
Date: Thu, Apr 13 2006 3:10AM
Subject: RE: Question about guideline 31 for Accessible and UsableWebSites
No previous message | No next message
John S. Britsios wrote:
"We added a title to the "Submit" button "Page will reload!", and using a server-side solution, we managed that when the user clicks there, the page reloads, and the user will be go back to the same place he/she have been, and he/she can view or hear the success or error message.
...
Also, if this is an appropriate solution, would it be necessary to add a notice before the "Submit" button, that the page will reload? Or add an alt tag on the button?"
Looking at your working example, and doing a little bit of checking, there's a screen reader issue to explore further.
Using Jaws, so this should be checked with other screen readers, there seems to be an order of precedent in the way Jaws will read certain attribute values.
As far as I can tell, the title attribute out weighs the alt and value attributes. If the title attribute is empty or absent, the alt attribute takes precedence over the value attribute, and only if both the title and alt attributes are empty or absent is the value attribute acknowledged.
In the form on your academy page, Jaws announces "page will reload, button", which although acknowledging the consequence of submitting the form in one respect, doesn't present any hint of the action that the button will carry out.
As I said, this was a quick exploration, with just a single technology, so a bit more rummaging would be in order
Regards,
L