id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
11700	Bringing accessability support for Widgets	Marek Lewandowski		"We should think about providing good a11y for widget.

Currently screen readers treats every widget as an end of the element. We need to be far better than that.

The most important requirements i see at the moment are:
* labels for widgets
* labels for editables

== labels for widgets ==

* Should be context sensitive, by that i mean they should be diffrent for image, placeholder, mathjax and codesnippet
* Label should be also possible to fetch some information from widget instance itself, i.e. image should be have its alt attribute included into label
* Should be specified in widget definition

== labels for editables ==

Here i have no clear conception as of yet, because you're only able to access editable using the tab key, but it iterates from the very beginning of the document, rather than current caret position.

2 ways comes to my mind, easier:

Solution 1
* leave current keyboard as it is
* upon getting into editable, user should be informed what widget editable belongs to

Solution 2
* Allow only to enter into editable (with {{{tab}}} key) only when widget is focused
* We don't need to inform our end-user what widget he's in (that reduces extra time spent on listening). The only one information he will need is the name of editable itself
* Important implementatino detail would be to allow focus cycling inside widget"	Bug	new	Normal		Accessibility