QA & Accessibility Lead, (Senior Consultant, Engineering & Technical Services)

We need to output HTML fragment with sections:

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job posting. First, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. We need to preserve all substantive info. Let's extract sections. The posting starts: "Job Requirements QA & Accessibility Lead (Senior Consultant, Engineering & Technical Services) At Fearless, we are seeking a QA & Accessibility Lead as part of our Senior Consultant, Engineering & Technical Services career path to support the modernization of a large-scale public-facing government website. This role will lead both quality assurance and accessibility across the Drupal implementation, ensuring the solution is functional, reliable, accessible, and ready for production. The QA & Accessibility Lead will own testing strategy across design, development, content and data migration, and release. This person will lead accessibility testing and remediation, functional and regression testing, migration validation, automated testing, defect management, UAT support, and production-readiness validation. They will work closely with designers, developers, content teams, and government stakeholders to integrate quality and accessibility throughout delivery rather than treating them as final-stage activities. This is a fully remote role. At Fearless, this Senior Consultant collaborates with cross functional teams to align the technical vision, implementation, and quality of software systems across development, reliability, testing, and operations. This role will possess the skills to be able to bridge business objectives with technical execution in software development, infrastructure, security, and testing at an advanced application level of proficiency. The Sr. Consultant role will work on projects that allow them to ensure scalable, secure, and reliable solutions while mentoring engineers, fostering collaboration, and aligning stakeholders with product and project goals." Then "Fearless Your Responsibilities In This Role" then bullet list. Then "Fearless Impact The Impact You Will Create in this Role:" then bullet list. Then "Fearless Customer Impact" bullet list. Then "Work Experience Project Skill & Experience Requirements" then list of requirements. Then "Preferred Experience" list. Then "Fearless Skills And Competencies" list. Then "Required Level Of Proficiency Advanced Application: ..." Then "Physical Requirements" list. Then "Benefits Life at Fearless" paragraph. Then "Compensation At Fearless" with salary range. Then "Benefits At Fearless" paragraph. We need to map to sections: About the role (intro), Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have many overlapping sections. We need to decide what goes where. "About the role": likely the introductory paragraph(s) describing role, remote, etc. "Responsibilities": the list under "Your Responsibilities In This Role". "Requirements": maybe the "Work Experience Project Skill & Experience Requirements" (mandatory requirements). Could also include "Physical Requirements"? But physical requirements maybe part of Requirements? However we have a separate "Physical Requirements" heading not in allowed list; we can fold into Requirements or maybe into Qualifications? The allowed headings are limited; we can put physical requirements under Requirements as a list. "Qualifications": maybe the "Preferred Experience" and "Fearless Skills And Competencies"? Or "Required Level Of Proficiency"? Actually "Qualifications" could be the required qualifications (education, experience). But we already used Requirements for mandatory experience. Could treat Requirements as mandatory experience/skills, Qualifications as education/certifications? Let's see. The posting includes: "Bachelor’s degree or equivalent work experience is required." That's a qualification. Also "Minimum of 7 years of total relevant professional experience." That's experience requirement. Could be under Requirements. "Preferred Experience" list could go under Qualifications? Or Skills? The allowed headings: Skills (maybe for skills and competencies). Benefits, Pay, Schedule. We have "Fearless Skills And Competencies" list which is skills/competencies. That fits Skills. We have "Required Level Of Proficiency Advanced Application:" which is a description of proficiency level; could be part of Skills or Qualifications. We have "Physical Requirements" list; could be part of Requirements (maybe as a sublist) or separate but we don't have a heading for it; we could include under Requirements as a list. We have "Benefits" sections: two paragraphs about benefits; we can combine into Benefits section. We have Pay: salary range. Schedule: not mentioned besides "fully remote role" and maybe "flexible, life-friendly schedules" under Benefits. No explicit schedule like full-time, hours. Could we create Schedule section? The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule not explicitly stated; we have "flexible, life-friendly schedules" mentioned under Benefits. That's a benefit, not schedule. So we should not create a Schedule section because no explicit schedule info (like "Full-time", "40 hours/week", etc). So omit Schedule. Now we need to output HTML with

headings and

• for lists,

  for prose. We must not repeat job title as heading. The page already shows it, so we don't output a heading for the title. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate. We need to include sections only when posting has real specific content. Let's draft sections:

  About the role

  At Fearless, we are seeking a QA & Accessibility Lead as part of our Senior Consultant, Engineering & Technical Services career path to support the modernization of a large-scale public-facing government website. This role will lead both quality assurance and accessibility across the Drupal implementation, ensuring the solution is functional, reliable, accessible, and ready for production. The QA & Accessibility Lead will own testing strategy across design, development, content and data migration, and release. This person will lead accessibility testing and remediation, functional and regression testing, migration validation, automated testing, defect management, UAT support, and production-readiness validation. They will work closely with designers, developers, content teams, and government stakeholders to integrate quality and accessibility throughout delivery rather than treating them as final-stage activities. This is a fully remote role. At Fearless, this Senior Consultant collaborates with cross functional teams to align the technical vision, implementation, and quality of software systems across development, reliability, testing, and operations. This role will possess the skills to be able to bridge business objectives with technical execution in software development, infrastructure, security, and testing at an advanced application level of proficiency. The Sr. Consultant role will work on projects that allow them to ensure scalable, secure, and reliable solutions while mentoring engineers, fostering collaboration, and aligning stakeholders with product and project goals.

  That seems to capture the intro. Now Responsibilities: list under "Your Responsibilities In This Role". We'll extract each bullet. List: - Own the accessibility and quality assurance strategy across design, development, migration, testing, and release. - Perform and coordinate automated, manual, and assistive-technology accessibility testing of webpages, components, templates, and migrated content. - Provide actionable accessibility remediation guidance to designers, developers, and content teams and validate completed fixes. - Define the accessibility checklist and in-editor automated checks supporting the content-provider certification checkpoint. - Ensure training materials, documentation, and other supporting content meet applicable accessibility standards. - Produce the Accessibility Audit and Testing Report and required conformance certification. - Develop and execute test plans covering functional, integration, regression, responsive, and cross-browser testing of the Drupal implementation. - Validate migrated content, files, links, redirects, metadata, and relationships across content types. - Develop automated tests and integrate testing into the CI/CD pipeline. - Track, prioritize, retest, and close defects in collaboration with engineering and product teams. - Support UAT, production-readiness validation, deployment, and post-production stabilization testing. - Document testing approaches, results, defects, accessibility findings, remediation status, and validation evidence. We'll put each as
• . Now Requirements: we have mandatory experience/education etc. Also physical requirements. Let's gather mandatory requirements from "Work Experience Project Skill & Experience Requirements": - Minimum of 7 years of total relevant professional experience. - Bachelor’s degree or equivalent work experience is required. - At least 3 years supporting enterprise-wide website modernization or digital transformation initiatives, with that work occurring within the past 5 years. - Participation in at least one government, higher education, or similarly regulated organization project. - Involvement in the implementation or support of at least one Drupal solution hosted on AWS. - Demonstrated leadership of digital/web accessibility and quality assurance for large-scale websites or digital applications. - Deep knowledge and practical application of WCAG 2.1/2.2 Level A and AA accessibility standards. - Proficiency with automated and manual accessibility testing methods and tools. - Strong background conducting assistive-technology testing, including screen-reader and keyboard testing. - Proven ability to identify accessibility barriers, provide actionable remediation guidance, and validate completed fixes. - Strong background in web application QA and testing, including functional, integration, regression, responsive, and cross-browser testing. - Demonstrated experience testing Drupal or comparable enterprise CMS implementations. - Proficiency validating content and data migrations, including content, files, links, redirects, metadata, relationships, and source-to-target accuracy. - Strong understanding of defect tracking and management, including documentation, prioritization, retesting, and closure. - Proven ability to develop and execute comprehensive test plans, test cases, validation procedures, and testing documentation. - Ability to collaborate effectively with engineering, UX/design, content, DevOps, and customer stakeholders throughout the delivery lifecycle. Also Physical Requirements list: - Ability to sit for extended periods while working on a computer or during meetings. - Must be able to travel occasionally to client sites or company meetings, which may involve driving or flying. - Ability to communicate effectively via phone, email, and in-person, requiring clear speech, listening, and written communication skills. - Ability to move within an office environment, including reaching for files, using office equipment, and occasional light lifting (up to 10 pounds). We could include physical requirements as part of Requirements (maybe as a sublist). But we need to decide if we want a separate heading? Not allowed. So we can include them under Requirements as a list. Now Qualifications: maybe includes Preferred Experience and Fearless Skills And Competencies? But we already have Skills heading for competencies. Qualifications could include education, certifications, etc. Let's see: Preferred Experience list includes certifications (IAAP CPACC, WAS, or CPWA), proficiency testing with multiple screen-reader technologies, background supporting accessibility within public-sector digital services, accessibility experience within large-scale Drupal implementations, experience developing and maintaining automated web tests, strong background with Drupal-specific QA and testing, experience integrating automated testing into CI/CD pipelines, familiarity with API testing tools and techniques, experience with visual regression testing, background validating links, redirects, and SEO-related migration requirements, experience performing QA for large-scale content and data migrations, familiarity with Jira or comparable defect and work-management tools. These are "preferred" not required. Could go under Qualifications as "Preferred Qualifications". But we need to decide if we want a Qualifications section. The posting includes "Fearless Skills And Competencies" which is more like skills/competencies. That fits Skills. Thus we could have: - Qualifications: includes Preferred Experience (maybe as a list) and also Required Level Of Proficiency? Actually Required Level Of Proficiency is a statement about proficiency level; could be part of Skills. But we need to avoid duplication. Let's think: The allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role, Responsibilities, Requirements (mandatory + physical), Qualifications (preferred experience), Skills (Fearless Skills And Competencies + Required Level Of Proficiency), Benefits, Pay. We'll not include Schedule. Now we need to ensure we don't create sections with filler text like "commensurate with experience". Not present. Now we need to output HTML fragment only. Let's craft each section. Qualifications: we can list the Preferred