0004764: make sure that the HTML i18n strategies used by various Taler components are accessible

ID	Project	Category	View Status	Date Submitted	Last Update
0004764	Taler	other	public	2016-11-08 13:51	2017-06-06 12:18

Reporter	Florian Dold	Assigned To	Florian Dold	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	fixed
Product Version	git (master)
Target Version	0.3	Fixed in Version	0.3

Summary	0004764: make sure that the HTML i18n strategies used by various Taler components are accessible
Description	... in the sense that they don't cause any problems with screen readers and other accessibility tools.
Tags	No tags attached.

Date Modified	Username	Field	Change
2016-11-08 13:51	Florian Dold	New Issue
2016-11-08 15:24	Christian Grothoff	Note Added: 0011454
2017-03-18 22:38	Christian Grothoff	Assigned To	=> Florian Dold
2017-03-18 22:38	Christian Grothoff	Status	new => informing
2017-03-18 22:38	Christian Grothoff	Resolution	open => fixed
2017-03-18 22:38	Christian Grothoff	Fixed in Version	=> 0.3
2017-03-18 22:38	Christian Grothoff	Note Added: 0011941
2017-03-18 22:39	Christian Grothoff	Product Version	=> git (master)
2017-03-18 22:39	Christian Grothoff	Target Version	=> 0.3
2017-06-06 12:18	Christian Grothoff	Status	informing => closed

Christian Grothoff 2016-11-08 15:24 manager ~0011454	https://addons.mozilla.org/en-US/firefox/addon/accessibility-evaluation-toolb/ seems like a great starting point for this.

Christian Grothoff 2017-03-18 22:38 manager ~0011941	I think the switch to jinja2-templates has definitively addressed this concern. Resolving.