Digital Accessibility Support Specialist

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Also remove duplicated lines, application instructions. We need to extract relevant content. Let's parse the posting. Position Summary: includes description of PSU, OIT, etc. That's about the role? Could be "About the role" or "Position Summary". We'll treat as "About the role". Provide paragraph(s) summarizing. Responsibilities: The bullet list of duties with percentages: Consultation, Training, and Support (30%); Digital Accessibility Resource Management (20%); Team Support and Related Projects (20%); Information Technology (IT) Contract Reviews (20%); Other Duties as Assigned (10%). Under each, details. We'll put as

• for each duty, maybe with subpoints? We'll keep as list items with the description. Requirements: Minimum Qualifications from classification: AA degree in computer science, etc., or similar certified coursework and at least one year related work experience. Additional Minimum Qualifications For This Position: list of many items (understand regulations, experience creating/validating/remediating digital resources in Google Workspace, etc., hands-on experience using screen reading software, ability to evaluate VPAT, ability to build partnerships, desire for people-first culture, ability to independently organize/execute multiple projects, ability to provide direct customer support, ability to synthesize technical concepts). We'll treat these as requirements. Preferred Qualifications: list of preferred items. Skills: Could be derived from qualifications? Might combine. But we can have a Skills section summarizing key skills: digital accessibility standards, WCAG, screen readers, VPAT, customer support, training development, etc. However we must not invent. We can extract from qualifications and preferred qualifications as skills. Benefits: The posting mentions "PSU’s excellent benefits package includes 95% premium-paid healthcare; a generous retirement and vacation package; and reduced tuition rates for employees, spouses, or dependents at any of the Oregon Public Universities." Also mention tuition discount earlier. So we can include Benefits section. Pay: "The starting salary rate for this position is between $48,852 and $73,500 per year. The starting salary may be negotiable above this range..." So we include Pay. Schedule: "Work Days/Hours On campus Monday-Friday, 8am-5pm. Up to one day remote, with the approval of the supervisor." So Schedule. We must not include sections with filler like "commensurate with experience". We have actual numbers. We must not include Job ID etc. We can include a short p for metadata like Position Number? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. So we could include a short p with Position Number etc. But maybe better to drop it as not needed. However we need to preserve ALL substantive information. Position Number D93018 is metadata but maybe minor. Could fold into a short p. We'll include a p at top maybe. We must not include application instructions, EEO, etc. We need to output only HTML fragment, no html/body tags, no markdown fences. Let's craft. Structure:

  Position Number: D93018; Classification Title: Info Technology Consultant 2; Working Title: Digital Accessibility Support Specialist; Department: TEC Off of Information Technology; Representation: OP - SEIU/OPEU Local 503; FTE: 1; Proposed Start Date: 11/16/2026.

  Then sections:

  About the role

  ... (summary of PSU, OIT, role)

  Responsibilities

  • Consultation, Training, and Support (30%): Triage and support incoming digital accessibility service requests and coordinate third-party remediation for PSU’s public-facing and internal, non-instructional digital resources. Provide expert consultation on accessible digital procurement, design, and management across OIT and university-wide projects. Collaborate with campus partners and support staff to meaningfully contribute to PSU’s continued digital accessibility maturity. Drive institutional capacity building through programs such as the International Association of Accessibility Professionals (IAAP) cohort, PDF Spring Cleaning event, and Digital Accessibility Liaison (DAL) Group. Develop and deploy digital accessibility workshops and trainings to support the PSU community.
  • Digital Accessibility Resource Management (20%): Stay current on evolving digital accessibility standards to ensure high-quality, up-to-date support and training content. Develop and continuously refine accessible, inclusive self-support resources (e.g., articles, checklists, templates, videos, etc.) and training materials for the PSU community. Additionally, collaborate with the DAC team to monitor Siteimprove quality assurance and accessibility reports to maintain and improve the usability of the OIT website.
  • Team Support and Related Projects (20%): Prioritize and complete daily tasks and project assignments on schedule while providing expert insights to advance team goals. Participate in complex projects with cross-campus stakeholders to advance understanding of digital accessibility and compliance. Report regularly on project statuses and challenges. Cultivate key relationships across OIT, PSU, and partner institutions. Actively support a people-first, inclusive team culture while establishing clear customer expectations to maintain a sustainable, balanced workload.
  • Information Technology (IT) Contract Review (20%): Execute IT service and solution contract reviews by evaluating vendor documentation against WCAG 2.X standards to assess baseline digital accessibility risk. Collaborate with OIT and the central contracts office to streamline procurement workflows, improve guidance materials, and ensure regulatory compliance. Support campus stakeholders and vendors with digital accessibility risk management and remediation roadmapping. Investigate reported barriers in OIT systems and support application administrators in remediating them.
  • Other Duties as Assigned (10%): Perform additional duties as needed to support team and organizational goals.

  Requirements

  • AA degree in computer science, information systems, educational technology, communications, or related field, or similar certified coursework in applicable fields.
  • At least one year of related work experience.
  • Understanding of digital accessibility regulations and standards (ADA, Section 504 of the Rehabilitation Act, WCAG 2.X).
  • Experience creating, validating, and remediating digital resources in Google Workspace, Microsoft Office, PDF, and HTML, in accordance with WCAG Guidelines 2.X, Level A and AA.
  • Hands‑on experience using industry‑leading screen reading software such as JAWS, NVDA, and/or VoiceOver to validate accessibility for digital products.
  • Ability to closely read, evaluate, and interpret a WCAG‑based Voluntary Product Accessibility Template (VPAT), communicating relative risk to procurement parties.
  • Ability to build meaningful partnerships with PSU digital accessibility stakeholders and OIT colleagues in a collaborative, team‑oriented environment.
  • Desire and commitment to a people‑first culture—prioritizing effective communication, trust‑building, celebration of differences, etc.
  • Ability to independently organize and execute multiple projects and tasks within a team environment—collaborate on complex decisions and prioritize work as needed.
  • Experience providing direct customer support and expertise—communicating effectively both orally and in writing to technical and non‑technical audiences.
  • Ability to synthesize and translate complex technical concepts into concise, user‑friendly written formats (e.g., best‑practice guidelines, support articles, training materials, etc.).

  Preferred Qualifications

  • Direct experience with HTML, CSS, JavaScript, ARIA, and mobile or web content management systems.
  • Ability to lead and/or manage complex projects—collaborating effectively with others on requirements development, prioritization, and tracking.
  • Oral communication skills including presenting in front of audiences and effectively delivering technical concepts to diverse and non‑technical audiences.
  • Experience providing oversight for IT accessibility solutions in a higher education environment.
  • Hands‑on experience working with or supporting other industry‑leading assistive technologies such as Dragon Naturally Speaking, Kurzweil, Read&Write, or Zoomtext, etc.
  • Professional experience utilizing automated accessibility audit and quality assurance tools and processes.
  • Record of exceptional customer service that creates a welcoming and supportive environment.
  • Review solutions and processes critically to make recommendations for continuous improvement.
  • Experience working directly with people with disabilities or lived experience as an assistive technology user.
  • Experience with work management and issue tracking systems such as Jira or Jira Service Management.
  • Certification such as a Certified Professional in Web Accessibility (CPWA) by the International Association of Accessibility Professionals (IAAP) or Section 508 Trusted Tester by the Department of Homeland Security.

  Skills

  Key skills include digital accessibility standards (WCAG 2.X, ADA, Section 504), screen‑reader testing (JAWS, NVDA, VoiceOver), VPAT analysis, accessible content creation in Google Workspace, Microsoft Office, PDF, HTML, training development, customer support, project coordination, partnership building, and familiarity with tools such as Siteimprove, Jira, and assistive technologies.

  Benefits

  • 95% premium‑paid healthcare.
  • Generous retirement and vacation package.
  • Reduced tuition rates for employees, spouses, or dependents at any Oregon Public University.
  • Substantial tuition discount for employees (as noted in department description).

  Pay

  The starting salary range is $48,852 – $73,500 per year, with possible negotiation above the range based on knowledge, experience, skills, department budget, and HR approval.

  Schedule

  On‑campus Monday‑Friday, 8 am–5 pm; up to one day remote per week with supervisor approval.

  We must ensure we didn't include any boilerplate like EEO, application instructions, etc. We removed those. Check for any duplicated lines: we didn't repeat. Check for any placeholder like "commensurate with experience" - we didn't include. Check for any mention of "Total Compensation Range & Benefits Statement" we captured Pay and Benefits. Check for "Work Days/Hours" we captured Schedule. Check for "Position Summary" we captured About the role. Check for "Minimum Qualifications" we captured Requirements. Check for "Additional Minimum Qualifications For This Position" we included in Requirements. Check for "Preferred Qualifications" we have separate section. Check for "We ask our employees and applicants..." that's OIT Attributes for Success and Key Cultural Competencies, Environmental Stewardship. Those are substantive but not explicitly requested sections. Should we include them? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we should include that info somewhere. Could be part of About the role or a separate section like "Organizational Culture" but we only allowed headings from list. However we could incorporate into About the role or Skills? The instruction says use headings for those specific section headings; but we can also have other headings? It says: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid