...
| Criteria | Level of Support & Supporting Features | Remarks and explanations |
|---|---|---|
| (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content). | SupportedSupports | Sonar issue severity icons have a description in their alt attribute |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. | Not applicable | |
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup. | Supports with exceptions | Coverage and duplicate line markers are only distinguishable from each other by color |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. | Not applicable | |
| (e) Redundant text links shall be provided for each active region of a server-side image map. | Not applicable | |
| (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape | Not applicable | |
| (g) Row and column headers shall be identified for data tables. | Supports with exceptions | The row and column headers in the pull request statistics table are identified while this is not the case in the issue overview dialog |
| (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers. | Not applicable | No data tables discovered with more than one level of headers |
| (i) Frames shall be titled with text that facilitates frame identification and navigation | Not applicable | No frames are used |
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. | Supports | |
| (k) A text -only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text - only page shall be updated whenever the primary page changes. | Not applicable | |
| (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by Assistive Technology. | Supports with exceptions | The details of the Sonar issues are not accessible by keyboard (currently require a mouse click) |
| (m) When a web page requires that an applet, plug -in or other application be present on the client system to interpret page content, the page must provide a link to a plug -in or applet that complies with 1194.21(a) through (l). | Not applicable | |
| (n) When electronic forms are designed to be completed on -line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. | Supports with exceptions | Tabs in repository settings are not accessible by keyboard |
| (o) A method shall be provided that permits users to skip repetitive navigation links. | Does not support | |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. | Not applicable |
...