Skip to content

Commit

Permalink
Removing extra space
Browse files Browse the repository at this point in the history
  • Loading branch information
laflannery authored Aug 19, 2024
1 parent f1a4d4a commit b3fe796
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion _playbook/checklists.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ roles:
- Project manager
- UX designer
---
The purpose of an accessibility checklist is to help identify accessibility issues in your product, website, or document. However, incorporating checklists into an accessibility strategy can often be tricky. One of the most common pitfalls when using or thinking about checklists is making sure you don't get stuck in a limited compliance mindset. There is no single checklist that covers all possible accessibility issues and as Intopia warned, [a checklist mentality can actually be harmful for inclusion](https://intopia.digital/articles/announcing-the-accessibility-not-checklist/). That said, if approached as part of a broader strategy, they can be very helpful when used thoughtfully. Access Armada has some interesting suggestions on [more strategic approaches to checklists](https://www.accessarmada.com/blog/building-accessibility-checklists-that-are-actually-useful/).
The purpose of an accessibility checklist is to help identify accessibility issues in your product, website, or document. However, incorporating checklists into an accessibility strategy can often be tricky. One of the most common pitfalls when using or thinking about checklists is making sure you don't get stuck in a limited compliance mindset. There is no single checklist that covers all possible accessibility issues and as Intopia warned, [a checklist mentality can actually be harmful for inclusion](https://intopia.digital/articles/announcing-the-accessibility-not-checklist/). That said, if approached as part of a broader strategy, they can be very helpful when used thoughtfully. Access Armada has some interesting suggestions on [more strategic approaches to checklists](https://www.accessarmada.com/blog/building-accessibility-checklists-that-are-actually-useful/).

Check warning on line 16 in _playbook/checklists.md

View workflow job for this annotation

GitHub Actions / remark-lint

[remark-lint] _playbook/checklists.md#L16

Hard to read sentence (confidence: 5/7) readability retext-readability
Raw output
    15:4-16:122  warning  Hard to read sentence (confidence: 5/7)         readability  retext-readability

Check warning on line 16 in _playbook/checklists.md

View workflow job for this annotation

GitHub Actions / remark-lint

[remark-lint] _playbook/checklists.md#L16

Hard to read sentence (confidence: 5/7) readability retext-readability
Raw output
  16:349-16:587  warning  Hard to read sentence (confidence: 5/7)         readability  retext-readability

## What makes a good accessibility checklist
* The checklist should build on automated testing approaches.
Expand Down

0 comments on commit b3fe796

Please sign in to comment.