An Accessible Salesforce Calendar for Government Teams
Agencies on Salesforce book inspections, appointments, facilities and field staff every day. The federal deadline for making those pages accessible just moved to April 2027. Here is what it asks of the calendar, and how MultiDatePick answers it.
In April 2024 the Department of Justice set a firm technical standard for state and local government websites and apps under ADA Title II: WCAG 2.1 Level AA. In April 2026 it gave agencies one more year to get there. That year is the window to fix the parts of your Salesforce org that residents and staff actually click, and the scheduling calendar is near the top of that list.
The dates that apply now
An interim final rule published April 20, 2026 extended both compliance dates by one year. The standard itself did not change.
| Public entity | Comply by | Standard |
|---|---|---|
| Serving 50,000 people or more | April 26, 2027 | WCAG 2.1 AA |
| Under 50,000, and special district governments | April 26, 2028 | WCAG 2.1 AA |
Two things are easy to miss. First, many articles still quote April 2026, which is out of date. Second, the Justice Department is explicit that the obligation to make services accessible did not pause: the dates set when the specific technical standard becomes enforceable, not when accessibility starts to matter. Federal agencies were never on this clock at all; they answer to Section 508, which already requires WCAG 2.0 AA, and every one of those criteria is also part of 2.1 AA.
Where scheduling shows up in a government org
Almost every public service on Salesforce has a calendar in it.
Inspections
Homeowners pick a day for a building or permit inspection.
Appointments
Residents book licensing, benefits and records visits.
Facility rentals
Families reserve pavilions, ballfields and community rooms.
Clinics
Vaccination slots with a fixed number of seats per hour.
Field staff
Inspectors, caseworkers and poll workers scheduled across a month.
Closures
Meeting rooms blocked for holidays and maintenance.
What MultiDatePick does, criterion by criterion
MultiDatePick was built to WCAG 2.1 AA from the start, not retrofitted for a sales deck. This is what that looks like in the component your residents and staff actually use:
| What a reviewer checks | What MultiDatePick does |
|---|---|
| Real grid semantics | ARIA grid pattern: grid, row, gridcell and columnheader, with aria-selected on every day cell |
| Keyboard-only use | Arrow keys move through the days, Tab moves between the calendar, status pills and time grid, Enter or Space selects, Escape closes. No keyboard traps. |
| Screen reader announcements | Every day cell, time slot and icon button carries an accessible name. Errors and confirmations are announced through role="alert" and role="status" without moving focus. |
| Automated testing | Zero axe-core violations across the Date, Date Time and Booking components, with 28 passing rules each |
| Language access | Built-in translations for 9 languages: English, Spanish, French, German, Italian, Japanese, Hindi, Brazilian Portuguese and Simplified Chinese |
| Documentation | A published VPAT 2.5 report covering WCAG 2.1 A and AA, Revised Section 508 and EN 301 549 |
The VPAT marks two criteria as Partially Supports, and says exactly why. Contrast: the default palette meets 4.5:1, but admins can choose their own status colors, and a vendor cannot guarantee a color it did not pick. Reflow: at 320 pixels wide the month grid keeps its seven columns and narrows rather than stacking. An honest report with two explained partials is worth more in a procurement file than a wall of unexplained Supports, and reviewers know it.
How it compares
Agencies usually weigh four ways to put a scheduling calendar in Salesforce. Only one of them gives you multi-date and resource booking, published accessibility documentation and resident data that never leaves your org, all on day one.
| Standard date field | External scheduling tool | Custom-built LWC | MultiDatePick | |
|---|---|---|---|---|
| Resident data stays in your Salesforce org | Yes | Usually not | Yes | Yes |
| Many dates, time slots and resources in one step | One date per field | Yes | Only what you build | Yes |
| Conflict and capacity checks | No | Yes | Only what you build | Yes |
| Accessibility documentation for procurement | Covered by Salesforce | Varies by vendor | You write and test your own | Published VPAT 2.5 |
| Works in Flows, record pages and Experience Cloud | Yes | Embedded or linked out | Only what you build | All of them |
| Time to a working calendar | Immediate | Integration project | Months | An afternoon, no code |
The standard date field is accessible, but it holds one date, so it cannot run a booking. An external tool can book, but residents' names, addresses and appointment history then live in someone else's system, which is a second security review and a second accessibility review. A custom build keeps the data home, but your team now owns the WCAG testing, the VPAT and every fix, forever. MultiDatePick is the only option on the list that clears every row.
Built for how government buys
- 100% Salesforce native. No external servers, no outbound callouts, no subprocessors. Resident data stays in your org under the sharing and field-level security you already configured, so there is no new data processor to approve. See Trust & Security.
- Passed Salesforce's AppExchange security review. The managed package went through Salesforce's own review before listing.
- Resident self-service. The Booking component runs on Experience Cloud sites, so residents can pick an inspection window or reserve a facility on the same accessible calendar staff use.
- No code to maintain. A Setup Wizard writes the configuration, with a live preview of the real component, so a small IT team is not signing up for a custom build it has to keep compliant.
Getting ready before April 2027
- Inventory every date picker your public touches. Experience Cloud pages first, then staff Screen Flows. Note which ones are standard fields and which are third-party or custom components.
- Request a current VPAT for every third-party component. Check the report date and that it was tested on the packaged version you actually install.
- Test the booking path with a keyboard alone. Pick a date, choose a time, save. If you cannot finish without a mouse, neither can a resident who relies on a keyboard or a screen reader.
The accessible Salesforce calendar, ready before your deadline
MultiDatePick is coming to the Salesforce AppExchange. Read the full conformance report, try the live demo, or get the launch note.
100% Salesforce native. Your data and your configuration never leave your org.