Move Calendar navigation into attachment?

Can you define the accessibility rationalle for the move?

I'm not sure, but it's worth bringing up here - http://groups.drupal.org/accessibility

I generally look for examples, standards & use cases.

Thanks for adding the accessibility tag to issue #373356.

I'm totally keen on leapfrogging off of other open source CMS solutions. WordPress is popular and has keen bloggers who use it well. Great to use solutions that have been tried & tested there and then work to improve upon them in Drupal.

So, for WCAG 2.0 the closest reference would be http://www.w3.org/TR/WCAG-TECHS/H73.html

The example here is pretty boring, but might be closer to the full month view (which we'll also need to address) - http://www.catea.gatech.edu/scripts/calendar.html

Thanks for joining the Accessibility group. Look forward to your other contributions.

There is no easy way to do this. The navigation is one view, the calendar is a different view, so there are no themes or handlers that can access both of them. Views outputs attachments before it processes the pages they are attached to, so they are totally separate (the navigation is the 'page' and the calendar is an attachment). It would take a complete redesign of the code to do this, not a trival task.

Sorry!

If it's critically important someone can try to make a patch, but it would probably be very difficult to find a way, especially a way that doesn't create a spaghetti mess of unmaintainable code.

It's quite the mass of code I must say. Hadn't really dug into the Calendar module before. And yes, this is certainly going to be larger than making a modification to a theme.

Just because there's no easy way to do this, doesn't mean that it can't be done, but it certainly is clear that you need the community to step forward and propose something that would be workable.

I'm partly wondering if Views needs to be extended (but more likely I just haven't got my head around it yet).

So looking at function calendar_week_header() one would think we could insert a title or or abbr attribute into the array and hopefully get that brought into the table when it is created. Unfortunately, my trial efforts didn't seem to be successful:

    $row[] = array('header' => TRUE, 'class' => "days ". $day, 'abbr' => 'wow', 'title' => 'righton', 'data' => $label);

I wasn't looking for ore than a hello world kinda response here. However, didn't get anything.

I was pointed to a jQuery approach being used to add accessibility to WordPress here - http://core.trac.wordpress.org/ticket/9408

This might work to just apply the appropriate tags to the calendar when the javascript is loaded. A bit harsh, but could be done.

I really don't think that having an accessible calendar is really something that we can opt out of as a community. Should we tell folks that if this is a requirement that they have to go to use WordPress - http://georgiatechcatea.wordpress.com/2007/01/16/accessible-calendars-fo...

Not easy, sure.

Not entirely within the scope of this module, possibly.

but won't fix seems a bit harsh.

Mike

First of all, I'm not sure I agree the calendar does not qualify as accessible just because the navigation isn't inside the table.

But if someone wants to find a way to fix it that's great.

One idea to play around with is creating the navigation inside the table by embedding a view of the navigation into the table. Or, because the navigation is actually the main view, create the table by embedding the calendar view into the navigation instead of attaching it. That puts all the parts into the same theme. That would still require a lot of refactoring of the code, but would probably be the most workable solution that doesn't require changes to the way Views works.

BTW, reading through the links above, the navigation is not the accessibility problem, we just need to add information to the row and column headers, which is totally doable without messing around with the problems getting the navigation into the same view.

If that's what everyone really wants, that should be an easy fix.

Doh. OK I see that they have a 'next' link in the header, now I'm with you. Sorry! I was not reading this carefully enough.

We we can start by getting the column and row headers in there. To get the information needed for the 'next' and 'prev' link we just need to use some of the same functions used to create the navigation, we don't actually have to MOVE the navigation into the table.

That's my understanding Karen. Thanks for looking into this. thePanz any further clarification needed?

Will be great to have more accessible calendars for sure.

Karen, if you want to have someone test the calendar who uses a screen reader, please let me know. I can try to track down a screen reader.

Mike

BUMP:
Any traction here? or is this stalled?

Thoughts on D7?

I'm going to close this issue until there is a clear example where moving the navigation into the table actually improves things for users of assistive technology. Existing links don't verify this actually makes a difference.