Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

[terra-signature] Implementation page doc updates #4033

Merged
merged 6 commits into from
Mar 8, 2024

Conversation

KV106606Viswanath
Copy link
Contributor

Summary

Updated implementation page documentation regarding consumers' responsibility to ensure the accessibility of the Terra Signature control.

What was changed:

Why it was changed:

Testing

This change was tested using:

  • WDIO
  • Jest
  • Visual testing (please attach a screenshot or recording)
  • Other (please describe below)
  • No tests are needed

Reviews

In addition to engineering reviews, this PR needs:

  • UX review
  • Accessibility review
  • Functional review

Additional Details

This PR resolves:

UXPLATFORM-9215


Thank you for contributing to Terra.
@cerner/terra

## Consuming teams are responsible for
- **Providing Descriptive Labels**: Ensure that the signature component is labeled clearly and descriptively for screen reader users. This includes providing labels for form fields and instructions for signing.

- **Implementing Keyboard Accessibility**: Ensure that all functionality of the signature component can be accessed and operated using a keyboard alone, without relying on mouse interactions.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **Implementing Keyboard Accessibility**: Ensure that all functionality of the signature component can be accessed and operated using a keyboard alone, without relying on mouse interactions.
- **Implementing Keyboard Accessibility**: Ensure that all functionality of terra-signature can be accessed and operated using only a keyboard, without any mouse interactions.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated


- **Implementing Keyboard Accessibility**: Ensure that all functionality of the signature component can be accessed and operated using a keyboard alone, without relying on mouse interactions.

- **Using ARIA Attributes**: Use ARIA (Accessible Rich Internet Applications) attributes to enhance the accessibility of the signature component, such as aria-label and aria-describedby, to provide additional context for screen reader users.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **Using ARIA Attributes**: Use ARIA (Accessible Rich Internet Applications) attributes to enhance the accessibility of the signature component, such as aria-label and aria-describedby, to provide additional context for screen reader users.
- **Using ARIA Attributes**: Use ARIA (Accessible Rich Internet Applications) [attributes](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA) to enhance the accessibility of terra-signature, such as [aria-label](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-label) and [aria-describedby](https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/Attributes/aria-describedby), to provide additional context for screen reader users.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

@@ -2,6 +2,9 @@

## Unreleased

* Added
* Added implementation page documentation regarding consumers responsibility to ensure the accessibility of the `terra-signature`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
* Added implementation page documentation regarding consumers responsibility to ensure the accessibility of the `terra-signature`.
* Added implementation page documentation regarding consumers responsibility to ensure the accessibility for `terra-signature`.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

@@ -35,6 +35,23 @@ This component requires the following peer dependencies be installed in your app
import Signature from 'terra-signature';
```

## Consuming teams are responsible for
- **Providing Descriptive Labels**: Ensure that the signature component is labeled clearly and descriptively for screen reader users. This includes providing labels for form fields and instructions for signing.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **Providing Descriptive Labels**: Ensure that the signature component is labeled clearly and descriptively for screen reader users. This includes providing labels for form fields and instructions for signing.
- **Providing Descriptive Labels**: Ensure that the terra-signature component is labeled clearly and descriptively for screen reader users. This includes providing labels for form fields and instructions for signing.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated


- **Using ARIA Attributes**: Use ARIA (Accessible Rich Internet Applications) attributes to enhance the accessibility of the signature component, such as aria-label and aria-describedby, to provide additional context for screen reader users.

- **Testing with Assistive Technologies**: Test the signature component with a variety of assistive technologies, such as screen readers, to ensure that it is fully accessible and usable by all users.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **Testing with Assistive Technologies**: Test the signature component with a variety of assistive technologies, such as screen readers, to ensure that it is fully accessible and usable by all users.
- **Testing with Assistive Technologies**: Test terra-signature with a variety of assistive technologies, such as screen readers, to ensure that it is fully accessible and usable by all users.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated


- **Testing with Assistive Technologies**: Test the signature component with a variety of assistive technologies, such as screen readers, to ensure that it is fully accessible and usable by all users.

- **Providing Alternative Text for Images**: If the signature component includes any images or icons, provide alternative text that describes the content or function of the image for users who cannot see it.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **Providing Alternative Text for Images**: If the signature component includes any images or icons, provide alternative text that describes the content or function of the image for users who cannot see it.
- **Providing Alternative Text for Images**: If terra-signature includes any images or icons, provide alternative text that describes the content or function of the image for users who cannot see it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated


- **Providing Alternative Text for Images**: If the signature component includes any images or icons, provide alternative text that describes the content or function of the image for users who cannot see it.

- **Ensuring Sufficient Color Contrast**: Ensure that there is sufficient color contrast between text and background colors to make the signature component readable for users with low vision or color blindness.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **Ensuring Sufficient Color Contrast**: Ensure that there is sufficient color contrast between text and background colors to make the signature component readable for users with low vision or color blindness.
- **Ensuring Sufficient Color Contrast**: Ensure that there is sufficient color contrast between text and background colors to make terra-signature readable for users with low vision or color blindness.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated


- **Ensuring Sufficient Color Contrast**: Ensure that there is sufficient color contrast between text and background colors to make the signature component readable for users with low vision or color blindness.

- **Documenting Accessibility Features**: Document the accessibility features of the signature component for end users, including instructions on how to use it with assistive technologies.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- **Documenting Accessibility Features**: Document the accessibility features of the signature component for end users, including instructions on how to use it with assistive technologies.
- **Documenting Accessibility Features**: Document the accessibility features of terra-signature for end users, including instructions on how to use it with assistive technologies.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

@github-actions github-actions bot temporarily deployed to preview-pr-4033 March 8, 2024 06:53 Destroyed
@sugan2416 sugan2416 merged commit e33de81 into main Mar 8, 2024
22 checks passed
@sugan2416 sugan2416 deleted the KV106606-Terra-signature-doc-updates branch March 8, 2024 08:18
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants