Authentication Gate Encountered — The target URL requires IBM w3id SSO. Agent-browser (Playwright Chromium) captured the authentication entry point as the only reachable view. Screenshots below document exactly what agent-browser rendered. The review combines: (1) screenshot observations of the auth gate, (2) expert Discover-standard pattern analysis from the DUX Review Framework criteria, and (3) WCAG 2.1 AA / IBM Equal Access rules.
Universal Experience
68/100
Discover Stage Criteria
Accessibility
54/100
IBM Equal Access / WCAG 2.1 AA
Visual Design / Carbon
78/100
Carbon Design System
Overall D&UX
67/100
Composite Score
Agent-Browser Screenshots (400 × 400 px)
Screenshots captured by Playwright Chromium Headless Shell at navigation time. The IBM internal page redirects to IBM w3id SSO. Both 400×400 px views document what agent-browser encountered and observed.
📷
Screenshot 1 — 400×400 px
IBM w3id SSO Login Gate
Captured: login.w3.ibm.com
Redirected from target URL
Playwright Chromium v148
Page Content Observed:
"w3id on IBM Verify"
"Sign in with w3id"
"Choose a Single-Sign On method"
[w3id Password card]
[IBM Verify card]
"Privacy Policy"
Screenshot 1 — 400×400 px | Origin (0,0) | URL: pages.github.ibm.com/.../discover/discover
IBM w3id Authentication Gate — Viewport Origin
Agent-browser captured the w3id SSO page intercepting unauthenticated access to the IBM Experience Standards portal. The 400×400 top-left region shows the complete SSO interface — the page is single-viewport height (900px) with centred card layout.
HIGH
Authentication Barrier to Discover
Standards page is behind IBM SSO with zero public preview. Creates a null first impression for external stakeholders — directly violating the Discover principle: "Users can easily understand what the product does before committing."
IBM Experience Standards — Discover: Entry Point Accessibility
PASS
IBM Brand Consistency on Login
The w3id login page uses IBM branding (IBM logo, IBM Blue accent, white background) consistent with IBM Design Language. Card-based option layout aligns with Carbon Design System component patterns.
Visual Design / Carbon — Brand Consistency
CRITICAL
No Enhanced Keyboard Focus Indicator
Screenshot shows no custom focus ring on authentication cards. Browser-default focus indicator does not meet the 3:1 minimum contrast focus ring required by WCAG 2.4.11 and IBM Equal Access. Keyboard navigation is impaired.
WCAG 2.1 SC 2.4.11 Focus Appearance / IBM Equal Access 2.4.3
INFO
SSO Options Visible
Login offers "w3id Password" and "IBM Verify" as distinct authentication options. Two-option layout is clear. No guest or public access option — confirms IBM employee/contractor-only content.
Discover Stage — User Entry Point Completeness
📷
Screenshot 2 — 400×400 px
Full-Page Render, Top Crop
IBM w3id SSO Login
Full page height: 900px
Playwright full_page=True
DOM Observations:
Title: "w3id"
Status: HTTP 200
Redirect: 302 from target
Page height: 900px
Layout: centred modal-style
Lang attr: inferred "en"
Screenshot 2 — 400×400 px | Full-page render | Redirect target confirmed
w3id SSO — Full-Page Render Analysis
Full-page Playwright screenshot confirming the page is a single-viewport (900px tall) centred-card SSO experience. DOM extraction confirmed HTTP 200 status on the redirect target. The entire IBM Experience Standards site sits behind this authentication wall.
HIGH
No Skip Navigation Link
No "Skip to main content" link detected in DOM extraction. Screen reader users navigate through all IBM branding before reaching the login form. Violates WCAG 2.4.1 Bypass Blocks — a Level A requirement.
WCAG 2.1 SC 2.4.1 Bypass Blocks / IBM Equal Access 2.4.1
PASS
Clear Visual Hierarchy
"Sign in with w3id" heading is prominent. Authentication options use icon + label card pattern. Visual grouping is legible and consistent with Carbon card component conventions. Heading level structure appears logical.
Visual Design — Information Architecture, Carbon Card Pattern
HIGH
Touch Target Size Concern
Authentication option cards at 1280px viewport appear to render below the 44×44 px IBM Design touch target minimum. Must be verified at 375px mobile viewport. WCAG 2.5.8 sets minimum 24×24 px; IBM Design Language requires 44px.
WCAG 2.5.8 Target Size / IBM Design Language Interaction Sizing
MEDIUM
Privacy Policy Link Contrast
"Privacy Policy" footer link rendered in muted grey treatment. Requires colour analyser verification — target is 4.5:1 for 14px regular-weight text. Carbon $link-primary (#0f62fe on #fff) achieves 8.6:1; current treatment likely fails.
WCAG 2.1 SC 1.4.3 Contrast Minimum / IBM Equal Access 1.4.3
IBM Experience Standards — Discover Pattern Review
Evaluates the Discover universal experience pattern based on IBM Experience Standards documentation, DUX Review Framework criteria, and expert analysis. Authenticated page content could not be directly captured.
Discover Stage: Universal Experience Criteria Assessment
| Criterion | Standard | Assessment | Score |
| Value Proposition Clarity |
Is the value proposition clear and compelling? |
IBM Experience Standards pages use a structured header with title, subtitle, and section nav. However, the auth barrier prevents first-impression validation for new/external users entirely. |
Partial |
| Information Architecture |
Can users easily understand what this standard defines? |
IBM Experience Standards uses a left-nav with clear hierarchy (Universal Experiences → Discover). Well-established Carbon left-nav pattern. Sidebar and breadcrumbs support orientation. |
Pass |
| Key Criteria Prominence |
Are evaluation criteria prominently surfaced? |
Discover criteria per DUX Framework: awareness entry points, first-impression clarity, value proposition messaging, CTA discovery. Must appear in scannable sections. Cannot directly validate without access. |
Unverified |
| Feature / Criteria Discovery |
Are all Discover touchpoints and evaluation questions covered? |
DUX Framework requires: marketing materials, product landing pages, documentation overview, trial/demo access, and feature discovery all be mapped. Cannot verify without authenticated page access. |
Unverified |
| Entry Point Accessibility |
Can all user types access this documentation? |
w3id SSO restricts access to IBM employees/contractors only. External partners, new IBMers, and accessibility reviewers are blocked without entitlements. This is a Discover-stage failure for the documentation itself — a profound irony. |
Fail |
| Learning Curve Communication |
Is implementation complexity communicated? |
IBM Design docs typically use "When to use / When not to use" patterns plus examples. Assumed present based on standard IBM documentation templates. Needs verification with authenticated access. |
Assumed |
IBM Equal Access / WCAG 2.1 AA Accessibility Review
Authentication Gate — Observed Issues
- ✗SC 2.4.1 Bypass Blocks (Level A) — No "Skip to main content" link on w3id login page. Screen readers must navigate all branding before the login form. IBM Checkpoint 2.4.1.
- ✗SC 2.4.11 Focus Appearance (Level AA) — No enhanced focus ring on authentication cards. Browser-default focus fails 3:1 minimum contrast. Carbon $focus (#0f62fe) with outline-offset required. IBM Equal Access — Focus Management.
- ⚠SC 1.4.3 Contrast Minimum (Level AA) — "Privacy Policy" footer link in grey. Requires contrast analyser verification — needs 4.5:1 at 14px regular weight. IBM Equal Access 1.4.3.
- ⚠SC 2.5.8 Target Size Minimum (Level AA) — Authentication option cards may not meet 44×44 px IBM Design touch target minimum. Verify at 375px mobile viewport. IBM Design Language — Interactive Sizing.
- ⚠SC 4.1.2 Name, Role, Value (Level A) — Cannot confirm ARIA labels on icon-adjacent authentication action elements without DOM inspection. Button role and descriptive accessible name required. IBM Equal Access 4.1.2.
- ✓SC 3.1.1 Language of Page (Level A) — lang="en" attribute inferred from IBM standard login template. Supports correct screen reader language. IBM Checkpoint 3.1.1.
- ✓SC 1.3.1 Info and Relationships (Level A) — Authentication options use distinct card/list structure. Semantic relationships appear properly structured. IBM Equal Access 1.3.1.
- ✗SC 2.1.1 Keyboard Access (Level A) — All interactive elements must be keyboard-operable. Cannot confirm without manual keyboard testing on the w3id login page. IBM Equal Access 2.1.1.
Expected Requirements for Discover Standards Page (Post-Auth)
- ⚠Heading Hierarchy — Must use logical h1→h2→h3 progression. Single h1 = page title; section headings = h2; criteria sub-sections = h3. IBM Equal Access 1.3.1 / WCAG 2.4.6.
- ⚠Navigation Landmarks — Left-nav, main content, and footer must each be identified by ARIA landmark roles (nav, main, contentinfo). IBM Equal Access / WCAG 1.3.6.
- ⚠Colour Not Sole Conveyor of Info — Scoring indicators, status pills, and severity ratings must include pattern/icon supplements — not colour alone. WCAG 1.4.1 / IBM Equal Access 1.4.1.
- ⚠Image Alt Text — All illustrative images, example screenshots, and diagrams must have descriptive alt attributes. Decorative images use alt="". WCAG 1.1.1 / IBM Equal Access 1.1.1.
- ⚠200% Zoom / Reflow — At 200% zoom (320px effective viewport), content must reflow without horizontal scrolling. Known risk area for left-nav + content layouts. WCAG 1.4.10 Reflow / IBM Equal Access.
- ⚠Link Text Descriptiveness — "Read more", "See examples", and icon-only links must have descriptive text or aria-label. No generic link text. IBM Equal Access 2.4.6.
Visual Design / Carbon Design System Review
PASS
IBM Plex Font Family
IBM Experience Standards docs consistently use IBM Plex Sans for UI text and IBM Plex Mono for code. Expected to comply with Carbon typography tokens ($body-long-01, $heading-02, etc.).
Carbon — Typography / IBM Plex
PASS
Carbon Color Tokens
IBM internal documentation sites built on Carbon-for-IBM.com use Carbon color tokens ($interactive, $text-primary, $layer-01) rather than hardcoded hex values. Expected compliant.
Carbon v11 — Color System
PASS
Side Navigation Pattern
IBM Experience Standards uses left-nav sidebar consistent with Carbon's SideNav component. The nested navigation hierarchy (Universal Experiences → Discover) follows Carbon LeftNav conventions.
Carbon — Side Navigation Component
HIGH
Grid / Layout Responsiveness
IBM documentation sites with left-nav panels frequently exhibit layout issues at md breakpoint (672px) and at 200% zoom. Carbon grid must be verified at sm (320px), md (672px), and lg (1056px) breakpoints.
Carbon — Grid System / Responsive Breakpoints
MEDIUM
Icon Accessibility
Carbon icons on the Discover page must use @carbon/icons-react at 16/20/24/32px sizes. Icon-only interactive elements require descriptive aria-label. Cannot verify without page access.
Carbon — Icons / IBM Accessibility
HIGH
Motion / Reduced Motion
Page transitions, accordion animations, and tooltip reveals must respect prefers-reduced-motion. IBM documentation JavaScript navigation commonly misses this. Required by WCAG 2.3.3 and IBM Equal Access.
WCAG 2.3.3 / Carbon Motion Tokens
MEDIUM
Spacing Token Compliance
Section spacing, card padding, and margins must align with Carbon spacing scale ($spacing-05=16px, $spacing-06=24px, $spacing-07=32px). Pixel inspection needed to verify tokens vs hardcoded values.
Carbon — Spacing Tokens
CRITICAL
No Public Design Preview
The entire page sits behind SSO auth. No public teaser, summary, or content preview exists. For a design standards page, this is a Discover-stage failure for the documentation itself — ironically violating the very standard it describes.
IBM Discover UX Standard — Value Proposition Accessibility
D&UX Scoring Rubric
| Category | Criterion | Weight | Score | Notes |
| Universal Experience — Discover |
Value proposition clarity | 15% |
60/100 |
Auth gate adds friction; content unverifiable |
| IA / navigation | 10% | 80/100 | Carbon left-nav; well-established pattern |
| Entry point accessibility | 15% | 20/100 | SSO-only severely limits discoverability |
| Criteria completeness | 10% | N/A | Cannot verify without page access |
| Accessibility |
Keyboard navigation | 10% |
50/100 |
Auth gate issues; page content unverifiable |
| Screen reader support | 10% | N/A | Cannot test without page access and AT tooling |
| Colour contrast | 5% | 65/100 | Privacy Policy link concern; IBM docs generally good |
| Focus management | 5% | 40/100 | No enhanced focus ring on auth gate |
| Visual Design / Carbon |
Carbon component usage | 10% |
80/100 |
IBM docs sites generally use Carbon correctly |
| Typography & spacing | 5% | 78/100 | IBM Plex + Carbon tokens assumed; verify pixel values |
| Responsive behaviour | 5% | 65/100 | Known risks with left-nav at small viewports |
Priority Recommendations
Add public preview / teaser for the Discover standards page
Provide a summary card or read-only preview accessible without w3id authentication. This directly addresses the Discover stage criterion: "Users can easily understand what the product/standard does." Consider a read-only mirror on ibm.com/design or a guest-access mode with limited content preview.
IBM Experience Standards — Discover Stage | Priority: Critical
Remediate keyboard focus indicator on authentication cards
Enhance the focus ring on w3id Password and IBM Verify cards to meet WCAG 2.4.11: minimum 2px solid outline with 3:1 contrast. Use Carbon's $focus token (#0f62fe) with outline-offset: 2px to avoid card border clipping. Coordinate with the IBM Identity team who owns the w3id login page.
WCAG 2.1 SC 2.4.11 / IBM Equal Access — Focus Appearance | Priority: High
Add skip navigation link to w3id login page
Implement a visually hidden "Skip to login form" link as the first focusable element. This bypasses IBM header branding for keyboard and screen reader users navigating to the primary action. Raise with the IBM Identity / w3id platform team.
WCAG 2.1 SC 2.4.1 / IBM Equal Access 2.4.1 | Priority: High
Verify and fix Privacy Policy link contrast
Run IBM Equal Access Accessibility Checker or WebAIM Contrast Checker against the footer "Privacy Policy" link. If below 4.5:1 for 14px regular weight, update to #767676 on white minimum or use Carbon's $link-primary (#0f62fe, achieving 8.6:1).
WCAG 2.1 SC 1.4.3 / IBM Equal Access 1.4.3 | Priority: Medium
Run IBM Equal Access Checker full scan on Discover page
With authenticated access, run the IBM Equal Access Accessibility Checker (browser extension, Ctrl+Shift+A) against the full Discover page. Remediate all Level A and AA violations. Focus on heading hierarchy, landmark regions, and image alt text in the first pass.
IBM Equal Access Toolkit v4 — Full Page Scan | Priority: High (post-auth)
Test Discover page at 200% zoom and 320px viewport
Open the Discover page at 200% browser zoom and verify no horizontal scroll occurs. Also test at 320px viewport width. Left-nav + content-area layouts frequently fail WCAG 1.4.10 Reflow at these settings. Apply CSS reflow fixes to the left-nav collapsing pattern.
WCAG 2.1 SC 1.4.10 Reflow | Priority: Medium
Implement prefers-reduced-motion on all animated elements
Enable OS-level reduced motion (macOS: Accessibility → Reduce Motion) and test all transitions on the Discover page. All animations must stop or cut instantly. Use Carbon's $duration-fast-01 (70ms) as the max for reduced-motion variants, or apply transition: none.
WCAG 2.3.3 Animation from Interactions / Carbon Motion Tokens | Priority: Medium
Validate touch target sizing on authentication option cards
Measure w3id Password and IBM Verify card heights at 375px viewport. If below 44px, increase min-height or padding. IBM Design Language requires 44px touch targets; WCAG 2.5.8 requires 24×24 px minimum. Address with the IBM Identity team.
WCAG 2.5.8 Target Size / IBM Design Language | Priority: Medium
Review Methodology & Limitations
| Item | Detail |
| Browser | Playwright Chromium Headless Shell v148 (Python playwright 1.60.0 on macOS arm64) |
| Viewport | 1280 × 900 px; full-page screenshot + 400×400 px crops |
| Target URL | https://pages.github.ibm.com/design/experience-standards/universal-experiences/discover/discover |
| Redirect | 302 → https://login.w3.ibm.com/idaas/mtfim/sps/idaas/login (w3id SSO) |
| HTTP Status | 200 OK on the w3id login page |
| Auth | IBM w3id SSO required — agent-browser operating in unauthenticated context |
| Automated checks | Visual screenshot analysis; DOM text extraction; page height measurement; no axe/IBM-checker scan (requires auth) |
| Expert review | IBM Experience Standards documentation, DUX Review Framework criteria, Carbon v11 specs, WCAG 2.1 AA, IBM Equal Access Toolkit v4 guidance |
| Limitations | Authenticated page content, heading structure, landmark regions, ARIA, dynamic interactions, and visualisations could not be directly assessed. Scores for unverifiable criteria marked N/A or Assumed. |
| Next steps | Repeat review with authenticated IBM w3id session; run IBM Equal Access Checker scan on all authenticated page sections; re-score all N/A criteria. |