Press "Enter" to skip to content

Google Can Read My Calendar, So Why the Hell Can’t It Find My Meeting?

I’ve been working with technology and accessibility for decades. I’ve tested software, worked with screen readers, and encountered plenty of situations where technology makes something unnecessarily difficult.

But sometimes, you run into something so ridiculous that you have to laugh.

On November 19, 2026, after attending a Los Angeles Metro Operations, Safety and Customer Experience Committee meeting, I wanted to find out when the next meeting was scheduled.

I maintain several Metro-related webpages, including meeting information, notices, and countdown scripts. Knowing when the next meeting takes place is important because I need that information to keep the pages current.

I had already spent considerable time testing an automatic bilingual meeting notice on my Operations webpage. That feature was working. The notice had switched to its inactive message after the day’s meeting, exactly as intended.

All I needed now was the date of the next meeting.

I figured I’d ask Google.

How difficult could that possibly be?

Asking Google a Simple Question

I have a Google account, Google Calendar, and a Google Assistant device. I’ve previously been able to ask about events during a particular week or other time period.

So I asked when the next Operations, Safety and Customer Experience Committee meeting was scheduled.

Google responded:

"Sorry, I didn’t understand."

All right. Maybe it didn’t recognize the full committee name.

I tried again, using different wording.

Same result.

Then I specifically asked about the meeting in my calendar.

This time, Google told me it couldn’t find anything.

I tried identifying the calendar containing my Metro events.

Again:

"Sorry, I didn’t understand."

What the hell?

I’m not asking the assistant to perform surgery, solve a complicated mathematical problem, or write a program.

I’m asking it to find an appointment.

An appointment in a calendar associated with the very account the assistant is supposed to use.

When a Human Being Becomes the Search Engine

I called my friend Preston for an unrelated reason. Earlier, Google Voice on my computer had been breaking up during calls, and I wanted to test whether rebooting the computer had resolved the problem.

While we were talking, I mentioned the calendar issue.

Preston offered to look up the meeting.

Initially, he went to my Operations webpage.

I explained that I hadn’t updated the page yet. That was precisely why I needed the meeting date.

He switched to the calendar, looked through the events, and found what I needed.

The next Operations, Safety and Customer Experience Committee meeting was scheduled for Thursday, January 21, 2027, at 1 p.m.

There it was.

A human being found the appointment that Google’s assistant couldn’t locate.

Of course, I could have opened Google Calendar on my iPhone and searched for it myself. But that wasn’t the point.

The point was that I had an assistant available and wanted to use it for the kind of task an assistant should reasonably be able to perform.

Let’s Ask Amazon Echo

Then I decided to try another assistant.

I asked my Amazon Echo when the next Operations meeting was scheduled.

Initially, that didn’t work either.

In several attempts, Echo acknowledged the request with a sound but provided no meaningful spoken answer.

That’s an accessibility concern in itself.

When someone relies on speech output, an acknowledgment sound doesn’t explain whether the assistant searched successfully, encountered an error, or simply couldn’t interpret the request.

An assistant should provide useful feedback, even when it cannot complete a task.

I wasn’t certain whether Echo was properly connected to my Google Calendar, so I decided to give it the benefit of the doubt.

Then I tried something different.

I asked Echo what was on my calendar for January 21, 2027.

This time, it worked.

Echo told me there was one event that day, at 1 p.m., and identified the Metro Operations, Safety and Customer Experience Committee meeting.

Well, how about that?

Echo could find the appointment when I supplied the date.

That established that Echo could access a calendar containing the event, even though it hadn’t successfully retrieved the meeting when I searched by name.

Google, Here’s the Date. Can You Find It Now?

Armed with the exact date, I returned to Google Assistant.

I asked:

"What’s on my calendar January 21st, 2027?"

Google told me it couldn’t find anything on my calendar for that day.

I tried again.

Same result.

Now this was getting interesting.

Echo could find the event. Preston could find the event. I knew the event existed.

Yet Google continued insisting it couldn’t find anything.

At this point, I decided to investigate the Google Assistant calendar settings.

And that’s where the evening took another turn.

An Unexpected VoiceOver Accessibility Problem

I opened the Google Assistant settings on my iPhone and navigated to Calendar.

The screen showed my Google account under "Your calendars," along with an expandable control.

I was using Apple’s VoiceOver screen reader.

VoiceOver announced the account and indicated that the list could be expanded.

Naturally, I double-tapped the control.

Nothing happened.

I tried again.

Still nothing.

Eventually, I turned VoiceOver off and located the expansion icon through direct touch.

That worked.

I was able to expand the account and see the available calendars.

This is a potential accessibility defect worth investigating further.

If a screen reader identifies an expandable control, users should be able to activate it through the standard screen-reader interaction.

They shouldn’t have to turn off their screen reader to reach a basic settings control.

I took screenshots of the settings screen and the expanded calendar list.

The expanded view showed two calendars associated with my account: my primary calendar and "L.A. Metro Events."

Both appeared checked.

After making the adjustment, the app reported that the update was successful.

I returned to the settings and tried the expansion control with VoiceOver again.

It still didn’t respond to the double-tap as expected.

That leaves two separate questions: whether the calendar configuration was contributing to the assistant’s search failures, and why the expansion control wasn’t working properly with VoiceOver.

Now Google Can Read the Meeting!

After checking the settings, I returned to Google Assistant.

I tried asking for the next Operations meeting again.

"Sorry, I didn’t understand."

I tried the full committee name.

Same result.

I tried identifying the Metro calendar.

Still no useful answer.

Then I changed the question entirely.

I asked:

"Hey Google, what’s on my calendar in January?"

Suddenly, Google could help!

It announced that there were seven entries and began reading them.

Among the events it identified were the January 6 San Fernando Valley Service Council meeting and the January 7 Public Safety Advisory Committee meeting.

And then it reached January 21.

There it was: the Metro Operations, Safety and Customer Experience Committee meeting at 1 p.m.

Wait a minute.

Google can read the event when I ask for January’s appointments, but it can’t tell me when that particular meeting is scheduled?

You’ve got to be kidding me.

The event exists. The assistant can retrieve it. It can announce the date, time, and at least part of the event title.

But when I ask it to find that meeting by name, it repeatedly tells me it doesn’t understand.

What Actually Failed?

There are several possible explanations.

The assistant may have difficulty matching a spoken meeting name against an event title. It may process date-range calendar requests differently from searches for individual events. There may also have been a calendar selection or synchronization issue earlier in the evening.

I can’t establish the exact technical cause from these tests.

I also can’t prove that the settings adjustment fixed the earlier date-specific retrieval failure, because I didn’t repeat that exact date query after the update.

What I can establish is what happened during my testing.

Google repeatedly failed to answer questions about a specific meeting.

Echo successfully retrieved the meeting when given its date.

Google’s calendar settings presented a control that I couldn’t activate using VoiceOver’s standard double-tap gesture.

And after the settings update, Google successfully read the Operations meeting during a January calendar listing, while continuing to fail when asked to find the meeting by name.

Those are observations, not guesses about Google’s internal systems.

Why This Matters for Accessibility

Voice assistants can be valuable tools for people with disabilities.

They allow users to retrieve information, manage appointments, operate devices, and complete tasks without navigating complicated visual interfaces.

But that usefulness depends on reliability.

If an assistant can retrieve a calendar event only when the user already knows approximately when it occurs, that limits its usefulness.

After all, the reason someone asks when an appointment is scheduled is often that they don’t know the date.

There’s also the matter of meaningful error messages.

"Sorry, I didn’t understand" doesn’t tell the user whether the assistant misunderstood the meeting name, couldn’t access the calendar, or failed to perform the search.

And an assistant that acknowledges a request but provides no spoken answer leaves the user with even less information.

These aren’t merely technical inconveniences. They can become accessibility barriers when people depend on voice interaction to obtain information.

The VoiceOver issue adds another dimension.

Even when the user decides to troubleshoot the assistant manually, the settings interface needs to remain accessible.

An inaccessible control shouldn’t become another obstacle between the user and the information they’re trying to retrieve.

The Irony of the Entire Evening

Here’s what makes this story particularly amusing.

Earlier that day, I had successfully tested a feature on my own website that automatically changes an English and Spanish meeting notice after a committee meeting.

The website knew when to stop advertising the meeting.

My calendar knew when the next meeting was scheduled.

Amazon Echo eventually found the meeting.

Preston found the meeting.

And Google Assistant, despite being able to read the appointment during a monthly calendar listing, couldn’t answer the question I had been asking all evening.

I wasn’t looking for anything complicated.

I wanted to update my webpage and prepare for the next meeting.

Instead, I spent part of the evening testing two voice assistants, investigating calendar settings, and discovering a potential screen-reader accessibility issue.

All because I asked:

"When is my next Operations meeting?"

By the time this article was prepared for publication, I had updated the Operations webpage and made additional site-wide changes to the templates responsible for displaying meeting notices when meetings are inactive.

Other meeting-related information was updated as well, but the details aren’t important to this story.

The important point is that I needed accurate meeting dates to complete that work. That’s why I asked the assistants in the first place.

The website updates are finished. The calendar information was available all along. Getting Google to find the meeting was apparently the difficult part.

Final Thoughts

I’m not suggesting that Google Assistant is incapable of doing useful things.

It plays SiriusXM quite well, for example.

And I know it can retrieve calendar information because I demonstrated that it could.

But there’s something fundamentally frustrating about an assistant that can read an appointment from a list while failing to locate that same appointment when asked directly.

Technology should make ordinary tasks easier, not turn them into troubleshooting exercises.

After decades of working with accessibility, I’ve learned that sometimes the simplest requests reveal the most interesting problems.

This was certainly one of those occasions.

And yes, I eventually got the meeting date.

But I didn’t get it the way I should have been able to.

Google, you can read my calendar. So why the hell can’t you find my meeting?


Discover more from Jared's Technology podcast network

Subscribe to get the latest posts sent to your email.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.