Acceptance criteria

• The Notification component Accessibility tab needs to be updated with the new content template.
• Michael Gower will be a good reference when working on this issue.

A11Y template

Look at other accessibility tabs to understand what type of content we are expecting on these pages.

Page description

• Determine which page description in the content template is most appropriate for Notification. This can be determined towards the end of the process.

What Carbon provides

This section documents any existing accessibility features that come out of the box in the carbon code, like keyboard navigation, focus order, regions, ect.

• Consult with developers and Michael Gower to determine what existing accessibility features currently exist for all variants of Notification.
• Write an H3 section for each accessibility feature.
• Provide an image that annotates or depicts the accessibility interaction for each H3 section.

Design recommendation

This section is less straightforward and will require close collaboration with Michael Gower. In this section, you will give guidance on what users will need to consider when designing with Notification that may require additional design attention from product users to create an accessible experience. Not all components will have this section.

• Consult with Michael Gower to determine what accessibility design recommendations need to be communicated for Notification.
• Write an H3 section for each design recommendation.
• Provide an image that annotates or depicts the design recommendation for each H3 section.

Developement considerations

Some of this information may already be available in the existing a11y tab content.

• Consult with developers and Michael Gower to determine what the developer considerations
• Provide a bulleted list of implementation considerations for ensuring accessibility. If there is the ability to reference the IBM toolkit or the ARIA authoring practices, that should be done.