Groups are subsets of participants for a given worksite in UVaCollab. Groups can be created on an ad hoc basis by instructors in course sites or by owners or administrators in collaboration sites. Groups are useful to organize study groups, project teams, and other non-official subsets of worksite participants. In course sites, each course roster section behaves like a group. i.e., group-aware tools recognize the section as a group.

You can use groups to make site content available to specific site participants.  For example, a private announcement can be made available to a group and email notification can be sent to members of that group.  You can also use groups to create group assignments, or limit access to a test or quiz with settings for specific groups.

For information on creating and editing groups, see How do I create groups?

WARNING: If an assignment or assessment has been released to groups, changing which groups have access to the assignment, or modifying or deleting a group after students have begun work on the assignment or assessment can result in the loss of submissions!

UVaCollab uses a single consistent Rich-Text Editor across all areas where text can be added that is more than a few lines. This editor is based on the most recent stable version of the CKEditor.

When creating content using the Rich-Text Editor, it is important that the author follow the simple guidelines below to ensure that the content can be read and understood by all. Creating well-structured and accessible content is a best practice which ensures that content is compatible with assistive devices, such as screen readers, and robust enough to be copied and pasted to other contexts or presented in unanticipated contexts.  Making content accessible is also a legal requirement.

The Rich-Text Editor's Accessibility Checker feature can help you check your content for accessibility issues and edit it to fix them.

The technical measure of accessibility for a web-based resource is the WCAG 2.0 standard from the W3C. The requirements of the WCAG 2.0 are summarized in the four-letter acronym POUR:

• Perceivable - Information must be presentable to users in ways they can perceive.
• Operable - User interface components, navigation and structure must be operable.
• Understandable - Information and the operation of user interface must be understandable, and structural elements should be used in a meaningful way.
• Robust - Content must be robust enough so that it can be interpreted reliably by a wide variety of technologies, including assistive technologies.

These relatively simple considerations make a big difference if applied when content is created. The W3C provides more information in their Introduction to Understanding WCAG 2.0.