Skip to main content
Web Design
November 2, 2026Terri Eades

Before Giving Tuesday, Try to Give $5 with Only Your Keyboard

Before Giving Tuesday, Try to Give $5 with Only Your Keyboard

A grandmother sits down at her kitchen table to give $5 to her grandson's school. A mouse is hard on her hands these days, so she uses the Tab key to move around the page, one box at a time. She picks an amount, presses Tab a few more times, and then she can't tell where she is. Nothing on the screen shows which box or button she's on. She tries a little longer, then closes the laptop and tells herself she'll ask someone to help later.

Nobody did anything wrong here. The page just never got tried this way. The good news is that you can try it yourself in about five minutes.

Quick answer

Put your mouse away and try to give $5 on your own donate page using only the keyboard, then try again on a phone. If you get stuck, lose track of where you are, or see an error you can't understand, fix it by mid-November so the page is ready for GivingTuesday on December 1 and Colorado Gives Day on December 8, 2026.

Why the keyboard test matters

The W3C's accessibility guidelines (WCAG 2.1) put it simply: "Everything can be done with a keyboard except freehand movements." The W3C also notes that many people rely on the keyboard, "including blind and some mobility impaired people." The formal rule, Success Criterion 2.1.1, says: "All functionality of the content is operable through a keyboard interface…"

Seeing where you are matters just as much. Success Criterion 2.4.7 asks that keyboard-operable pages have "a mode of operation where the keyboard focus indicator is visible." In the W3C's words, without one, "sighted keyboard users cannot operate the page." That's exactly where our grandmother got stuck.

The five-minute donate-page test

Use a laptop or desktop first. Open your school's or foundation's donate page in a normal browser window.

  1. Put the mouse away. Tab moves forward, Shift+Tab goes back, and Enter or Space selects a button or choice. Start at the top of the page and press Tab.
  2. Watch for the outline. As you press Tab, look for a visible outline or highlight on each link, box, and button.
  3. Pick an amount and fill in the form. Choose a preset amount, then try "Other" and type $5. Fill in your name, email, and any other fields.
  4. Stop before paying, or actually give $5. Either works. Giving $5 to your own school is a nice way to see the thank-you page and receipt email too.
  5. Do it again on a phone. Open the same page on your phone.

Write down anything that went wrong, with the step number and a short note like "lost the outline after the amount buttons." That list is what you or your web person will fix.

Errors in plain words

Now run one more quick check. Go back through the form and leave one required field blank on purpose, such as ZIP code, then try to continue.

WCAG Success Criterion 3.3.1 says that when an input error is detected automatically, "the item that is in error is identified and the error is described to the user in text." In everyday terms, look for three things:

  • It names the field and says what to do. "Please enter your ZIP code" is clear. "Invalid input" is not.
  • It sits next to the field. A message only at the top of the page is easy to miss, especially on a phone.
  • It's in words, not only in color. A red outline alone doesn't help someone who can't see red well.

Done when: a first-time visitor could read the message and fix the field without guessing.

Where does your donate form actually live?

Many schools and foundations don't build their own donation form. They embed one from a donation platform inside a page on their website. That's normal, and it matters for who fixes what.

  • If the embedded form fails the test, write down what happened, step by step, and send it to the platform's support team. That's their form to fix, and it's a fair request from a customer.
  • If the page around the form is the problem, such as a menu you can't Tab through, no visible outline before you reach the form, or text too small on a phone, that's a website fix on your side.

One note: an accessibility overlay or widget isn't the answer here. Real fixes happen on the page itself or in the platform's form.

If your foundation uses Google Ad Grants

This section is only for eligible 501(c)(3) organizations, such as an education foundation or literacy nonprofit, that run Google Ad Grants. Schools themselves usually can't hold the grant, but a school's foundation may.

Before giving season, check your ads against Google's Ad Grants website policy:

  • "Your nonprofit must own the domain(s) your ads point to."
  • That domain "cannot automatically redirect visitors to a different web address, a third-party platform (like a donation portal), or a social media page."
  • "Your entire website must be served over HTTPS."
  • "Donation links must work and go to a secure page dedicated to donations."

In practice: click your own ad's destination and make sure it opens your foundation's secure site, not a redirect. Then click the Give button and confirm it opens a working, secure donation page. Then run the keyboard test on that page too.

A simple timeline

  • This week: run the keyboard, phone, and error tests. Write down what you find.
  • By mid-November: fix what's on your website and send platform issues to the platform.
  • Before December 1: retest everything for GivingTuesday.
  • Before December 8: retest once more for Colorado Gives Day. ColoradoGives.org says "Early giving is open," and online donations made "now through Colorado Gives Day on December 8" will be boosted by its $1 million+ Incentive Fund, so Colorado families may be giving well before the day itself.

A note from the school side

From my years on the school side, the donate form is often the one step nobody tests before a giving day. We check the emails, the social graphics, and the thank-you letters, but the form gets assumed. Five minutes with the Tab key is a kind thing to do for every family who wants to give.

What this is not

  • Not legal advice. This is a practical check, not a compliance opinion.
  • Not an overlay or widget fix. Add-on accessibility toolbars don't replace fixing the page or the form.
  • Not a full WCAG audit. This test covers one important path on your site. A full audit looks at much more.


Ready to grow your business?

Get a free AI audit and discover how we can help.

Common Questions

Want one practical tip per week?

Morning Announcements is a free weekly newsletter for Colorado schools and nonprofits. Subscribe and get the Colorado Digital Front Door Audit free.