There are several new accessibility tickets on trac dealing with the use of “tabindex” and other accessibility enhancements. A few are already committed. It would be good if these can be tested and any substandard/improper behavior fixed while still early in the development cycle for 3.5.
Core Development- We’re getting very close This week focusing on… May 9, 2013
- Hello everyone Applications for Google Summer of Code… May 3, 2013
- GSoC Chat May 2, 2013
- Plugins SVN repository will be going read only… April 23, 2013
- Twenty Thirteen project update, April 23, 2013 April 23, 2013
- WordPress UI
- Hey UI gang Here to help you wind… May 17, 2013
- Hello UIers The kind folks at Balsamiq have… May 17, 2013
- Howdy gang On this fine Friday evening we… May 11, 2013
- MP6 1.0 May 4, 2013
- MP6 0.9 April 26, 2013
- Forum Posts
- After Gadget on "Labeling comment field (for accessibility)" May 18, 2013
- ceo on "Labeling comment field (for accessibility)" May 17, 2013
- After Gadget on "Labeling comment field (for accessibility)" May 17, 2013
- esmi on "Labeling comment field (for accessibility)" May 17, 2013
- ceo on "Labeling comment field (for accessibility)" May 17, 2013
esmi 8:21 pm on July 25, 2012 Permalink
I’ll be installing 3.5 bleeding edge on my local dev server shortly but, if I can, I’ll try to set up a remote 3.5 install that some of the others in this group can use for testing. Then we’ll try to collate some group feedback for you. Do you have a deadline date that we can use?
Andrew Ozz 10:05 pm on July 25, 2012 Permalink
No strict deadline but would be good to deal with this before coding on the new features in 3.5 starts. About a week would be great.
esmi 12:11 pm on July 26, 2012 Permalink
Had a quick look through all of the current 3.5 tickets. Graham seems to be on top of a few of them. I’ve also added comments where appropriate. The rest seem fine to me.