[wp-trac] Re: [WordPress Trac] #9445: All Input Tags are not Section 508 Compliance

[WordPress Trac]

#9445: All Input Tags are not Section 508 Compliance
----------------------------+-----------------------------------------------
 Reporter:  dmo7            |        Owner:  anonymous
     Type:  task (blessed)  |       Status:  reopened 
 Priority:  normal          |    Milestone:  2.8      
Component:  Accessibility   |      Version:  2.7      
 Severity:  normal          |   Resolution:           
 Keywords:  has-patch 508   |  
----------------------------+-----------------------------------------------

Comment(by Elpie):

 Replying to [comment:24 ryan]:
 > Hidden inputs are different than hidden labels.  It makes no sense to me
 to ignore a hidden label for a visible input, but I digress.  We had a
 blind user who used to work at Freedom Scientific look over these not so
 long ago and all was deemed fine.  We'll go with whatever the current
 thinking is though.
 >
 > We can certainly look over all hidden labels and determine if they need
 to be visible to all. Just change the styling on the hidden class and see
 how horrid things look. I suspect it will be inaccessibly ugly. :-)

 Yes, in each case I was referring to the element, not the field.
 Having a look at what is there, with the styling on the hidden class
 commented out would certainly show what could be displayed and what should
 be hidden :-)

 However, I think you should be careful about making changes to labels for
 2.8. There are some well-meaning, but misinformed folk around here and
 unless the changes are done properly there is a real risk that instead of
 improving accessibility, changes will harm it.

 The alt tags that were suggested should not be committed. And the only
 change I would recommend would be to change the hidden class in CSS to use
 screen offset instead of display:none. This, on its own, will improve
 accessibility.

 If the team sets up a wp-accessibility mailing list those of us who are
 proficient in ATAG, WCAG, and WAI-ARIA can get stuck in and bring forward
 accessibility patches for the 2.9 milestone.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/9445#comment:37>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software