Each article can be filtered by role (content creator or developer), or by a range of topics (links, headings, navigation, etc.). You can also adjust how many items are shown per page, and navigate by the pager.
Definition of roles
Website editor, instructor working in canvas
Web admin or developer, mainly working on web themes or complex applications
Note about roles
Roles are determined by the person most likely responsible for an area of web design and development. Guidelines can overlap, and depending on a project or site, the responsibilities may fluctuate.
The title element is necessary for users to understand what the page is about, what site they are on, and if the page changed. Meaningful titles can also help with search engine optimization and make content more discoverable.
Headers tell users which cells in a table categorize certain data, rather than being part of the data. This makes it easier to understand a table semantically, especially if using assistive technology to navigate a table.
Labels tell the user what to put into a text input, a checkbox/radio button, or what will happen if a button is pressed. Labels also provide a benefit of putting the user in the field if they click on an actual label for a text input.
Landmarks are helpful for understanding a broad sense of the page layout, and can help assistive technology users easily navigate to different areas of a webpage. Landmarks include a header, main content, footer, and navigation, among others.
Content that flashes repeatedly can be harmful to people with photo-sensitivity or seizure disorders like epilepsy. Flashing content can lead to reactions like vomiting and nausea, and trigger seizures if the flashes are severe enough.
Perceivable: users must be able to detect the content using a variety of senses.
Operable: users must be able to navigate and use all functionality in web content.
Understandable: users need web content that is readable and predictable.
Robust: users can still access content, even if technologies update or change.
As of today, Western's official resolution states we must adhere to WCAG 2.0 as a bare minimum. However, we recommend meeting WCAG 2.1, as 2.1 is backward compatible and satisfies 2.0 criteria, in addition to new criteria added in 2018.