Make WordPress Accessible

Updates from December, 2012 Toggle Comment Threads | Keyboard Shortcuts

  • Jen 5:40 pm on December 24, 2012 Permalink

    Team Rep Voting Results 

    When only one active team member votes, it’s tough to think there’s much interest in team repping. 🙂

    So, here are the results, but the low turnout begs the question of if this is an active team, or if we should be thinking about rolling in to existing groups (like UI is rolling into the main core group and designers will be embedded in all the other teams as well with a central design “interest group” vs a “responsible-for-this-product group”). But before we have that conversation, here are the voting results.

    Only three people actually voted.
    Please describe your role with the accessibility team.

    • 1 – I don’t participate yet, but want to
    • 1 – I am not currently active in the group, but have been in the past
    • 1 – I am active in the group, and have been within the past 3 months
    • 0 – I don’t plan to get involved

    Describe your accessibility team activity.

    • 1 – I contribute accessibility info to the Codex
    • 1 – Other Option (“Working on developing accessibility-ready tag for theme directory”)
    • 1 – I don’t contribute to the accessibility team activities
    • 1 – I participate in plugin and theme reviews for wordpress.org directory
    • 1 – I contribute to discussions on the blog
    • 0 – I contribute to core patches

    1st rep – 3 votes for Esmi
    2nd rep – One for Joe, one for Graham, one for Andrew Ozz

    Neither Esmi or Graham voted. Esmi also proposed that she step back to the support role in the previous thread about team reps. The comment in that thread by Graham made it sound like he equates accessibility team with core accessibility. In short, it doesn’t feel particularly teamy up in here. An active team should have enough going on that each week there’s stuff to report. That’s the team rep job — to write the weekly reports on activity and issues facing the team.

    Given the givens, my inclination is to ask Esmi to remain the point of contact for this group, and once we’re past the winter holidays, to work out what exactly falls within the scope of this group/what the product it’s responsible for is, and go from there to a decision around whether this is in fact a distinct project team or whether it’s an interest/skills group that contributes to multiple project teams (like design will be). If it’s decided then that it is in fact a distinct project team, we’ll figure out what to do about the lack of participation in the team rep voting re 2nd slot. Sound okay?

    • Cyndy Otty 6:31 pm on December 24, 2012 Permalink | Log in to Reply

      I reiterate my last comment of stating I am very against the idea of folding Accessibility into another group. While I understand the lack of activity here and all playing into that idea, I have a lifetime of experience dealing with similar issues being folded into others and the results are generally not favorable.

      Also, I can only speak for myself, but I didn’t vote because I was waiting to see if Graham would respond to Esmi about being the second . . . and then I realized voting was over and I had missed my chance. I would have voted for Esmi and Graham, fwiw.

    • Joe Dolson 10:18 pm on December 24, 2012 Permalink | Log in to Reply

      I would have voted for Graham, had he responded, but didn’t want to be volunteering somebody without their indication of interest. The low voter turnout had a lot to do with the lack of any expression of desire to actually be the team leader – there was little idea who to vote for.

      I think it’s a very fair question about the role of this team: is accessibility a separate group, or is it an essential part of all groups? But if it’s an essential part of all groups, are there enough people involved to be able to effectively contribute to all groups?

      I think it’s crucial that accessibility be a voice in core, UI, and theming: but I’m afraid that the issues for accessibility get overlooked in those larger environments.

      Regardless, having a post-holidays discussion of the future role of The Accessibility team seems like a practical choice to me.

    • Rian Rietveld 8:12 am on December 26, 2012 Permalink | Log in to Reply

      Sorry for not responding earlier. Esmi and Graham both would have my vote. If Esmi would like the job, that’s totally ok with me. I agree with Cindy: I am very against the idea of folding Accessibility into another group. But I also know this means a real commitment from us as a group.
      So: I don’t participate yet (that much) but in the next year I will do my best to add to the discussion and research.

    • N Johnson 9:59 pm on December 26, 2012 Permalink | Log in to Reply

      I create small volunteer WordPress sites. I have your feed in my RSS page, but find this feed frustrating and don’t pay much attention to it. My day job has nothing to do with WordPress but in my role as Front-end developer I am responsible for accessibility I am used to having much more control over CSS, jquery etc than plugins allow, unless I dig which I often do.

      I haven’t read the entire thread, so if someone else has thought of this I apologize, but has anyone thought of why each image requires a “title” tag but not an “alt”. Why not merge them into one required “Description” field, that spits out alt and title.

      • Joe Dolson 12:24 am on December 28, 2012 Permalink | Log in to Reply

        Well, this is off topic for the current thread, but I can give you a partial answer: it is not a good solution to combine title and alt, largely because there are situations where those two fields should be different. In fact, in most situations, they should be different. Requiring the alt attribute is problematic because purely decorative images should have blank alt attributes. In many cases, neither the title attribute nor the alt attribute would have any content — and this would be considered accessible.

        Practically speaking, there should be a required title field for the image, so that there’s a title characteristic saved with the record. But then it should be a separate title from the one used in the image when inserted. From an interface standpoint, however, that’s confusing as hell…as a result, it really needs to be a content developer’s responsibility to handle appropriate title and alt attribute usages.

    • GrahamArmfield 9:04 am on December 29, 2012 Permalink | Log in to Reply

      Apologies for not taking part in the vote, I have been really busy with client work just recently which obviously has to take precedence. But I have to admit I must have forgotten to check the box to receive follow up comments – so the date just slipped by.

      I’m flattered to receive some (real/virtual) votes and sorry that people were waiting round for me to reply. It’s academic now but I would not have been able to commit at this stage to being a rep at this time. I’m hoping to get more active in the future so maybe next time I’ll feel able to put myself forward.

      Agree that we should debate where this forum should go and what’s within its remit.

      I hope you all had a good Christmas time.

    • elfin 4:11 pm on December 30, 2012 Permalink | Log in to Reply

      I didn’t vote, but that was deliberate – I don’t know others posting here well enough to make an informed decision about their suitability for the role in question. So I could only vote for esmi. Joe, I wasn’t sure if you wanted to help out to that extent or you would have been on my list.

      I wish I could step up and help out more – but my current workload prohibits that.

    • Sylvia Egger 12:15 pm on January 3, 2013 Permalink | Log in to Reply

      I voted but wasn’t very comfort about it because I don’t know who is in the #a11y group right now. I would suggest that there is a kind of “group leader” who takes the effort to communicate to the group about current task and so on. I feel a little bit lost behind.

      • esmi 3:21 pm on January 8, 2013 Permalink | Log in to Reply

        Anyone who is motivated to post or comment here could be considered to be part of the a11y group. It’s not a pre-selected a group of people as such. Jane contacted me and asked If I would initially head up the a11y initiative and I went out trying to promote it anyone who I thought might be interested. We also have cross-links with the UI and Core developer groups and are trying to set up something similar with the Theme Repo team.

        If anyone would like to become involved on a more formal basis, please feel free to contact me directly (follow the link on my username).

  • Jen 5:54 pm on December 9, 2012 Permalink

    Team Reps 

    Hello, accessibility team! It’s time to vote for team reps to communicate on behalf of the group to the other contributor groups. While there’s been some talk (mostly from me) about possibly rolling accessibility into the main core group, plugins group, etc. rather than segregating it, that’s still a discussion, not a plan. So for now we need to make sure this team is at the table.

    Esmi has been the acting rep. You get 2 slots. These folks will be responsible for reporting on the progress of the group to the other team reps via weekly updates, as well as occasional chats and such. If you haven’t seen the spiel on one of the other team blogs about how team reps/voting/terms work, the longer explanation is after the jump.

    Note: It should be people who want the responsibility. Anyone interested in being a team rep should leave a comment saying as much so people know who they can/should vote for. Voting is open until December 15, and results will be posted here once voting closes.

    Go vote!

    (More …)

    • Graham Armfield 8:45 am on December 10, 2012 Permalink | Log in to Reply

      Thanks for the notification Jane.

      When do we need to vote by? Since I’m not close in to the WordPress core I don’t know who is interested in standing as rep and who is not, so I’ll be waiting for a bit to see who expresses an interest. But obviously I don’t want to miss out on the voting.


      • Jane Wells 1:55 pm on December 10, 2012 Permalink | Log in to Reply

        As stated in the post, voting closes December 15. Anyone interested in being a rep for this accessibility group doesn’t need to be close to core, they just need to be close to what happens here in this group.

    • esmi 12:32 pm on December 10, 2012 Permalink | Log in to Reply

      I’m happy to stand again as team rep but, given the amount of Trac work you have been doing, Graham, would you like to take a stab at it?

      • Jane Wells 1:53 pm on December 10, 2012 Permalink | Log in to Reply

        There should be two reps. Worth reading the longer explanation of how terms work…. esmi+ghaham would be a good example of how it’s meant to go, with one person already familiar with the role helping the newer person learn the ropes.

    • esmi 7:10 pm on December 10, 2012 Permalink | Log in to Reply

      OK. Re-phrasing…

      Graham: Would you like to take over as lead rep with me as support?

      • Jane Wells 7:14 pm on December 10, 2012 Permalink | Log in to Reply

        Just to re-state what’s in the longer backstory part, the intention with 2 is that one serves as primary rep the first 3 months of the 6-months term, then swaps to the backup role for the 2nd half of it while the other person takes the lead. It’s not written in stone or anything, but that’s the intention.

    • Cyndy Otty 6:17 pm on December 12, 2012 Permalink | Log in to Reply

      Well, first, let me extend a big thank you to esmi for her work. 🙂 If I actually felt like I knew what I was talking about technically, I would totally volunteer to help, but unless I’m misunderstanding the duties, it sort of sounds like having that expertise would be necessary. (I think Graham would be a great second, though. Just saying.)

      And, for the record, I don’t think wrapping Accessibility in with Core is a good plan. Having a dedicated section solely for Accessibility does split things, yes, but it also speaks to the fact that it is actually important in and of itself and (hopefully!) a priority.

    • Joe Dolson 7:06 pm on December 13, 2012 Permalink | Log in to Reply

      So…I’d like to vote…but I’m hoping to know whether Graham is interested in becoming a team rep before voting – Graham, do you have an interest in that? I’m willing to consider it, if you’re not, although I’m a little uncertain about the time…

    • Sveta 4:10 pm on December 21, 2012 Permalink | Log in to Reply

      Can also all WP videos be accessible via good quality captions, too? I notice that none of videos on the WordPress.tv are accessible. As one of hundreds millions of deaf and hard of hearing people around the world, I cannot understand anything said in the videos. YouTube auto captions are not the “final” product – they need to be cleaned manually or replaced by professional transcripts to make it 100% error free, include proper punctuation, speaker identifications, sound descriptions, etc. Our needs are not to be ignored, either. Thanks!

      • Jane Wells 4:21 pm on December 21, 2012 Permalink | Log in to Reply

        This has no bearing on the topic of the post — in the future, please keep comments relevant.

        We have attempted working with subtitling projects to handle captioning of wordpress.tv videos, but the third-parties always seems to have issues that we can’t get around (or at least haven,t been able to as yet), largely because we don’t have any contributors familiar enough with Flash programming.

        This is an issue for the wordpress.tv committee, not the code accessibility team. WordPress.tv is currently being managed by the Events team at https://make.wordpress.org/events.

  • Joe Dolson 6:49 pm on December 5, 2012 Permalink  

    Just updated the WP Accessibility plug-in page to provide extensive information about what problems the plug-in solves and why. I also included links to important relevant documents on each item.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar