At Mozilla, we want the web running well for everyone, not just in one or two browsers. This means cross-browser, user-agent independent, and cross-device.

Web Compatibility, the ability for all Web content to run in all browsers, is important. There are multiple web content engines running on multiple devices, and sometimes with a little testing and some small tweaks to their site, developers can ensure that more users can have the full experience that is desired.

For more background and data on Web Compatibility, read the recent blog post on Mozilla Hacks.

Activity Format

While this activity can be run solo, we encourage you to run an event in your community to get together people who care about the Web. The goal is to test sites, diagnose problems, and discuss how to evangelise locally to developers about a Web that works for everyone.

Read the event guide on how to set up an event page and how to organize an event.

For duration, we recommend a half-day (or full evening) event with a minimum of 10-15 attendees.

Event Flow

  • Set yourself up with Firefox. Any or all of the following versions:
  • Install the Webcompat.com Reporter add-on
    • Firefox for Android Nightly and Aurora already have a “Report Site Issue” option in the main menu; no add-on needed.
    • No add-ons support for iOS, but people can report bugs manually at webcompat.com
  • Choose the sites you want to test
    • We recommend the top sites in your country, as measured by a reputable local source or using the Alexa Top Sites by Country reference
    • Also sites that you need or use frequently in your communities!
  • Test and Report!
    • If you encounter a site that does not work in Firefox, but works in another browser, then click the add-on button and follow the steps to report
    • Pay special attention to what we are looking for in reported issues
    • If you want to become an expert in web compatibility, go here

Directly at the end of the activity

Immediately after the event don’t forget to share the link to the impact form with your attendees:

Remember this is how you’ll know who attended your event, and if you successfully inspired them to action! We recommend adding it to your final slide AND emailing it out after the event.

Output

In addition to the recommended event flow here are some things we’d like you, the event organizer, to do.

  • Fill out the post-event metrics on the event page you setup on the Reps portal
  • Optionally, tell us about your event. This can be before or after. We love to hear about upcoming plans, and of course love to hear about what was achieved at the event with a picture or two!
  • Encourage attendees who want to continue to work on Web Compat to sign up to the mailing list

Extra

While the focus of this activity should be on testing sprints, there are other ways to stay more involved with the community after.

  • Bug diagnosis: This is about trying to understand the underlying issues behind bug reports, and where possible, providing suggested fixes for site owners. More information
  • Site outreach: This is about trying to get in contact with websites that have issues and (politely!) providing ways that they can improve compatibility or fix their bugs. More information

Webcompat’s contributors page has more basic information on how to get started and join the community.