Digital Accessibility Coordinator
Northeast Ohio Medical University (NEOMED) · Rootstown, OH · 1 mo ago
$49k–$53k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Key info:
- Position Type: Admin/Professional
- Department: Institute for Teaching Excellence
- Full or Part Time: Full Time
- Pay Grade: MN8
- Department Specific Information: description about NEOMED, mission, role description.
- Why You'll Love This Role: bullet points: Purpose-Driven Work, Collaborative Culture, Room to Grow, Flexibility & Balance (hybrid work environment with up to two remote days per week after six months). This could be part of About the role or Benefits.
- Starting Salary Range: $49,120 – $52,503, commensurate with experience. The instruction says: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range, but also says "commensurate with experience". The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states salary range, but also includes "commensurate with experience". Is that considered filler? The phrase "commensurate with experience" is typical but they said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", ...). So if we include Pay section, we must not have filler text. The salary range is specific numbers, but the phrase "commensurate with experience" is filler. However we could include the salary range and maybe omit the filler phrase? The instruction: "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That suggests if the only content for that section is filler, we shouldn't create the section. But we have actual numbers plus filler. We could include the salary range and maybe note that it's commensurate with experience? That would be filler. Better to avoid Pay section altogether? But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (salary range). However they also say not to include filler. We could include the salary range and maybe not mention the commensurate phrase. The posting says: "Starting Salary Range: $49,120 – $52,503, commensurate with experience." We could extract the range and present it as "$49,120 – $52,503". That's specific. The phrase "commensurate with experience" is extra but we could omit it as it's filler. The instruction says not to emit a heading followed by filler/placeholder text. If we include the range, it's not filler. So we can include Pay section with that range.
- Benefits & Perks: list of benefits: Healthcare Coverage (medical, dental, vision through Medical Mutual), FSA/HSA, short- and long-term disability, long-term care coverage options, Life insurance, Retirement (state retirement plan with 14% employer matching), Paid Time Off (generous vacation and sick leave, 11 paid holidays), Additional Benefits: Hybrid work environment (up to two remote days per week after six months) (Policy#...), Educational benefits with partner universities (Policy#...), Ongoing investment in professional growth through on-site training and Lean Six Sigma certification, Employee wellness activities and initiatives.
Thus we have Benefits section.
- Schedule: Not explicitly stated besides hybrid work environment (up to two remote days per week after six months). That's more about flexibility, not schedule. No explicit schedule like Monday-Friday 9-5. So we should not create Schedule section.
- Skills: Not explicitly listed as a separate section, but qualifications include skills: ability to create accessible content, proficiency in Microsoft Office, experience delivering technical training, experience supporting LMS digital accessibility platforms, assistive technologies, tools. Could be under Qualifications or Requirements. We'll follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. But we need to avoid thin sections. Let's see what content we have for each.
About the role: Could be the introductory paragraph: "Join Northeast Ohio Medical University's (NEOMED) Institute for Teaching Excellence NEOMED is a mission-driven medical university focused on educating future healthcare professionals and improving the health of our region. We're seeking a Digital Accessibility Coordinator who is excited to collaborate with faculty and staff to make teaching and learning more accessible, flexible, and engaging for all learners. In this role, you'll partner across the university to design, support, and improve accessible course materials and learning environments as part of a collaborative teaching and learning team." plus Why You'll Love This Role bullet points.
Responsibilities: The "Principal Functional Responsibilities" section with bullet points.
Requirements: Could be the "Qualifications" section (Bachelor's degree etc.) plus maybe "Physical Requirements". But we have separate Qualifications and Preferred Qualifications. We could treat "Qualifications" as required qualifications, and "Preferred Qualifications" as preferred. The instruction says use headings like Requirements, Qualifications, Skills. We need to decide mapping.
We have:
- Qualifications (required): Bachelor's degree in education, digital communications, or related field; Demonstrate ability to create digitally accessible and compliant academic content by applying accessibility standards (WCAG 2.1/2.2 AA standards, ADA Section 508); Proficient in Microsoft Office applications; Prior experience delivering technical training sessions and materials to professional audiences; Experience supporting LMS digital accessibility platforms, assistive technologies, and tools.
- Preferred Qualifications: Master's degree in education or related field; Experience with monitoring and reporting institutional data for accessibility compliance in higher education setting; Experience delivering faculty professional development sessions in a higher education environment; Served as administrator or co-administrator for digital accessibility platform, LTI tool, or other application.
- Physical Requirements: Must be able to utilize a phone, computer and screen and other office equipment.
We could combine Qualifications and Preferred Qualifications under a single "Qualifications" heading, with sub-bullets maybe marking preferred. Or we could have "Requirements" for required qualifications and "Preferred Qualifications" as a separate heading if we want. But instruction says prefer a few substantive sections over many thin ones. So maybe combine required and preferred under Qualifications, noting which are preferred.
Skills: Could be extracted from qualifications: ability to create accessible content, proficiency in Microsoft Office, experience delivering technical training, experience supporting LMS platforms, assistive technologies, tools. Could be a Skills section.
But we might avoid Skills if it's thin.
Let's think: We have substantive content for About the role (intro + why you'll love), Responsibilities (detailed bullet list), Qualifications (required + preferred), Benefits, Pay. That's five sections. That's okay.
We need to ensure we don't include filler like "commensurate with experience" in Pay. We'll output Pay range only.
We must not include Job ID/requisition numbers as headings; we can drop them.
We must remove boilerplate like EEO, application instructions, etc.
We must not repeat job title as heading.
We must output only HTML fragment.
Let's craft sections:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content.
We need to parse the posting.
Key info:
- Position Type: Admin/Professional
- Department: Institute for Teaching Excellence
- Full or Part Time: Full Time
- Pay Grade: MN8
- Department Specific Information: description about NEOMED, mission, role description.
- Why You'll Love This Role: bullet points: Purpose-Driven Work, Collaborative Culture, Room to Grow, Flexibility & Balance (hybrid work environment with up to two remote days per week after six months). This could be part of About the role or Benefits.
- Starting Salary Range: $49,120 – $52,503, commensurate with experience. The instruction says: do NOT create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range, but also says "commensurate with experience". The instruction says: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. The posting states salary range, but also includes "commensurate with experience". Is that considered filler? The phrase "commensurate with experience" is typical but they said never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", ...). So if we include Pay section, we must not have filler text. The salary range is specific numbers, but the phrase "commensurate with experience" is filler. However we could include the salary range and maybe omit the filler phrase? The instruction: "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". That suggests if the only content for that section is filler, we shouldn't create the section. But we have actual numbers plus filler. We could include the salary range and maybe note that it's commensurate with experience? That would be filler. Better to avoid Pay section altogether? But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them (salary range). However they also say not to include filler. We could include the salary range and maybe not mention the commensurate phrase. The posting says: "Starting Salary Range: $49,120 – $52,503, commensurate with experience." We could extract the range and present it as "$49,120 – $52,503". That's specific. The phrase "commensurate with experience" is extra but we could omit it as it's filler. The instruction says not to emit a heading followed by filler/placeholder text. If we include the range, it's not filler. So we can include Pay section with that range.
- Benefits & Perks: list of benefits: Healthcare Coverage (medical, dental, vision through Medical Mutual), FSA/HSA, short- and long-term disability, long-term care coverage options, Life insurance, Retirement (state retirement plan with 14% employer matching), Paid Time Off (generous vacation and sick leave, 11 paid holidays), Additional Benefits: Hybrid work environment (up to two remote days per week after six months) (Policy#...), Educational benefits with partner universities (Policy#...), Ongoing investment in professional growth through on-site training and Lean Six Sigma certification, Employee wellness activities and initiatives.
Thus we have Benefits section.
- Schedule: Not explicitly stated besides hybrid work environment (up to two remote days per week after six months). That's more about flexibility, not schedule. No explicit schedule like Monday-Friday 9-5. So we should not create Schedule section.
- Skills: Not explicitly listed as a separate section, but qualifications include skills: ability to create accessible content, proficiency in Microsoft Office, experience delivering technical training, experience supporting LMS digital accessibility platforms, assistive technologies, tools. Could be under Qualifications or Requirements. We'll follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. But we need to avoid thin sections. Let's see what content we have for each.
About the role: Could be the introductory paragraph: "Join Northeast Ohio Medical University's (NEOMED) Institute for Teaching Excellence NEOMED is a mission-driven medical university focused on educating future healthcare professionals and improving the health of our region. We're seeking a Digital Accessibility Coordinator who is excited to collaborate with faculty and staff to make teaching and learning more accessible, flexible, and engaging for all learners. In this role, you'll partner across the university to design, support, and improve accessible course materials and learning environments as part of a collaborative teaching and learning team." plus Why You'll Love This Role bullet points.
Responsibilities: The "Principal Functional Responsibilities" section with bullet points.
Requirements: Could be the "Qualifications" section (Bachelor's degree etc.) plus maybe "Physical Requirements". But we have separate Qualifications and Preferred Qualifications. We could treat "Qualifications" as required qualifications, and "Preferred Qualifications" as preferred. The instruction says use headings like Requirements, Qualifications, Skills. We need to decide mapping.
We have:
- Qualifications (required): Bachelor's degree in education, digital communications, or related field; Demonstrate ability to create digitally accessible and compliant academic content by applying accessibility standards (WCAG 2.1/2.2 AA standards, ADA Section 508); Proficient in Microsoft Office applications; Prior experience delivering technical training sessions and materials to professional audiences; Experience supporting LMS digital accessibility platforms, assistive technologies, and tools.
- Preferred Qualifications: Master's degree in education or related field; Experience with monitoring and reporting institutional data for accessibility compliance in higher education setting; Experience delivering faculty professional development sessions in a higher education environment; Served as administrator or co-administrator for digital accessibility platform, LTI tool, or other application.
- Physical Requirements: Must be able to utilize a phone, computer and screen and other office equipment.
We could combine Qualifications and Preferred Qualifications under a single "Qualifications" heading, with sub-bullets maybe marking preferred. Or we could have "Requirements" for required qualifications and "Preferred Qualifications" as a separate heading if we want. But instruction says prefer a few substantive sections over many thin ones. So maybe combine required and preferred under Qualifications, noting which are preferred.
Skills: Could be extracted from qualifications: ability to create accessible content, proficiency in Microsoft Office, experience delivering technical training, experience supporting LMS platforms, assistive technologies, tools. Could be a Skills section.
But we might avoid Skills if it's thin.
Let's think: We have substantive content for About the role (intro + why you'll love), Responsibilities (detailed bullet list), Qualifications (required + preferred), Benefits, Pay. That's five sections. That's okay.
We need to ensure we don't include filler like "commensurate with experience" in Pay. We'll output Pay range only.
We must not include Job ID/requisition numbers as headings; we can drop them.
We must remove boilerplate like EEO, application instructions, etc.
We must not repeat job title as heading.
We must output only HTML fragment.
Let's craft sections:
About the role
Join Northeast Ohio Medical University's (NEOMED) Institute for Teaching Excellence. NEOMED is a mission-driven medical university focused on educating future healthcare professionals and improving the health of our region. We're seeking a Digital Accessibility Coordinator who is excited to collaborate with faculty and staff to make teaching and learning more accessible, flexible, and engaging for all learners. In this role, you'll partner across the university to design, support, and improve accessible course materials and learning environments as part of a collaborative teaching and learning team.
Why you'll love this role:
- Purpose‑driven work: Support accessible, inclusive academic programs grounded in UDL best practices.
- Collaborative culture: Work alongside faculty, staff, and academic leaders committed to continuous improvement.
- Room to grow: Build your expertise through professional development and hands‑on work with emerging tools and technologies.
- Flexibility & balance: Enjoy a hybrid work environment with up to two remote days per week after six months.
Responsibilities
- Collaborate with stakeholders to develop, support, and implement procedures and systems to facilitate digital accessibility compliance and best practices.
- Work with faculty, staff, and college curriculum teams to evaluate, remediate, and implement accessible educational content while applying universal design for learning principles to enhance learner engagement and flexibility.
- Contribute to, consult, and manage concurrent academic projects using accessibility best practices in alignment with state and federal regulations.
- Assist in monitoring and reporting institutional progress toward accessibility compliance goals and deadlines.
- Provide support to troubleshoot digital accessibility‑related issues in systems (e.g., Learning Management System (LMS), LMS digital accessibility platform, learning tools interoperability (LTI), Microsoft applications) under the ITE.
- Occasionally support the LMS administration team with troubleshooting and establishing best practices for LTI tools.
- Create and deliver programming and training through the ITE connected to position responsibilities, including development, design, curation, and delivery of session/workshop materials.
- Collaborate and serve as liaison to university stakeholders to improve digital accessibility practices in teaching and learning.
- Partner with faculty and staff to create digital accessibility guidelines, style guides, and workflows that align with university policy and WCAG standards.
- Maintain and update online ITE presence (website, intranet, LMS) with appropriate external and internal resources.
- Perform other duties as assigned.
Qualifications
- Bachelor's degree in education, digital communications, or related field.
- Demonstrated ability to create digitally accessible and compliant academic content by applying accessibility standards (WCAG 2.1/2.2 AA, ADA Section 508).
- Proficient in Microsoft Office applications.
- Prior experience delivering technical training sessions and materials to professional audiences.
- Experience supporting LMS digital accessibility platforms, assistive technologies, and tools.
- Preferred: Master's degree in education or related field.
- Preferred: Experience with monitoring and reporting institutional data for accessibility compliance in a higher‑education setting.
- Preferred: Experience delivering faculty professional development sessions in a higher‑education environment.
- Preferred: Served as administrator or co‑administrator for a digital accessibility platform, LTI tool, or other application.
- Physical requirement: Must be able to utilize a phone, computer, screen, and other office equipment.
Benefits
- Healthcare coverage: competitive medical, dental, and vision insurance through Medical Mutual.
- Flexible Spending Account (FSA) or Health Savings Account (HSA).
- Short‑ and long‑term disability coverage.
- Long‑term care coverage options.
- Life insurance.
- Retirement: state retirement plan with 14% employer matching.
- Paid time off: generous vacation and sick leave, plus 11 paid holidays each year.
- Hybrid work environment (up to two remote days per week after six months).
- Educational benefits with partner universities.
- Ongoing investment in professional growth through on‑site training and Lean Six Sigma