Accessibility Group update for March 14, 2013

Custom Menus

Further progress made on #14045 last week thanks to @ceo, @grahamarmfield and especially @lessbloat (who has been amazing!). There are further improvements that could be made but, due to development time restraints, we’re reasonably happy to go with what @lessbloat has already done. We’ll save any further enhancements for a future ticket once we have feedback from screen reader users post 3.6.

Comment Form

Re #15080, @shaun_10up and @ceo have been taking the lead and hit some problems with our suggested patches. Testing revealed that there is a significant difference in the way that screen reader software handles content within forms. so we may have to shelve this for now and take time out to do some more work on a universally effective solution.


The Accessibility page for the Theme Developer’s handbook & the Accessibillty section for the Theme Review Guidelines are both complete.


@esmi and @joedolson are continuing to work with the Theme Review Team on the new, optional, theme accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). ( audit.

Other TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. Tickets