Considering short titles/descriptions for potential violations

[MelSumner]

I've been thinking about how to word potential violations so that they are more uniform than they are now.

Previous feedback has suggested that the "error word" should come first. Given that feedback, I'm working on a new list of short titles/descriptions for potential violations.

I'm going to shop around this issue link to get some feedback, so if you are following this repo and have feedback, please do provide some.

This is my first iteration. I've tried using it in a RL scenario and ran into a few issues with it but I don't know if it's because it's simply new to me, or is actually a little unwieldy.

Short Descriptions, a working list:

1. Clipped or hidden content on text resize
2. Clipped or hidden content on zoom
3. Disabled interactive element(s)
4. Disabled zooming and scaling
5. Disallowed keyboard trap
6. Disallowed links inside of alert messages
7. Disallowed: popup appears on page load
8. Disallowed: whitespace used for layout
9. Illegal use of positional word(s)
10. Illogical focus sequence
11. Incomplete accessible name
12. Inconsistent identification
13. Inconsistent navigation
14. Incorrect ARIA attribute value
15. Incorrect image ALT attribute value
16. Incorrect use of alerts
17. Incorrect use of autofocus
18. Incorrect use of input/label (not associated)
19. Incorrect use of toast for error message
20. Incorrectly hidden interactive/focusable elements
21. Incorrectly marked presentational image
22. Insufficient abbreviation label
23. Insufficient color contrast
24. Insufficient color contrast with surrounding text
25. Insufficient distinguishability
26. Insufficient image ALT attribute value
27. Insufficient target size
28. Invalid ARIA attribute used
29. Invalid color-only link
30. Invalid link text
31. Invalid role used
32. Invisible focused interactive element
33. Lack of multiple ways
34. Malformed alerts cause alert to be missed
35. Malformed autocomplete
36. Malformed element
37. Malformed HTML
38. Mis-ordered heading levels
39. Missing accessible name for button
40. Missing accessible name for duplicate landmark
41. Missing accessible name for link
42. Missing accessible name for list element
43. Missing attribute
44. Missing autocomplete
45. Missing error prevention
46. Missing focus indicator
47. Missing focus management after modal closes
48. Missing focus trap
49. Missing h1 on page
50. Missing keyboard support
51. Missing label for input
52. Missing role
53. Missing scrollable region keyboard access
54. Missing skiplink/bypass block
55. Missing status announcement
56. Missing table header text
57. Missing visible label in accessible name
58. Missing warning for automatic actions
59. multiple h1 per page
60. multiple main landmarks
61. nested interactive
62. Obscured focusable element
63. Redundant attribute(s)
64. Redundant label
65. Unassociated error message for input
66. Unclear error text
67. Unclear heading
68. Unclear help text
69. Unclear label
70. Unmarked headings
71. Unprevented data loss
72. Unreachable element via keyboard
73. Unsupported orientation
74. Unsupported text spacing

[MelSumner]

I think I need to pair these with some kind of category so they are easier to scan. They might be good on their own for something like an issue title, but if used for something like an audit, then it would be better to provide an additional category, so the potential violations can be grouped that way. I don't know if that will work just yet, I should try it out though.