Comments on Understanding WCAG 2.0 Draft Updates dated July 11, 2013

*There are two draft updates I’d like to provide comment on:*

* *

*Focus Visible*:
Understanding SC 2.4.7

[Being add]

If there is only one keyboard actionable control on the screen, the success
criterion would be met because the visual design presents only one keyboard
actionable item.

[End add]



Comment: If there is no visible focus on the page, how would someone know
that only one item was actionable?  If the only actionable item was a
custom edit field, how would a person properly edit text if there was no
blinking caret?  Adding this exception creates a loop hole that allows for
inaccessible content.   Please do not add this item.



*Labels or Instructions*:
Understanding SC 3.3.2

[begin add]

*Note: *If labels are provided, the label relationship to the object
labeled must be programmatically determined or described in text per
*Understanding
Success Criterion 1.3.1 Info and
Relationships<http://www.w3.org/WAI/GL/2013/WD-UNDERSTANDING-WCAG20-20130711/complete-diff.html#content-structure-separation-programmatic>
*.

[end add]



Comment: This addition implies that the label must be programmatically
associated when a label is used.  It is possible that a visual label might
be present in addition to a title attribute or use of aria-label thus
removing the need for an explicitly associated label.  The problematic text
“the label relationship to the object labeled must be programmatically
determined” should be changed to say “a label with the same text must be
programmatically determinable”.



Jonathan



-- 
Jonathan Avila

Chief Accessibility Officer
SSB BART Group
jon.avila@ssbbartgroup.com

703.637.8957 (o)
Follow us: Facebook <http://www.facebook.com/#!/ssbbartgroup> |
Twitter<http://twitter.com/#!/SSBBARTGroup>
 | LinkedIn <http://www.linkedin.com/company/355266?trk=tyah> |
Blog<http://www.ssbbartgroup.com/blog>
 | Newsletter <http://eepurl.com/O5DP>