Accessibility

Hello All,

 I am facing a simple and strange error in my localhost (Xampp). When i try to start the apache engine i got the follwing error message.

Error Message:

3:02:22 PM [Apache] Error: Apache shutdown unexpectedly.
3:02:22 PM [Apache] This may be due to a blocked port, missing dependencies,
3:02:22 PM [Apache] improper privileges, a crash, or a shutdown by another method.
3:02:22 PM [Apache] Press the Logs button to view error logs and check
3:02:22 PM [Apache] the Windows Event Viewer for more clues

As much as I believe in fixing accessibility problems at the source, we still need more contributors who have a better understanding in web accessibility.

This is a great crowd funding campaign organized by the great folks at http://knowbility.org

Accessibility training should be intensive, and this team has the experience of delivering great trainings through AccessU but can broaden their impact if it is able to be done online.

This is a general wiki to discuss things related to Drupal's accessibility during DrupalCon (and related sprints).

What Are We Doing?

Presentation on Accessibility

The Accessible Experience: Designing for Everyone, by dcmouyard
Wednesday · 10:45-11:45
Room 19 - Lullabot | 4th floor

BoF Session

Drupal 8 Accessibility
Wednesday · 03:45-04:45
Room 8A - JustDigital | 3rd floor

Drupal 7 still remains the most accessible open source CMS available. The changes that the community began implementing in 2008 to improve accessibility for the entire user interface (public, content editor, administrator and developer) has still not been matched by any other piece of web software (open source or proprietary). By focusing accessibility efforts on improving Core, we are able to fix accessibility problems by default regardless of what themes, or extensions are used in any given implementation.

Hi all. Am looking for resources related to making Views filters accessible when they are exposed in a block and where AJAX is enabled.

Are there any examples or how-to resources out there that document what it takes to modify the default views templates to enable aria-live etc. in a way that would allow these features to be turned on and meet WCAG?

I saw a couple of related issues about D8, but am looking specifically for a technique that might be usable on a present-day D7 project.

Thanks!

I mentioned in the recap of the Green by 2014 initiative that I've been working to organize a follow-on effort to continue building our automated accessibility testing tools. I just published the announcement at the following URL.

https://medium.com/p/c1a3a275fe1a

Here's the title and sub-title:

"Open-source accessibility testing for the modern web"

"Collaborating to improve Quail, an open-source web accessibility testing tool that will integrate with existing continuous integration processes and developer toolchains."

I had a lofty goal: to get us down to zero test failures on the daily run of Accessibility module against Drupal 8 core.

I knew in my heart that this was an extremely unlikely goal to reach. We faced many obstacles including:

• A broken TestSwarm module for Drupal 8 that prevented our daily test from running.
• A inadequately documented set up process for the Accessibility module, the TestSwarm module and the Quail library.
• A well curated list of issues to work on.

Hi All, I'm a total newbie to the group but hoping for a bit of help.

I volunteer with a great non-profit integrated dance organization here in Canada where people with and without disabilities come together to create and perform.

We're looking at a complete website overhaul in the new year and need to choose a CMS. An acquaintance of the organization is most familiar with (and suggesting) Drupal due to accessibility for people with disabilities.

Drupal 8 will meet higher standards of access than our previous releases. As developers and site builders, we continue to incorporate new techniques and tech access technologies into Drupal.

For the International Day of People with Disabilities (IDPwD) on December 3rd, 2013, let’s celebrate some of the individuals who have helped us achieve these improvement. This list is by no means exhaustive and many more individuals have contributed code, testing and documentation than are listed below.

We have 4 more weeks to get our automated testing suite, QUAIL and the Accessibility module, working and down to zero test failures.

Contributing to the Green by 2014 effort most critically needs assistance fixing the Testswarm module so that our automated (QUAIL) tests will run again on a daily basis.

This is a short update for the Green by 2014 effort to establish an automated accessibility testing suite for Drupal.

Executive summary

Drupal Accessibility triage meeting to action the results of the Minnesota evaluation is Scheduled.

The meeting will be held over skype on:
28th October
San Fransisco 7:45pm
EST 10:45pm
2nd September
India 8:15am
Convert to your time zone!

The meeting will be on Skype. Please share your skype id at rajaram(dot)shyamala(at)gmail(dot)com or share it with me on IRC drupal-accessibility.

Review the results of the Minnesota evaluation at https://groups.drupal.org/node/311503

My plan to do weekly updates about the Accessibility module was quickly derailed by an injury, but I'm slowly getting back on the saddle and off pain meds, and wanted to let everyone know what's been going on the past few weeks.

First, the Drupal 8 branch of the module is now in feature parity with the Drupal 7 module. This means that we are well on our way of having a full release by the time Drupal 8 comes out. Because of better entity APIs and WYSIWYG in core, the 8 branch is 1/3 lighter than the 7.x branch.

Hi there,

I hope this is the appropriate forum for my question and if not my apologies.

I'm creating a Drupal 7 site to manage academic course content for various 3rd level modules I must deliver over the next year. I had envisaged a menu structure which would react to keyboard events as well as "on-hover" ones. In other words, when the students click on the course title, a submenu would appear giving course specific information.

The Current implementation of element provides a button role. Not sure if this is sufficient from the understandings at: http://accessibleculture.org/articles/2012/03/screen-readers-and-details....

As is not accessible on all browsers,To polyfill for accessibility we need to:

1) set tabindex ="0" - make it keyboard focusable
2) assign ARIA role button -> DONE!
3) aria-expanded attribute that changes based on state
4) non-summary content to be hidden by using dispaly:none when elements are collapsed

Drupal Accessibility triage meeting to action the results of the Minnesota evaluation is Scheduled.

The meeting will be held over skype on:
15th September
San Fransisco 7:45pm
EST 10:45pm
16th September
India 8:15am
Convert to your time zone!

The meeting will be on Skype. Please share your skype id at rajaram(dot)shyamala(at)gmail(dot)com or share it with me on IRC drupal-accessibility.

Review the results of the Minnesota evaluation at https://groups.drupal.org/node/311503

Do you know of modules to add a slideshow to a D7 site that are accessible to screen reader users? Thanks.

Hello everyone,

The UX/UI Summit at BadCamp is back again for it's second year. And boy, are we excited or what! This year's summit is going to feature two tracks: 2 workshops and 5 sessions with the goal to educate the community in the matters of UX (note: accessibility is also a part of UX!) More information: http://2013.badcamp.net/events/drupal-ui-ux-summit

If you are planning to attend BadCamp, we would strongly encourage to attend the event.

Weekly scrum call for folks working on accessibility issues in Drupal core and contrib. Discuss what you did last week & your plan for the coming week!