Update to data table accessibility tab

[mbgower]

Rewrite of content and addition of 4 images

Changelog

New

• {{new thing}}

Changed

• {{change thing}}

Removed

• {{removed thing}}

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/carbon-design-system/carbondesignsystem/H1y3s8i14e6gGrKHL4Dq1oDtH1me
✅ Preview: https://carbondesignsystem-git-fork-mbgower-1a210f-carbon-design-system.vercel.app

[mjabbink]

@mbgower I think the below copy can get the “why/benefit” part I mentioned in the other issue.

[mbgower]

@mjabbink I'd missed your other comment which reads in part:

Suggestion
What Carbon provides
Carbon bakes keyboard operation into its components, as well as many other accessibility considerations. This allows for... benefits, advantages... the why.

I've opened an internal issue to address your request.
When we were testing, we got some pushback on having too much text at the top. I'll see if I can't put something succinct in as part of what is effectively boiler plate when I start working on my next component (in a few weeks), and run it by some sponsor users. Then I can just loop back and add it to these already created components.

We've had prior discussions about working a benefits section into subsequent iterations, so this ties in pretty well.

In the meantime, I'm just going to push the existing text since it's gone through handoff. That okay?

[mjabbink]

The additional sentence that describes the “so that you can... ” or “in order to provide...” is helpful to provide context to why Carbon provides the thing you’re talking about. The designers need to know that information.

[mbgower]

@mjabbink
I agree that the 'why' is super useful. We have that in our sketch kit material, each topic of which is about one thing (say, having good text contrast or alternative text). When we're putting emphasis on a specific consideration, it's relatively easy to say "This especially benefits group X". Here's an example from the sketch kit.

There's a challenge doing that with a component. All its design features, be they interaction, visual styling, states, etc., are there to support its function. I can say its focusing handling can help a user with low vision. Or the way the component is keyboard operable can help blind users and others who need to operate via the keyboard API. Or the way the inline help is implemented can help users with cognitive disabilities.
I can probably say some very generic things about most components at an abstract level, but when faced with any single component there is going to be a specific aspect we want to call out. We're doing that through the subsections -- how carbon's data table handles keyboard navigation, how a sortable column header is surfaced and how a sorted column is indicated.
I could go into the benefits of some of these particular implementation features on a specific group; we could consider working that into the template. But it's hard to make generic statements without having to get into a longer statement to qualify what is being talked about.
Does that make sense?

[mjabbink]

What Carbon provides

Carbon bakes keyboard operation into its components, as well as many other accessibility considerations which can better optimize or improve experiences for screen readers.

or

Carbon bakes keyboard operation into its components, as well as many other accessibility considerations which can improve experiences for blind users and others who need to operate via the keyboard API.

[laurenmrice]

👍