So I was reading Practical Accessibility Tips with WCAG 2.0
Always Use Explicit Labels is in 7 core now and has been backported ot 6.
The use the tabindex attribute is also quite scarce. Think it only shows up in the user.module as an attribute added to the form:
'#attributes' => array('tabindex' => '1'),Right now we're indicating Required Fields using:
<label for="edit-name">Username: <span class="form-required" title="This field is required.">*</span></label>However, I believe the WCAG 2.0 way for required fields is would be:
<label for="edit-name">Username: <span class="form-required"><abbr title="This field is required.">*</abbr></span></label>It's just a simple change on line 2467 of includes/form.inc
$required = !empty($element['#required']) ? '<span class="form-required" title="' . $t('This field is required.') . '">*</span>' : '';There are no instances of the use of the abbr tag in core other than the filters.
Some questions.
1) Would inserting a tabindex be useful or is the order of the form elements clear enough?
2) Will screen readers interpret abbr more consistently than a titled span element?