Skip to main content

Google Scholar

Summary

Google Scholar presents significant accessibility challenges that create barriers for users with disabilities, particularly those using screen readers and keyboard navigation. While the platform does include some accessible features like properly labeled search fields and some link text, critical issues such as keyboard traps, missing heading structures, and unlabeled interface elements prevent users from effectively navigating and utilizing the platform's research capabilities.

The testing revealed issues including the complete absence of heading structures on the homepage, keyboard traps in filter controls, unlabeled buttons and regions, inaccessible dialog boxes, and tables without proper names or structure. These problems significantly impact the ability of users with disabilities to conduct academic research effectively.

Addressing these concerns would enable equitable access to Google Scholar's vast repository of academic resources for all users, including those relying on assistive technologies.

Top 3 Issues:

  1. Keyboard Traps in Filter Controls a. Radio button groups for Articles/Case Law selection trap keyboard focus, preventing users from navigating out without using the Escape key. b. Impact: Keyboard-only users and screen reader users become trapped and cannot continue navigation without specialized knowledge. c. WCAG Success Criteria: 2.1.2 No Keyboard Trap (A)
  2. Missing Heading Structure a. The homepage contains no heading elements, making it impossible for screen reader users to understand page organization or navigate efficiently. b. Impact: Screen reader users cannot quickly navigate to different sections of the page or understand the information hierarchy. c. WCAG Success Criteria: 1.3.1 Info and Relationships (A), 2.4.6 Headings and Labels (AA)
  3. Unlabeled Buttons and Missing ARIA States a. Critical interface elements like the hamburger menu button are announced as "unlabeled 0 button" and expandable menus don't communicate their expanded/collapsed state. b. Impact: Users cannot understand the purpose of controls or know whether their actions have produced the expected results. c. WCAG Success Criteria: 4.1.2 Name, Role, Value (A), 1.1.1 Non-text Content (A)

Disabilities Impacted

Blind and Low-Vision Users

  • Issues: Complete absence of heading structure, unlabeled buttons, keyboard traps, missing ARIA states for expandable elements, inaccessible dialogs, and tables without proper names or structure.
  • Impact: Screen reader users face extreme difficulty understanding page content, navigating between sections, and completing basic research tasks. The lack of proper semantics forces users to listen to entire pages linearly without the ability to skip to relevant content.

Users with Motor Disabilities

  • Issues: Keyboard traps in radio button groups, lack of escape instructions, inaccessible interactive elements in bar graphs, and unpredictable focus management.
  • Impact: Keyboard-only users become trapped in interface elements, requiring them to know specific key commands (Escape) that aren't communicated. Some functionality is completely inaccessible without a mouse.

Neurodiverse Users

  • Issues: Inconsistent navigation patterns, lack of clear heading structure, missing feedback for user actions, and confusing focus order.
  • Impact: The absence of clear page organization and inconsistent behavior makes it difficult for users to develop a mental model of the interface, increasing cognitive load and making research tasks unnecessarily complex.