Hello,
We are using the Prometheus Calendar control as a datepicker similar to the
Shared Calendar Example.
One of our customers is running the app through
HiSoftware's AccVerify tool to ensure the application is Section 508 compliant.
If i run the shared calendar example through the tool and clear the date fields, the control is failing with the following errors:
<snip>
Rule: 1.1.2 - All INPUT elements are required to contain the alt attribute or use a LABEL.
- Failure - INPUT Element, of Type TEXT, found at Line: 183, Column: 110
- Failure - INPUT Element, of Type TEXT, found at Line: 187, Column: 129
- Failure - INPUT Element, of Type TEXT, found at Line: 187, Column: 215
<snip>
If i run the example through the tool without clearing the fields, it generates the following warnings that are still considered to be failures:
<snip>
Rule: 1.1.2 - All INPUT elements are required to contain the alt attribute or use a LABEL.
- Warning - INPUT Element, of Type TEXT, found at Line: 183, Column: 110 contains a non-empty 'value' attribute. This is a practice referred to as "self-labeling." Self-Labeling is argued to be accessible under Priority One or Section 508 guidelines/standards. We recommend using a Label as the Preferred method or the use of an 'alt' attribute to make this element accessible.
- Warning - INPUT Element, of Type TEXT, found at Line: 187, Column: 129 contains a non-empty 'value' attribute. This is a practice referred to as "self-labeling." Self-Labeling is argued to be accessible under Priority One or Section 508 guidelines/standards. We recommend using a Label as the Preferred method or the use of an 'alt' attribute to make this element accessible.
- Warning - INPUT Element, of Type TEXT, found at Line: 187, Column: 234 contains a non-empty 'value' attribute. This is a practice referred to as "self-labeling." Self-Labeling is argued to be accessible under Priority One or Section 508 guidelines/standards. We recommend using a Label as the Preferred method or the use of an 'alt' attribute to make this element accessible.
<snip>
In the example, there is a label who's 'for' attribute is being set to
'<%= RadDatePicker1.DateInput.ClientID + "_TextBox" %>'
but there are two other inputs rendered for each datepicker that still violate the 508 1.1.2 rule.
In my page, I tried adding the AssociatedControlId property on the label that precedes the control on the form, but I'm still receiving failures as well.
Any suggestions?