docs(accessibility-development): Updates documentation as part of content audit.

[edonehoo]

Closes #3777

[patternfly-build]

Preview: https://patternfly-org-pr-3780-site.surge.sh

[edonehoo]

Tried moving the screen reader info here, but I still may be misconstruing its purpose?

Also not sold on the page name, but I thought it'd be easier to distinguish from the new design page if I led with develop..

[thatblindgeye]

@jessiehuff currently we aren't using this role on our alerts. Any objection to removing that part here or do you think it's worth a convo as to whether we should be using that role?

[edonehoo]

Would the whole example be removed, then? I removed it in my last push to visualize, but can add it back and modify.

[thatblindgeye]

I think keeping the example could be useful, at least to show how using hidden text can be used.

[jessiehuff]

We can definitely update this example to be more current. A lot of this content has been around for years, and I know that a few years back I did a good bit of work to try to get alerts to work across screen readers so I'm sure that things have changed since this content was originally created. So no objection to removing that part of the example. :)

[edonehoo]

There's so much text on this page & I'm trying to figure out how we can make it easier for people to digest, while ensuring that all the necessary info is present... I think Eric maybe mentioned this, but I'm wondering what should be in the table vs written out into a separate section. Maybe there's too much text to fit into a table, but I do think it would simplify and organize things better hm - thoughts?

[thatblindgeye]

This is coming along great! Couple more comments below. Would you want to have a Meet about the above to brainstorm?

[edonehoo]

Small thing - the headers in the data list don't perfectly align with the other contents. Doesn't really matter, but wanted to mention it in case it was a quick change (if it's even possible/necessary)

[jessiehuff]

Totally open to converting some of this into a table! I'm not quite sure how to organize the information though to create one. 🤔 Open to Eric's suggestion of meeting up about it. I do think this is a good idea in general though. I know that one of our researchers did a study about org, and a good bit of the feedback was that we often have a lot of content as blocks of text which makes it difficult for users to understand information quickly.

[thatblindgeye]

This is looking good! Had a couple quick updates below. If we would want to try setting up a meet to go over the amount of content and such I'd be on board, but if we want that to be a follow up that could also work.

[edonehoo]

@thatblindgeye @jessiehuff general thing - I keep tweaking the heading naming and I think I've looked at it for too long and everything sounds bad hah. LMK what you think about the state that this page is in now.

I think a meeting to discuss alternative presentation options would be awesome! Since the other ally docs are close to being ready to merge I think it may be best to let this one get there too & then do a follow up for the higher level brainstorming of design rearranging?

[thatblindgeye]

🎉 Agreed about getting this in and doing a followup for further enhancements/tweaks. I think the heading naming is good! That's always one of those things that can be difficult to land on (well naming in general 😆 ), but if we think of alternatives we can always revisit those as well.