Access Consultant

The user wants me to reformat a job posting into clean, well-structured semantic HTML. I need to follow the rules: - Use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use

• for any list of duties/requirements/benefits, and

  for prose. - Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. - Preserve ALL substantive information; do NOT invent or summarize away detail. - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. - IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. - Prefer a few substantive sections over many thin ones. - Output ONLY the HTML fragment — no /, no markdown code fences. Now, analyze the input. It's a job posting for "Access Consultant" at George Mason University, Department: University Life, Disability Services. The posting includes: - Department, Classification, Job Category, Job Type, Work Schedule, Location, Workplace Type, Sponsorship Eligibility, Salary, Criminal Background Check. - About The Department - About The Position - Responsibilities (with subsections: Access and Accommodations, Consultation, Education, And Outreach, Administrative Tasks And Unit Collaboration, Departmental And Divisional Responsibilities) - Required Qualifications - Preferred Qualifications - Instructions To Applicants (application instructions, posting dates) - Mason Ad Statement (boilerplate) - Equity Statement (boilerplate) - Campus Safety Information (boilerplate) I need to remove boilerplate: Mason Ad Statement, Equity Statement, Campus Safety Information, Instructions To Applicants (application instructions). Also remove duplicated lines? There's "Supports divisional initiatives and other special projects as assigned" appears twice? Actually in Departmental And Divisional Responsibilities, there are two similar bullet points: "Supports divisional planning initiatives and other special projects assigned;" and "Supports divisional initiatives and other special projects as assigned, actively participating at in-person events and volunteer opportunities to represent Disability Services and University Life effectively to the campus community;" - they are similar but not identical. I'll keep both as separate list items. Also, the metadata at top: Department, Classification, Job Category, Job Type, Work Schedule, Location, Workplace Type, Sponsorship Eligibility, Salary, Criminal Background Check. These are minor metadata. I should fold them into a short

  or drop them. The rules say: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So I can create a

  with key details like location, schedule, salary, etc. But the user also says: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So I could create a "Position Details" section with a

  summarizing metadata. However, the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid a "Position Details" heading. But the example headings are typical job posting sections. I think it's okay to have a "Position Details" heading with a paragraph. But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state Salary and Work Schedule. So I could create a "Pay and Schedule" section? But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Salary and Work Schedule. So I could create a "Pay" section and "Schedule" section? But the rule says "Prefer a few substantive sections over many thin ones." So maybe combine into a "Position Details" section with a paragraph. Better: I'll create a

  at the beginning with key metadata: "Full-time (1.0 FTE, 40 hrs/week), Hybrid eligible, Fairfax, VA. Salary: Anticipated starting low $60k, commensurate with education and experience. Not eligible for visa sponsorship. Criminal background check required." That's a paragraph. Then sections: About the Department, About the Position, Responsibilities (with subsections), Required Qualifications, Preferred Qualifications. I need to use

  for each section heading. For Responsibilities, there are subsections. Should I use

  ? The rules only mention

  for section headings. It says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't mention subheadings. But the responsibilities have clear subsections. I could either make them separate

  headings (like "Access and Accommodations", "Consultation, Education, and Outreach", etc.) or keep them as part of Responsibilities with

  ? The rule says "use

  for section headings". It doesn't forbid

  . But to be safe, I'll use

  for each major section, and for subsections within Responsibilities, I'll use

  ? However, the output is HTML fragment, and using

  is fine. But the instruction says "use

  for section headings". It might be okay to use

  for each subsection as well, but that would create many headings. The example includes "Responsibilities" as a heading. The subsections are part of Responsibilities. I think I'll keep Responsibilities as one

  and then use

  for subsections, but the rule didn't mention

  . Alternatively, I could make each subsection a separate

  heading. That might be acceptable. Let's see: The posting has "Responsibilities" then bullet points grouped under subheadings. I'll treat each subheading as a separate

  ? But the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have more headings. I'll use

  for each major section: "About the Department", "About the Position", "Responsibilities", "Required Qualifications", "Preferred Qualifications". For the subsections under Responsibilities, I'll use

  to keep hierarchy. That seems semantic. But the rule says "Output ONLY the HTML fragment — no /, no markdown code fences." So I'll output just the HTML. Now, I need to convert lists to

  • . The responsibilities are listed with semicolons and line breaks. I'll parse each bullet point. The text uses semicolons and line breaks. I'll split by semicolons? Actually the text shows each responsibility as a bullet point ending with semicolon. For example: "Access and Accommodations: Establishes and manages individualized accommodation plans for students with disabilities by reviewing and interpreting confidential medical and psychological documentation, determining eligibility, and identifying reasonable accommodations in accordance with applicable laws and university policies;Monitors the effectiveness of approved accommodations through communication with students and relevant university stakeholders and modifies accommodation plans as appropriate based on changes in student needs;Maintains accurate and confidential student records in accordance with the Americans with Disabilities Act Amendments Act (ADAAA), Section 504 of the Rehabilitation Act, and the Family Educational Rights and Privacy Act (FERPA) to protect student privacy and support regulatory compliance; andFacilitates the implementation of approved accommodations by collaborating with students, faculty, and university stakeholders to reduce barriers and ensure students with disabilities have equitable opportunities to participate and succeed." This is a list of four items separated by semicolons. The last one has "and" before it. I'll split each into separate
  • . Similarly for other subsections. I'll need to clean up the text: remove trailing semicolons, "and" at start of last item. Also, the Required Qualifications and Preferred Qualifications are lists separated by semicolons. I'll split each into
  • . Now, let's structure: 1. Position Details paragraph (metadata) 2.

    About the Department

    with

    content. 3.

    About the Position

    with

    content. 4.

    Responsibilities

    -

    Access and Accommodations

    with
    • ...
    -

    Consultation, Education, and Outreach

    with
    • ...
    -

    Administrative Tasks and Unit Collaboration

    with
    • ...
    -

    Departmental and Divisional Responsibilities

    with
    • ...
    5.

    Required Qualifications

    with
    • ...
    6.

    Preferred Qualifications

    with
    • ...
    I'll omit Instructions To Applicants, Mason Ad Statement, Equity Statement, Campus Safety Information. Now, write the HTML. Let's craft the metadata paragraph:

    Full-time (1.0 FTE, 40 hrs/week), Hybrid eligible, Fairfax, VA. Salary: Anticipated starting low $60k, commensurate with education and experience. Not eligible for visa sponsorship. Criminal background check required.

    Now, About the Department: The text is a few paragraphs. I'll combine into one or two

    tags. The text: "Disability Services supports qualified students with disabilities in participating fully in George Mason University’s programs and services. A qualified student with a disability is a student with a disability who meets the academic and technical standards required for admission or participation in the university's education program and services. As defined in the Americans with Disabilities Act (ADA) and section 504 of the Rehabilitation Act of 1973, a person has a disability if the person has a physical or mental impairment that substantially limits one or more major life activities, has a record of such an impairment, or is regarded as having such an impairment. Disability Services is committed to upholding the letter and spirit of the laws, such as the Americans with Disabilities Act of 1990 and Section 504 of the Rehabilitation Act of 1973. Disability Services strives to foster partnerships with students, faculty, and staff to create welcoming and supportive environments that enable all members of the university community to participate." I'll put as a single

    or maybe two. I'll keep as one

    . About the Position: Text: "The Access Consultant reports directly to the Assistant Director of Disability Services and works collaboratively with students to determine reasonable and appropriate accommodations and services to which they are entitled under the Americans with Disabilities Act (ADA) and Section 504 of the Rehabilitation Act. Using independent judgment and professional expertise, the Access Consultant works closely with students, faculty, university stakeholders, parents and families, and community members to support an accessible environment. The Access Consultant also serves on university committees, representing disability and accessibility-related issues and concerns, and contributes to initiatives that promote campus accessibility, disability awareness, and effective practices that support participation for individuals with disabilities." One

    . Now Responsibilities subsections. I'll parse each