Look at incorporating ATAG 2.0

[mgifford]

Select Topic Area

General

GitHub Feature Area

Discussions

Body

This could happen in a number of places, but no reason not to start in anything where there is an WYSIWYG like interface.

Authoring Tool Accessibility Guidelines (ATAG) 2.0 is:
https://www.w3.org/WAI/standards-guidelines/atag/

Best example of this I know of is:
https://github.com/a11yfirst/

There is a demo here:
https://a11yfirst.gitlab.io/custom/a11yfirst.html

But there are a few things that can be done here.

Check heading orders.

An author should be flagged if headings are skipped:

H2

H4

They should get a "Where is the H3?" message, perhaps even "Want me to make that H4 an H3?"

Headings should go down:

H1

H2

H3

But probably a page shouldn't start with an H3.

There are rules that could ould implement.

Same thing with Alt text. Why just make the alt text the filename here? It's a bad example. My file was named Editor.png and new the alt text is "Editor". That's easy but a bad practice.

Why not prompt the user to give you an alt text. Or better yet, use some AI to describe the image and then show it to the author to validate.

That is how Drupal CMS does it https://www.drupal.org/project/ai_image_alt_text

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐