Closed sidion closed 10 years ago
having a separate accessibility document is likely a very good idea, my only comment would be that the addition of this request is a request action for attendees to facilitate accessibility. So it is a statement of conduct not necessarily of policy. Just a thought though.
-1; in my opinion, this is not appropriate for the code of conduct.
(+1 on having an accessibility policy however)
I agree with Mark: :-1: to merging this pull request, but :+1: and :star: to @sidion for proposing the idea. Perhaps raise the issue on the code4lib mailing list and see if you can generate some momentum?
Leaving the issue open for the time being so the community has more time to discuss this.
IMHO, this would be a good addition to the How To Plan A Code4LibCon page: http://wiki.code4lib.org/index.php/How_To_Plan_A_Code4LibCon -- and I agree with deborahgu: it should be part of a total accessibility policy. There is already a mention of the Code of Conduct on that page, but it would be good to make it an actual link instead of just a mention, and make it part of the broader context reducing barriers to participation of all kinds.
If there's a consensus of having an accessibility policy, I'd be happy to volunteer to write a rough draft that could then be thrown to the wolves. :)
I'm in favor. As a conference planner (of another conference), I was frustrated by knowing that I SHOULD be asking accessibility questions but not knowing what they WERE - I'd love to see code4lib have a policy providing that sort of guidance so we can all up our game. On Dec 1, 2013 1:08 PM, "Deborah Kaplan" notifications@github.com wrote:
If there's a consensus of having an accessibility policy, I'd be happy to volunteer to write a rough draft that could then be thrown to the wolves. :)
— Reply to this email directly or view it on GitHubhttps://github.com/code4lib/antiharassment-policy/pull/42#issuecomment-29579038 .
:+1: to that, @deborahgu! Great!
+1 from me as well. @deborahgu, I don't think we really need consensus to develop a draft policy, although we might want some sort of acceptance process once a draft exists.
@anarchivist: Proposing a strawdog acceptance process: 1) share draft with mailing list; 2) incorporate feedback; 3) request +1/-1s; 4) put into place (e.g. plug into conference planning procedures)?
Sounds fine to me.
@deborahgu: I wouldn't mind getting in on helping to draft it
Great! @deborahgu & @arty-chan: can y'all create a repo under the code4lib GH organization? Be happy to hook that up if not.
I don't think either of us are members of the org, @mjgiarlo - so it would be awesome if you could create it to get us started.
OK, done:
https://github.com/code4lib/accessibility-policy
And I gave you all direct push/pull access: @sidion @anarchivist @thatandromeda @Arty-chan @deborahgu @escowles
Though forking the repo into your own accounts and contributing via pull request has been a useful community governance mechanism, so y'all may wish to avoid direct pushes.
Closing this issue now, though feel free to comment is there are loose ends. Thanks much, @sidion, for getting this started!
Adding a request to improve accessibility for in person events