Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define accessibility best practice guide for Adapt #3379

Open
kirsty-hames opened this issue Mar 28, 2023 · 3 comments
Open

Define accessibility best practice guide for Adapt #3379

kirsty-hames opened this issue Mar 28, 2023 · 3 comments

Comments

@kirsty-hames
Copy link
Contributor

Adapt accessibility has been implemented in conformance with WCAG however there is often multiple solutions or conflicting opinions to meeting criteria. In addition, we have interactions/functionality in Adapt that isn't part of standard web leaving it to us as developers to determine the appropriate implementation.

In order to ensure consistency in Adapt and provide support for developers it would be good to document a best practice guide.

I see this having the following uses:

  • A resource guide for developing/maintaining Adapt functionality. Including examples of implementation and reasoning for why we've chosen a particular implementation if applicable (e.g. ARIA heading levels vs H tags).
  • A resource guide for authoring content in Adapt (e.g how content should read and knowing how to mark it up Update a11y documentation #2553).
  • A measure for reviewing where Adapt is now and addressing any inconsistencies (e.g. review use of ARIA holistically rather looking at plugins in isolation).
@oliverfoster
Copy link
Member

image

@oliverfoster
Copy link
Member

@oliverfoster
Copy link
Member

#2553 (comment) Zero width spacing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

No branches or pull requests

2 participants