Sample Pass to Assess each SC for requirement or best practice

[mgifford]

Looking at #69

Looking through each of these, which is clearly a WCAG requirements and which is a best practice. Using SC 1.1.1 as an example, what would it look like?

Using all the elements that relate to 1.1.1 from https://www.w3.org/WAI/planning/arrm/tasks/

and adding it to AI using this prompt:

"I have a series of accessibility items, with their IDs and descriptions, related to various WCAG Success Criteria. Please process this data into a single Markdown table with three columns: ID, Requirement/Practice, and Classification.

For the Classification column, label each item as either:

Requirement: If it is a direct mandate of a WCAG Success Criterion (A or AA) or a Sufficient Technique for meeting that SC.

Best Practice: If it is an Advisory Technique or a general guideline that is recommended for robust accessibility but is not strictly required for conformance.

Please also include a concise Rationale column explaining why it was classified that way.

Data to Process:

[INSERT NEW DATA HERE]"

I got the following result:

ID	Requirement/Practice	Classification	Rationale
IMG-002	Informative images are described with a clear and meaningful text equivalent (alt attribute or other equivalent means).	Requirement	Direct application of the core WCAG 1.1.1 mandate (Sufficient Technique).
IMG-003	Purely decorative images are provided with null alt attribute values (or other equivalent means).	Requirement	Required implementation for the "Decoration, Formatting, Invisible" exception.
IMG-016	Alternate means of accessing CAPTCHA information are provided, such as audio CAPTCHA, logical question, or other equivalent means.	Requirement	Explicitly required by the CAPTCHA exception in 1.1.1.
IMG-017	Images which do not convey information are defined as decorative.	Requirement	Content step to ensure the "decorative" exception is correctly applied.
IMG-018	Charts, graphs, infographics and other visual representations of information don't rely on color alone to convey information.	Requirement	This is a direct mandate of a separate WCAG SC: 1.4.1 Use of Color (A).
CSS-005	CSS pseudo-selectors such as :before and :after are not used to integrate informative content.	Requirement	Direct mandate of 1.3.1 Info and Relationships (A).
IMG-001	Informative alternate text is provided for images (i.e. not "spacer" or image file name).	Best Practice	Focuses on the quality and meaningfulness of the alt text (Advisory/Guideline).
IMG-004	Null alt attribute values are used for images that are already described in text in adjacent page content.	Best Practice	Practice to avoid redundancy, improving the screen reader experience.
IMG-005	Adjacent linked images and text links pointing the same URL are combined into single links.	Best Practice	Improves efficiency and reduces link repetition (related to 2.4.4 Link Purpose).
IMG-006	Alt text used for images of text include all relevant text found in the image.	Best Practice	Ensures a complete and equivalent text alternative for images of text.
IMG-007	Informative images are marked up as foreground images, and not embedded as part of the CSS.	Best Practice	Technique to ensure informative images are accessible when CSS is absent.
IMG-008	The purpose or function of complex images is accurately described in text.	Best Practice	Content requirement for a full description (long description or summary).
IMG-009	The purpose or function of complex images is conveyed using a text description, via an alt attribute.	Best Practice	Practice to provide a short label via alt that precedes a long description.
IMG-010	The full explanation of complex images is accurately described in text.	Best Practice	Focuses on the completeness and accuracy of the long description.
IMG-011	A mechanism that conveys the way through which the full explanation of complex images is defined.	Best Practice	Requirement for a UX/design mechanism (e.g., a "View Data" link).
IMG-012	The full explanation of complex images is provided through the longdesc attribute (or other equivalent means).	Best Practice	Refers to a specific, now largely deprecated, HTML technique.
IMG-013	Images primarily conveying function use alternative text to describe their purpose, rather than what they look like.	Best Practice	Focuses on writing functional alt text (e.g., "Search" vs. "magnifying glass").
IMG-014	Text alternatives of static and linked images do not replicate any information that is already being conveyed by screen reader technology.	Best Practice	Practice to avoid redundancy (e.g., do not start alt text with "Image of...").
IMG-015	Text alternatives of dynamically updated images are simultaneously updated as the images change.	Best Practice	Advanced technique (e.g., ARIA live regions) to ensure equivalence is maintained in dynamic content.
CSS-001	Icon fonts used to convey information are provided with a text equivalent.	Best Practice	Application of 1.1.1 to a modern implementation technology.
CSS-002	The meaning of icon fonts is determined programmatically using the aria-label attribute (or other equivalent means).	Best Practice	Specific ARIA technique for providing an accessible name/text equivalent.
CSS-003	Icon fonts whose default accessible name do not represent what the icon is, are overwritten using an aria-hidden attribute (or other equivalent means).	Best Practice	Specific technique to correctly implement the decorative exception (aria-hidden="true").
CSS-004	Background images identified as decorative are implemented as such.	Best Practice	Implementation technique (CSS) to correctly meet the decorative exception.
SCT-001	Emoticons, emojis, ASCII art, and other non-markup language constructs are supported with equivalent text alternatives and conveyed to assistive technologies.	Best Practice	Application of 1.1.1 to common non-standard text/image elements.