No Coding Skills, Real Contributions: My WP Credits Story

Hi, I’m Ania! This is my final report for the WP Credits program. Over the past few months, I supported the accessibility side of the WordPress community, focusing on testing open Gutenberg editor issues and exploring Theme Review. This report summarizes what I worked on, what I learned, and how this experience shaped me as a contributor.

Teams and Projects I Contributed To

I worked primarily on accessibility-related testing within the Gutenberg project, verifying whether reported editor bugs were still reproducible in the current version. I also explored the Theme Review team, drafting a Trac-style review comment focused on keyboard navigation.

Learning Resources

I started by learning practical accessibility testing methods, including keyboard-only navigation, and browser tools like Lighthouse and the WAVE extension. My mentor, Magdalena Ślęzak , helped connect me with the Accessibility community, and I also worked with Shiva on Theme Review topics.

Challenges and Solutions

My biggest challenge at the start was simply figuring out how to contribute without any coding skills – many “Good First Issue” labels on GitHub still assumed JavaScript knowledge. I solved this by learning to distinguish between issues that needed code and ones that just needed testing and confirmation, and by focusing specifically on reproducing and reporting bugs rather than fixing them.

Another challenge was setting up a proper test environment (installing the Gutenberg plugin, creating test posts with specific blocks) to accurately reproduce reported behavior. I worked through this step by step, testing carefully before writing up each result.

My Contributions

GitHub Issue #22056: Tested Audio block autoplay behavior – confirmed the originally reported bug could not be reproduced in the current Gutenberg version, likely due to browser autoplay policy changes. https://github.com/WordPress/gutenberg/issues/22056
GitHub Issue #10854: Tested the empty Cover block on the frontend – confirmed the bug is still reproducible after 7+ years, rendering as a black box. https://github.com/WordPress/gutenberg/issues/10854
Trac ticket #27753: Drafted a theme review comment on keyboard navigation. https://themes.trac.wordpress.org/ticket/27753#comment:1

Key Takeaways from WP Credits

WP Credits taught me that you don’t need to write code to make a meaningful contribution – a clear, well-documented bug report is just as valuable to maintainers as a pull request. I also learned that the WordPress community is genuinely welcoming to newcomers with no technical background, as long as you’re willing to ask questions.

New Skills Gained

Technical: reproducing and documenting bugs on GitHub, formatting structured test reports (date, version, browser, OS), basic accessibility testing (keyboard navigation, screen reader awareness)
Soft skills: asking for help clearly in community spaces like Slack, writing precise and objective bug descriptions, patience with long-standing, unresolved issues

Personal Reflections and Next Steps

I was surprised by how much a non-coder can genuinely contribute to a project like Gutenberg – testing and reporting bugs turned out to be real, valued work. Going forward, I plan to keep testing open issues, especially ones related to accessibility, and to continue exploring Theme Review with support from my mentor and Shiva.