accommodation-request

Featured

Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.

AI & Automation 1,404 stars 250 forks Updated today MIT

Install

View on GitHub

Quality Score: 96/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Accommodation Request Skill Reasonable accommodations (US: ADA; UK: reasonable adjustments under the Equality Act; similar elsewhere) are a right, but getting them often stalls on how the request is framed: people over-share medical detail, ask for a vague "help," or frame it as a favor rather than an adjustment to a barrier. Employers and institutions respond best to a specific request that names the *barrier* and the *adjustment that removes it* — they generally don't need your diagnosis, only the functional limitation and what helps. This skill writes that request, guides how much to disclose, and prepares you for the interactive back-and-forth that follows. It is not legal advice; it routes to the formal process and to advocacy if you hit resistance. ## What This Skill Produces - A **barriers-and-adjustments map**: for each thing that's hard, the specific workplace/course barrier and the concrete adjustment that removes it (framed as an adjustment to a barrier, not a personal favor) - The **request letter/email**: to the right person (HR, disability services, manager per the process), citing the process, naming the adjustments, and inviting the interactive dialogue - **Disclosure guidance**: how much to share (usually the functional limitation and what helps, not the diagnosis), what you're not obliged to reveal, and where medical documentation is genuinely needed - A **process plan**: the interactive/good-faith dialogue that's expected, how to handle "...

Details

Author
mohitagw15856
Repository
mohitagw15856/pm-claude-skills
Created
8 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Featured

accessible-travel-planner

Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.

1,404 Updated today
mohitagw15856
Data & Documents Listed

bug-reporting

Load this skill whenever you are filing, reviewing, or generating accessibility bug reports — whether from automated tool output, manual testing, user reports, or testing with disabled people. The purpose of this skill is to make accessibility findings easier to report accurately, connect them to real people and tasks, and let developers reproduce, understand, and fix them without unnecessary back-and-forth. Absolutely always describe the barrier and its task impact before citing a WCAG criterion. Under no circumstances guess a disability diagnosis, treat automated tool output as a conformance conclusion, or expose secrets/personal data in a report.

49 Updated 1 weeks ago
mgifford
Code & Development Listed

event-accessibility-inclusion

Decide which accessibility and inclusion provisions a technical event commits to - the physical, sensory, dietary, economic and digital-access set, at what depth, sized for whom, funded from where - plus the public declaration of it and the data-handling posture for accommodation requests. Use whenever asked what accessibility a conference should offer, whether to caption talks, whether to run a quiet room, childcare or travel grants, how to write an accessibility page, or how to answer an accommodation request, even if the user never says "accessibility". Decides the bar, not delivery. Do NOT use for the code of conduct - use samber/dev-event-organizer-skills@event-code-of-conduct. Not legal advice; access duties vary by jurisdiction.

2 Updated 1 weeks ago
samber