Web Site Design Suggestions for
Nonprofits, NGOs, Small Government Agencies &
other mission-based / cause-based initiatives

That said, I do have some very strong feelings about web design, and you should too, even if you are not a web designer yourself. You need to understand some standards of good design and be ready to demand them of whomever is going to design your web site, be it an in-house employee, a consultant or a volunteer.

Some fundamentals regarding web site design, and content that affects design, for nonprofits, NGOs, civil society organizations, government agencies, schools and other mission-based organizations:

• The reaction from a first-time visitor shouldn't be "Wow, look at the design!" but rather, "Wow, I immediately found exactly the information I was looking for!" or "Wow, this organization does great work!" Don't bury web page content under oh-so-many graphics and animated features and a video that starts playing as soon as I go to your page. The most important thing to remember when designing your Web site is what your audiences want out of the site. If a Web site wins design awards, but your customers don't use it, it's "virtually" worthless to users. Most users will visit your Web site to find information, not graphics; information should drive the design of your Web site.
• The answers to your organization's FAQs should be immediately, obviously easy to find. 

• Make sure it's obvious WHERE your organization is, geographically-speaking. There are organizations with your same name - a visitor needs to know which one you are, the one across town or the one across the country?
  

• Make sure the name of your organization appears in the TEXT of your web site, not just within a graphics file - and on many pages, not just the "about us" page. This greatly increases the possibility of your site being found when someone types your organization's name into a search engine - also known as Search Engine Optimization (SEO).

• Some people will do a search for a particular topic on a search engine and come directly to a page within your web site, bypassing your homepage. Therefore, it is important that each page has the name of your organization on it, somewhere (many organizations have a footer on every page with the full name of the organization), so a visitor knows who is publishing the info. This is also helpful if someone prints out one of your web pages - so that the name of your organization is there, just it would be on a printed page.
  

• Make sure the keywords and phrases you want people to use to find your web site via a search engine appear in the TEXT of your web site, not just within a logo. That includes the full name of your organization. That helps people searching within your website, helps improve SEO, and helps a sight-impaired user navigating the page.
  

• If your organization is focused on helping the homeless in a certain town and state, the word homeless and homelessness, as well as the name of that town and state, need to be in the text of your key web site pages, including the home page. The word volunteer needs to be on your web site as well, on a page that says these aforementioned keywords. Again, this greatly increases the possibility of your site being found when someone types certain keywords into a search engine and helps someone who might come to your page directly, bypassing your home page.
  

• Each web site page you want to show up in search engine results should contain the primary keyword someone might search for in that title's page title. If you have a page of tips on kitchen composting for apartment dwellers, that is exactly what your title on the page should say, not: "Tips on ways to be greener." Your "Tips" phrase can appear on the page, of course. This not only helps with SEO but also helps users with sight impairments.
  

• Each page should also include a single and relevant H1 Title that includes the primary key word you would want someone to use to find that resource via a search online. That primary keyword should also feature in the first paragraph of your content underneath the H1 title. This helps greatly with SEO.
  

• I've read that 2% of a web site's content should contain the organization's primary and secondary keyword - homelessness, youth, arts, domestic violence, etc., for the site to rank highly in web searches. My advice: think of your home page and each page your home page links to as primary web site landing pages, pages that should stand-alone: someone could see JUST that page and know who your organization is and its primary focus, without having to look at any other page. Using synonyms of your desired keyword within your content as well also increases SEO.
  

• The World Wide Web shouldn't be the World Wide Wait. Your web pages should load quickly for everyone, not just those with lightening-fast broadband. The more large graphics you have on a page, the more slowly it loads.
  

• A professional designer may develop your site, but someone in-house or a volunteer should be able to make regular changes to the site without needing assistance of the designer. The designer should create pages that allow these changes to happen easily.

• Learning what makes a good web site often involves learning what makes a rotten web site. See websitesthatsuck.com to learn more.

• Design your site with a variety of people in mind: people using a beautiful, new Macintosh and people using old IBM clones running an outdated web browser. People with lightening-fast Internet access and people with something that is as slow as a dial up. People using an iPhone and people using an Android. All of those people should be able to read your website. That means embracing universal design for every or most pages and either making every page mobile-ready or creating a duplicate mobile-ready site. That means making your web site accessible for people with disabilities, including people using assistive technologies. It means I don't have to have two hands to make a choice on a menu. It means if I'm blind user and my technology is reading your website to me, it makes sense (which also means, if I'm a sighted user and driving in my car and asking my in-the-car virtual assistant to find something on your website, I can). These recommendations from the State of Illinois can help.
  

• Break up text into small paragraphs whenever possible, and break up massive amounts of information into separate pages, as appropriate; for instance, break up your newsletter into one web page per story, rather than putting them all into one big file. But don't make all information a slide show: I don't want to have to click through pages, and wait for new graphics to download, just to finish reading something on your web site of a few paragraphs. You absolutely can have detailed, long-reads on your web site, but they shouldn't be primary landing pages of your web site. Note: a study from Backlinko.com showed that longer form content ranked stronger in SEO than short content!

• Surprise: most people do not want to read your newsletter in PDF unless it is super short - one, maybe two pages. Any content in a PDF should also be on separate HTML pages so that they are easier to read, searchable and findable. Yes, there are ways to make PDFs accessible for people with disabilities, but it's labor intensive and beyond the expertise of most folks.
  

• Avoid using large or gratuitous graphics that don't add to the content of the page, or take a long time to download for someone with slow Internet access. Graphics should enhance the information on the site - there should be a reason for every graphic, every photo, every video.

• Images should include Alt text in the markup/code; complex images should have more extensive descriptions near the image (a caption or descriptive summaries). Otherwise, you deny information to a visitor using a screen reader. But Alt text needs to actually describe the photo: woman smiling at camera, group of people jumping all at once, man sitting at a computer, etc., not just the name of the person in the photo. There are many more accessibility tips here. 

• Do not rely on color as a navigational tool or as the sole way to differentiate items. This makes choices inaccessible for someone who has sight impairments regarding color (color blindness). Also, be conscious of color-contrast - I am not considered a person with a disability, but I can't easily read dark gray text on a light gray background. 
  

• Users not using a mouse - who are using keyboards - should be able to navigate your web site. Users should be able to navigate the site just tabbing through and hitting "return." Pages should be tagged in the background coding to worked with voice-control systems as well. All of this functionality is easy to design for if you do it from the get-go - it's VERY hard to do AFTER you have already designed a website. Insist on this being done by whomever is designing your website and remember that you can recruit volunteers with this skill, or willing to acquire this skill. There are many more accessibility tips here. 
  

• Provide transcripts for podcasts and videos. Volunteers can help you do this. YouTube automatically transcribes your videos - you just need to go in and fix what their system thinks you've said. I taught myself to do this in about 30 minutes. I've also uploaded podcasts to YouTube, made the viewing private, let YouTube transcribe it, then I've edited that automatically-generated script while listening to the audio - ta da, transcript of my podcast. 
  

• If you have a video on your site, you should provide closed captioning. YouTube automatically does this for your videos - you just need to go in and fix what their system thinks you've said. I taught myself to do this in about 30 minutes.