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

[OUDS] Docs: Add 'Getting started > Accessibility' page #2675

Merged

Conversation

louismaximepiton
Copy link
Member

@louismaximepiton louismaximepiton commented Aug 2, 2024

Related issues

Listed in #2589

Description

This PR adds the "Getting Started > Accessibility" page based on:

Please that not all content can be reintroduced in this first PR, as some components or concepts are not yet described in the rest of the documentation.

There are some Bootstrap inconsistencies with WCAG in the doc.

  • Modals component
  • Dropdowns component
  • Tooltips component
  • Color utility
  • Background utility
  • Carousels component
  • Spinners component
  • Focus mixin and design defined
  • Scroll target style
  • Target size mixin
  • Text utility

Types of change

  • New documentation (non-breaking change which adds functionality)

Live previews

@louismaximepiton louismaximepiton added the docs Improvements or additions to documentation label Aug 2, 2024
@louismaximepiton louismaximepiton added this to the OUDS milestone Aug 2, 2024
Copy link

netlify bot commented Aug 2, 2024

Deploy Preview for boosted ready!

Name Link
🔨 Latest commit c0d0cc1
🔍 Latest deploy log https://app.netlify.com/sites/boosted/deploys/66b320491287a500089edbe3
😎 Deploy Preview https://deploy-preview-2675--boosted.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@julien-deramond julien-deramond changed the title Docs: Add 'Getting started > Accessibility' page [OUDS] Docs: Add 'Getting started > Accessibility' page Aug 5, 2024

## Overview and limitations

The overall accessibility of any project built with OUDS Web depends in large part on the author's markup, additional styling, and scripting they've included. However, provided that these have been implemented correctly, it should be perfectly possible to create websites and applications with OUDS Web that fulfill [<abbr title="Web Content Accessibility Guidelines">WCAG</abbr> 2.2](https://www.w3.org/TR/WCAG/) (A/AA/AAA), [Section 508](https://www.section508.gov/), and similar accessibility standards and requirements.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WCAG 2.1 → WCAG 2.2 modification should be done in Bootstrap first. And globally if necessary.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, I'll do it Bs side first, I'll revert it in here.

site/content/docs/0.0/getting-started/accessibility.md Outdated Show resolved Hide resolved
site/content/docs/0.0/getting-started/accessibility.md Outdated Show resolved Hide resolved
site/content/docs/0.0/getting-started/accessibility.md Outdated Show resolved Hide resolved
@julien-deramond julien-deramond self-requested a review August 7, 2024 07:24
@julien-deramond julien-deramond merged commit d58331e into ouds/main Aug 7, 2024
14 checks passed
@julien-deramond julien-deramond deleted the ouds/main-lmp-getting-started-accessibility branch August 7, 2024 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Improvements or additions to documentation
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants