# About this course

This is a self-paced course on **document accessibility for City and County of San Francisco (CCSF) web editors**. 

The course covers what web editors on SF.gov and other CCSF websites need to do to make the documents they upload accessible, meeting WCAG 2.1 Level AA standards.

Accessibility is built into SF.gov. Many requirements to comply with WCAG 2.1 AA have already been met. 

However, document accessibility requirements must be met separately. 

**Editors must make sure documents are accessible before they upload them to SF.gov.**

{% hint style="info" %}
Read [Updates to Title II and DAIS](/digital-accessibility-for-sf.gov-editors/new-standards-for-digital-accessibility/updates-to-title-ii-and-dais.md) for more information.
{% endhint %}

### What to do

You will take the course by:

* **Reading** the pages

You will **verify you took the course** by filling out a short form at the end.

You can **keep using the course materials** for reference in the future.

### Anyone in the City and County of San Francisco (CCSF) can take this course

While this course is primarily written for SF.gov editors, **document accessibility requirements are the same** for all CCSF websites. CCSF employees who upload documents to SF.gov or non-SF.gov websites can use this course. 

### Further, optional learning

Some sections of this course contain **further learning** sections, marked as optional. You're not required to read the information here or watch the videos, but we encourage you to! You'll find accessibility best practices that will help all users access your services.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sfdigitalservices.gitbook.io/digital-accessibility-for-sf.gov-editors/document-accessibility-for-sf.gov-editors/about-this-course.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.