"Fast Five" Essentials to Preparing Materials: Difference between revisions
m Move page script moved page ALLY:"Fast Five" Essentials to Preparing Materials to "Fast Five" Essentials to Preparing Materials without leaving a redirect |
No edit summary |
||
| Line 5: | Line 5: | ||
''Select the link to be taken directly to that section of the article.'' | ''Select the link to be taken directly to that section of the article.'' | ||
__TOC__ | __TOC__ | ||
== In-program Styles == | == In-program Styles == | ||
Using appropriate headings in the appropriate order in your current program is necessary. | Using appropriate headings in the appropriate order in your current program is necessary. They add structure and create consistency in documents and allow screen readers to easily—audibly—scan the information. Additionally, authors can easily create such things as a [https://support.microsoft.com/en-us/office/insert-a-table-of-contents-882e8564-0edb-435e-84b5-1d8552ccf0c0 Table of Contents] or [https://support.microsoft.com/en-us/office/use-the-navigation-pane-in-word-394787be-bca7-459b-894e-3f8511515e55 view an Outline]. | ||
{{Warning | |||
|body = '''Title or Subtitle''' | |||
It is an '''''extremely''''' rare instance that you will use the style "Title" or "Subtitle" found in the Styles Gallery, Pane, or Pulldown. If you have questions, please reach out to [mailto:accessibility@swarthmore.edu accessibility@swarthmore.edu]. | |||
}} | |||
{{ExpandStart | {{ExpandStart | ||
|title = Use in-program styles to create structure | |title = Use in-program styles to create structure | ||
|page = [[Creating PDFs]] | |||
|page = [[ | |||
|addpanel = false | |addpanel = false | ||
}} | }} | ||
=== Apple === | === Apple === | ||
| Line 39: | Line 29: | ||
* [https://support.apple.com/guide/pages/intro-to-paragraph-styles-tanaa39b0aa3/mac Intro to paragraph styles in Pages | Mac help]. | * [https://support.apple.com/guide/pages/intro-to-paragraph-styles-tanaa39b0aa3/mac Intro to paragraph styles in Pages | Mac help]. | ||
=== Google === | === Google === | ||
* [https://support.google.com/docs/answer/116338?hl=en | * [https://support.google.com/docs/answer/116338?hl=en&ref_topic=1361461 Docs] | ||
** Our KB article: [[ALLY:Google_Docs_Changing_The_Look_of_Headings_and_Paragraphs|Google Docs: Changing The Look of Headings and Paragraphs]] | ** Our KB article: [[ALLY:Google_Docs_Changing_The_Look_of_Headings_and_Paragraphs|Google Docs: Changing The Look of Headings and Paragraphs]] | ||
** Google's Support page: [https://support.google.com/docs/answer/116338?hl=en&ref_topic=1361461 Add a title, heading, or table of contents to a document] | ** Google's Support page: [https://support.google.com/docs/answer/116338?hl=en&ref_topic=1361461 Add a title, heading, or table of contents to a document] | ||
* [https://support.google.com/docs/answer/46973?hl=en&ref_topic=1361470 Sheets] | * [https://support.google.com/docs/answer/46973?hl=en&ref_topic=1361470 Sheets] | ||
* [https://support.google.com/sites/answer/7529116?hl=en&ref_topic=7184581&sjid=13385373985229223832-NA Sites] | * [https://support.google.com/sites/answer/7529116?hl=en&ref_topic=7184581&sjid=13385373985229223832-NA Sites] | ||
* [https://support.google.com/docs/answer/1705254?hl=en&ref_topic=19434 Slides] | * [https://support.google.com/docs/answer/1705254?hl=en&ref_topic=19434 Slides] | ||
=== HTML === | === HTML === | ||
In '''HTML''', titles should exist within the <code> | In '''HTML''', titles should exist within the <code><title></code> tag. There should only be one, and it should also be somehow related—and maybe even exactly the same—as the <code><h1></h1></code>. Use headings to establish structure. | ||
=== LaTeX === | === LaTeX === | ||
| Line 69: | Line 49: | ||
Styles that are important to structure in a LaTeX file are: | Styles that are important to structure in a LaTeX file are: | ||
* Insert sections in document body:<code> \section{_}</code>, <code>\subsection{_}</code>, etc. | * Insert sections in document body: <code>\section{_}</code>, <code>\subsection{_}</code>, etc. | ||
* Numbered lists in use: <code>\enumerate | * Numbered lists in use: <code>\begin{enumerate} \item ... \end{enumerate}</code> | ||
* Bulleted list use:<code> \itemize | * Bulleted list use: <code>\begin{itemize} \item ... \end{itemize}</code> | ||
See also: | See also: | ||
* [https://blogs.ed.ac.uk/isintern/2023/08/15/lewis-forbes-latex-and-accessibility/ Lewis Forbes – LaTeX and Accessibility | University of Edinburgh student intern blog] | * [https://blogs.ed.ac.uk/isintern/2023/08/15/lewis-forbes-latex-and-accessibility/ Lewis Forbes – LaTeX and Accessibility | University of Edinburgh student intern blog] | ||
* [ | * [https://www.danwjoyce.com/data-blog/2018/2/20/latex-to-html-via-pandoc LaTeX to HTML via PANDOC | Dan W. Joyce] | ||
=== Markdown === | === Markdown === | ||
In '''Markdown''', your title exists after a singular hashtag, <code># Title</code>. Hashtags give markdown structure. The relationship between Markdown and HTML shows us that <code> | In '''Markdown''', your title exists after a singular hashtag, <code># Title</code>. Hashtags give markdown structure. The relationship between Markdown and HTML shows us that <code><h1></h1></code> and <code><title></code> are often similar or the same. | ||
* [https://www.smashingmagazine.com/2021/09/improving-accessibility-of-markdown/ Improving the accessibility of your markdown | Smashing Magazine] | * [https://www.smashingmagazine.com/2021/09/improving-accessibility-of-markdown/ Improving the accessibility of your markdown | Smashing Magazine] | ||
| Line 87: | Line 65: | ||
{{Note | {{Note | ||
|body = | |body = '''HTML, LaTeX, and Markdown to PDF''' | ||
It is not accessible to move .tex, .md, and .html files to PDF. If you give folks the source document, they can render or convert it to whatever preferred file extension they'd like to read from. | |||
'''HTML, LaTeX, and Markdown to PDF''' | |||
It is not accessible to move .tex, . | |||
}} | }} | ||
=== Microsoft === | === Microsoft === | ||
| Line 107: | Line 78: | ||
** Our KB article: [[ALLY:Using_Word's_Properties_to_flow_into_a_more_accessible_PDF|Using Word's Properties to flow into a more accessible PDF]]. | ** Our KB article: [[ALLY:Using_Word's_Properties_to_flow_into_a_more_accessible_PDF|Using Word's Properties to flow into a more accessible PDF]]. | ||
=== Moodle === | === Moodle === | ||
==== Atto Editor ==== | ==== Atto Editor ==== | ||
* Swarthmore ITS Blog post: [https://blogs.swarthmore.edu/its/2022/06/02/atto-text-editor-moodle-accessibility-part-2/ Reach all users with Atto text editor in Moodle]. | |||
* Swarthmore ITS Blog post | |||
* Moodle's [https://docs.moodle.org/402/en/Atto_editor Atto Editor documentation]. | * Moodle's [https://docs.moodle.org/402/en/Atto_editor Atto Editor documentation]. | ||
==== TinyMCE Editor ==== | |||
==== [https://docs.moodle.org/402/en/TinyMCE_editor TinyMCE Editor] | * [https://docs.moodle.org/402/en/TinyMCE_editor TinyMCE Editor Documentation] | ||
{{ExpandEnd}} | {{ExpandEnd}} | ||
< | {{Warning | ||
|body = '''Heading 1''' | |||
You will only ever use Heading 1 or <code><h1></h1></code> once in your materials. | |||
* In Microsoft Office, Heading 1 will usually coincide with "Title" in the document’s metadata. | |||
* In HTML, <code><h1></h1></code> and <code><title></code> often have some kind of relationship. | |||
If you have questions, please reach out to [mailto:accessibility@swarthmore.edu accessibility@swarthmore.edu]. | |||
}} | |||
[https://youtu.be/0xAv1l04aJI Screen Reader Demo With Headings [YouTube]] | |||
== Convey Meaning with Words == | == Convey Meaning with Words == | ||
{{ExpandStart | {{ExpandStart | ||
|title = How to use words to convey meaning... | |title = How to use words to convey meaning... | ||
}} | }} | ||
=== Links === | === Links === | ||
When providing a link somewhere within your text, be sure to provide context. Screen readers provide users the opportunity to scroll through links, so links such as | When providing a link somewhere within your text, be sure to provide context. Screen readers provide users the opportunity to scroll through links, so links such as "click here" and "more" do not make sense out of context. | ||
* Deque University | * Deque University: [https://dequeuniversity.com/tips/link-text Use link text that makes sense when read out of context] | ||
* WebAIM | * WebAIM: [https://webaim.org/techniques/hypertext/link_text Links and Hypertext: Link Text and Appearance] | ||
=== Color === | === Color === | ||
Color is not read aloud by screen readers, so consider calling attention to important text with words. | |||
* | * <span style="color:blue">'''Important:'''</span> Paper due on April 15th. All late papers will be deducted one grade per day late. | ||
* | * <span style="color:brown">'''Note:'''</span> All applicants must sign on line 11 and line 15 in order to have their pay direct deposited. | ||
* <span style="color: | * <span style="color:green">'''Urgent:'''</span> Pay attention to all directions before handing in this form. | ||
When using color, | When using color, ensure high contrast. Use [https://webaim.org/resources/contrastchecker/ WebAIM's Contrast Checker] or [https://www.siegemedia.com/contrast-ratio Lea Verou's Contrast Ratio Checker]. | ||
=== Alt-Text, Captions, Image Descriptions, etc. === | === Alt-Text, Captions, Image Descriptions, etc. === | ||
Providing descriptive text is necessary for all users to understand the meaning of an image. | |||
* [https://www.w3.org/WAI/tutorials/images/ W3C WAI Images Tutorial] | |||
* [https://webaim.org/techniques/images/ WebAIM: Accessible Images] | |||
* | * [https://alt-text-as-poetry.net/ Alt Text as Poetry] | ||
* [https://poet.diagramcenter.org/index.html Benetech's Poet Training Tool] | |||
{{ExpandEnd}} | {{ExpandEnd}} | ||
== In-program Accessibility Checkers == | == In-program Accessibility Checkers == | ||
{{ExpandStart | {{ExpandStart | ||
|title = Use in-program accessibility checkers to find and fix | |title = Use in-program accessibility checkers to find and fix | ||
}} | }} | ||
=== Adobe Accessibility Checker === | |||
=== [https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html Adobe | * [https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html Adobe Help: Create and verify PDF accessibility] | ||
=== Google === | === Google === | ||
[https://bit.ly/GoogleAccessibilityChecker Install and run Grackle] for Docs, Sheets, and Slides. | |||
=== LibreOffice === | === LibreOffice === | ||
Go to '''Tools → Accessibility Check''' | |||
' | === Microsoft Office === | ||
* [[ALLY:Use_Microsoft's_Accessibility_Checkers|Microsoft Office: How to use Accessibility Review]] | |||
Go to '''Review → Check Accessibility''' | |||
=== Moodle === | |||
== | |||
==== Atto Editor ==== | |||
# '''Expand''' the editor's menu (down arrow). | |||
# '''Click on''' the "Accessibility checker" icon (stick figure in a circle). | |||
==== | |||
# '''Expand''' the editor's menu | |||
# '''Click on''' the | |||
==== TinyMCE Editor ==== | |||
Go to '''Tools → Accessibility Checker''' in the editor. | Go to '''Tools → Accessibility Checker''' in the editor. | ||
{{ExpandEnd}} | {{ExpandEnd}} | ||
== Captioning == | == Captioning == | ||
{{ExpandStart | {{ExpandStart | ||
|title = Ensure all video has captions and transcripts; ensure all audio has transcripts | |title = Ensure all video has captions and transcripts; ensure all audio has transcripts | ||
}} | }} | ||
=== [https://support.google.com/docs/answer/9109474?hl=en Google Slides] === | === [https://support.google.com/docs/answer/9109474?hl=en Google Slides] === | ||
=== [https://support.microsoft.com/en-au/office/present-with-real-time-automatic-captions-or-subtitles-in-powerpoint-68d20e49-aec3-456a-939d-34a79e8ddd5f Microsoft Office 365 PowerPoint] === | === [https://support.microsoft.com/en-au/office/present-with-real-time-automatic-captions-or-subtitles-in-powerpoint-68d20e49-aec3-456a-939d-34a79e8ddd5f Microsoft Office 365 PowerPoint] === | ||
=== [[Auto Captioning Videos in Panopto|Panopto]] === | |||
=== [[ | |||
=== [[ALLY:Auto-Captioning_Video_in_YouTube|YouTube]] === | === [[ALLY:Auto-Captioning_Video_in_YouTube|YouTube]] === | ||
=== [[Automated Captioning in Zoom|Zoom]] === | |||
=== [[ | |||
{{ExpandEnd}} | {{ExpandEnd}} | ||
== Setting a Language == | == Setting a Language == | ||
* MacOS: [https://support.apple.com/guide/mac-help/change-the-system-language-mh26684/mac Change system language] | |||
* Windows: [https://support.microsoft.com/en-us/windows/manage-the-input-and-display-language-settings-in-windows-12a10cb4-8626-9b77-0ccb-5013e0c7c7a2 Manage language settings] | |||
* MacOS: [https://support.apple.com/guide/mac-help/change-the-system-language-mh26684/mac Change | |||
* Windows: [https://support.microsoft.com/en-us/windows/manage-the-input-and-display-language-settings-in-windows-12a10cb4-8626-9b77-0ccb-5013e0c7c7a2 Manage | |||
{{ExpandStart | {{ExpandStart | ||
|title = Setting your document or content language | |title = Setting your document or content language | ||
}} | }} | ||
=== Apple Pages === | === Apple Pages === | ||
# Go to '''File > Advanced > Language & Region'''. | |||
# Choose the appropriate **Language** and **Region**. | |||
=== Adobe Acrobat === | === Adobe Acrobat === | ||
# Navigate to [https://helpx.adobe.com/acrobat/using/create-verify-pdf-accessibility.html#fix_accessibility_issues Fix accessibility issues]. | |||
# Set the **Document Language** in the file properties. | |||
=== Microsoft Office === | |||
* [https://support.microsoft.com/en-us/office/add-an-editing-or-authoring-language-or-set-language-preferences-in-office-663d9d94-ca99-4a0d-973e-7c4a6b8a827d Add an editing or authoring language]. | |||
=== Google Docs === | |||
* [https://support.google.com/docs/answer/187189?hl=en Translate documents or write in a different language]. | |||
=== HTML === | === HTML === | ||
* [https://www.w3.org/International/questions/qa-html-language-declarations Declaring language in HTML]. | |||
* | |||
{{ExpandEnd}} | {{ExpandEnd}} | ||
== Additional Resources == | == Additional Resources == | ||
* https://blogs.swarthmore.edu/its/2025/08/20/introducing-an-accessible-syllabus-template/ | * [https://blogs.swarthmore.edu/its/2025/08/20/introducing-an-accessible-syllabus-template/ Accessible Syllabus Template] | ||
* [https://webaim.org/blog/word-and-powerpoint-alt-text-roundup/ WebAIM | * [https://webaim.org/blog/word-and-powerpoint-alt-text-roundup/ WebAIM: Microsoft’s built-in alt text generator] | ||
* [https://www.swarthmore.edu/accessibility/general-course-material-guidelines General Course Material Guidelines for Faculty] | * [https://www.swarthmore.edu/accessibility/general-course-material-guidelines General Course Material Guidelines for Faculty] | ||
* [[Accessibility File Scan]] tool for course materials. | |||
* | * [https://teachaccess.org/resources/creating-accessible-course-content/ Creating Accessible Course Content] from TeachAccess. | ||
* [https://teachaccess.org/resources/creating-accessible-course-content/ Creating Accessible Course Content] from | * [https://webaim.org/blog/webaim-million-2022/ WebAIM Million Report] | ||
* [https://webaim.org/blog/webaim-million-2022/ WebAIM Million Report] | |||
[[Category:Accessibility]] | |||
[[Category:Google]] | |||
[[Category:Microsoft]] | |||
[[Category:Pdf]] | |||
[[Category:Captions]] | |||
[[Category:Panopto]] | |||
[[Category:Youtube]] | |||
[[Category:Zoom]] | |||
Revision as of 18:29, 8 May 2026
Most employees and students can take advantage of these tools in order to create materials for all constituents—employees, alumni, and students—to work and learn with confidence.
Table of Contents
Select the link to be taken directly to that section of the article.
In-program Styles
Using appropriate headings in the appropriate order in your current program is necessary. They add structure and create consistency in documents and allow screen readers to easily—audibly—scan the information. Additionally, authors can easily create such things as a Table of Contents or view an Outline.
Apple
- Apple's article: Create accessible documents, spreadsheets, or presentations with Pages, Numbers, or Keynote.
- Toronto Metropolitan University Pressbooks: Technique 5: Use Headings.
- London College of Communication Teaching Hub: Create accessible documents using Apple Pages and Keynote.
- Intro to paragraph styles in Pages | Mac help.
- Docs
- Our KB article: Google Docs: Changing The Look of Headings and Paragraphs
- Google's Support page: Add a title, heading, or table of contents to a document
HTML
In HTML, titles should exist within the <title> tag. There should only be one, and it should also be somehow related—and maybe even exactly the same—as the
. Use headings to establish structure.
LaTeX
In LaTeX, title is again metadata. Insert the title in the preamble metadata: \title{_}.
Styles that are important to structure in a LaTeX file are:
- Insert sections in document body:
\section{_},\subsection{_}, etc. - Numbered lists in use:
\begin{enumerate} \item ... \end{enumerate} - Bulleted list use:
\begin{itemize} \item ... \end{itemize}
See also:
- Lewis Forbes – LaTeX and Accessibility | University of Edinburgh student intern blog
- LaTeX to HTML via PANDOC | Dan W. Joyce
Markdown
In Markdown, your title exists after a singular hashtag, # Title. Hashtags give markdown structure. The relationship between Markdown and HTML shows us that
and <title> are often similar or the same.
- Improving the accessibility of your markdown | Smashing Magazine
- 7.14 Improve accessibility of HTML pages | R Markdown Cookbook
Microsoft
- Excel
- PowerPoint
- Word
- Our KB article: Using Word's Style Gallery to Create Structure in Your Document.
- Microsoft's Support page: Make your Word documents accessible to people with disabilities.
- Our KB article: Using Word's Properties to flow into a more accessible PDF.
Moodle
Atto Editor
- Swarthmore ITS Blog post: Reach all users with Atto text editor in Moodle.
- Moodle's Atto Editor documentation.
TinyMCE Editor
Screen Reader Demo With Headings [YouTube]
Convey Meaning with Words
Links
When providing a link somewhere within your text, be sure to provide context. Screen readers provide users the opportunity to scroll through links, so links such as "click here" and "more" do not make sense out of context.
- Deque University: Use link text that makes sense when read out of context
- WebAIM: Links and Hypertext: Link Text and Appearance
Color
Color is not read aloud by screen readers, so consider calling attention to important text with words.
- Important: Paper due on April 15th. All late papers will be deducted one grade per day late.
- Note: All applicants must sign on line 11 and line 15 in order to have their pay direct deposited.
- Urgent: Pay attention to all directions before handing in this form.
When using color, ensure high contrast. Use WebAIM's Contrast Checker or Lea Verou's Contrast Ratio Checker.
Alt-Text, Captions, Image Descriptions, etc.
Providing descriptive text is necessary for all users to understand the meaning of an image.
In-program Accessibility Checkers
Adobe Accessibility Checker
Install and run Grackle for Docs, Sheets, and Slides.
LibreOffice
Go to Tools → Accessibility Check
Microsoft Office
Go to Review → Check Accessibility
Moodle
Atto Editor
- Expand the editor's menu (down arrow).
- Click on the "Accessibility checker" icon (stick figure in a circle).
TinyMCE Editor
Go to Tools → Accessibility Checker in the editor.
Captioning
Google Slides
Microsoft Office 365 PowerPoint
Panopto
YouTube
Zoom
Setting a Language
- MacOS: Change system language
- Windows: Manage language settings
Apple Pages
- Go to File > Advanced > Language & Region.
- Choose the appropriate **Language** and **Region**.
Adobe Acrobat
- Navigate to Fix accessibility issues.
- Set the **Document Language** in the file properties.
Microsoft Office
Google Docs
HTML
Additional Resources
- Accessible Syllabus Template
- WebAIM: Microsoft’s built-in alt text generator
- General Course Material Guidelines for Faculty
- Accessibility File Scan tool for course materials.
- Creating Accessible Course Content from TeachAccess.
- WebAIM Million Report