Before They Even Apply: Bridging the Gap Between 2017 Application UX and Modern Standards

In 2017, I systematically evaluated 62 community college applications across the country. Published under my maiden name, Stark, in 2017, the study revealed that the majority of systems scored well below the System Usability Scale benchmark of 68.

Nearly a decade later, these issues persist across higher education. When we map those findings against today’s digital design frameworks—Nielsen’s heuristics, WCAG 2.2, and service design—one conclusion stands out: Application friction serves as a direct equity barrier.

Here is how the systemic failures of 2017 stack up against modern digital standards.

Usability Area	2017 Research Findings (Stark, 2017)	Modern UX & Digital Service Standard
Findability & Entry Points	Applications buried three to five clicks deep, with interchangeable terms like Apply, Admissions, Enrollment, and Registration.	Clear primary call-to-action button visible above the fold on the homepage, backed by standardized site taxonomy and search-optimized metadata.
Language & Cognitive Load	Unexplained institutional jargon like matriculation, residency, or home campus, alongside dense wall-of-text instructions at the top of pages.	Plain-language microcopy, progressive disclosure, contextual tooltips, and reading levels tuned to broad public audiences.
Flow & Navigation	Non-linear steps jumping across vendor systems, broken Back buttons that wipe data, and missing progress trackers.	Single canonical path with step-based indicators, predictable navigation, and clear step labels aligned to user mental models.
System Status & Feedback	Unclear save states, ambiguous submission screens, and session timeouts occurring without warning.	Real-time feedback, persistent autosave indicators, and explicit session timeout warnings with countdowns.
Error Prevention & Recovery	Cryptic system errors, error summaries placed at the top of long pages, and zero input retention upon failure.	Inline field-level error messages in plain language, input preservation, and smart validation tolerant of formatting variants.
Consistency & Standards	Jarring visual and structural shifts when moving from the college homepage to third-party vendor application portals.	Unified design systems, pattern libraries, and seamless visual transitions across vendor-hosted subdomains.
Mobile Responsiveness	Layouts breaking on phones, tiny tap targets, and mandatory embedded print-only PDFs required within the application flow.	Mobile-first responsive design fully ready for completion on a smartphone without printing, scanning, or desktop workarounds.
Security & Friction	Early demands for sensitive data like Social Security Numbers without context, alongside fragmented logins across multiple portals.	Just-in-time contextual explanations for sensitive data, single sign-on integration, and staged identity verification matched to actual risk.
Help & Escalation	Hidden support contacts, static FAQs unaligned to the form flow, and zero live or asynchronous assistance options.	Contextual inline help, visible support affordances offering chat, email, or phone, and explicit response-time expectations.

Key Takeaways: What Has Changed and What Hasn’t

When we overlay these findings onto contemporary digital strategy, four shifts stand out:

• Heuristics are baseline expectations now. In 2016, applying Nielsen’s Ten Usability Heuristics to higher education forms represented novel academic research. Today, feedback loops, clear language, and error recovery are baseline expectations in consumer software.
• Accessibility is an equity imperative. Under WCAG standards, dense jargon, missing field labels, and non-responsive forms create active barriers for students with disabilities, lower digital literacy, or mobile-only internet access.
• Admissions is a complete service journey. Modern service design maps the entire student lifecycle. Treating the application as a single cohesive experience builds continuity between the website, the form, and the onboarding portal.
• Measurement requires institutional governance. Usability evaluation needs to be an ongoing institutional practice. Modern organizations routinely track System Usability Scale scores, task completion rates, and step-by-step funnel drop-offs.

The Core Question

Why are higher education institutions still falling behind in treating digital systems usability as a core student service?

When poorly designed software stands between prospective students and their education, it creates unnecessary institutional friction.

Before They Even Apply is available now on Amazon.

Comments are open: What friction points are you still seeing in higher education admissions workflows today?