Posted by coderintherye on January 11, 2011 at 11:09pm
Hi guys, I'd like to revive a meeting of the a11y folks to discuss issues that didn't make the cut for D7 so we can create some fresh D8 issues for them.
For instance, a short discussion with sun about http://drupal.org/node/447816 came to the conclusion we should create two new issues out of that one based on webchick's b) and c) in #232.
There are other a11y issues that got pushed back to D8. What is our strategy going to be? Please add up links to other issues we should discuss.
Granted, perhaps everyone feels we should still focus on D7 issues, but I'd like to push forward a lot of stuff while it is still fresh in our minds, so at least stuff is well documented for a year from now when D8 really gets rolling on development.
Comments
I'm in
I would be glad to join for this meeting. Skype has seemed to work a bit better than IRC, so I'm comfortable with Skype unless others strongly prefer IRC.
I would like to brainstorm D8 plans for:
Form API (with better fieldsets);
Form error presentation;
Drag-n-Drop.
Others might want to talk about adding more ARIA, theming, and more.
www.pixotech.com
I don't feel the need to work
I don't feel the need to work on D7 issues, I am happy to follow the standard procedure of working on head and backporting where it is possible. There is a list of issues in the comments on http://groups.drupal.org/node/97504
Areas that we need to address, in no particular order:
FAPI, ARIA, HTML5, Drag and Drop (including hierarchical table drag), autocomplete (working upstream with jQuery), Overlay (and any other modals).
Most importantly we need to find a method of:
1. Performing a full evaluation of all current D7 Core UIs
2. Ensuring that * no * new UIs or UI changes are committed without an evaluation
In both of the above cases the evaluations need to be conducted by a person, or persons, with proficiency. We are not looking for bugs, we are looking to verify that there are no bugs. A person with low proficiency in accessibility might catch bugs, but they cannot as easily confirm that no bugs exist. I am not sure how to go about accomplishing these two tasks, but I am certain of their importance in ensuring that the Drupal product continues to reflect the Community's value of inclusion.
Perhaps it would be good to have one, or two, calls before Drupalcon, and some more in depth meetings in Chicago for those who attend. It may be possible to include those who are not attending in some of the meetings via Skype if there is strong enough interest and the meeting sizes are not too large.
Accessibility Consultant & Web Developer - Zufelt.ca
@ezufelt on Twitter | LinkedIn profile
Do we need to talk about HTML5?
Seems to me that we need to at least be in on the discussion about when and how Drupal should be redeveloped in HTML5. That discussion is going on right now. Is there anything we should discuss about it at this point — other than our undying devotion to longdesc? ;-)
Next Steps
It does seem like there is some traction to redesign D8 in HTML5. There are a few D8 threads in the issue queue about it already and I'm sure there will be more.
It's certainly going to be interesting to see how we deal with backward compatibility for older browsers & progressive enhancement for new code. I posted a bit of a note here on that thread:
http://drupal.org/node/675348#comment-3942580
Anyways, this all sounds great! Looking forward to the chat. I do find Skype easier than IRC to use. I set up a public accessibility group to see if that makes it easier for folks to join. That was one of the reasons to use IRC. We can also edit & post notes to GDO from time to time.
--
OpenConcept | Twitter @mgifford | Drupal Security Guide