Accessibility Guide
Search the Guide
How to use
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
Content creator: Website editor, instructor working in canvas
Developer: 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.
Search results
56 results
Headings describe the content beneath it in a concise way. They act as a table of contents for your page and outline the major sections, sub-sections, and so on. Headings are helpful for everyone to understand how content is divided and relates to each other, but is especially helpful for users of assistive technology who use headings to navigate a page.
Applicable Roles
Content Creator DeveloperMaking content as simple as possible helps all users understand your content, and complete tasks like registering for an event successfully. Simple, clear structure can also help users with reading or cognitive disabilities, where it is more difficult to read complex content.
Applicable Roles
Content CreatorDigital content can be presented to users on a variety of devices; users might also have additional display preferences for those devices like larger font or more spacing. The content should adapt to those preferences without overflowing, getting cut off, or not adjusting its font size.
Applicable Roles
DeveloperHTML is good at providing semantics, and CSS for providing styles to web pages. Making sure styling is maintained in CSS and not HTML is important for assistive tech to parse content correctly, and to not announce content that is really just a stylistic placeholder.
On the opposite side, meaningful content like images conveyed through CSS need a way to be interpreted correctly so users know the content exists.
Applicable Roles
DeveloperValid markup helps assistive technologies interpret your site correctly and predictably. Users might also have different versions of certain assistive technology, or choose different operating systems or browsers. Whatever tools they use, web content needs to be written validly so a variety of people can use your site.
Applicable Roles
DeveloperWCAG 2.1 and WCAG 2.2
Web Content Accessibility Guidelines (WCAG) 2.2 is the most recent baseline W3C Recommendation for developing accessible web content. WCAG is based on four principles:
- 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, Washington state policy requires WCAG 2.1 as the accessibility standard. However, we recommend meeting WCAG 2.2, as 2.2 is backward compatible and satisfies 2.1 criteria, in addition to new criteria added in 2023.
ARIA 1.2
Accessible Rich Internet Applications (ARIA) provides a range of information to users about complex widgets and states of other interfaces.
Note: semantic HTML should be used instead of ARIA whenever possible.
There are resources for learning more about using ARIA when needed: