I am recommending that we add Andrew Macpherson to the Maintainers.txt
I remember first talking to Andrew at DrupalCon London when he came to the Accessibility BoF then. It was hard to forget meeting him that first time because he was mostly blue, but also because he was clearly interested in this topic.
Andrew's been active in quite a few accessibility issues in Drupal 8 and is contributing some great work on this issue.
Accessibility is a big issue and we need more champions. We have a goal of meeting WCAG 2.0 AA for Core and we're good, but there is still a lot of work to do to get there.
Managing the issue queue is important, but so is educating the community. I do think that Andrew can and is willing to play a role in educating the Drupal developers about the importance of accessibility in Camps & Cons in Europe.
Especially with the new release cycle it will be important to see that new features are not introducing barriers to people with disabilities.
Comment | File | Size | Author |
---|---|---|---|
#30 | add_andrew_macpherson-2725947-30.patch | 430 bytes | John Cook |
#28 | add_andrew_macpherson-2725947-28.patch | 490 bytes | John Cook |
#25 | andrewmacpherson2maintainers-2725947-25.patch | 430 bytes | naveenvalecha |
andrewmacpherson2maintainers.patch | 490 bytes | mgifford | |
Comments
Comment #2
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedSubscribing ;-) Thanks for asking me on board Mike.
Comment #3
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedBumping the status - I don't know what the process is for this kind of issue, but I guess it needs to have a status which will attract attention :-)
I've written some of my thoughts about future accessibility directions in D8 and D9 in the accessibility group on g.d.o
I was really stoked when Mike asked if I'd consider becoming a core maintainer. I have barely stopped bouncing around my home.
Comment #4
Wim LeersAndrew has also been contributing to for example the RefreshLess module in a very constructive, productive way — the same way we work in Drupal core. It's been a pleasure working with him on that.
So, +1.
We'd be silly not to let him bounce around Drupal core's accessibility issues then :)
Comment #5
mgiffordI love what Andrew wrote up here about the future of Drupal 8 & 9 accessibility - https://groups.drupal.org/node/511349
Thanks Wim!
Comment #6
cmcnally CreditAttribution: cmcnally commentedAbsolutely agree. Thanks Mike. Wholeheartedly agree with the points that Andrew raises regarding Inline Form Errors, Drupal.Announce, Tabbing Order, and ARIA properties for vertical tabs. Yes, we need to keep innovating on this! You've definitely got my +1!
Comment #7
cehfisher CreditAttribution: cehfisher commentedWe need more people like Andrew to help further accessibility in Drupal +1
Comment #8
Anonymous (not verified) CreditAttribution: Anonymous as a volunteer commentedAndrew's contribution to Drupal's accessibility capabilities is invaluable, empowering everyone no matter what their abilities to be able to make full use of the internet.
Plus he made a Druplicon outfit - what more needs saying?! ;)
+1
Comment #9
stella CreditAttribution: stella at Annertech commentedJust wanted to add my +1. He's been inspirational at advocating accessible designs and user experiences at Annertech, and I think he would be a great addition to further accessibility in Drupal core.
Comment #10
timmillwoodI support this under one condition!
@andrewmacpherson must submit a core conversation about Accessibility to DrupalCon Dublin. (Disclaimer: I am on the track team for core conversations.)
Comment #11
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedYep a core conversation is a good idea. Do they go through the normal session submission process? It's not open yet for Dublin, but I'm certainly intending to go.
The g.d.o post mentioned earlier has some of our ideas. I think the foggiest a11y outlook ahead of us has to do with adopting a front-end framework, for progressive decoupling and more application-like behaviour. Whatever happens there will involve a lot of refactoring, so the challenge will be to maintain our current level of a11y (at least) - though I expect there will also be more opportunities to innovate around accessible widgets and notifications.
Comment #12
mgifford@timmillwood - nice!
Comment #13
timmillwood@andrewmacpherson - yes, core conversations go through normal session submissions, they should be opening oven the next few weeks.
Comment #14
xjmAwesome, thanks @mgifford for the recommendation and @andrewmacpherson for being willing to take this on! Sounds like he will be an excellent addition as an Accessibility topic maintainer.
Before we add this, @andrewmacpherson, can you confirm that you're comfortable with the core governance policy, particularly the topic maintainer responsibilities? (We already have the signoff of another topic maintainer from @mgifford.)
Setting to NR for that confirmation. Thanks!
Comment #15
xjmOh also, just a reminder for committers: This is for a topic maintainer role, so per https://www.drupal.org/contribute/core/maintainers#decisions (see point 11) this should be assigned to Dries once it is RTBC again with that confirmation.
Comment #16
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedRe: #14 - Yes, I'm happy with the core governance policy. I've read though it all a couple of times since this issue was opened.
Comment #18
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedThe bot is happy again.
Comment #19
xjmYay! Thanks @andrewmacpherson.
Comment #21
daffie CreditAttribution: daffie commentedComment #22
naveenvalechasetting to RTBC as was in #18
Comment #25
naveenvalechaThis needed a reroll after #2744881: jhodgdon stepping away from MAINTAINERS.txt
Comment #26
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedAh, thanks naveenvaalecha. Back to RTBC then...
Comment #28
John Cook CreditAttribution: John Cook at CTI Digital commentedRe-rolled patch.
Comment #30
John Cook CreditAttribution: John Cook at CTI Digital commentedAnd again.
Comment #31
John Cook CreditAttribution: John Cook at CTI Digital commentedComment #32
mgiffordLooks good again.
Comment #34
xjmComment #35
xjmComment #38
naveenvalechaTestbot fluke, back to RTBC
Comment #41
naveenvalechathe above are random updatepathtestcase failures
Comment #42
Dries CreditAttribution: Dries commented+1 from me! Feel free to commit this patch, or I can do it later this week.
Comment #45
xjmYAY! Thanks @Dries!
And welcome @andrewmacpherson!
Committed 3f1ad36 and pushed to 8.2.x and 6046b58 to 8.1.x. Also adding @andrewmacpherson as an issue maintainer at https://www.drupal.org/node/3060 (you'll now have lots more options in the assigned field!) and as a member for https://groups.drupal.org/core (to be able to post announcements about the topic to the core list).
Comment #46
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedThanks everyone!
I always wondered how that worked!
Comment #47
markconroy CreditAttribution: markconroy as a volunteer commentedWell done Andrew. This is great news.
From working with you over the last three years at Annertech, my knowledge of and consideration for accessibility has increased massively, so much so that I have you mentioned as a mentor on my profile.