Portuguese Accessibility Tester

Remote from: Europe
Annual salary: Undisclosed
Salary information is not provided for this position. Check our Salary Directory to estimate the average compensation for similar roles.
Department: QA & Testing
Employment type: Full Time,
Job posted: 26 Jul 2026
Apply before: 26 Aug 2026
Experience level: Entry-Level
Junior
Views / Applies: 13 / 1

About company

About Welo Global

Smarter AI. Better Business.

Computer Software
2006

Actively Hiring

AI Summary

Welocalize is hiring a Portuguese Accessibility Tester to validate the language-specific accessibility of localized digital content. The role involves checking that accessibility elements are accurate and functional in Portuguese, using assistive technology like screen readers. Testers must have native-level Portuguese, hands-on AT experience, and knowledge of WCAG 2.1/2.2 and EN 301 549. Work is project-based with clear scopes, requiring independent testing and defect reporting via tools like Jira.

Role DNA

Job Complexity

Easy Hard

Pace & Pressure

Relaxed Fast-paced

Autonomy Level

Guided Full Ownership

Communication Load

Independent Highly Collaborative

AI Insight The role requires a combination of linguistic fluency, technical accessibility knowledge, and experience with assistive technologies, but it is project-based with clear guidelines, making it moderately difficult.

Salary Analysis

AI Insight The offered salary is not specified, but for a Portuguese Accessibility Tester in the US market, the estimated median is around $50,000. This is typical for specialized testing roles with language requirements, though rates may vary based on project volume and experience.

Core Skills Required

Portuguese Accessibility Testing WCAG Screen Reader Testing JAWS NVDA Assistive Technology Localization QA Jira

Cover Letter Sample

I am excited to apply for the Portuguese Accessibility Tester position at Welocalize. With native fluency in Portuguese and extensive experience in digital accessibility testing, I am confident in my ability to ensure that localized content is both compliant and user-friendly for Portuguese-speaking users.

My hands-on experience with screen readers such as JAWS, NVDA, and VoiceOver, combined with a deep understanding of WCAG 2.1/2.2 and EN 301 549, allows me to identify not only technical issues but also real-world usability challenges. I have a keen eye for detail and am skilled in logging defects clearly using Jira.

I am particularly drawn to this role because it combines my language skills with my passion for accessibility, ensuring that digital products are inclusive for all. I am comfortable working independently on project-based assignments and am adept at meeting deadlines while maintaining high-quality standards.

I look forward to the opportunity to contribute to your team and help make digital content accessible to Portuguese-speaking users worldwide.

Sample Interview Questions

Can you describe your experience with assistive technology in Portuguese, and how you would test a webpage for screen reader compatibility?

I have used JAWS and NVDA extensively to test Portuguese websites. I would first verify the language code in HTML, then navigate using only the keyboard, checking that all elements are announced correctly and that alt text is accurate and natural. I would also test with VoiceOver on macOS and iOS to cover different platforms.

How do you ensure that translated content remains accessible after localization?

I check for mixed-language content, verify that HTML lang attributes are correct, and review multimedia elements like captions and audio descriptions for synchronization and natural language. I also test hidden text and error messages to ensure they are properly exposed to assistive technology.

Describe a time you found a critical accessibility bug and how you reported it.

I once found that a button labeled 'Submit' in English was translated but the label was truncated in Portuguese, causing screen readers to announce incomplete text. I logged the defect in Jira with WCAG 2.1 reference, attached a screenshot, and classified it as critical. I then participated in a review call to discuss the fix.

What are the key differences between WCAG 2.1 and WCAG 2.2, and how would they apply to a Portuguese language website?

WCAG 2.2 adds new criteria like Focus Not Obscured and Dragging Movements, which affect interactive elements. For a Portuguese site, I would ensure that focus indicators are visible and that drag-and-drop functions are also operable with keyboard and assistive technology, considering the language's syntax and layout.

How do you stay updated on accessibility standards and assistive technology changes?

I follow the W3C Web Accessibility Initiative, participate in online forums, and regularly test with the latest versions of JAWS, NVDA, and VoiceOver. I also take courses on platforms like Deque University to keep my skills current.

About Welocalize

Welocalize, a Welo Global brand, serves localization teams through AI-enabled multilingual content solutions that enable enterprises to operate and scale globally. Welocalize combines AI, automation, and human expertise to support enterprises in more than 300 languages, enabling accurate, culturally aligned, and compliant multilingual content at scale.

About the Role

Welocalize is expanding its network of accessibility testers to validate the language-specific accessibility of localized digital content: web pages, applications, and documents.
You will serve as a native-language expert reviewer, confirming that accessibility elements not only survive translation but are accurate, understandable, and functional in the target language.
This role requires fluency in the target language, hands-on experience with assistive technology in that language, and familiarity with Digital Accessibility standards and guidelines such as PDF/UA, WCAG 2.1 & 2.2, and EN 301 549 to complement accessibility testing done internally.
Work is assigned on a project basis. You will receive a defined scope, a testing checklist, and access credentials. Findings are reported in a structured defect log and specific bug tracking system.

What You Will Do

The actual scope will vary by assignment, but the general extent of this role is outlined below.

Language Validation: Confirm correct language codes in HTML and PDF metadata, and identify mixed-language content missing proper declarations.
In-Language Screen Reader Testing: Using native-language screen readers (JAWS, NVDA, VoiceOver, TalkBack, or Narrator), review translated accessible text — including hidden elements, tooltips, error messages, alt text, and UI labels — for accuracy, natural phrasing, and clarity when read aloud.
Multimedia Accessibility Review: Evaluate captions, transcripts, and audio descriptions for accuracy, synchronization, and natural language, and confirm multimedia controls are properly labeled in the target language.
Defect Reporting: Log findings with WCAG/PDF-UA references, supporting screenshots or recordings, and severity classifications; participate in review calls with the QA Lead as needed.

What We Are Looking For

Required

Native or near-native fluency in Portuguese; you are the authoritative voice on whether translated content reads naturally and is understandable.
Demonstrated hands-on experience testing digital content with assistive technology/AT.
Working knowledge of WCAG 2.1 & 2.2 AA and EN 301 549.
Ability to evaluate content from a native-speaker accessibility perspective — not just technical compliance, but real-world usability for screen reader users who speak the language.
Reliable access to relevant devices and operating systems to replicate real-world usage in the target locale.

Nice to have

Strong written communication skills in English for defect reporting and general communications.
Experience with PDF accessibility testing using PAC 3 or Adobe Acrobat Pro Accessibility Checker.
Familiarity with internationalization, localization, and translation workflows; understanding of how accessibility elements can be affected during format conversion.
Personal use of assistive technology.

Tools and Environment

Welocalize provides access credentials and a structured test plan per engagement. Testers are expected to supply their own device and assistive technology setup appropriate to the target locale.
Commonly used tools in this role include:
- Screen readers: JAWS, NVDA, VoiceOver (macOS/iOS), TalkBack (Android), Narrator (Windows)
- Browser/screen reader pairings aligned to the target locale’s most common usage patterns
- Caption and transcript review: native video players, .srt/.vtt file review
- PDF accessibility: PAC 3, Adobe Acrobat Pro (provided where required)
- Defect logging: Jira bug tracking system is most frequently used

What to Expect

Assignments are project-based with clear scope documents, test checklists, and agreed turnaround timelines provided before work begins.
Scope for each engagement will specify the exact language, content type, pages or documents in scope, and priority areas.
You will not be expected to remediate or fix issues; your role is testing and reporting.
Welocalize values feedback: if checklist items are unclear or a finding falls outside the defined scope, flag it and we will address it.

How to Apply

Click on Apply Now button and share with us the following:
- A brief introduction covering your language, screen reader experience, and accessibility background.
- Any relevant certifications (CPACC, WAS, DHS Trusted Tester, or equivalent).

Apply now >