Search results

Looking for feedback (and possible home): Well-Known URI for Accessibility Issue Reporting

Status: Open.

#188 In w3c/wai-wcag-em;

· AutoSponge opened on Mar 25, 2026

Remove procedure section numbers?

Status: Open.

#186 In w3c/wai-wcag-em;

· iadawn opened on Mar 19, 2026

Rework Step 1.3 support baseline?

Status: Open.

#185 In w3c/wai-wcag-em;

· iadawn opened on Mar 19, 2026

"Comprehensively evaluate" misleading

Status: Open.

#184 In w3c/wai-wcag-em;

· iadawn opened on Mar 19, 2026

Digital product conformance?

Status: Open.

#183 In w3c/wai-wcag-em;

· iadawn opened on Mar 19, 2026

Problematic definition of view

Status: Open.

#182 In w3c/wai-wcag-em;

· WilcoFiers opened on Mar 17, 2026

Documenting outcomes - include severity and user impact

Status: Open.

#179 In w3c/wai-wcag-em;

· lsr-explore opened on Mar 15, 2026

Include identification of assistive devices to be used in the evaluation

Status: Open.

#178 In w3c/wai-wcag-em;

· lsr-explore opened on Mar 15, 2026

Reference Accessibility Maturity Model in the abstract for context

Status: Open.

#177 In w3c/wai-wcag-em;

· lsr-explore opened on Mar 15, 2026

4.2 Explore the target digital product - include a step that identifies sensitive or high risk functionality

Status: Open.

#176 In w3c/wai-wcag-em;

· lsr-explore opened on Mar 15, 2026

Make it clearer that looking at all pages instead of sample is also good practice

Status: Open.

#175 In w3c/wai-wcag-em;

· hidde opened on Mar 11, 2026

Documenting test process as a step

Status: Open.

#174 In w3c/wai-wcag-em;

· karlgroves opened on Mar 11, 2026