Skip to content
KiweelyKiweelyKiweely

Building WCAG 2.2 AA Accessible Employee Screens on Top of Workday

Custom employee screens placed in front of Workday are workplace accommodation surfaces under the ADA, Section 508, and the European Accessibility Act. Meeting WCAG 2.2 Level AA requires contrast-verified tokens, 2px focus rings, 44px touch targets, semantic labels, and reduced motion.

  • By Kiweely
  • 7 min read
On this page

Every custom employee portal, frontline phone app, or chat approval card placed in front of Workday is a mandatory workplace tool—meaning a single inaccessible control blocks a blind, low-vision, or motor-impaired worker from checking pay, requesting leave, or clocking hours. Core Workday web pages already target W3C WCAG 2.2, US Section 508, and ETSI EN 301 549 out of the box without tenant setup (Edit Tenant Setup - System), so replacing Workday’s menus with a custom web app that fails WCAG 2.2 Level AA creates an immediate legal and operational regression.

Many internal engineering teams and low-code portal builders treat accessibility as a post-launch audit item. By the time an accessibility specialist tests a custom time-off calendar or payslip viewer with NVDA, JAWS, VoiceOver, or TalkBack, fixing contrast, keyboard traps, and tiny icon buttons requires rewriting the component library. Baking WCAG 2.2 Level AA constraints directly into the design tokens and component primitives prevents those failures before the first Workday API call is wired.

Five WCAG 2.2 AA Failures That Break Custom HR Screens

Employee self-service workflows combine dense tabular data (payslip lines, accrual balances), interactive date pickers (Request Time Off), file dropzones (Create Expense Report), and modal confirmations. Across those controls, five specific WCAG 2.2 AA criteria account for almost every failed workplace accommodation review:

WCAG 2.2 Criterion Minimum Requirement Practical Engineering Standard for Workday Screens
WCAG 2.2 Criterion1.4.3 Contrast (Minimum) & 1.4.11 Non-Text Contrast Minimum Requirement4.5:1 for body text (3:1 for large text); 3:1 for UI control boundaries and active states. Practical Engineering Standard for Workday ScreensLock text and surface pairs in a verified token table across light and dark themes. Add a 3:1 keyline around bright accent fills on white backgrounds so buttons never vanish in sunlight or low vision.
WCAG 2.2 Criterion2.4.7 Focus Visible & 2.4.11 Focus Not Obscured (Minimum) Minimum RequirementKeyboard focus indicator must be clearly visible and never hidden behind sticky top bars or docked footers. Practical Engineering Standard for Workday ScreensRender a solid 2px high-contrast focus ring offset 2px from every interactive element, and set scroll-margin-top / scroll-margin-bottom to clear fixed navigation or approval bars.
WCAG 2.2 Criterion2.5.8 Target Size (Minimum) & Mobile Ergonomics Minimum RequirementAt least 24 × 24 CSS pixels under WCAG 2.2 AA (44 × 44 CSS pixels under WCAG AAA and Apple HIG; 48 × 48 dp on Android). Practical Engineering Standard for Workday ScreensEnforce 44px to 48px hit areas on every mobile tap target—including remove-attachment icons, date cells, and row actions—even when the visual glyph inside is 16px or 20px.
WCAG 2.2 Criterion1.4.1 Use of Color & 4.1.2 Name, Role, Value Minimum RequirementMeaning cannot rely on color alone; every custom control must expose programmatic name, role, and live state. Practical Engineering Standard for Workday ScreensPair every status (Approved, Pending, Needs You, Stopped) with both a distinct geometric glyph and a visible or screen-reader-accessible word; bind error messages with aria-describedby and aria-invalid="true".
WCAG 2.2 Criterion2.3.3 / 2.2.2 Motion & Pause, Stop, Hide Minimum RequirementRespect user motion preferences and allow pausing any non-essential movement lasting over 5 seconds. Practical Engineering Standard for Workday ScreensHonor @media (prefers-reduced-motion: reduce) globally so panels and sheets appear in their finished state without sliding, bouncing, or fading.

Designing Accessible Workday Forms and Approval Flows

1. Contrast Floors and Sunlight-Safe Accent Keylines

Brand palettes frequently fail when marketing colors are repurposed for form controls. A bright lime, yellow, or cyan primary button might carry crisp dark text (on-accent above 10:1), yet the button shape itself can measure 1.2:1 against a pure white background—violating WCAG 1.4.11 Non-Text Contrast (3:1 minimum for control boundaries). Adding a 1px border token calibrated to at least 3:1 against white preserves the brand accent while keeping the button boundary unmistakable for users with low contrast sensitivity or warehouse workers standing under glare.

Similarly, muted gray hint text (“Enter hours in 0.5 increments” or “Balance projected as of November 20”) must never drop below 4.5:1 against both the page ground and recessed card wells, and disabled or offline rows should step down to a readable muted ink token rather than applying opacity: 0.4 across the entire container.

2. Semantic Date Entry Instead of Mouse-Only Calendar Grids

Custom date-range widgets built from <div> grids are the single most common keyboard trap in custom Request Time Off apps. When a worker navigates via keyboard or screen reader:

  • Provide plain, labeled date inputs or a properly structured <table role="grid"> where arrow keys move day by day, Page Up/Page Down switch months, Enter/Space toggles selection, and Escape closes popovers while returning focus to the trigger button.
  • Announce Workday validation results returned from GET /workers/{ID}/validTimeOffDates (such as non-working days, company holidays, or blackout dates) inside individual day labels ("Thursday, November 26, Company Holiday, unavailable") rather than coloring the square gray.
  • When Workday rejects a submission—for example, a request that breaches a plan’s Time Off Lower Limit or a locked Time Tracking period—move focus to an error summary with role="alert" or directly to the offending field, stating plainly whether anything was changed in Workday and what the worker needs to adjust.
html
<div class="field-group">
  <label for="daily-hours">Hours requested for Friday, November 20</label>
  <input
    id="daily-hours"
    name="dailyQuantity"
    type="number"
    step="0.5"
    min="0.5"
    max="24"
    aria-invalid="true"
    aria-describedby="hours-hint hours-error"
  />
  <p id="hours-hint">Available Vacation Plan balance on this date: 6.0 hours.</p>
  <p id="hours-error" role="alert">
    Stopped: Nothing was submitted to Workday. Reduce hours to 6.0 or select Unpaid Time Off.
  </p>
</div>

3. Accessible Authentication and Biometric Re-Entry (WCAG 3.3.8)

WCAG 2.2 Criterion 3.3.8 Accessible Authentication (Minimum) prohibits forcing users to transcribe, memorize, or solve cognitive puzzles to sign in unless an assistive mechanism (password managers, copy-paste, or WebAuthn/passkeys/SSO) is supported. When a custom screen authenticates through Workday’s OAuth 2.0 Authorization Code Grant with PKCE (Register API Client) delegated to your corporate SAML 2.0 or OIDC identity provider, employees sign in once with enterprise SSO and re-enter subsequent phone sessions with Face ID, Touch ID, or Android fingerprint—satisfying both strict zero-password security and WCAG 3.3.8.

4. Responsive Tables That Do Not Force Two-Dimensional Scrolling

WCAG 1.4.10 Reflow requires screens to work at 320 CSS pixels wide (400% desktop zoom) without requiring horizontal and vertical scrolling at the same time, except for genuinely two-dimensional layouts. A desktop manager table listing Position ID, Job Profile, Target Hire Date, Location, and Requisition Status across six columns becomes unreadable when pinched onto a phone viewport. Below 600px (or at 400% zoom), transform multi-column Workday tables into stacked label-and-value definition blocks (<dl>), keeping every row action at a 48px touch height with a single tab stop per linked row.

Pre-Launch WCAG 2.2 AA Verification Checklist for Workday Screens

Run these six checks against real Workday Sandbox data before publishing any employee-facing screen:

  1. Automated Token & DOM Audit: Run axe-core against every state—empty, loading, populated, validation error, and approval modal—in both light and dark modes with zero violations.
  2. Unplugged-Mouse Pass: Complete an entire flow (sign in via SSO, select an eligible Time Off Type, adjust daily quantity, review projected balance, and submit or cancel) using only Tab, Shift+Tab, arrow keys, Space, Enter, and Escape. Verify the 2px focus ring is never clipped by a sticky header (2.4.11).
  3. 400% Zoom & 200% Text Spacing: Zoom a 1280px desktop browser window to 400% and verify no text truncates, overlaps, or forces horizontal page scrolling.
  4. Touch Target Inspection on Mobile: Measure every interactive control on iPhone and Android viewports; verify hit boxes measure at least 44 × 44 CSS pixels (48 × 48 on phone controls), well above the WCAG 2.2 24px floor.
  5. Screen-Reader Announcement Audit: Test with VoiceOver (macOS/iOS) or NVDA (Windows) to confirm icon-only controls, status glyphs, and currency/unit figures (8 Hours vs. 1 Day) read aloud in natural order.
  6. Reduced-Motion Toggle: Enable Reduce motion in macOS/iOS or Windows Accessibility settings and confirm zero auto-playing motion or sliding layout shifts remain.

How Kiweely Enforces Accessibility Across Custom Workday Experiences

Kiweely Leaf is coming next to let HRIS administrators describe custom employee portals, frontline phone apps, manager views, and chat approvals in plain English on top of live Workday APIs—without a Workday Extend license and with zero employee HR data stored at rest. Every screen Leaf generates is assembled from Kiweely’s verified component system, where light and dark contrast pairs are script-checked, every focusable element carries a 2px high-contrast focus ring, every phone control answers touches across a 48px square, states pair pixel glyphs with screen-reader text, and prefers-reduced-motion holds every transition still. For employees who prefer asking or acting in Claude, ChatGPT, or Gemini using screen readers, voice dictation, or keyboard chat, Kiweely Bridge is also coming next with per-employee Workday OAuth and accessible out-of-band browser approval cards.

Frequently asked questions

Which accessibility standards apply to custom employee portals built on Workday APIs?

Enterprise employee self-service portals are evaluated against W3C Web Content Accessibility Guidelines (WCAG) 2.2 Level AA, US Rehabilitation Act Section 508, Title I of the Americans with Disabilities Act (ADA), and ETSI EN 301 549 in the European Union.

What changed between WCAG 2.1 AA and WCAG 2.2 AA for Workday self-service forms?

WCAG 2.2 added Target Size Minimum (2.5.8, requiring at least 24 by 24 CSS pixels with spacing), Focus Not Obscured Minimum (2.4.11, preventing sticky headers from hiding focused inputs), Redundant Entry (3.3.7), and Accessible Authentication Minimum (3.3.8).

Why do color-coded status pills fail accessibility reviews on time-off and expense screens?

Relying on green, amber, or red alone violates WCAG 1.4.1 (Use of Color), and pale pastel badges regularly fail the 4.5:1 text contrast floor (1.4.3) and 3:1 non-text boundary rule (1.4.11). Every status must pair a distinct shape or glyph with an explicit text label.

How should custom Workday screens handle operating-system reduced-motion settings?

Inspect prefers-reduced-motion: reduce in CSS and JavaScript so transitions snap immediately to their final state, auto-playing walkthroughs pause by default, and zero essential balance or approval information depends on animation.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.