[Easy Checks] Input

Good morning,

I looked at the updated easy checks
<https://www.w3.org/WAI/test-evaluate/easy-checks/>  and thought to share
my thoughts.

   - The updated version remains lengthy and in my opinion it still fails
   the requirement analysis of easy to use
   <https://www.w3.org/WAI/EO/wiki/Easy_Checks_2022#Requirements_Analysis>
[....
   presents a lot of textual and detailed information, getting in the way of a
   pleasant user experience and its main purpose].     I suggest using it as
   "Documentation for the Easy Checks" while each check remains short with a
   structure that is easy to follow.
   - Currently, each check uses a separate bookmarklet. I recommend using a
   single bookmarklet, like ANDI
   <https://www.ssa.gov/accessibility/andi/help/install.html>, to cover
   most checks for better user learning. This approach would be more
   beneficial for the audiences, supporting their learning development as they
   progressively build their understanding of accessibility using the same
   tool.
   - Also, there are naming discrepancies (e.g., "Images Alternative Text"
   vs. "Text Alternative") that should align with W3C naming conventions in
   WCAG.


I have attached a proposal for one of the easy checks, specifically "Text
Alternative," which encompasses the three points mentioned above. I look
forward to discussing these suggestions further in our meeting.

See you at 8:30 AM EST :)
Rabab Gomaa