Typing Speed Arcade

Type fast. Level up. Share.

Contact

How to reach us and what to include for the fastest help.

How to Reach Us

For support, feature requests, and general questions, email us at everydayroyalties@gmail.com. We usually reply within 2–3 business days (Mon–Fri, Central Time).

Tip: Include screenshots of any issues and your browser version for the fastest resolution.

Support Scope

Bug reports (visual glitches, scoring anomalies, broken links)
Feature ideas (new drills, passage types, leaderboard options)
Accessibility feedback (screen readers, contrast, keyboard-only navigation)
Policy questions (privacy, terms, content guidelines)

What to Include in a Bug Report

Steps to reproduce (what you clicked/typed)
What you expected to happen
What actually happened (error messages, odd behavior)
Your browser & version (e.g., Chrome 129), device/OS
Any installed extensions that might affect typing or scripts

DMCA & Content Requests

If you believe content on the site infringes your rights, contact everydayroyalties@gmail.com with the URLs involved, a description of your claim, and your contact details. We will review and respond.

Outages & Status

Typing Speed Arcade is a static site with no login or server-side leaderboards. If the site doesn’t load, try refreshing, disabling heavy extensions, or checking from a different browser. Report persistent issues to everydayroyalties@gmail.com.

Contact & Support

Email us with feedback, bug reports, or suggestions. We typically reply within 2–3 business days.

Support scope

Report bugs or visual issues
Suggest passages or features
Share accuracy or speed questions

Hours

Monday–Friday, 9am–5pm (Central Time)

We don’t offer personal training services; our content is educational.

Quick help & next steps

Get started

Take a baseline test
Pick 1 drill for 10 min
Log WPM & errors/100w

Need help?

See FAQ or Contact

Updated 2025-10-05

Get a Fast Reply

Subject: “Bug: [page] — [feature]” or “Help: [topic]”.
Include URL + steps to reproduce; attach a screenshot or short screen recording.
Tell us your browser/OS so we can reproduce quickly.

What We Help With

Account or progress issues (if accounts are enabled)
Content corrections or requests
Accessibility feedback and keyboard layout questions

Updated 2025-10-05

What to Include in a Support Message

The more detail you share, the quicker we can understand and reproduce any issue you’re seeing. When you reach out, it helps to include:

The browser and device you’re using (for example: Chrome on Windows, Safari on iPhone).
Whether the issue happens every time or only sometimes.
A short description of what you expected to happen vs. what actually happened.
Any error messages or screenshots of the page.
Whether you tried refreshing the page or clearing saved scores.

We don’t track account history, so details in your message are how we understand what you’re running into.

What We Can and Can’t Do

We’re happy to improve the tool and fix bugs. There are also limits to what we’re able to offer.

We can review bug reports, clarify how results are calculated, and consider feature ideas.
We can explain how to use the practice guides and suggest ways to interpret your numbers.
We cannot provide medical, legal, or occupational health advice.
We cannot guarantee specific WPM results or speed targets by a certain date.

Our goal is to keep the experience reliable, transparent, and respectful of your time and privacy.

Examples of Helpful Messages

Here are sample ways to phrase common questions or reports so we can quickly understand what you need.

Bug example: “On Chrome 129 on Windows, the timer froze at 0:15 when I pressed backspace repeatedly.”
Feature idea: “It would help me to have a mode with only numbers, because I type a lot of spreadsheets.”
Clarification: “I'm not sure how accuracy is calculated when I correct mistakes—can you explain?”
Accessibility note: “The contrast on the timer text is hard to see in low light.”

You never have to use formal language—plain descriptions of what you see on the screen are perfect.

Respectful Communication Guidelines

Typing Speed Arcade is maintained with the intention of being helpful and welcoming. Messages that follow a few simple guidelines make collaboration easier.

Be specific, not harsh, when something doesn't work the way you expected.
Assume good intent—bugs are almost always oversights, not deliberate choices.
Mention what's working well in addition to what you would like to see improved.
Avoid sharing sensitive data in your message; describe issues in general terms instead.

Clear and respectful notes help keep the site evolving in a way that feels good for everyone.

When You Might Not Need to Reach Out

Sometimes questions resolve themselves once you try a couple of quick checks on your side.

Refresh the page if something looks stuck or partially loaded.
Try a different browser to see whether the behavior is the same.
Disable aggressive extensions that block scripts or modify pages.
Check your connection if timers or stats are behaving unpredictably.

If those steps don't help, that's a great time to send a quick, detailed message.

What Happens After You Send a Message

Understanding what happens behind the scenes can make it easier to reach out.

Your email is read by a human who cares about clarity, reliability, and respect.
Issues are grouped with similar reports so patterns are easier to spot.
Possible fixes are tested to avoid creating new bugs while solving the old one.
Ideas are filed for future updates, even if they can't be built immediately.

You might not see every change right away, but thoughtful messages do make a difference.

Examples of Messages We Cannot Act On

Some types of requests are outside the scope of this project.

Personal coaching for careers, medical questions, or detailed life decisions.
Guarantees about reaching specific test scores by a certain date.
Requests to share or sell data about other users.
Spam-style promotions unrelated to typing, learning, or wellbeing.

Clarifying these limits helps keep the inbox focused on improving the tool itself.

What Happens After You Reach Out

It can help to know what to expect when you send feedback or a question about the site.

Your message is reviewed alongside other reports and suggestions.
Similar themes are grouped so common issues can be prioritized.
Ideas that fit the vision for Typing Speed Arcade are added to a future roadmap.
Bug reports are especially valuable, because they help improve everyone's experience.

Thoughtful notes from players are one of the main ways arcade-style tools stay fun and functional.

Before You Send a Message, Check These Quick Steps

A few small checks can sometimes fix a problem immediately—or make your message much clearer.

Refresh the page and see if the issue still happens on a clean load.
Try a different browser or device if you have one available.
Note the exact time the problem happened and what you were doing.
Grab a screenshot if something looks strange on the screen.

If you still need help afterward, including these details will make it easier to understand what you're seeing.

Ideas for Future Modes and Features

If you like dreaming about what could come next, here are the kinds of suggestions that can shape future updates.

New practice themes like “code snippets,” “email replies,” or “essay intros.”
Accessibility options such as high-contrast modes or adjustable font sizes.
More detailed stats like graphs of accuracy and speed over time.
Community challenges built around shared goals instead of just top scores.

Specific, concrete ideas like these make it easier to understand what players would find genuinely useful.

How to Describe Accessibility Needs

If you have specific accessibility needs, clear descriptions make it easier to explore possible changes.

Mention visual preferences such as contrast, font size, or color sensitivities.
Describe input challenges like difficulty reaching certain keys or using both hands.
Share the devices you use most so suggestions can match your real setup.
Explain how long you can comfortably play before needing a break.

You never have to share more than you're comfortable with, but even a few details can help shape more inclusive ideas.

When It Makes Sense to Reach Out

You don't need permission to send a message, but some moments are especially good times to share feedback.

You've noticed a repeatable bug that happens under specific conditions.
You have a feature idea that would clearly help many different types of players.
You want to share appreciation for a mode, article, or small detail that helped you.
You're confused by something that you can't resolve with practice and the FAQ alone.

Thoughtful feedback at these moments can shape the future of tools like this one.

Examples of Constructive Feedback

Here are a few more examples of the kinds of messages that are especially helpful.

Mode clarity: “It would help if the instructions for this mode explained how scores are calculated.”
Difficulty balance: “This level feels much harder than the others—was that intentional?”
Positive highlight: “The way you show accuracy after each game makes it easy to see what changed.”
Edge case bug: “When I resize the window mid-game, the timer overlaps the text on my laptop.”

Specific, respectful notes like these make it easier to maintain and improve tools over time.