Hi, I’m not sure of this has been discussed before, but I saw the vote on the new MP6 theme. http://polldaddy.com/poll/7437854/. Has a colour scheme with sufficient contrast been suggested already? Maybe not for the default theme, but as a choice? In all of this themes the grey in the input fields is very light, did someone do some calculations on this?
Updates from October, 2013 Toggle Comment Threads | Keyboard Shortcuts
Yesterday’s meeting focused almost entirely on developing a global accessibility statement for WordPress. It was decided that the statement should be broad in nature, and that it will generally support accessibility with links to more specific information that this group maintains.
The voluntary accessibility theme check process was mentioned, that process is nearly ready to launch.
Much thanks to Mel Pedley @esmi for her guidance and leadership as team representative for the past 18 months. I will now serve as team representative.
You can also contact us with words of encouragement or feedback on Twitter @WPAccessibility.
The main focus of the meeting ( and the group) was still on one of our primary objectives — the development of a global accessibility statement for WordPress. After reviewing Drupal’s accessibility statement again, it was decided to begin work on drafting our own statement that can then be presented to the wider community for discussion.
Another small but busy IRC meeting on #wordpress-ui where discussion focused on assessing the translate.wordpress.org site for possible accessibility issues.
If you have a little spare time, please do try to contribute to the site feedback request. Any observation — no matter how small — is valuable. If you need some ideas on what to look for, please check out our Site Feedback Guide.
We had another lively IRC meeting on Wednesday.
3.6 Post Formats
It was previously decided that both the video and audio post formats could benefit from an ability to add links to captions (for videos) or transcripts (for audio files) and some preliminary investigations were started to look at the possibility of submitting patches. However, as there has been some concern about the release schedule for 3.6 and the possibility that Post Formats might be removed from the release, this has been shelved until we hear further.
I think I’ve finally finished! *gasp* Thank you to everyone who provided earlier feedback and jogged my memory.
Is there anything on the completed page I need to re-word or explain in more detail?
As previously, please post all feedback here rather than on the draft page itself.
I’ve raised this post as I feel that the issue of the Add Media panel accessibility needs some debate amongst the accessibility community.
The main problem as I see it is that it is not possible to select/deselect any of the media without using a mouse.
The functionality primarily acts like a group of checkboxes – selecting one or multiple elements, with feedback that they have been selected. However, that is not how the functionality has actually been implemented – it’s a series of divs contained within an unordered list. There appears to be nothing to receive focus. There are links for each file, but the links appear empty although they are used to show the selected icon. These links are also initially invisible using CSS techniques that hide them from screen readers – hence the no tabbing into the images issue.
Is the use of ARIA going to really be able to help here?
When mouse users select an image they can update the attribute values for that image using the panel to the right – which updates its content automatically. Allowing keyboard users to quickly reach the attributes boxes would obviously be desirable – the alternative being tabbing through all the previously uploaded files.
The media selector panel has been implemented with infinite scrolling, so on mature and/or larger sites with many images/files (I have one) the list of images gets bigger and bigger. From an accessibility perspective I’d favour paging over infinite scrolling, but what’s your take on that?
Is this another area where bending the new functionality to include accessibility might be too much? Is this another place where an accessibility mode is going to be required?
What do you think?
- Should the “Visit plugin site” offsite link (in Plugins → Installed Plugins open in a new window/tab? (A no-brainer?)
- The best way to pre-warn users of an offsite link
Some practical suggestions for the latter might come in very useful right now.