Director for Accessibility & Testing
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat the job title as heading. The job title is "Director for Accessibility & Testing". Not to be used as heading.
We need to preserve all substantive information. Let's extract:
- Posting Number S15752P (metadata) - we can fold into a short
or drop. Probably include as a short paragraph: Posting Number: S15752P.
- Working Title: Director for Accessibility & Testing (but that's the job title, we shouldn't repeat as heading; maybe include in a paragraph? The instruction: 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. So we can include a short paragraph with Posting Number and Working Title? The Working Title is essentially the job title; maybe we can include it in a paragraph as part of metadata. But they said do NOT repeat the job title as a heading; they didn't forbid including it in a paragraph. However they said "fold minor metadata into a short
or drop it." So we can include a
with Posting Number and maybe Working Title.
- Department: VPSA-Accessibility & Testing
- About the University of Georgia: paragraph(s). We'll put under
About the University
maybe? The rule: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings as needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So likely they expect those specific headings. But we can also use other headings if they match the content? The examples are just examples; we can use any heading but must be . Probably we should use headings like About the University, About the Department, Position Summary, Minimum Qualifications, Preferred Qualifications, Knowledge Skills Abilities, Responsibilities (maybe split into sub-sections?), Schedule, Benefits. However they said "Prefer a few substantive sections over many thin ones." So we may combine some.
We need to include sections only when posting has real specific content. We have:
- About the University of Georgia (substantive)
- About the College/Unit/Department (maybe minimal but we have some: department website? Actually they have "College/Unit/Department website" but no URL given. Might be placeholder. We could drop that as it's not substantive. The line: "College/Unit/Department website" with no URL. That's filler. So we may omit About the College/Unit/Department section.
- Position Summary (substantive)
- Minimum Qualifications (substantive)
- Preferred Qualifications (substantive)
- Knowledge, Skills, Abilities And/or Competencies (substantive)
- Duties/Responsibilities (substantive, with three sub-sections each with percentage time)
- Work Schedule (substantive)
- Benefits (substantive: Benefits Eligible, Retirement Plan TRS or ORP)
- Pay: we should not include because it's just "Commencement with Experience" placeholder.
- Also we have "FLSA Exempt FTE 1.00" maybe include in a metadata paragraph.
- "Is driving a responsibility of this position? No" etc. That's a bunch of yes/no questions. Might be considered metadata; we could include in a short paragraph under "Additional Information" but maybe drop as it's not crucial? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep those details. They are substantive? They are details about the position. We could include them in a
list.
- Also "Credit and P-Card policy" etc. That's also substantive.
- "Background Investigation Policy" etc.
- "Contact Information" etc.
We need to decide what to keep. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO Policy Statement, USG Core Values Statement, etc. Also remove "Special Instructions to Applicants" maybe? That's application instructions? It says "Priority consideration will be given to those who complete the application process by 9/28/2026; however, screening will continue until the position is filled. We are unable to offer a work visa sponsorship for this position. You must be authorized to work in the U.S. to apply." That's application instructions; we should remove.
Also "Posting Specific Questions" and "Applicant Documents Required Documents" etc are application instructions; remove.
Thus we keep: Posting Number, Working Title, Department, About the University, Position Summary, Minimum Qualifications, Preferred Qualifications, Knowledge Skills Abilities, Duties/Responsibilities (with sub-sections), Work Schedule, Benefits, FLSA Exempt FTE, maybe other yes/no fields, Credit and P-Card policy, Background Investigation Policy, Contact Information (Recruitment Contact). Also maybe "Location of Vacancy Athens Area". That's substantive.
We need to format as HTML fragment.
Let's decide sections:
-
About the University
... (the paragraph about UGA)
- Position Summary
... (the paragraph)
- Minimum Qualifications
Bachelor’s degree in a related field plus 12 years of professional experience to include 5 years of supervisory experience or equivalency.
- Preferred Qualifications
... (list)
Could be a with items.
- Knowledge, Skills, and Abilities
- ... each item
- Responsibilities
maybe we can include subheadings inside? But we cannot use headings other than ? The instruction only says use for section headings; it doesn't forbid using etc but safer to stick to . We could embed the sub-sections as
with bold headings? But we need to preserve the percentages. Could use
- with internal for subheading.
Better:
Responsibilities
- Unit Leadership and Staff Supervision (60%) ...
...
- Schedule
Monday-Friday 8:00 AM – 5:00 PM. Some nights and weekends may be necessary.
- Benefits
Benefits eligible; retirement plan options include TRS or ORP.
- Additional Information
maybe we can combine metadata: Posting Number, Working Title, Department, FLSA Exempt FTE 1.00, Location, etc. But we already have a short paragraph for metadata at top. Could do Posting Number: S15752P. Working Title: Director for Accessibility & Testing. Department: VPSA-Accessibility & Testing. FLSA Status: Exempt. FTE: 1.00. Location: Athens Area.
- Also include the yes/no fields: Is driving a responsibility? No. Is this a Position of Trust? Yes. Does this position have operation, access, or control of financial resources? Yes. Does this position require a P-Card? No. Is having a P-Card an essential function? No. Does this position have direct interaction or care of children under 18 or direct patient care? No. Does this position have Security Access (e.g., public safety, IT security, personnel records, patient records, or access to chemicals and medications) Yes. Credit and P-Card policy: Be advised a credit check will be required for all positions with financial responsibilities. For additional information about the credit check criteria, visit the UGA Credit Background Check website. Background Investigation Policy: Offers of employment are contingent upon completion of a background investigation including, a criminal background check demonstrating your eligibility for employment with the University of Georgia; confirmation of the credentials and employment history reflected in your application materials (including reference checks) as they relate to the job-based requirements of the position applied for; and, if applicable, a satisfactory credit check. You may also be subject to a pre-employment drug test for positions with high-risk responsibilities, if applicable. Please visit the UGA Background Check website.
We could put those under Additional Requirements
or similar.
But we need to avoid too many sections; maybe combine all metadata into one after the heading? However the instruction: "Prefer a few substantive sections over many thin ones." So we should aim for maybe 6-8 sections.
Let's list sections:
1. About the University
2. Position Summary
3. Minimum Qualifications
4. Preferred Qualifications
5. Knowledge, Skills, and Abilities
6. Responsibilities
7. Schedule
8. Benefits
9. Additional Information (metadata + yes/no + checks)
That's 9 sections, maybe okay.
We need to ensure we don't include filler like "commensurate with experience". We'll omit Pay.
Now we need to write the HTML.
Let's extract the exact text for each.
About the University of Georgia:
"Chartered by the state of Georgia in 1785, the University of Georgia is the birthplace of public higher education in America and is the state’s flagship university (https://www.uga.edu/). The proof is in our more than 240 years of academic and professional achievements and our continual commitment to higher education. UGA is currently ranked among the top 20 public universities in U.S. News & World Report. The University’s main campus is located in Athens, approximately 65 miles northeast of Atlanta, with extended campuses in Atlanta, Griffin, Gwinnett, and Tifton. U
for prose. We must not repeat the job title as heading. The job title is "Director for Accessibility & Testing". Not to be used as heading. We need to preserve all substantive information. Let's extract: - Posting Number S15752P (metadata) - we can fold into a short
or drop. Probably include as a short paragraph: Posting Number: S15752P. - Working Title: Director for Accessibility & Testing (but that's the job title, we shouldn't repeat as heading; maybe include in a paragraph? The instruction: 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. So we can include a short paragraph with Posting Number and Working Title? The Working Title is essentially the job title; maybe we can include it in a paragraph as part of metadata. But they said do NOT repeat the job title as a heading; they didn't forbid including it in a paragraph. However they said "fold minor metadata into a short
or drop it." So we can include a
with Posting Number and maybe Working Title. - Department: VPSA-Accessibility & Testing - About the University of Georgia: paragraph(s). We'll put under
About the University
maybe? The rule: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use other headings as needed? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So likely they expect those specific headings. But we can also use other headings if they match the content? The examples are just examples; we can use any heading but must be . Probably we should use headings like About the University, About the Department, Position Summary, Minimum Qualifications, Preferred Qualifications, Knowledge Skills Abilities, Responsibilities (maybe split into sub-sections?), Schedule, Benefits. However they said "Prefer a few substantive sections over many thin ones." So we may combine some.
We need to include sections only when posting has real specific content. We have:
- About the University of Georgia (substantive)
- About the College/Unit/Department (maybe minimal but we have some: department website? Actually they have "College/Unit/Department website" but no URL given. Might be placeholder. We could drop that as it's not substantive. The line: "College/Unit/Department website" with no URL. That's filler. So we may omit About the College/Unit/Department section.
- Position Summary (substantive)
- Minimum Qualifications (substantive)
- Preferred Qualifications (substantive)
- Knowledge, Skills, Abilities And/or Competencies (substantive)
- Duties/Responsibilities (substantive, with three sub-sections each with percentage time)
- Work Schedule (substantive)
- Benefits (substantive: Benefits Eligible, Retirement Plan TRS or ORP)
- Pay: we should not include because it's just "Commencement with Experience" placeholder.
- Also we have "FLSA Exempt FTE 1.00" maybe include in a metadata paragraph.
- "Is driving a responsibility of this position? No" etc. That's a bunch of yes/no questions. Might be considered metadata; we could include in a short paragraph under "Additional Information" but maybe drop as it's not crucial? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep those details. They are substantive? They are details about the position. We could include them in a
. Probably we should use headings like About the University, About the Department, Position Summary, Minimum Qualifications, Preferred Qualifications, Knowledge Skills Abilities, Responsibilities (maybe split into sub-sections?), Schedule, Benefits. However they said "Prefer a few substantive sections over many thin ones." So we may combine some. We need to include sections only when posting has real specific content. We have: - About the University of Georgia (substantive) - About the College/Unit/Department (maybe minimal but we have some: department website? Actually they have "College/Unit/Department website" but no URL given. Might be placeholder. We could drop that as it's not substantive. The line: "College/Unit/Department website" with no URL. That's filler. So we may omit About the College/Unit/Department section. - Position Summary (substantive) - Minimum Qualifications (substantive) - Preferred Qualifications (substantive) - Knowledge, Skills, Abilities And/or Competencies (substantive) - Duties/Responsibilities (substantive, with three sub-sections each with percentage time) - Work Schedule (substantive) - Benefits (substantive: Benefits Eligible, Retirement Plan TRS or ORP) - Pay: we should not include because it's just "Commencement with Experience" placeholder. - Also we have "FLSA Exempt FTE 1.00" maybe include in a metadata paragraph. - "Is driving a responsibility of this position? No" etc. That's a bunch of yes/no questions. Might be considered metadata; we could include in a short paragraph under "Additional Information" but maybe drop as it's not crucial? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep those details. They are substantive? They are details about the position. We could include them in a
list. - Also "Credit and P-Card policy" etc. That's also substantive. - "Background Investigation Policy" etc. - "Contact Information" etc. We need to decide what to keep. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO Policy Statement, USG Core Values Statement, etc. Also remove "Special Instructions to Applicants" maybe? That's application instructions? It says "Priority consideration will be given to those who complete the application process by 9/28/2026; however, screening will continue until the position is filled. We are unable to offer a work visa sponsorship for this position. You must be authorized to work in the U.S. to apply." That's application instructions; we should remove. Also "Posting Specific Questions" and "Applicant Documents Required Documents" etc are application instructions; remove. Thus we keep: Posting Number, Working Title, Department, About the University, Position Summary, Minimum Qualifications, Preferred Qualifications, Knowledge Skills Abilities, Duties/Responsibilities (with sub-sections), Work Schedule, Benefits, FLSA Exempt FTE, maybe other yes/no fields, Credit and P-Card policy, Background Investigation Policy, Contact Information (Recruitment Contact). Also maybe "Location of Vacancy Athens Area". That's substantive. We need to format as HTML fragment. Let's decide sections: -
About the University
... (the paragraph about UGA)
-Position Summary
... (the paragraph)
-Minimum Qualifications
Bachelor’s degree in a related field plus 12 years of professional experience to include 5 years of supervisory experience or equivalency.
-Preferred Qualifications
... (list)
Could be a- with items.
-
- ... each item
- with internal for subheading.
Better:
Responsibilities
- Unit Leadership and Staff Supervision (60%) ... ...
Schedule
Monday-Friday 8:00 AM – 5:00 PM. Some nights and weekends may be necessary.
-Benefits
Benefits eligible; retirement plan options include TRS or ORP.
-Additional Information
maybe we can combine metadata: Posting Number, Working Title, Department, FLSA Exempt FTE 1.00, Location, etc. But we already have a short paragraph for metadata at top. Could doPosting Number: S15752P. Working Title: Director for Accessibility & Testing. Department: VPSA-Accessibility & Testing. FLSA Status: Exempt. FTE: 1.00. Location: Athens Area.
- Also include the yes/no fields: Is driving a responsibility? No. Is this a Position of Trust? Yes. Does this position have operation, access, or control of financial resources? Yes. Does this position require a P-Card? No. Is having a P-Card an essential function? No. Does this position have direct interaction or care of children under 18 or direct patient care? No. Does this position have Security Access (e.g., public safety, IT security, personnel records, patient records, or access to chemicals and medications) Yes. Credit and P-Card policy: Be advised a credit check will be required for all positions with financial responsibilities. For additional information about the credit check criteria, visit the UGA Credit Background Check website. Background Investigation Policy: Offers of employment are contingent upon completion of a background investigation including, a criminal background check demonstrating your eligibility for employment with the University of Georgia; confirmation of the credentials and employment history reflected in your application materials (including reference checks) as they relate to the job-based requirements of the position applied for; and, if applicable, a satisfactory credit check. You may also be subject to a pre-employment drug test for positions with high-risk responsibilities, if applicable. Please visit the UGA Background Check website. We could put those underAdditional Requirements
or similar. But we need to avoid too many sections; maybe combine all metadata into oneafter the heading? However the instruction: "Prefer a few substantive sections over many thin ones." So we should aim for maybe 6-8 sections. Let's list sections: 1. About the University 2. Position Summary 3. Minimum Qualifications 4. Preferred Qualifications 5. Knowledge, Skills, and Abilities 6. Responsibilities 7. Schedule 8. Benefits 9. Additional Information (metadata + yes/no + checks) That's 9 sections, maybe okay. We need to ensure we don't include filler like "commensurate with experience". We'll omit Pay. Now we need to write the HTML. Let's extract the exact text for each. About the University of Georgia: "Chartered by the state of Georgia in 1785, the University of Georgia is the birthplace of public higher education in America and is the state’s flagship university (https://www.uga.edu/). The proof is in our more than 240 years of academic and professional achievements and our continual commitment to higher education. UGA is currently ranked among the top 20 public universities in U.S. News & World Report. The University’s main campus is located in Athens, approximately 65 miles northeast of Atlanta, with extended campuses in Atlanta, Griffin, Gwinnett, and Tifton. U
Knowledge, Skills, and Abilities
Responsibilities
maybe we can include subheadings inside? But we cannot use headings other than? The instruction only says use for section headings; it doesn't forbid using etc but safer to stick to . We could embed the sub-sections as
etc but safer to stick to . We could embed the sub-sections as
with bold headings? But we need to preserve the percentages. Could use