search

Kcaden20 / critical-code-cookbook

This is the official repository for the Critical Code Cookbook Website
2 stars 0 forks source link

Adding Accessibility Notice #15

Closed Kcaden20 closed 2 years ago

Kcaden20 commented 2 years ago

We should make sure to write and add an accessibility notice to the website.

@xinemata Should it be included in the About Page or be something separate?

xinemata commented 2 years ago

Great question. I think this depends on the format & length of the accessibility statement. For TogetherNet, we created a separate page since we were advised to use the W3C Accessibility Statement Generator Tool and the document turns out to be somewhat lengthy. Would it be a lot of trouble to create an additional page for this?

Kcaden20 commented 2 years ago

No I don’t think so. There’s a default page maker, I’ve set up. The one thing would be figuring out where to list the link to it?

Would we want it in the footer?

On Wed, Jun 22, 2022 at 12:04 PM Xin Xin @.***> wrote:

Great question. I think this depends on the format & length of the accessibility statement. For TogetherNet https://togethernet.org/accessibility-statement.html, we created a separate page since we were advised to use the W3C Accessibility Statement Generator Tool https://www.google.com/url?q=https://www.w3.org/WAI/planning/statements/&source=gmail-html&ust=1651415631246000&usg=AOvVaw3CsAkpSCo9Tsd4vRGdUtb9 and the document turns out to be somewhat lengthy. Would it be a lot of trouble to create an additional page for this?

— Reply to this email directly, view it on GitHub https://github.com/Kcaden20/critical-code-cookbook/issues/15#issuecomment-1163308712, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADHWC32I24ZVBU6NTPSY5X3VQM2R7ANCNFSM5ZQKRJLQ . You are receiving this because you were assigned.Message ID: @.***>

-- Kevin Cadena Designer, Web Developer & Teacher @.** **@.**> kevincadena.com* http://kevincadena.com

xinemata commented 2 years ago

Can we place it in the main nav after About?

On Jun 22, 2022, at 10:06 AM, Kcaden20 @.***> wrote:

 No I don’t think so. There’s a default page maker, I’ve set up. The one thing would be figuring out where to list the link to it?

Would we want it in the footer?

On Wed, Jun 22, 2022 at 12:04 PM Xin Xin @.***> wrote:

Great question. I think this depends on the format & length of the accessibility statement. For TogetherNet https://togethernet.org/accessibility-statement.html, we created a separate page since we were advised to use the W3C Accessibility Statement Generator Tool https://www.google.com/url?q=https://www.w3.org/WAI/planning/statements/&source=gmail-html&ust=1651415631246000&usg=AOvVaw3CsAkpSCo9Tsd4vRGdUtb9 and the document turns out to be somewhat lengthy. Would it be a lot of trouble to create an additional page for this?

— Reply to this email directly, view it on GitHub https://github.com/Kcaden20/critical-code-cookbook/issues/15#issuecomment-1163308712, or unsubscribe https://github.com/notifications/unsubscribe-auth/ADHWC32I24ZVBU6NTPSY5X3VQM2R7ANCNFSM5ZQKRJLQ . You are receiving this because you were assigned.Message ID: @.***>

-- Kevin Cadena Designer, Web Developer & Teacher @.** **@.**> kevincadena.com* http://kevincadena.com — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were assigned.

xinemata commented 2 years ago

This has been completed. Closing the issue.