Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesChoose a WordPress theme expert by checking their experience with your site’s specific theme architecture, asking for a concrete testing and documentation plan, and probing how they handle security, accessibility, scope, and handoff. WordPress does not certify or endorse individual theme experts, so assess the candidate’s work and explanations directly.
1. Match their experience to your theme and project
Start with the theme your site actually uses and the work you need done. WordPress supports both block and classic themes: block themes are built mainly with HTML and a configuration file such as theme.json, while classic themes commonly use PHP, JavaScript, and CSS. The WordPress Theme Developer Handbook explains the distinction.
As an Amazon Associate I earn from qualifying purchases.
Ask the candidate whether they have worked with your theme type, the relevant templates, and features like the ones in your brief. A generic claim of “WordPress experience” does not establish that they have handled your particular theme architecture or project scope.
- Ask for public examples or a walkthrough of work they are permitted to share.
- Ask what they personally handled on a similar project and which parts involved other people.
- Ask how they would approach the specific templates or features you need changed.
Treat a portfolio as a starting point for discussion, not automatic proof that the candidate completed every part of each project. WordPress’s official materials do not define a hiring credential or approved-provider list.
2. Ask for a specific testing and documentation plan
A credible candidate should be able to explain what they will test, when they will test it, and what notes or evidence they will hand over. WordPress release guidance calls for thorough testing, including with content, and proper documentation. It also points to the Theme Check plugin as one way to check a theme against current theme review standards; a passing tool result alone does not establish overall quality. See Releasing Your Theme.
For your project, discuss tests relevant to the changes, such as:
- Changed templates and pages, using more than one kind of content where appropriate.
- Layouts at relevant screen sizes and in supported browsers.
- Keyboard use for navigation and controls.
- What the candidate will document about the changes and any remaining limitations.
Ask for the proposed checks in plain language. Automated checks can help identify issues, but no single check proves a theme is correct, secure, accessible, or visually sound.
Free tools Windows power users keep installed
One-click scans. No signup required.
3. Probe how they think about theme security
Ask the candidate to explain how they validate and secure theme code, including how they handle untrusted values, and how they would investigate a suspected vulnerability. The WordPress Theme Handbook security guidance provides a technical basis for that discussion.
Also ask what they would do if they discovered a vulnerability. WordPress says theme security reports should be handled confidentially through the appropriate reporting route. A responsible response is not to publish details of a suspected flaw before it has been handled appropriately; see WordPress Theme Review Guidelines.
4. Test accessibility claims with practical questions
Do not treat the label “accessibility-ready” as a guarantee that a theme meets WCAG AA. WordPress says the designation means a theme meets the Theme Review Team’s basic requirements, not that it meets WCAG AA. The Theme Review accessibility guidance offers useful prompts for a practical discussion.
Rank #4
Ask the candidate to demonstrate or explain how they check:
Recommended Free Tools
- Whether navigation and controls work with a keyboard.
- Text contrast and the structure of headings and other content.
- Whether content and functionality remain available when text is resized.
- How they check the experience across different screen sizes.
The cited WordPress handbook guidance includes a 4.5:1 contrast ratio for ordinary text under its WCAG 2.0 discussion and says content and functionality should remain available when text is resized up to 200%. These are specific checks, not a complete accessibility audit.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.5. Define scope, responsibilities, and handoff
Before work begins, agree on what is included and excluded, which assumptions affect the estimate, how changes will be approved, and what you will receive at completion. Ask how the candidate distinguishes visual presentation from functionality that should remain if you change themes later.
That distinction is reflected in WordPress.org’s rules for themes submitted to its directory: directory themes must not bundle plugins or non-design functionality such as forms, and the rules identify shortcodes, custom post types, and custom blocks among prohibited theme contents in that submission context. Use the Theme Review Guidelines to prompt a technical conversation; directory-submission rules are not universal contract terms for every private project.
Discuss practical project safeguards as part of your agreement, including who controls hosting and administrator accounts, what access the expert needs, how backups and rollback will be handled, and when project access will end. These are client-side topics to settle with the candidate, not requirements established by WordPress’s theme guidance.
Compare candidates on evidence, not confidence
Use the same questions for each candidate, then compare the substance of their answers. This is a practical decision framework, not an official WordPress scoring rubric.
| What to compare | Evidence to look for |
|---|---|
| Relevant experience | Examples and explanations tied to your theme architecture, templates, and requested work. |
| Testing and documentation | A specific plan for checking changed pages and handing over useful notes. |
| Security and accessibility | Clear explanations and practical demonstrations, rather than unsupported assurances or labels. |
| Scope and handoff | Defined deliverables, dependencies, approval process, exclusions, and completion materials. |
Prefer the person who can explain trade-offs and boundaries clearly over the person who offers only broad assurances. Official WordPress guidance can help you evaluate technical answers, but it does not certify a candidate or guarantee the outcome of a hiring decision.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
