|
| 1 | +# Pull Request |
| 2 | + |
| 3 | +## Intent |
| 4 | +<!-- Describe the intent of the changes. --> |
| 5 | + |
| 6 | +## Proposed Changes |
| 7 | +<!-- Provide specific details of what is changing. --> |
| 8 | + |
| 9 | +### Changes to Section Headers |
| 10 | +<!-- Write down which headers have changed. |
| 11 | +old-header -> new-header |
| 12 | +--> |
| 13 | + |
| 14 | +### Changes to Page URLs |
| 15 | +<!-- Write down which pages have changed. |
| 16 | +old/page.md -> new/page.md |
| 17 | +--> |
| 18 | + |
| 19 | +## Related or Fixed Issues |
| 20 | +<!-- Examples: |
| 21 | +Fixes #123 |
| 22 | +Related to #101 |
| 23 | +--> |
| 24 | + |
| 25 | +## Accessibility Checklist |
| 26 | + |
| 27 | +I have ensured all of the following for new or changed content: |
| 28 | + |
| 29 | +- [ ] all images have appropriate alt text. [Guidelines](https://www.wcag.com/blog/good-alt-text-bad-alt-text-making-your-content-perceivable/) |
| 30 | +- [ ] all images with text have sufficient contrast ratio. [Checker](https://webaim.org/resources/contrastchecker/) |
| 31 | +- [ ] all image text is transcribed or described in body text. |
| 32 | +- [ ] all technical terms, jargon, and abbreviations are introduced before they are used. |
| 33 | + |
| 34 | +## Style Checklist |
| 35 | + |
| 36 | +I have done all of the following: |
| 37 | + |
| 38 | +- [ ] searched for other relevant pages and crosslinked from my content to them. |
| 39 | +- [ ] searched for other relevant pages and crosslinked from them to my content. |
| 40 | +- [ ] added redirects in `mkdocs.yml` for any moved headers or pages. |
| 41 | +- [ ] defined new technical terms, jargon, and abbreviations in the glossary. |
| 42 | +- [ ] searched for existing technical terms, jargon, and abbreviations in the glossary and added crosslinks to them. |
| 43 | +- [ ] properly formatted and introduced key branding terms. [List here](https://docs.rc.uab.edu/contributing/contributor_guide#terminology). |
0 commit comments