Call for Topics:
Please reply with suggested topics for our November Drupal Accessibility Skype Meeting.
Tuesday, November 8, 2011
5pm GMT/11am CST
on Skype (contact m.gifford or brandonbowersox on Skype to be added to the group if this is your first time joining)
Anyone interested in working on Accessibility using Drupal is invited. Because of daylight savings time ending this Sunday, November 6 in the United States, note that this meeting will be at 5pm GMT.
Please respond with suggested topics
The call is a voice conference call on Skype. We'll be asking for a volunteer to post notes to the g.d.o. group so that people who could not attend can still review the notes and post comments. We will try to limit the main agenda to one hour.
See http://groups.drupal.org/node/175049 for our plans for December and making this a regular monthly event the Second Tuesday of each month.
What would you like us to discuss this month?
Comments
Suggestions
I'm going to be super busy w/ the jQuery-UI accessibility review, but I'd like to pop in.
I can give a brief explanation of the review that I am doing and how it relates to Drupal accessibility.
We should follow up on action items from last month.
We should look at major areas of Core accessibility work needing to be done and perhaps form teams to try to move those issues forward.
a. ARIA in Core.
b. Form accessibility.
c. Design, colours, etc.
d. Language of parts.
Accessibility Consultant & Web Developer - Zufelt.ca
@ezufelt on Twitter | LinkedIn profile
Headings for lists of links
While helping out the conversion of core templates to HTML5, I've noticed several places where lists of links do not have headings (e.g. node links)
It would be helpful if we had guidelines on when headings are needed.
@dcmouyard on Twitter
Whenever there are lists
Hey, thanks for checking in about this. I think that WCAG 2.0 guidelines are pretty straight forward.
http://www.w3.org/TR/2010/NOTE-WCAG20-TECHS-20101014/H69
--
OpenConcept | Twitter @mgifford | Drupal Security Guide
I thought so too, but...
I thought so too, but I was getting pushback that some lists of links aren’t navigation links and thus don’t need a heading.
I’m not well-known in the Drupal community, so some people don’t give much weight to my opinions. It would be nice if we had a guideline somewhere that I could just point people to saying “this is what the accessibility team recommends.”
@dcmouyard on Twitter
Accessibility and Drupal
A best practice defined here would be good:
http://drupal.org/node/394094
You can also just post some of the issues where this is being discussed. But better to improve the docs where we can so that there is more clarity.
--
OpenConcept | Twitter @mgifford | Drupal Security Guide
Not enough information…
Mike, it depends on context. I would think that lists of links should be easy to navigate to, which would usually mean that there should be a heading before them, or close to just before them.
Even so, I can't categorically state that a heading is always needed for a list of links.
So I'd have to see the specific case where dcmouyard is getting pushback before I could say whether it would always call for a heading.
There just isn't a simple answer that fits all cases.
What can we do to produce a rule
Is there a rule of thumb that we can develop to determine when we'd want headings for D8 (released in 2 years) and then a second one for when we'd want D9 support?
I just want to get to a place where we have a clear plan that @dcmouyard and others can refer to.
--
OpenConcept | Twitter @mgifford | Drupal Security Guide
I’m not well-known in the
This isn't true. I think it's sad that you come to this conclusion because I disagree with you on one issue. Especially, when most of your other suggestions are in the latest patch, despite reservations I have about them. Your participation is absolutely valued, and I have weighed your opinions considerably for the patch in question. It's just that when approaching 100 comments an issue, it's generally time to reign things in and agree to disagree. I've stated the reasons behind why I think invisible text is wrong in this case, and stand by them.
Anyway, please don't take my disagreement to mean that I don't give weight to your opinions, or let one disagreement discourage you.
It would be great if times
It would be great if times for these meetings could be posted in UTC.
I will do my best to attend, but a sudden move leaves me likely moveing a few items at about the time the meeting starts. I'll jump in whenever I'm free.
OT:
H69 is implementation. If you look to SC 2.4.1 you will see that it refers to content repeated on each page. Therefore, headings for main content, footer, etc, are necessary* to meet this SC, but headings e.g. for node links, are IMO not.
Accessibility Consultant & Web Developer - Zufelt.ca
@ezufelt on Twitter | LinkedIn profile
Drupal 8 Moving to Aria
In this case, should we define the use cases for D8 for lists? Could we simply state that in D8 we should assume that ARIA will be well enough supported and we can use the more elegant ARIA landmark roles?
Whatever we do it should be clear and consistent. When reviewing HTML5, it's the ideal time to standardize.
Trick as always is not to look at what people are doing now, but forecast what it is going to be like in 2 years when D8 is ready for prime time.
--
OpenConcept | Twitter @mgifford | Drupal Security Guide
d. language of parts
Not sure if I am able to attend this meeting. So, a short report on language of parts. There is a meta-issue now: http://drupal.org/node/1323338 Seperate issues are tagged by 'language of parts'. Did some testing and Gabor is actively looking at these issues. There is progress in some of these issues, and I did testing for body, textfield and title field. Some remarks:
- language attribute is allowed by default in the filters, but there is a XHTML/html5 related bug
- the span tag, often used for language attributes, is not included by default.
WYSIWYG: there is quick comparison on ckeditor and tinymce from Belgium here: http://translate.google.ca/translate?hl=en&sl=nl&u=http://blog.anysurfer...
DIdn't succeed in contacting the developers of these editors.
Agenda
Welcome
- who is willing to post notes this month?
jQuery-UI accessibility review update - Everett
List of links question (Headings for lists of links) - Dan/needs docs?
Follow up on last month's items - any progress updates?
Identify working teams for:
a. ARIA in Core.
b. Form accessibility.
c. Design, colours, etc.
d. Language of parts. - Hanno sent an update (d. language of parts)
www.pixotech.com
Notes of the meeting held on November 8 2011
Introduction of members
Brandon, Siddhant, Nitin, Gareth, Mike Gifford, Hadi, Dan, Everett, Cliff
jQuery UI 1.9 testing by Everett Zufelt
Request to others to come up and contribute to wigits
autocomplete transformation to jQuery UI. But, UI one isn't that accessible as drupal
heading for list of links
heading a way to meet success criteria of skip passed blocks of content repeating on pages
Not to hide heading
nav element paired with role=navigation ( Compatibility with ARIA)
Staying with heading in drupal 8 and introducing land marks. later removing headings
Last month's updates
Reviewing drupal with performence of ATAG
Cliff suggested that there is need of 2 examples having implemented ATAG
Language of parts
HTML cleanup code can be altered to have lang attribute.
But, is it necessary to introduce the change?
How many people will implement? Already html elements instead of WYSIWYG.
ARIA in core
HTML 5 aware of ARIA. ARIA can be implemented with HTML5
Would be suitable to have experts working on HTML 5 here.
Forms API
Need to improve on the way the html gets rendered
Color
While implementing high contrast themes:
Text fields have forecolor set. but backcolor of the text field doesn't change.
Meeting ends
Siddhant Chothe,
Senior Software Developer at Techvision
Thanks
Appreciate you taking the minutes Siddhant! Thanks for posting them here.
--
OpenConcept | Twitter @mgifford | Drupal Security Guide