Contact Info
Adam Sapp
Web Manager
- asapp@georgiasouthern.edu
- 9124782437
-
Room 1013
Anderson Hall
Statesboro
Basics
- Web Colors & Fonts
- For consistency and accessibility standards, don’t use mixed font sizes, colors and/or faces.
- Web logos for download
- Lists & comma use – following Georgia Southern University standards – don’t use a comma to separate the last items of a list: e.g. cats, dogs and squirrels (not: cats, dogs, and squirrels)
- For help in content writing see the Web and Calendar Content Quick Style Guide.
Accessibility
Georgia Southern University strives to make our official websites accessible for all visitors including those with disabilities. Accessibility standards for the web are established by Section 508 and the Web Content Accessibility Guidelines (WCAG) 2.1 as well as the University System of Georgia (USG). The official University themes address many of these standards, but content editors need to be able to understand how to address problematic areas in their site’s content. Here are some basic guidelines:
- Text color – text must be in high contrast with the background (7:1 for normal text, 4.5:1 for headlines). The styles within the University themes are compliant with this standard, content editors should not alter the color of the text on their websites.
- Images – require a text alternative (a.k.a. “alt” text ) – WordPress will insert alt text for you when you use the “Add Media” tab in the page editor. If you insert your images manually, you’ll need to enter alt text as well. If an image is purely decorative, use alt=”” (null value) to indicate that assistive technology should ignore it.
- Links – use descriptive text to help users clearly identify the purpose of a link. For example, link the descriptive phrase “working with tables” instead of “more info” or “click here.” The same applies to PDFs or other documents which should include a note to indicate that the link opens a PDF: University’s Identity Standards (PDF).
- Structure – content should be structured in a way that guides visitors using assistive technology logically through the page. This can be done by using meaningful markup such as headings, paragraphs, <strong> or <em> for emphasis, and by avoiding markup that is purely presentational e.g. “align”, “bgcolor”, <b>, <i>. Headings should be used in order (h2 followed by h3, h4, h5) when possible. Using tables to create layouts should also be avoided – the table html tag indicates tabular data, so search engines and assistive technologies alike may misinterpret your content if misused.
Web Accessibility Standards
Summaries of the web accessibility standards established by Section 508 and the Web Content Accessibility Guidelines (WCAG) 2.1 are provided below. Click the link in the WCAG outline to view detailed information about each standard.
WCAG 2.1 Guidelines
View WCAG 2.1 guidelines in full
- Perceivable
- Provide text alternatives for any non-text content so that it can be changed into other forms people need, such as large print, braille, speech, symbols or simpler language.
- Provide alternatives for time-based media.
- Create content that can be presented in different ways (for example simpler layout) without losing information or structure.
- Make it easier for users to see and hear content including separating foreground from background.
- Operable
- Make all functionality available from a keyboard.
- Provide users enough time to read and use content.
- Do not design content in a way that is known to cause seizures.
- Provide ways to help users navigate, find content, and determine where they are.
- Make it easier for users to operate functionality through various inputs beyond keyboard.
- Understandable
- Robust
Section 508 Standards
View section 508 standards in full
1194.22 Web-based intranet and internet information and applications.
- A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content).
- Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
- Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
- Documents shall be organized so they are readable without requiring an associated style sheet.
- Redundant text links shall be provided for each active region of a server-side image map.
- Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
- Row and column headers shall be identified for data tables.
- Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.
- Frames shall be titled with text that facilitates frame identification and navigation.
- Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.
- A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
- When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
- When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
- When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
- A method shall be provided that permits users to skip repetitive navigation links.
- When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
Content
- News – read our recommendations for using categories and tags to help visitors find related content.
- Read Web Content 101 – our quick, one-page guide to web writing – and SEO 101 for search engine optimization basics.
- Home page titles – use a descriptive title when possible – e.g. “Advanced Teacher Preparation” or “Ed.D. in Curriculum Studies” instead of “Welcome” or “Overview.”
- Visibility – all pages marked “Published” are indexed by search engines and are visible to the public whether there is a link to that page on your site or not. Any pages that are not ready for public viewing must be set to “Draft” status until they are ready for publication. The same applies to News and Content Blocks.
- By convention, underlined text on the web is “clickable” – to avoid confusing your visitors, don’t underline text that is not linked.
- Links:
- As a rule all links should open in the same window or tab. Opening a link in new window disorients users and disables the use of the back button, a crucial navigation tool on mobile devices.
- Links to PDFs and other docs – let your visitors know when a link will open a PDF or other document type by a adding parenthetical note – e.g. (PDF) or (Word doc) – or include a graphic icon beside the link.
- During migration, correct all links within your content that point to your old site. The web team will set up redirects for top-level pages, but it is your responsibility to ensure links within your content work after launch.
- Links to restricted-access sites – include a note when a link will require visitors to enter login credentials (e.g. add a note stating “MyGS login required” when linking to a SharePoint site that requires users to login).
- Review your site regularly to ensure your content is up-to-date and accurate. You’ll also receive reports from our web governance tool, SiteImprove, to help you find and fix broken links and misspellings on your site.
Organizing Your Site
- Consolidate related content when possible – if you only have a few sentences or paragraphs for each section of a site, include the content on a single page and use headings to break it up, rather than creating separate pages for small amounts of text.
- When you have substantial amounts of inter-related content, create “sections” within your site with Parent pages (use the Page Attributes box to assign parent pages).
- Parent pages also establish your site’s URLs (e.g., WingSPAN is given the parent page “Programs” to create this url: http://admissions.georgiasouthern.edu/programs/wingspan/)
- Breadcrumbs are provided on all our sites to help users navigate between pages easily – creating a logical organization with parent and child pages establishes breadcrumbs and makes them useful. Here’s an example of breadcrumbs for the “Working with Tables” page under the parent page “Learn WordPress”.
- Parent pages should not be blank – they should include content and links to their “child” pages.
- Colleges will be expected to retain their current url structure in WordPress.
- Navigation Menus:
- Drop downs should not be placed under the “Home” tab – by convention the “Home” button takes visitors back to the home page in a single click.
- Links to documents in a navigation menu should include a parenthetical note – (PDF) or (Word Doc) for instance – so visitors understand that they will be downloading a document when they click the link. It’s better, however, to send visitors to a page on your site that contains the link to the document, rather than linking directly to documents in a navigation menu.
- Don’t link to “coming soon” or “draft” pages – wait until the content is published.
Images & Media
Image Sizing
(Block type codes for use in filenames are listed in parentheses).
- Hero Images (hero)
- 1600×900 (72 or 150 ppi)
- Images focus should be shifted to the right side of the frame to ensure the page title does not interfere with the purpose of the image.
- CTA (cta)
- 1000×667 (72 or 150 ppi)
- Feature Panels (fp)
- 900×675 (72 or 150 ppi)
- Visual Router Grid (vr)
- 900×675 (72 or 150 ppi)
- Headshots (headshot)
- 400×600 (72 or 150 ppi)
Image Naming Conventions
When saving and uploading images, rename the file to clearly describe its content and include relevant keywords. For example:
- Good: hero-georgia-southern-campus-aerial-view.jpg
- Poor: IMG_12345.jpg
All image filenames must include the following in the exact order:
- Type of block the image is going into (ex: hero)
- Followed by Georgia Southern (ex: hero-georgia-southern)
- College/Department (ex: hero-georgia-southern-cri)
- Descriptive and Include Relevant Keyword (ex: hero-georgia-southern-cri-arc-fitness)
Not only will this allow us to easily search our vast image library, but it also improves SEO by helping search engines understand the image and increases visibility in Google Image Search, supporting accessibility.
Compression & Uploading
Before uploading images, ensure they are optimized for fast loading without sacrificing quality. Use an image compression tool (such as Optimizilla, Squoosh or Photoshop’s “Save for Web” feature) to reduce file size while maintaining clarity. Smaller, optimized images improve page speed—an important factor for both user experience and SEO. When uploading, always include optimized alt text:
- Write clear, concise descriptions that accurately reflect the image’s content and purpose.
- Naturally incorporate relevant keywords that align with the page’s topic.
- Ensure alt text provides meaningful context for users relying on screen readers and for search engines indexing the image.
Examples:
- Good Alt Text: Georgia Southern University’s Armstrong Campus quad with students walking between palm trees
- Poor Alt Text: Campus or Image123
Optimizing both file size and alt text ensures images load quickly, are accessible to all users and are discoverable in search results, helping each page perform better in search rankings.
Photography for Use on Your Site
Photos of campus events, buildings, etc. can be found on the sites below. Do not use images downloaded from Google or other places that you have not paid for or gotten permission to use.
Marketing Your Website
SEO – your departmental WordPress website is optimized for search engines out of the box – when you publish new content, your sitemap is automatically updated and a notification is sent to major search engines.
Restricted Block Usage
Failure to adhear to UCM’s restricted block policy will result in the responsible user’s access to the website being revoked for up to 90 days and the user must attend a revoked access meeting with Adam Sapp and Amy Huggins before their access will be restored.
Policy Reminder: Do NOT Use or Edit Custom HTML Blocks in WordPress
To ensure consistency, accessibility, and security across all pages on the Georgia Southern website, web contributors and web editors are strictly prohibited from using the Custom HTML block in WordPress.
What You Must Do
- Use only approved WordPress blocks (Paragraph, Heading, Image, Button, Columns, etc.).
- If you need a layout or function that you believe requires custom HTML, submit a request to the University Communications and Marketing (UCM) Web Team for review and implementation.
- Never paste or modify HTML, inline styles, or scripts within the editor.
Monitoring & Enforcement
- UCM actively monitors website activity and page revisions across all university sites. If unapproved HTML is found:
- The responsible user’s access to the website will be revoked for up to 90 days.
- The code will be removed immediately to maintain site security and compliance.
This policy applies to all sites and roles, including Web Contributors, Authors, and Editors.
Questions or Requests
If you need assistance achieving a specific layout or functionality, contact the UCM Web Team via ClickUp. We’re happy to help ensure your content stays compliant, accessible, and on brand.