Fork me on GitHub

Split: Accessibility  Bottom

  • Split from: http://community.zikula.org/module-Forum-viewtopic-topic-54798-start-0.htm#pid238599

    Melinda

    Steven, great post.
    Steffen, had never though of correcting typos in the Wiki as being a help, but that IS something I know how to do. icon_smile
    David, Mateo, Steffen, Steven, Igor and a number of other developers here have helped me out greatly since I started using PostNuke/Zikula. I am nowhere close to being able to design and write my own module, theme, block or whatever - much less figure out PHP. But I DO know how to break things. icon_smile And, being that my mom was an English major and pretty much beat spelling and grammar into my head, I do know how to correct typos.
    My husband, Flip, is blind. While we were talking with David one day, the "problem" of screen readers not being too happy with some of the stuff in PostNuke/Zikula, David suggested that Flip basically go through the website we have and other sites, and then make suggestions on how to make it more screen reader friendly. David has been out of contact for a little bit of time, but I think he's getting back into having the time to work on the modules, etc. I'm wondering where to send Flip's suggestions. To the module creator? To the NOC? Here in the forum? So many options.
    However, that all being said, even though we started recently with PostNuke/Zikula (with .764) and have a couple of sandbox sites up with Zikula 1.0, we can see the improvement in the CMS as a whole and the "add-ons" as well.
    All you coders, keep doing what you do so well. When a new module, theme, block, etc. comes out, I will try my dangdest to break it for you. icon_biggrin Flip is more than willing to test it for accessibility too. You can e-mail him at ke4obt@samobile.net
    Again, thanks to all of you for your hard work, sweat, tears, and loss of family time.
    Keep up the good work.

    Mickey

    Hi Mickey,

    I am easily sidetracked. You can give me all of Flip suggestions. I will make sure the information gets to where it needs to go. Catch me Skype, I am way overextended with many many things. I am trying to get back into my support role here, after being very very flaky since December. I can disappear without warning for weeks at a time. But sooner or later I will surface.

    I have started a very long post, directly related to this thread. Hope to finish it soon.

    Dave



    edited by: AmmoDump, Jul 08, 2008 - 08:24 AM

    --
    David Pahl
    Zikula Support Team
  • @David: The longer the post the lower the chances anybody reads to the end icon_biggrin
    @Mickey: Maybe you best post your findings on the forums here. We started to make the core "accessibility-ready" some years ago, but being "not directly affected" sure let us oversee (no bad joke here) things.

    --
    best regards from Kiel, sailing city

    Steffen Voss

    Member of the Zikula Steering Committee
    Read The Zikulan's Blog "If you want people to RTFM, make a better FM!"
  • *hangs head*
    Dave,
    I wasn't trying to "front" on ya. Was just trying to recognize the help you've given us and that I know you've been busy.
    The changes that we've made on our working site have all been on the .764 version. They've all been successful.
    However, now that Zikula 1.0 is out, should we sort of give up on the .764 and just go "whole-hog" with 1.0? Set up the site and let Flip do his dangdest?? icon_smile
    Many kudos to you for your patience with us.
    Steffen,
    no bad joke indeed icon_smile
    Flip said that for the most part, his screen reader reads most of the stuff to him, except mainly for the images. For example, in pnMessages, the up arrow and down arrow image files were used in 2 different places for 2 different operations - sort by sender and sort by date (up and down). The only thing we had to do to fix that for the screen reader was to change the name of the image being called for one of the operations. Then it worked like a charm. The "fix" for that would be if the dev is using 2 images like that, to have an alt text to show what that image is supposed to do or what location it's supposed to be in.
    Another example, in MembersList, at the bottom of the page, there was a caret being used as an up arrow for "previous page" and a down arrow/"V" for "next page". The screen reader just said "caret" or something else without defining where it would go up or down TO. That was fixed by Igor (since I was apparently sleeping, or at work or something). The caret/up arrow was changed to read "previous page" and the down arrow/"V" to read "next page".
    But, I agree, until Flip started using a screen reader, I was it for him. I love that silly program/system. icon_biggrin Sure does save my voice from reading page after page for him.
    Flip can use an alt-L to show where the labels should go. For example, a link only tells him "link", it doesn't tell where it goes to, if it goes to another page, another section, etc.
    I'll start another post with all the suggestions for "accessibility" problems. Where do you want me to start it? In the dev section, in the general section?? Just let me know and I'll start typing my poor little fingers off. icon_smile
    Flip can do some posting, but it is easier for him to do it as a voice message Can that be done here in the forum? I know attachments are ok, but a voice mail, basically??? It would be in MP3 format. His typing - as he puts it - he's seen chimpanzees that can type better than he can and he's been at it for a lot longer. icon_cool

    Mickey
  • If you have concrete ideas like the pnMessages example, you should report these in the project's tracker at Cozi (which is the NOC successor)

    --
    best regards from Kiel, sailing city

    Steffen Voss

    Member of the Zikula Steering Committee
    Read The Zikulan's Blog "If you want people to RTFM, make a better FM!"
  • Melinda


    Another example, in MembersList, at the bottom of the page, there was a caret being used as an up arrow for "previous page" and a down arrow/"V" for "next page". The screen reader just said "caret" or something else without defining where it would go up or down TO. That was fixed by Igor (since I was apparently sleeping, or at work or something). The caret/up arrow was changed to read "previous page" and the down arrow/"V" to read "next page".
    Mickey


    Yes, I remember, I just used the pager flexibility...

    Code

    <!--[pager show=page rowcount=$pager.numitems limit=$pager.itemsperpage firstpos=$pager.startnum posvar=startnum shift=1 txt_prev="Previous Page" txt_next="Next Page"]-->


    Maybe a topic... 'tips and tricks' because I think lot of ppl just don't know something like this exists....

    - Igor

This list is based on users active over the last 60 minutes.