search

cloudbearings / ez-access-web

Automatically exported from code.google.com/p/ez-access-web
0 stars 0 forks source link

Default support for <input type="image" /> as a button #25

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The <input type="image" /> has image map-like functionality but is used on some 
websites as a button because it renders in a consistent manner.

I think we should probably support this input type and treat it as a button by 
default. EZ Access should read (in order of priority):
"[aria-label], button."
"[Explicit/Implicit Label], button."
"[Alt-text], button."
"Image, button." (if no alt-text or other label)

You may need to supply a reasonable click coordinate in the image (perhaps the 
upper right corner of the image), but I am fine if the image works when EZ 
ACTION is pressed even if the coords do not make so much sense.

I have some test cases on the temporary webpage: 
https://mywebspace.wisc.edu/jbjordan/web/ez/buttons.htm

Original issue reported on code.google.com by jbjor...@gmail.com on 9 May 2013 at 3:12

GoogleCodeExporter commented 9 years ago 
I have noticed that currently EZ Access reads buttons like this:
"[Label] [Value], button"

Where [Label] is supplied by a <label> element or aria-label attribute.
And where [Value] is either the content of the <button> tag or the value 
attribute.

There are some pros and cons with this behavior:
Pro: If the [Value] changes but the [Label] is consistent, then the 
"status/[Value]" of the button is always provided.
Con: This is not how other screen readers seem to behave. The [Label] 
completely replaces the [Value] in the few I have tried.

Whatever we decide is the proper reading, <input type="image" /> should be 
consistent with other buttons.

Original comment by jbjor...@gmail.com on 9 May 2013 at 3:32

GoogleCodeExporter commented 9 years ago 
I think for the sake of keeping it consistent with other input tags etc., it 
should not overwrite. Other tags (data-ez-sayalt or others) provide this 
functionality.

Additionally, if the button doesn't have a value (an image or something) the 
label would 'take its place'.

My argument is don't overwrite for consistency.

Original comment by aeharding on 24 May 2013 at 12:40

GoogleCodeExporter commented 9 years ago 
Agreed

Original comment by jbjor...@gmail.com on 28 May 2013 at 4:15